Matching
Matching is the whole trick: Jira knows who reported a request, Attio knows who the customer is, and the reporter's email address is the only thing that joins them.
These pages cover matching people and matching companies, the domains that are never looked up and why, and what the card does when there is no answer or too many.
#In this section
How an issue is matched to an Attio recordA project matches a request either by the reporter's own email address or by the domain of it. Exactly one of the two runs, and everything the card shows follows from that choice.Matching a company by its email domainCompany matching uses only the part after the @, so every reporter at a customer resolves to one record. Here is what is taken from the address, how subdomains are handled, and why four matches show nothing.Why a reporter on Gmail never matches a companyWhen a project matches by company, a long built-in list of free-mail domains is never looked up. This is what is on it, the two families nothing can override, and how to edit both domain lists safely.When the card cannot name a customerNo reporter, no readable address, nothing matching, or several things matching: what the card says in each case, what an agent sees that an administrator does not, and how long an answer lasts.
#Related
Get this right and the rest follows.
