Industries

AI agents in small-business appointment booking

How people's agents could book clinics, salons, garages and trades without phone tag, the calendar standards involved, and the US and Canadian calling rules.

Clinics, dental offices, salons, garages and trades run on appointments, and many of those appointments are made by phone. People’s assistants have started calling for them: Google’s Business Profile help page says Google may place automated calls to businesses to book appointments for customers. When the business answers with its own automated system, two machines negotiate a time slot in speech. A booking is a small set of fields, so it is one of the clearest cases for sending the request as data instead.

Where agents meet today

The phone line

Google’s help page describes automated calls and texts it places to businesses to book appointments, check restaurant wait times, and confirm prices and availability. Businesses can opt out during a call, in their Business Profile settings, or by replying STOP to a text. For the business, the call arrives like any other. It learns which assistant is calling, and for whom, only from what the voice says, and it has no structured record of what was agreed beyond its own notes. When two voice agents meet on a phone call covers what goes wrong when both ends are machines.

Calendar and booking standards

The data side is standardized already:

  • iCalendar (RFC 5545) is the IETF format for events, to-dos and free/busy information, independent of any calendar service.
  • HL7 FHIR defines Schedule, Slot and Appointment resources for health care. A Schedule exposes available Slots, an Appointment books one, and AppointmentResponse lets participants accept or decline.

Booking software holds the same kinds of data. What’s missing is a public, verified way for a person’s agent to reach it directly instead of dialling.

What a booking request needs

A booking is a short list of fields: the service, the staff member if the customer cares, a time window, the customer’s name and contact details, and any intake questions the business asks, such as the vehicle model for a garage or a new-patient form for a clinic. The business adds its policy: deposit, cancellation window, no-show fee. When both sides exchange those fields directly, a booking that might take several calls becomes one request and one confirmation.

A booking, step by step

Illustrative:

  1. A customer’s agent asks a garage’s agent for an oil change and tyre rotation for a named vehicle next Tuesday morning.
  2. The garage’s agent returns two open slots, the estimated duration and the cancellation policy.
  3. The customer’s agent books one and gets back a confirmation with a booking reference.
  4. The day before, the garage’s agent sends a reminder to the customer’s agent, which can confirm or move the booking without a call.

Top use cases

Use case Who talks to whom Notes
Appointment booking Customer agent and business agent Availability, booking, rescheduling, cancellation
Restaurant reservations Diner agent and restaurant agent Party size, time, special requests
Home services quotes Homeowner agent and trade agent Photos, measurements, visit windows
Pharmacy refills and lab scheduling Patient agent and pharmacy or lab agent Refills and specimen collection times
Meeting scheduling Assistant agents on each side Consultations and follow-ups

Regulatory considerations

The rules that touch small-business booking are mostly about calls, messages and personal information. Checked on 26 September 2026. This is not legal advice.

United States

  • AI voices are “artificial” (FCC). In February 2024 the FCC ruled that calls using AI-generated voices are artificial under the Telephone Consumer Protection Act, which restricts certain calls made with artificial or prerecorded voices.
  • Revoking consent. Rules the FCC adopted in 2024 say consumers can revoke consent to robocalls and robotexts by any reasonable means, and callers must honor revocation within a reasonable time of no more than ten business days. The provision that would make one revocation apply to all of a caller’s unrelated robocalls and robotexts, 47 CFR 64.1200(a)(10), has been delayed twice; FCC Order DA 26-12 of 6 January 2026 moved it to 31 January 2027.
  • Health information. HHS describes a business associate as a person or organization that creates, receives, maintains or transmits protected health information for a covered entity. A booking vendor handling a clinic’s patient information generally fits that description, which requires an agreement limiting how the vendor uses it.

Canada

  • Appointment messages (CASL). Canada’s Anti-Spam Legislation exempts messages that solely facilitate, complete or confirm a transaction the recipient already agreed to, or that provide a requested quote, from the consent requirement. The identification and unsubscribe requirements still apply.
  • Automated calls (CRTC). Under the Unsolicited Telecommunications Rules, telemarketers may make solicitation calls with an automatic dialing-announcing device only with the consumer’s prior express consent, and the telemarketer must be able to prove it.
  • Rules under review. CRTC 2026-132 (11 June 2026) opened a review of those rules and asks whether the current definition of an automatic dialing-announcing device captures software that uses synthesized or AI-generated voices. Interventions were due 27 July 2026 and replies 11 August 2026, and no decision had been published when checked.
  • Privacy. PIPEDA applies to small businesses’ commercial activity except where a substantially similar provincial law applies instead: Alberta’s and British Columbia’s Personal Information Protection Acts, Québec’s private-sector act, and provincial health laws for health custodians such as Ontario clinics. Québec’s section 12.1 requires notice when a decision is based exclusively on automated processing, which could include an automated refusal of a booking. Bill C-36, introduced on 15 June 2026 to replace Part 1 of PIPEDA, is at second reading.

Where to start

  1. Publish availability, read-only. Open slots by service and staff member are the first thing every booking conversation needs.
  2. Take bookings as fields, with a confirmation. Service, time, name, contact and any intake questions, then a confirmation both sides keep.
  3. State the policy in the answer. Deposits, cancellation windows and no-show fees belong in the structured response, so the customer’s agent can show them before it books.
  4. Know which agent is booking. Check which provider’s agent is calling and whom it represents before holding a slot, and rate-limit so automated traffic can’t block the calendar.
  5. Keep a person on the phone for everyone else. People will keep calling. Making your customer service agent-ready walks through the setup in order.

Questions

Does a small business need its own AI agent to accept bookings from people's agents?
Not necessarily. The business needs an endpoint that answers structured requests for availability and bookings. That endpoint can sit in front of the booking software it already uses, which already holds the calendar and the rules.
Can a business stop automated booking calls from Google?
Google's Business Profile help page says a business can ask Google to stop during a call, switch off the relevant setting in its Business Profile, or reply STOP to texts.

Sources

  1. Google Business Profile Help: About automated calls and texts from Google to your business (accessed )
  2. RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar) (accessed )
  3. HL7 FHIR R4: Appointment resource (accessed )
  4. FCC: FCC Makes AI-Generated Voices in Robocalls Illegal (8 February 2024) (accessed )
  5. Federal Register: Strengthening the Ability of Consumers To Stop Robocalls (5 March 2024) (accessed )
  6. FCC Order DA 26-12 (6 January 2026), extension of the effective date of 47 CFR 64.1200(a)(10) (accessed )
  7. HHS OCR: Business Associates (accessed )
  8. Justice Laws: Canada's Anti-Spam Legislation, S.C. 2010, c. 23 (section 6) (accessed )
  9. CRTC: Key Unsolicited Telecommunications Rules (accessed )
  10. Compliance and Enforcement Notice of Consultation CRTC 2026-132: Review of the Unsolicited Telecommunications Rules (accessed )
  11. OPC: Provincial laws that may apply instead of PIPEDA (accessed )
  12. LégisQuébec: Act respecting the protection of personal information in the private sector (section 12.1) (accessed )
  13. LEGISinfo: Bill C-36 (45-1), Protecting Privacy and Consumer Data Act (accessed )