Skip to Content

Help centre / CRM guides

Send outcomes back to your CRM

Show bookings, call-back requests, and handovers on the contact’s CRM record.

Write-back is off for every CRM connection until an owner or admin switches it on. Start with a connected CRM and contacts imported from it.

Switch it on

  1. Open Integrations and select Configure import on your CRM.
  2. Under Write back to your CRM, tick Add bookings, call-back requests and handovers to the contact’s record.
  3. Check the line beneath it starts with On.

Switching it on writes to your CRM from then on. Upcoming appointments that were booked earlier are added within about 15 minutes.

What is written

In VenditaIn your CRM
The agent books an appointmentAn event or meeting on the person’s record
The booking movesThe same record is updated
The booking is cancelledThat record is removed
The contact asks for a call backA task to call them
The call-back is completed or no longer neededThat task is marked complete, with the reason
The agent hands the conversation to a personA task, marked urgent when it is

Each record carries what the team needs to act: what was said, the campaign, and a link to the conversation in Vendita. See the exact records for HubSpot, Pipedrive, Zoho CRM, and Salesforce.

Vendita only writes for contacts that came from that CRM. A contact added by CSV gets nothing written, unless a later CRM import matches it by email.

Contacts, leads, and deals are never created, changed, or removed. Vendita only updates or removes records it created.

Keep the two in step

  • Move or cancel an appointment in Vendita, not in the CRM. Vendita does not read changes made to these records in the CRM.
  • Complete a call-back in Vendita and its CRM task is closed for you. A handover task stays open until your team closes it in the CRM.
  • A failed write never blocks a booking. Vendita retries it automatically.

Check it is working

Under the switch, Vendita shows how many records are written, waiting, and failed, with the last error when there is one.

If writes fail, check that the CRM is still Connected on Integrations and that the connecting CRM user can create events and tasks. Reconnect if the card shows Needs attention.

Switch it off

Untick the same box. New outcomes stop being written. Records already in the CRM stay as they are.

Use an assistant or the API instead

Ask your connected assistant:

Show my CRM connections and whether write-back is on for each. Don’t change anything.

Or call PUT /crm/connections/{id}/write-back with {"enabled": true} using an API key that has the crm:write permission.

On this page