Run a chatbot, voice, and phone agent that books appointments

Answers customer questions, tracks orders, and books calendar appointments across chat, voice, and phone.

How the work actually flows

It branches. Exactly one path is taken.

Pattern: Exclusive Choice (4) · Simple Merge (5)

flowchart TD trig>"customer sends message or call"]:::trig s0["receive customer request"]:::task s1["classify request type"]:::task s2["respond to customer"]:::task trig --> s0 s0 --> s1 gx{"× what is the request about"}:::gate s1 --> gx p00["check order tracking system"]:::task gx -->|"order status"| p00 p10["read requested date"]:::task gx -->|"appointment booking"| p10 p11["book calendar event"]:::task p10 --> p11 p20["search documents for answer"]:::task gx -->|"general question"| p20 jn{"○ send response"}:::gate p00 --> jn p11 --> jn p20 --> jn jn --> s2 out[/"question answered or appointment booked"/]:::out pay{{"consistent support across every channel"}}:::pay s2 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepOne path onlyPaths rejoinResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
AI Agents & Autonomous SystemsAI Chatbots & AssistantsVoice & PhoneKnowledge Base & RAGImage & Media ProcessingScheduling & CalendarFile & Cloud StorageCustomer Support & Ticketing
Connects
Google CalendarGoogle DriveOpenAIQdrant

The problem it solves

Customers want quick answers whether they're typing in a chat window, calling in, or leaving a voicemail, but staffing that across every channel is expensive and inconsistent. Booking appointments and answering the same product questions over and over also eats into time your team could spend elsewhere.

Who it fits

Customer support teams or service businesses that field questions and bookings across chat, voice, and phone.

How it works

  1. A customer sends a message or call through chat, voice, or phone
  2. The request is routed based on what it's about: order status, booking, or a general question
  3. For orders, the system checks status through an order tracking system
  4. For appointments, AI reads the requested date and books it in Google Calendar
  5. For general questions, AI searches your documents and answers using what it finds
What you get

Customers answered on whichever channel they pick

You get a chat, voice, and phone assistant that answers questions, tracks orders, and books appointments across every channel your customers use.

What you get

An automatic response to the customer, plus a booked calendar event or order status when relevant.

What you need

A conversational AI platform, Google Calendar, an OpenAI API key, and a vector database for document search.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook