Locksmith Software Stack (2026): How the AI Receptionist, Scheduling, Payments and Books Fit Together

A locksmith software stack has five layers: the phone number, the answering (where an AI receptionist sits), the job records, the money, and the follow-up. The stack works when each kind of record has one home and the layers pass information to each other without someone retyping it. This guide shows how the layers connect, which data should live where, and how to map your own stack in an afternoon before you buy anything.

Disclosure: TheKeyBot publishes this guide and sells software that covers several of these layers, including an AI receptionist. Other products are described from their own pages as of October 2026, without ranking. For what to ask vendors and how to test them, see our buyer's guide; this post is about how the pieces fit.

Key takeaways

• Five layers, one job each. Phone, answering, job records, money and follow-up. Trouble starts when two systems both think they own the same record.
• The number comes first. Google says the phone number on your profile "must be under the direct control of the business" (Google), so build everything else around a number you control.
• The AI receptionist is only as good as what it can read. Jobber's Receptionist, for example, works from "the business data already in your Jobber account" (Jobber).
• Connections fail in predictable ways. Stripe's documentation warns that webhook events may arrive out of order or more than once, and it retries failed deliveries for up to 3 days (Stripe).
• Count your double entry. The cheapest stack on paper can be the most expensive one if someone retypes every job.

What are the layers of a locksmith software stack?

Each layer can be its own product or part of a bigger one. Jobber, for instance, lists a Receptionist add-on for $29 a month on top of its field-service plans (Jobber), while TheKeyBot Core bundles an AI receptionist with scheduling and GPS dispatch, POS and payments, and QuickBooks sync for $500 a month with 500 AI minutes (pricing). Neither approach is right for every shop; what matters is that each layer is covered once.

Where does the AI receptionist sit, and what does it need?

The answering layer sits between your phone and your job records. On every call it reads from the layers around it and writes back into them.

What it reads: your services and price book, your service area (which Google says shouldn't extend farther than about 2 hours of driving from your base, per its profile guidelines) and hours, your schedule if it books, and your customer list if it recognizes repeat callers. Jobber says its Receptionist can "book jobs based on your real availability" because it runs on the data in your Jobber account (Jobber). ServiceTitan says its AI Virtual Agents "can work alongside your current phone platform or as part of Contact Center Pro" (ServiceTitan).

What it writes: a message, a booked job, a call summary, a transcript or recording, and an alert to whoever is on call. Housecall Pro says you get "call summaries, booking details, and customer info logged in your call log and calendar" (Housecall Pro). TheKeyBot's FAQ says that when it books a job it can notify dispatchers or technicians by SMS or email or by updating your CRM (FAQ).

That gives you the two failure modes to check before you buy. If the receptionist can't read your schedule, it will promise times you can't keep. If it writes somewhere nobody looks, a booked job sits unseen. Our complete guide to AI receptionists for locksmiths covers setup, and what an AI receptionist can't do covers the handoffs.

One platform, connected tools or separate tools?

There are three ways to build the stack. The trade-offs are real either way, so pick by your shop, not by the pitch.

A useful rule: if you already run field-service software you like, test its built-in answering first, or add an answering layer that writes into it. If you have no system of record yet, a platform that covers several layers saves you from building connections at all. Our guide to AI across the whole locksmith shop walks through what each layer can automate.

How do the tools talk to each other?

Three mechanisms cover almost everything:

• Built-in syncs. The vendor connects two products for you. Jobber, for example, says it "syncs with QuickBooks Online" (Jobber), and TheKeyBot Core lists QuickBooks sync (pricing). Ask what syncs (customers, invoices, payments) and in which direction.
• Webhooks and APIs. One system tells another when something happens. Stripe's documentation explains that after you register an endpoint, "Stripe pushes real-time data to it when events happen in your Stripe account" (Stripe).
• Call forwarding. The phone layer hands calls to the answering layer. Jobber says you can forward from your current provider "either after hours or after a set number of rings" (Jobber), and carriers such as Verizon Business Digital Voice let you choose the number of rings before a no-answer forward.

Connections fail in predictable ways, and Stripe's own documentation lists several. It says it "doesn't guarantee the delivery of events in the order that they're generated," that endpoints "might occasionally receive the same event more than once," and that in live mode it keeps retrying a failed delivery for up to 3 days (Stripe). In a locksmith shop, that shows up as a duplicate customer, a job marked unpaid after the card went through, or an invoice that synced twice. Check for those three things weekly during the first month of any new connection.

What does each layer cost?

Add up the layers, not the headline price. These are published list prices as of October 2026, before taxes, add-ons and per-user fees; they are examples, not a ranking.

The comparison that matters is the total for the layers you need. A bundle is cheaper only if it replaces tools you would otherwise pay for, and a set of cheap tools is cheaper only if someone isn't spending hours a week retyping between them.

Which data should live where?

Pick one home, the system of record, for each kind of data. Other tools can show a copy, but only the home gets edited.

Two rules from regulators shape the last three rows. PCI DSS applies to entities that "store, process, or transmit cardholder data" (PCI Security Standards Council), so keep card data inside the processor. The FTC's data security guide says to "Keep only what you need for your business" (FTC), which argues for a retention period on recordings. And in a February 2024 order, the FCC set a limit of 10 business days for honoring requests to stop robocalls and robotexts (FCC 24-24), so opt-outs must reach every tool that texts.

What does the phone layer need?

The phone layer is the foundation, because your number is printed on your van, your listings and your ads.

• Keep control of the number. Google's guidelines say to use "a local phone number instead of a central call center helpline number whenever possible" and that the number must be under the business's direct control (Google).
• Know how you'd move it. Federal rules require carriers to complete a simple wireline-to-wireline or simple intermodal port "within one business day" (47 CFR 52.35). See keeping your number when you add an AI receptionist.
• Don't rely on your Business Profile for call records. Google removed call history from Business Profile on July 31, 2024, so your carrier or answering layer has to keep them.
• Measure ad calls separately. Google Ads call reporting records whether each ad call was missed or received, and Google's Local Services Ads ranking page says missed calls may negatively affect your responsiveness. Our phone number strategy guide covers tracking numbers.

What do three example stacks look like?

These are illustrations, not recommendations, and the shops are made up.

A solo mobile locksmith. Phone: one cell number the owner controls. Answering: a message-taker after hours, such as KeyBot Lite at $149 a month with 100 calls included (Lite), or a field-service platform's receptionist add-on. Job records: a calendar and a notes app. Money: a card reader or payment links. Follow-up: a manual review text. The weak link here is the job record, which lives in the owner's head; that holds until a second technician starts.

A three-van shop on field-service software. Phone: the shop number, forwarded after hours and after a few unanswered rings. Answering: the platform's built-in AI agent or an AI receptionist that writes into the platform. Job records and scheduling: the platform. Money: the platform's payments plus a QuickBooks Online sync. Follow-up: the platform's automations, set to send every customer the same review link. The weak link here is the price book, kept in a spreadsheet the receptionist can't read.

An eight-van shop buying ads. Phone: tracking numbers per ad source plus the main line. Answering: AI with escalation to a dispatcher during the day. Job records: one platform with dispatch and GPS. Money: processor plus accounting sync, with a weekly payment-to-job check. Follow-up and reporting: call tracking and attribution so ad spend can be matched to booked jobs. TheKeyBot's Pro plan ($750 a month, 1,000 minutes) is one option that adds call tracking and attribution to the Core bundle (pricing). The weak link here is duplicate customers created by three different intake channels.

For scheduling at larger sizes, see what breaks at 3, 8 and 20 trucks.

How do you map your own stack this week?

Set aside an afternoon and work through these steps with whoever answers your phones.

1. List every tool and its monthly cost, including the phone bill, any answering service, field-service software, payment processor, accounting, and texting or review tools.
2. Follow one real job from first ring to paid invoice. Write down every system it touches and every time someone types the same information again.
3. Mark the home for each kind of data using the table above. Where two tools both claim the same record, pick one.
4. Count the double entry. For one week, tally how many times someone retypes a customer, a job or a payment.
5. Check the phone layer. Confirm the number is in your name, and know whether you'd forward or port it if you changed answering vendors.
6. Fix the cheapest gap first. That may be connecting answering to your job records rather than buying a new platform.
7. Re-map after any change, and check for duplicates and missing payments weekly for a month.

Where does TheKeyBot fit?

TheKeyBot covers different layers depending on the plan. KeyBot Lite ($149 a month) is the answering layer only: it answers 24/7 in English and Spanish and sends the message to your phone, without quoting or booking. Core ($500 a month with 500 AI minutes, then 45 cents a minute) adds scheduling and GPS dispatch, POS and payments, QuickBooks sync and unlimited users, so it can be the system of record for a shop that doesn't have one. Pro ($750) adds call tracking and attribution, a power dialer and AI transcription, and Elite ($1,200) adds AI marketing, Google Ads management, the Jarvis AI business brain and a dedicated account manager. Every plan includes a dedicated AI phone number and no setup fees, and Core, Pro and Elite include a 14-day free trial (pricing).

The honest caution: if you already pay for field-service software that schedules and takes payments, Core duplicates those layers. In that case compare your platform's own agent with an answering-only option before adding a second system of record.

Frequently Asked Questions

What is a locksmith software stack?

It is the set of tools a shop runs on: the phone number and carrier, the answering layer (an AI receptionist, a service or a person), the job records and schedule, the payment and accounting tools, and the follow-up tools for reminders and reviews.

Should the AI receptionist be part of my field-service software?

It depends on whether you like your field-service software. If you do, test its built-in agent or an answering product that writes into it; if you have no system of record yet, a platform that bundles answering, scheduling and payments avoids building connections.

What is a system of record?

It is the one place where a kind of data is edited, such as your customer list or your schedule. Other tools can show copies, but keeping one home per record prevents duplicates and conflicting prices.

How do locksmith software tools connect to each other?

Mostly through built-in syncs between products, webhooks and APIs that send events from one system to another, and call forwarding between the phone and the answering layer. Check every new connection weekly for duplicates and missing payments during the first month.

How do I avoid losing my phone number when I change software?

Keep the number registered to your business, forward it to new services rather than adopting a vendor's number as your main line, and know the porting steps. Federal rules require carriers to complete simple wireline and intermodal ports within one business day.

Does TheKeyBot replace my other software?

TheKeyBot Core covers answering, scheduling and GPS dispatch, POS and payments, and QuickBooks sync, so it can replace several tools for a shop without a system of record. KeyBot Lite covers answering only, which suits shops that already run their jobs elsewhere.

---

Sources

1. Google Business Profile Help, "Guidelines for representing your business on Google": https://support.google.com/business/answer/3038177?hl=en
2. Jobber Receptionist: https://www.getjobber.com/features/ai-receptionist/ and pricing: https://www.getjobber.com/pricing/
3. Housecall Pro CSR AI: https://www.housecallpro.com/features/csr-ai/
4. ServiceTitan AI Virtual Agent: https://www.servicetitan.com/features/pro/voice-agent
5. Stripe Docs, "Receive Stripe events in your webhook endpoint": https://docs.stripe.com/webhooks
6. Verizon Business Digital Voice, call forwarding: https://businessdigitalvoice.verizon.com/?p=9196
7. 47 CFR § 52.35, porting intervals (Cornell LII): https://www.law.cornell.edu/cfr/text/47/52.35
8. Google Ads Help, "Analyze call reporting data": https://support.google.com/google-ads/answer/7180997?hl=en
9. Google Local Services Help, "About ad rankings": https://support.google.com/localservices/answer/7527305?hl=en
10. PCI Security Standards Council, PCI DSS: https://www.pcisecuritystandards.org/standards/pci-dss/
11. FTC, "Protecting Personal Information: A Guide for Business": https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business
12. FCC Report and Order FCC 24-24 on revoking consent (February 2024): https://docs.fcc.gov/public/attachments/FCC-24-24A1.pdf
13. TheKeyBot pricing: https://www.thekeybot.com/pricing
14. TheKeyBot FAQ: https://www.thekeybot.com/faq