Integrates with is not a fact, it is a mood
In this category the word covers everything from a direct calendar write to a webhook you would have to build yourself. Three states, stated plainly, is the whole fix.
The short version
- Our three states are: writes directly, through Zapier, and entered by your team from the call summary. Every row carries one.
- Native for us means Google Calendar, Outlook and webhooks, each a direct write with nothing in between.
- A logo wall is not an integration matrix. A logo can mean a partnership, a webhook, or a page someone wrote.
- The question to ask any vendor: does it write, and what exactly does it write?
What the word has been stretched to cover
Walk through the integration pages in this category and you find the same design: a grid of logos, each meaning something different and none of them saying which. Behind one logo is a native two-way sync. Behind another is a Zapier template. Behind a third is a webhook that a developer could point at the tool if you hired one.
All three get described the same way, and the buyer finds out which they bought during implementation. That is not usually deception so much as a category that has let a useful word go soft, and once one vendor uses it loosely the rest cannot afford to be precise.
The cost lands on the buyer as a specific failure: you choose a vendor because it integrates with your scheduling system, and two weeks later you are looking at a Zapier bill and a field mapping nobody mentioned.
Three states, and why the third one matters most
Writes directly means our system writes into theirs without an intermediary. Through Zapier means it works, and there is a hop, an account and a cost that is not ours: we send a webhook, and catching it with Webhooks by Zapier needs a paid Zapier plan. The third state means no connector exists, and the call arrives as a transcript and summary for your team to enter.
Labelling every row is what turns the list from marketing into information. A reader can trust each label, because every system on the page carries one and none is left to a logo.
It also keeps us precise. Because every row has a stated route, a Zapier hop never gets blurred into a native write, and a buyer never finds out in week two.
What to ask, whoever you are buying from
Does it write, or does it only read? A tool that can see your calendar but not create an event is not going to book an appointment, and that distinction is invisible in a logo grid.
What exactly does it write? A booking that creates a blank event at the right time is very different from one that carries the caller's name, number and reason for calling into the description.
If it goes through Zapier, whose account pays for that? Zapier's own pricing is not a rounding error at volume, and a vendor describing that path as an included integration has moved a cost onto you.
And ask what happens when the write fails. A booking that silently does not appear is worse than one that never claimed to work, because you will not find out until the customer does.
How to read our matrix in two minutes
Start with your calendar. Google Calendar and Outlook write directly, so a booking lands while the caller is still on the line.
Then find your job or practice software. A Zapier row runs on our signed webhook and a paid Zapier plan. Any other row arrives as a transcript and summary for your team to enter.
Hear it handle one of your own calls
Your scenario, your greeting, a couple of minutes.