Once Zoho Desk is connected to Zoho CRM, the next job is deciding how contacts and accounts should sync and which fields map to which. This is Step 2 of the integration, and the choices you make here decide which way data flows, which records are included, and how duplicates are spotted.
After the integration is complete, CRM users are added to Zoho Desk automatically as Light Agents. They can be @mentioned in tickets and receive notifications through CRM Signals. Mentioning @CRM Contact Owner in a ticket notifies the matching contact owner in Zoho CRM through CRM Signals.
To stop test or junk records travelling between systems, set your delete preferences under Setup, then Integrations, then Zoho, then Zoho CRM. On the Configuration Details tab, under Preferences, choose whether contacts and accounts are kept or deleted when their equivalent is deleted from the other service.
| When a CRM record is deleted | What happens in Zoho Desk |
|---|---|
| Always delete the corresponding record | The record and its associates go to the recycle bin. |
| Delete only if there are no associates | The record goes to the recycle bin only if it has no associates. Otherwise only the mapping between the records is removed. |
| Never delete the corresponding record | Only the mapping between the records is removed. |
For deletions in Zoho Desk, the choice is to always delete the corresponding CRM record, or never delete it and remove only the mapping.
Associates are the child records linked to a contact or account. For contacts these are tickets, time entries, activities, and attachments. For accounts they are tickets, contacts, contracts, and attachments. Because "always delete" takes associates with it, choose it carefully.
Sync History under the same integration page shows the last seven days of syncs, including how many records were added, updated, or failed. The Failure Log lists individual records that didn't sync, with the time and reason, and a Try Again option to re-sync a record. Common causes include a record that looks like a duplicate because its original is already mapped, and a field mapped to the wrong type, for example text into an integer field.