Guide
How to link Emails to Accounts, Leads, Customers in Fibery CRM?
You have your emails in Fibery, now what?
Let's say, you have an Accounts database with all leads and customers and you want to connect emails to these accounts. Here is the main idea and steps. We will setup an auto-relation between Account and Email database based on domain.
Every Account you want to link emails to should have a field to represent the Domain Name (e.g. fibery.io). We will use this field to link Emails to Accounts via an automatic relation. You might already have a Website field already in the Accounts db. In this case you could use the Website field to create a Domain Name formula field. It will look like this:
Replace(
Replace(Replace(Replace(Website, "http://", ""), "https://", ""), "www.", ""),
"/",
""
)
For the sync'd Contact database, we will setup a Domain Name field as a formula, where we extract the domain from Contact's Email address. It will look like this:
Right(Email, Length(Email) - Find(Email, "@"))
The Email database is more complicated, since you will be syncing sent and received emails and so we should choose correct domain depending on that. The Email database is linked to the Contact database via several relations, including From and To. We'll create a Customer Domain formula field in the Email database. If From Domain is your company domain, then we ignore it and take first domain from To (it is a list of Contacts). Here is the formula:
If(
From.[Domain Name] != "fibery.io",
From.[Domain Name],
To.Sort([Public Id]).First().[Domain Name]
)
Now we can setup an automatic relation between Email and Account. Create a new relation, enable "Automatically link Emails to Accounts" in the Advanced section and select to match on the Customer Domain field for Email and the Domain Name for Account.
The last step is to properly setup the Emails relation view inside an Account entity. By default, a List is created automatically, but you will probably want to group it by Thread. For any Account entity, configure the Emails relation view so that Thread (recursive) is the grouping option for the list.