AI Receptionist Integrations: How CRM, Calendar and Stripe Connections Work

An AI receptionist integration is a connection that moves what happened on a call into software you already use, such as a customer record in your CRM, an event on your calendar or a payment link from Stripe, without anyone retyping it. Most integrations are built from the same three parts: APIs, webhooks and a permission grant called OAuth. This guide explains how each kind of connection works, what tends to break, what to ask a vendor, and exactly what TheKeyBot's own plans list.

Key takeaways

• "Integrates with" can mean one field moving one way. Ask for the field list, the direction and the timing of every connection.
• An AI that books should check availability at the moment of booking. Google's Calendar API can check up to 50 calendars in one free/busy request, and Microsoft Graph has a getSchedule method that does the same for Outlook calendars.
• Payment connections usually send a link, and the processor reports back by webhook. Stripe retries failed webhook deliveries for up to three days and doesn't guarantee their order, so ask how the vendor handles late and duplicate events.
• Limits and expiring access are normal. HubSpot caps private apps on its Free and Starter tiers at 100 requests per 10 seconds, and Jobber access tokens expire after 60 minutes, so every integration needs someone maintaining it.
• Give each connection the least access it needs, using OAuth scopes and, on Stripe, restricted API keys.
• TheKeyBot's pricing page lists POS and payments plus QuickBooks sync on Core and above. Lite lists no integrations; it sends each message to Telegram.

What does "integration" mean for an AI receptionist?

Every connection does some mix of three jobs: it reads data (is 2 p.m. open?), writes data (create the customer, book the job) and listens for changes (the deposit was paid, the customer cancelled). Those jobs map onto three building blocks.

• APIs are the doors a piece of software opens to other programs, so they can read or write its data on request.
• Webhooks run the other way. When something happens, one system sends a message to a web address the other system listens on.
• OAuth is how you grant permission without handing over your password. The standard behind it, RFC 6749, opens with this line: "The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service." The word that matters is "limited."

The same vendor can be deep in one connection and shallow in another, so judge each one separately.

Which connections matter most for your shop?

Not every shop needs every connection. Start with the one that removes the most retyping or the most risk, and leave the rest for later.

A worked example, with made-up numbers, shows why the first connection is often enough. Suppose a two-truck shop books 80 jobs a month from phone calls, and someone spends about 3 minutes retyping each one into the schedule and the customer list. That's 240 minutes, or 4 hours a month, plus the occasional typo in an address or phone number. A working calendar or field-service connection removes most of that; a CRM connection on top may save another few minutes a week. Count your own minutes before paying extra for a connection.

How do calendar integrations work?

Booking takes two steps, and both have to happen during the call. First the AI asks the calendar which times are free. Google's Calendar API has a free/busy method that "Returns free/busy information for a set of calendars" and accepts up to 50 calendars per request. Microsoft's equivalent, getSchedule, gets free/busy availability for a group of users or resources over a time period, in time slots that default to 30 minutes. Then the AI writes the booking, which on Google is the events insert method, described simply as "Creates an event."

The harder part is staying in sync after the call. If a technician moves a job on their phone, the AI needs to know. Google offers push notifications that alert an app when a watched calendar changes, but its documentation also says, "Currently, there's no automatic way to renew a notification channel." Channels can expire, and the vendor has to replace them. Ask how the vendor keeps its view of your calendar current, and how often it double-checks.

If you take bookings through a scheduling page such as Calendly, the AI may book through that instead. Calendly's developer guide describes webhook subscriptions that send data in real time when events are scheduled or canceled, and Smith.ai lists "AI Scheduling (Calendly & more)" among its AI features.

Three questions settle most calendar problems:

1. Which calendar is the source of truth? One place should own the schedule. If techs keep personal calendars too, decide which one the AI reads.
2. Does it check availability at the moment of booking, or work from a copy made earlier?
3. How are job lengths, travel buffers and time off handled? Our guide to what booking and dispatch require covers the setup, and our booking walkthrough goes from first ring to calendar entry.

How do CRM and field-service integrations work?

A CRM connection writes the caller into your customer list: name, phone number, address, what they needed and what was promised. The details that decide whether it helps are matching (does a repeat caller update their existing record or create a second one?), field mapping (does the vehicle or job type land in a field you can filter on, or in a notes blob?) and timing (during the call, or minutes later?).

Platforms limit how fast other software can talk to them, and a busy day can hit those limits. HubSpot's usage guidelines put privately distributed apps on Free and Starter tiers at 100 requests per 10 seconds per app and 250,000 per day per account, and say an app that exceeds its limits receives a 429 error response for all subsequent API calls. A well-built integration slows down and retries; a poorly built one drops records. Ask which one you're buying.

Field-service platforms work the same way, with more objects to map. Jobber's developer documentation says its API is GraphQL over HTTPS, that apps get access through OAuth 2.0 with scopes defining exactly what data they can read or write, that access tokens expire after 60 minutes and are refreshed, and that requests are limited to 2,500 per 5 minutes. Jobber's documentation also says API versions are supported for at least 12 months, which means someone has to update the integration when versions change. Ask any vendor which objects it writes (client, request, quote, job or visit), and who fixes the connection when the platform changes.

If you're still choosing the rest of your software, our locksmith software category map and scheduling and dispatch evaluation framework show where each piece fits.

How do payment integrations like Stripe work?

The usual pattern has three steps. The AI, or the system behind it, asks the payment processor to create a payment link for the deposit. The link goes to the caller by text, and Stripe's Payment Links are built to be copied and shared over email, SMS or social media. When the caller pays, the processor sends a webhook back saying so.

That last step is where integrations go wrong, and Stripe's webhook documentation is candid about it:

"Stripe doesn't guarantee the delivery of events in the order that they're generated."

The same page says Stripe attempts delivery for up to three days with exponential back-off in live mode, that endpoints might occasionally receive the same event more than once, and that without signature verification an attacker could send fake webhook events. A sound integration verifies each event, ignores duplicates and doesn't mark a deposit paid twice. Ask the vendor how it handles all three.

Two more things to check:

• Keys and access. Stripe recommends restricted API keys for most use cases, so an integration gets the exact permissions it needs and no more. If a vendor asks for your full secret key, ask why.
• Fees and card security. On Stripe's standard U.S. pricing, domestic card payments cost 2.9% plus 30¢, plus 0.5% for manually entered cards. A link keeps the card number off the call, which matters because the PCI Security Standards Council's phone-payment guidance says recorded card security codes must be made unrecoverable after authorization.

Our guide to taking deposits on the phone covers what to say on the call.

How do accounting integrations like QuickBooks work?

Accounting connections move customers, invoices and payments into your books, and some listen for changes. Intuit's developer documentation says QuickBooks Online webhooks "automatically notify you whenever data changes in your end-user's QuickBooks Online company files." Before you switch one on, decide which system creates the invoice, how deposits are recorded against the final bill, which income account each job type maps to, and how sales tax is handled. Ask your bookkeeper to check the first week of synced entries.

Do you need Zapier or another no-code connector?

Only when the AI receptionist can send webhooks but has no built-in connection to the app you use. Zapier's webhook trigger gives you a unique address the AI can post to, and its help page lists the feature on its Free, Professional, Team and Enterprise plans. The trade-offs are another account to pay for, another place for things to fail, and someone who has to notice when a step stops running.

What can go wrong, and how will you know?

Integrations rarely fail loudly. A record stops appearing and nobody notices for a week. Plan for these:

Whatever the vendor says, ask for a written description of each integration: the fields, the direction, the trigger and the failure alerts. The FTC's guide to protecting personal information gives the same advice about any service provider that touches customer data: put your security expectations in writing in the contract, then verify compliance.

What does TheKeyBot connect to?

Disclosure: TheKeyBot, which publishes this guide, makes an AI receptionist. Here is what our own pages list, and nothing more.

• Core, Pro and Elite. The pricing page lists POS and payments and QuickBooks sync on Core and above, alongside the 24/7 inbound AI receptionist, scheduling and GPS dispatch, and unlimited users. Core is $500 a month with 500 AI minutes, then 45 cents a minute.
• Built-in pieces. The features page describes a built-in customer database (customer history, vehicle records, service notes) and a scheduling calendar with an online booking portal. Those are parts of the system rather than connections to outside software.
• Lite. KeyBot Lite ($149 a month) takes the message and sends it to your phone through Telegram, with a simple dashboard for recordings, transcripts and usage, per the Lite page. It doesn't quote or book, and its listing shows no integrations.

If you depend on a specific CRM, field-service app or calendar, ask us, as you would any vendor, to show it working on a test call before you commit. Core, Pro and Elite include a 14-day free trial, and Lite's first 5 answered calls are free. Our Lite vs Core guide explains when the bigger system is worth it.

How do you test an integration on a trial?

Run these on any vendor with your real accounts connected, and check the other system after each step, not the AI's summary:

1. New caller. Call from a number your CRM has never seen. Check that the record appears, with each field in the right place, and how long it took.
2. Repeat caller. Call again from the same number. Check that the existing record is updated rather than duplicated.
3. Booking and change. Book a slot, then move it in your calendar. Call again and ask for the old time; the AI shouldn't offer the slot you just filled.
4. Deposit. Ask for a deposit link, pay a small real amount and refund it, or use the vendor's test mode if it has one. Check that the job shows the payment without you marking it.
5. Accounting. If you connect QuickBooks or similar, check the customer, invoice and payment in your books after the test day.
6. Disconnect. Remove the integration's access, place a call, and see whether anyone tells you the record didn't sync.

Put the results next to the vendor's other answers in our buyer's checklist, and see our trial test-call script for the calls themselves.

What should you do this week?

1. List your systems: phone, calendar, customer list, field-service app, payments, accounting.
2. Pick a source of truth for customers, the schedule and money, so no two systems fight over the same record.
3. Write the field list you need from every call, such as name, number, address, job type, vehicle, price quoted and deposit status.
4. Ask each vendor for written integration details: fields, direction, trigger, failure alerts.
5. Run the six tests above on your finalists before you sign.

Frequently Asked Questions

What is an AI receptionist integration?

It's a connection that moves call results into your other software, such as a customer record in your CRM, an event on your calendar or a payment link from your processor. Most are built from APIs, webhooks and OAuth permissions.

Can an AI receptionist book directly into Google Calendar or Outlook?

Some can. Google's Calendar API and Microsoft Graph both let software check free/busy availability and create events, so ask whether the vendor checks availability at the moment of booking and how it notices changes you make later.

How does an AI receptionist take a deposit through Stripe?

Usually it creates a payment link, texts it to the caller, and waits for Stripe to report the payment by webhook. Ask how the vendor handles late, duplicate and out-of-order events, and keep card numbers off the call.

What happens if an integration breaks?

Often nothing visible: records quietly stop syncing. Ask whether the vendor alerts you when a connection drops or a request fails, and check the connected system yourself during the first weeks.

Do I need Zapier to connect an AI receptionist?

Only if the AI can send webhooks but has no built-in connection to the app you use. A connector like Zapier fills that gap, at the cost of another account and another step to maintain.

What integrations does TheKeyBot include?

TheKeyBot's pricing page lists POS and payments and QuickBooks sync on Core, Pro and Elite, alongside scheduling and GPS dispatch. KeyBot Lite sends messages to Telegram and lists no integrations.

---

Sources

1. IETF, RFC 6749, "The OAuth 2.0 Authorization Framework": https://datatracker.ietf.org/doc/html/rfc6749
2. Google Calendar API, "Freebusy: query": https://developers.google.com/workspace/calendar/api/v3/reference/freebusy/query
3. Google Calendar API, "Events: insert": https://developers.google.com/workspace/calendar/api/v3/reference/events/insert
4. Google Calendar API, "Push notifications": https://developers.google.com/workspace/calendar/api/guides/push
5. Microsoft Graph, "calendar: getSchedule": https://learn.microsoft.com/en-us/graph/api/calendar-getschedule?view=graph-rest-1.0
6. Calendly Developer, "Create a Webhook Subscription": https://developer.calendly.com/docs/api-guides/receive-data-from-scheduled-events-in-real-time-with-webhook-subscriptions
7. Smith.ai, AI Receptionist pricing: https://smith.ai/pricing/ai-receptionist
8. HubSpot, "API usage guidelines and limits": https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
9. Jobber Developer documentation: https://developer.getjobber.com/docs/
10. Stripe Documentation, Payment Links: https://docs.stripe.com/payment-links
11. Stripe Documentation, webhooks: https://docs.stripe.com/webhooks
12. Stripe Documentation, API keys: https://docs.stripe.com/keys
13. Stripe, pricing: https://stripe.com/pricing
14. PCI Security Standards Council, "Protecting Telephone-Based Payment Card Data" (November 2018): https://listings.pcisecuritystandards.org/documents/Protecting_Telephone_Based_Payment_Card_Data_v3-0_nov_2018.pdf
15. Intuit Developer, QuickBooks Online webhooks: https://developer.intuit.com/app/developer/qbo/docs/develop/webhooks
16. Zapier Help, "Trigger Zap workflows from webhooks": https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zap-workflows-from-webhooks
17. Federal Trade Commission, "Protecting Personal Information: A Guide for Business": https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business
18. TheKeyBot pricing: https://www.thekeybot.com/pricing
19. TheKeyBot features: https://www.thekeybot.com/features
20. TheKeyBot, KeyBot Lite: https://www.thekeybot.com/lite