Google Calendar
Ready
Reads free and busy, offers only what is genuinely open, and writes the booking in with the caller's details on it.
What your voice assistant connects to
The full list, with what each one can do and where it stops. Two systems on this page only go one way, and that is written on them rather than left for you to find out.
How to read this page
Choose the software you already use, then check the actions supported by that connection. A customer lookup, a booking and an enquiry email are different things, and we explain those differences below.
Talkify provides the connections. If your system is not listed, ask about a custom integration before planning around it.
Everything on this page, at a glance
Google Calendar
Microsoft 365 & Outlook
Calendly
Cliniko
Fergus
Simpro
ServiceM8
Tradify
iTrade
Xero
Explore all 30 Talkify connections
Connections are provided by Talkify. Capabilities vary by system: Tradify sends enquiries by email, iTrade requests visits, and Calendly sends a booking link.
Diaries and bookings
The assistant reads the diary you already keep and writes the booking into it while the caller is on the phone. It does not keep a diary of its own, because a second diary is how double bookings happen.
Calendly
Ready
Books into your event types, honouring your buffers and your notice period rather than working around them.
Cliniko
Clinic appointments. It books the appointment. It is reception, so it will not answer a clinical question or triage a symptom.
Square Appointments
Australia only. Square has no New Zealand seller market, so this is not something a New Zealand business can use, and we will not sell it as though it is.
Job management
This is where the honest differences live. The systems have different capabilities, and some connections are one way, which changes what you can promise a caller.
Fergus
The fullest of the five. It looks the customer up, reads the diary and creates the job. Three ways to book: hold a slot, put in a request, or create the job outright. Fergus has no engine that decides who does the work, so we pick, using your rules.
Simpro
Customer lookup and lodging the job. One build per business, because Simpro is hosted separately for each company.
ServiceM8
Customers and jobs. Worth knowing: ServiceM8 sells its own AI phone product, and using theirs means moving your number onto their phone service. This never asks you to move your number, which is the practical difference between the two.
iTrade
It lodges a request for a visit. iTrade does not confirm a time, so the assistant will not tell a caller they have a booking. It says a request is in and somebody will confirm.
Tradify
One way, by email. The enquiry goes in. It cannot look a customer up in Tradify, cannot read your Tradify diary and cannot book into it, because Tradify has no public interface for any of that. Anyone telling you otherwise is guessing.
On the tools and here for this section alone? The trades version of all of this, with the job software covered properly, is on tradieansweringservice.com.
Systems for one kind of business
Booking a car in is not booking a massage. These connect to the system your industry actually runs on, which is usually where the caller's history lives as well.
MechanicDesk
Ready
Workshops. It takes the rego, finds the car, and books the work in. Bookings are written in rather than read back out, so the workshop diary stays the workshop's.
GymMaster
Ready
Gyms. The member's number ties them to their record, so a caller can ask about their own membership without reciting a number down the phone.
Zenoti
Ready
Salon, spa and clinic bookings, with the service list and the practitioner as you have them set up.
Workshop Software
The other workshop system. Same job as MechanicDesk: the car, the rego, the booking.
TaxiCaller
Transport. It takes a pickup and a drop off and puts the job in. It needs addresses it can find on a map, so a vague pickup gets asked about rather than guessed at.
Customers, accounts and the office
The caller's number is the first key. Once it knows who is ringing, it can answer about their account and write the call back where your team already works.
HubSpot
Ready
Looks the caller up before it answers, and logs the call and the outcome against them afterwards.
Pipedrive
Ready
Same again. New enquiries land as a deal rather than as a note somebody has to type up.
GoHighLevel
Ready
Contacts in, calls logged out, so the follow up sequences you already run pick the caller up automatically.
Xero
Ready
Account questions. What is owed, what is overdue, when it is due. It only ever answers about the account the caller's own number belongs to. An invoice number said out loud is not enough on its own, which is deliberate.
MYOB
Ready
Accounts and invoicing, for businesses that run MYOB rather than Xero.
Trello
Ready
Calls, or just the ones you choose, land on a board as cards for someone to pick up.
Slack
Ready
A post per call in the channel you choose, as the call finishes, with who rang and what happened.
Microsoft Teams
Ready
The same, in Teams, for offices that live there instead.
Payments, and the limit on them
The assistant can take a payment mid-call. What it cannot do, ever, is hear a card number. A link goes out by text, the caller pays on the payment page, and the assistant is told whether it went through.
That is not a limitation we are working around. It is the reason this is safe to put on a phone line at all.
Stripe payments
A payment link by text, paid on Stripe's own page, with the outcome read back on the call.
Windcave payments
The same, for businesses already taking payments through Windcave.
Everything else, and what comes with it anyway
If your system is not named above, there are still three ways in. And some of what people go looking for an integration for is already part of it.
REST API and webhooks
Ready
One API with per-account tokens, and webhooks that fire as calls, texts and leads happen. If you have a developer, this is the door.
Zapier
Ready
For everything with a Zapier connector and no developer to hand.
Leads
Ready
Calls, texts, website chat and your own web forms in one list, so an enquiry is not sitting in four places at once.
Website chat
Ready
The same assistant, on your website, answering out of the same documents so the two channels never disagree.
Front Counter
Ready
For a place with no booking or ordering system of its own. The assistant takes the booking or the order on the phone, it appears on a tablet by the till, and your staff work it and clear it.
On-call roster
Rings round whoever is on until somebody actually accepts the job, rather than trying three numbers and giving up.
Running something else?
Tell us what you use and we will quote the integration work. If it has an API, a connection can be built. If it has not, we will tell you that instead of promising one.