AI Voice Agent + Square: Salon Bookings, Restaurant Orders, and KDS Integration

Square's 2026 announcements delivered three things voice teams can use immediately: AI-powered voice ordering, salon-onboarding automation, and tighter Bookings/Orders/Catalog APIs. CallSphere's Salon GlamBook deployment runs on this exact stack.

What the integration unlocks

flowchart TD
  Client[MCP client · Claude Desktop] --> MCP[MCP server]
  MCP --> Tool1[Tool: Calendar]
  MCP --> Tool2[Tool: CRM]
  MCP --> Tool3[Tool: KB search]
  Tool1 --> SaaS1[(Calendly)]
  Tool2 --> SaaS2[(Salesforce)]
  Tool3 --> SaaS3[(Notion)]

For a salon: a stylist's regular calls in. CallSphere's voice agent looks them up by phone in Square Customers, sees their last service was a balayage 8 weeks ago, offers the same with their preferred stylist Tuesday at 11. Customer confirms. The booking creates a Square Booking, charges the deposit via Square's terminal API, and the stylist's calendar is updated before the customer hangs up.

For a restaurant: order calls drop in at peak. The voice agent confirms items, modifiers, and pickup time. The order posts to the Square Orders API; KDS prints in the kitchen; the customer's card is pre-authorized via Square Payments. Zero double-entry.

How the Square API exposes it

Three core surfaces. (1) Bookings API — POST /v2/bookings, POST /v2/bookings/availability/search, PUT /v2/bookings/{booking_id}. (2) Orders API — POST /v2/orders, POST /v2/orders/{order_id}/pay, PUT /v2/orders/{order_id}. (3) Catalog API — POST /v2/catalog/list, POST /v2/catalog/search-catalog-items for menu/service lookup.

Auth: OAuth 2.1 with PKCE for multi-tenant; MERCHANT_PROFILE_READ, APPOINTMENTS_WRITE, ORDERS_WRITE, PAYMENTS_WRITE, and ITEMS_READ scopes. Webhooks: booking.created, order.updated, payment.updated.

How CallSphere implements it

CallSphere's Salon GlamBook deployment integrates Square Bookings + Payments natively. The voice agent runs Catalog search at session start to load services, prices, and durations into context. Booking writes go straight into Square; reschedule and cancellation tools are wired one-to-one to Square endpoints. Restaurant deployments (early access) use the Orders API plus a kitchen display routing tool. CallSphere's healthcare vertical does not use Square but the Salon and Restaurant patterns ship today.

Explore a live demo and compare current plans to find the right fit for your business.

Build steps

1. Register a Square app in the Developer Dashboard. Pick OAuth (multi-tenant) over personal access tokens.
2. Implement the OAuth 2.1 + PKCE flow. Store refresh tokens encrypted; rotate every 30 days.
3. At CallSphere tenant onboarding, pull the merchant's Catalog (services or menu items). Cache in Postgres for 5 minutes; refresh on catalog.version.updated webhook.
4. For salons: implement get_available_slots calling bookings/availability/search filtered by team member and service. Implement schedule_appointment calling POST /v2/bookings.
5. For restaurants: implement create_order calling POST /v2/orders with line items, modifiers, and pickup time. Pay via POST /v2/orders/{id}/pay with a saved card or Square Terminal device ID.
6. Subscribe to booking.updated and order.updated webhooks so out-of-band staff edits propagate back into the voice agent's session memory.
7. Set explicit timeouts (3s soft, 6s hard) on Square calls; fall back to "I will text you the link" if Square is slow.

Code snippet

// Create a Square salon booking from CallSphere voice
const booking = await fetch("https://connect.squareup.com/v2/bookings", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${squareAccessToken}`,
    "Content-Type": "application/json",
    "Square-Version": "2026-04-15",
  },
  body: JSON.stringify({
    booking: {
      start_at: chosenSlot.rfc3339,
      location_id: locationId,
      customer_id: caller.squareCustomerId,
      appointment_segments: [{
        duration_minutes: 75,
        service_variation_id: serviceId,
        team_member_id: stylistId,
        service_variation_version: serviceVersion,
      }],
      seller_note: "Booked by CallSphere voice agent",
    },
    idempotency_key: turn.callId,
  }),
});

FAQ

Does Square block AI agents from booking? No. Square's own AI Voice Ordering proves the stack supports it. Use idempotency keys on every write.

How do reschedules work? PUT /v2/bookings/{booking_id} with the new start_at. The voice agent confirms then writes; Square emails the customer.

Can the agent take payment over the phone? Yes via Card-on-File (source_id of a saved card) or via a Stripe Link Agent Wallet handoff for new cards. Avoid asking for PAN on a recorded call.

Does this work on Square for Restaurants? Yes. The Orders API plus the KDS routing rules cover the workflow. CallSphere is in early access with two restaurant pilots.

Explore a live demo and compare current plans to find the right fit for your business.

Sources

• Square API Documentation
• Square AI Voice Ordering
• New Square AI Agent Automates Daily Tasks - PYMNTS
• Square Bookings API