CRM Sync Errors
Fix call outcomes and fields not reaching Zoho, Salesforce or your own CRM: the call, the connection, field mapping and record matching.
Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.
After each call, Xebit writes the outcome, the summary and your structured fields to your CRM, through the Zoho and Salesforce connector or through a webhook your own handler processes. When data does not arrive, check four things in order: the call, the connection, the field mapping and the record it should land on.
Check the call first
- Sign in to the Xebit VoiceCloud dashboard at
voice.xebit.aiand open the call's details. - Sign in to the Xebit VoiceKit admin console on your own host and open the call's details.
- Check the call's disposition. A call that failed to connect has no conversation, so there are no captured fields to send.
- Check the fields were captured. If they are empty in the call's details, the problem is the agent, not the sync. See Configure an Agent.
Zoho or Salesforce not updating
- Is the connection active? Check the integration is still connected. A changed password, revoked access or an expired authorisation on the CRM side stops updates.
- Does the CRM user have permission? The account the connector uses needs permission to update the objects and fields you mapped.
- Is the agent using the connector? Confirm the agent or campaign is set to send results through it.
See Integrations.
Data arrives but fields are wrong or empty
What it usually means: a mismatch between the agent's fields and the CRM's fields.
- Check each agent field is mapped to the CRM field you expect.
- Check types match. A date field in the CRM needs a date; a number field needs a number.
- For pick lists, check the values the agent captures match the CRM's allowed values exactly. A lead status of "Qualified" will not land in a pick list that says "Sales qualified".
- Check required fields in the CRM. A record update can be rejected if a mandatory field is missing.
Data lands on the wrong record, or a new one
- Check how the call is matched to a record, such as by contact number or by an ID you passed in when the call started.
- Make sure numbers are stored the same way in both places. E.164 in Xebit and a local format in the CRM will not match.
- If you pass a CRM record ID with the contact, check it is being sent with every call.
Webhook based sync
If you sync through your own webhook handler, or to a CRM without a prebuilt connector, check whether the event reached your endpoint at all. If it did not, see Webhook Failures. If it did, the problem is in your handler or its call to the CRM: check its logs. Other CRMs connect through webhooks or the REST API, and Xebit builds that hook as part of deployment.
Network reachability
On Xebit VoiceCloud, your CRM and any webhook endpoint must be reachable from the internet.
On Xebit VoiceKit, your deployment must be able to reach the CRM. On an air gapped deployment nothing leaves the network, so only a CRM hosted inside your network can be updated.
Still need help?
Email hello@xebit.ai or use the contact page, with the call ID, the CRM you use and the fields you expected to see.
Support is included in your Xebit VoiceKit licence.