Live during the call, not a sync
Sarah books into one place: your active connection on the Integrations page. During each call she reads your availability from it live, offers times inside your Hours that are free, and writes the booking before the call ends.
This is not a two-way sync. There is no background copy of your calendar and nothing to reconcile. If you move or delete something in your CRM, that is simply what Sarah reads on the next call. In systems that keep customer records, she looks for the caller's phone number first, so a returning customer is matched instead of duplicated.
Test calls from your dashboard never write to your CRM. A test that ends in a booking says so: it is a test, so nothing was sent.
What lands in each system
Google Calendar:an event on your booking calendar, with the caller's name, phone, address, service and notes.
Jobber: a client and a Request with a scheduled assessment, not a Job. You convert it when you are ready. Visits go to anyone, one technician, or take turns, as set in Edit setup.
Housecall Pro: by default, a lead in your Job Inbox with no time on it. Sarah tells the caller their request went to your scheduling team, and you confirm the time. If you choose Book the job on the schedule, she books a job at a confirmed time instead.
GoHighLevel: a contact and an appointment on the calendar you chose. Estimate requests and new leads also become opportunities in the pipelines you picked.
Workiz: a job with your chosen job type, length and assignee. JobNimbus: a contact and a task, using the task type, workflow and status you chose.
Square Appointments: a customer and a booking. Zoho CRM: a contact and a service appointment. Clio Manage: a calendar entry, with a contact. Acuity Scheduling: an appointment. Cal.com: a booking.
Callback requests and leads
When a caller wants you to call back rather than book, Sarah passes the message to you by text or email and tells the caller you'll call them back, reading out the last four digits of their number. On Jobber, Housecall Pro, GoHighLevel, Workiz and JobNimbus, the callback is also written into your CRM as a lead when the caller is new, or when an existing customer is asking about new work. A question about a job that's already booked or done, or a sales call, stays an alert only. On the other systems, every callback reaches you as the alert only.
Moving and cancelling
Callers can move or cancel a booking by calling back, where your system lets Ansa change bookings. To protect your customers, Sarah needs the caller's phone number plus their full name or the job address before she touches anything. She then changes the existing record in your system rather than creating a new one.
When a write fails
Sometimes your system refuses a write, for example because a key expired or access was removed. Sarah tells the caller someone will call them back, and you get an alert starting Ansa: new bookingwith the caller's name, phone, service and time, the reason it isn't in your CRM yet, and whether it will be added automatically. It comes by text with Text alerts on and a Mobile phone saved, otherwise by email.
Ansa holds the booking and retries it on its own, for example on the next call or right after you reconnect. If the alert says it will be added automatically, don't enter it by hand: you'd end up with a double booking. Only enter it yourself when the alert tells you to add it manually.
A held booking is never written to a different calendar. It waits for the connection it belongs to. For the fixes, see A booking didn't reach my CRM.