Does it integrate with my CRM?

The word integration covers a huge range. At one end, a record appears in your CRM with fields populated. At the other, you get an email you have to copy and paste from.

Between them sits Zapier, which works reliably and adds a short delay, usually under a minute. For most inbound workflows that is invisible.

The honest thing a vendor can do is label each connection. Most do not, which is why buyers discover the truth in week two.

What object gets created? A contact is useful. A contact plus a call record with the transcript attached is much more useful, and the difference is rarely on the feature page.

What happens on a repeat caller? A system that creates a second contact every time someone rings makes a mess quickly. Ask how it matches on phone number.

Is it one-way or two-way? Writing a lead into your CRM is easy. Reading your CRM so the assistant knows who is calling is a different and rarer capability.

What happens when it fails? A Zapier step that errors silently is worse than no integration, because you believe the record exists. Ask where failures surface.

Say you run a landscaping company on Jobber, which sits in the Zapier column of our matrix. GreetKeeper has no Zapier app, so the trigger is Webhooks by Zapier catching the webhook we send, and that trigger needs a paid Zapier plan. A sensible flow has three actions after it. First it searches Jobber for a client with the caller's phone number. If nobody matches, it creates the client. Then it adds a new request to that client, carrying the call summary and the reason for calling.

A homeowner rings at 6:50pm about a retaining wall. By 6:52 there's a request in Jobber under her name for your office manager to quote in the morning. When she calls again on Thursday, the search step finds her and the second request attaches to the same client, so you don't end up with two of her.

Zapier counts each action as a task. At 400 calls a month, a three-action flow uses 1,200 tasks, so look at your Zapier plan's monthly limit before you switch this on. Which actions exist depends on your CRM's own Zapier connector, so read that list first.

Make the first call from a number your CRM has never seen and confirm a new record appears with the fields filled in. Call again from the same phone, and check that you still have one contact rather than two.

For the third, block your caller ID. Matching on phone number can't work when there's no number, so you need to know what gets created and whether a person will have to tidy it up. On the fourth, give a different name from the one your CRM holds for that number, as a spouse or a colleague might. Does the old name get overwritten?

The last test is the unpleasant one. Pause the Zapier flow, place a call, and see what happens. Find out where the failure shows up, who gets told, and whether the call's details are recoverable once the flow is back on. A missed sync you know about is a small chore, while one that fails silently is a lead nobody called back.

Google Calendar and Outlook write directly, which covers the booking side for most businesses.

Field-service and practice systems such as ServiceTitan, Jobber and Clio are reached through Zapier. GreetKeeper has no Zapier app: we send a webhook, you catch it with Webhooks by Zapier on a paid Zapier plan, and the other tool's Zapier action writes the record. We label that as Zapier rather than calling it native, because the distinction is the whole point of publishing a matrix.

Where something does not connect, the matrix says so. That is more useful than a logo and it is the honest version of a feature page.