AI front desk for service businesses

Every customer gets a clear next step.

Chronicle handles calls and messages, keeps customer context close, books from your connected availability, and pauses exceptions for a person before taking the next step.

Explore capabilitiesSee plans
Illustrative example · Dental Clinic
Playbook →

Elena Rostova

+1 (415) 555-0142 · Inbound

On call
01:24
Intent:Emergency booking
Calendar:Cal.com
Customer

Hi, I have severe tooth pain and need an emergency visit tomorrow morning if possible.

Chronicle

I'm sorry you are in pain, Elena. I'm the AI assistant for BrightSmile Dental. Dr. Martinez has an emergency slot open tomorrow at 9:30 AM or 11:00 AM. Would 9:30 AM work best for you?

Customer

Yes, 9:30 AM is perfect. Thank you so much!

Appointment booked

Dr. Martinez · Tomorrow at 9:30 AM · SMS confirmation sent

01 / Core operations

Three core functions, one shared front desk.

Chronicle is built for service businesses that run on phone calls, messages across multiple channels, and calendar appointments. Every conversation informs the same customer record.

  • Voice channel

    Inbound calls & voice handling

    Answers customer calls using your connected phone provider, captures intent, and books appointments or prepares follow-up actions.

    • Connected provider integration

      Connect your existing business number through a supported telephony provider.

    • Conversational intake

      Greets callers, identifies the reason for calling, and collects required details naturally.

    • Call transcription & summary

      Calls are transcribed and summarized, with key details linked to chronology.

    • Warm transfer capability

      Route live calls to team members based on availability, urgency, or department rules.

    See lifecycle workflow
  • Multichannel

    Unified messaging & inbox triage

    Triage customer inquiries across SMS, WhatsApp, email, and live website chat in a single shared chronology thread.

    • One unified thread

      Customers can call today and text tomorrow; all history stays in the same continuous record.

    • WhatsApp & two-way SMS

      Handle inquiries on connected mobile channels using your business guidance and policy boundaries.

    • Email triage & drafted replies

      Ingests support and service emails, identifies intent, and drafts contextual replies ready for sign-off.

    • Built-in web chat widget

      Engages visitors directly on your website to answer questions and capture booking requests 24/7.

    See lifecycle workflow
  • Calendar write

    Supervised bookings & scheduling

    Checks live calendar availability, books appointments directly into Google Calendar or Cal.com, and pauses exceptions for human sign-off.

    • Direct calendar write

      Check available appointment slots and write confirmed bookings to a supported, connected calendar.

    • Your operating rules

      Use the services, opening hours, buffer times, and approval requirements configured for your workspace.

    • Self-serve rescheduling

      Customers can reschedule or cancel appointments within the boundaries and notice windows you define.

    • Policy notice

      Communicate cancellation policies and service prerequisites clearly before booking confirmation.

    See lifecycle workflow

Human approval gates cover all three channels

Configure approval checkpoints for work that needs a person. Your team can review the request, its context, and the prepared action before deciding what happens next.

Inspect approval gate

02 / Visible execution path

From hello to a next step you can see.

Chronicle keeps its prepared response, your team's decision, and the customer's context in the same record, so every step can be reviewed later.

Execution trace · five-step lifecycle

  1. 01

    Inbound contact

    Customer reaches out via phone call, SMS, WhatsApp, email, or chat.

  2. 02

    Context match

    Chronicle matches caller ID or address against customer records and history.

  3. 03

    Intent & rule check

    Analyzes the request against your configured services, hours, and booking rules.

  4. 04

    Human approval gate

    If the request is outside standard boundaries, it pauses for human sign-off.

  5. 05

    Action & record

    Books calendar, sends reply, or alerts team, then logs the chronology.

Human authority

Held for review

Holds sensitive or unusual work for the right person.

When a request falls outside the rules you configure, Chronicle keeps the context together and waits for a named approver.

Example checkpoint · Sarah Lin

Same-day shift < 24h → 4:30 PM slot

Provisional hold placed with Dr. Vance while awaiting operator sign-off.

Machine preparedHuman decides

03 / How Chronicle works

Every stage visible, every rule yours.

From the moment a customer contacts your front desk to the completed action, each stage follows the boundaries you set.

Stage 01 - Calls and messagesMeets customers on the channels you connect.

Chronicle answers incoming calls and messages when enabled, captures what each customer needs, and shows the context directly in your inbox.

  • Inbound calls
  • SMS inquiries
  • WhatsApp routing
  • Email triage
Stage 02 - Customer contextKeeps request, history, and booking state together.

Instead of starting from zero on every call, Chronicle surfaces past conversations, current bookings, and caller history in one continuous thread.

  • Caller history
  • Booking records
  • Previous notes
  • Thread summary
Stage 03 - Business rulesUses your services, opening hours, and policies.

You configure what Chronicle can answer and schedule, so routine inquiries get immediate, accurate answers while edge cases pause for your team.

  • Service catalog
  • Operating hours
  • Deposit rules
  • Custom playbook
Stage 04 - Human approval gatePauses sensitive work before anything leaves the front desk.

When a request falls outside standard rules, Chronicle drafts the proposed step, keeps all context attached, and waits for your sign-off before taking action.

  • Exceptions hold
  • Draft review
  • One-click approval
  • Audit trail
Stage 05 - Execution and chronologyBooks, replies, or hands over with the context intact.

Based on the access and rules you set, Chronicle confirms the next step or hands the conversation to your team, then saves the outcome in chronology.

  • Confirmed appointment
  • Customer reply
  • Human handoff
  • Saved chronology

04 / Who uses Chronicle

Built for owners, front desk teams, and operations.

Whether you run a single location or several, Chronicle follows the team structure and rules you set up.

Business owners

Front-desk coverage without giving up control.

  • Set the services, hours, tone, connected channels, and approval limits Chronicle should follow.
  • See calls, messages, bookings, and exceptions in the same workspace.
  • Pause new activity or keep selected decisions behind a human approval gate.
  • Use chronology to understand the conversation, decision, and confirmed next step.

Chronicle prepares repeatable work; your team remains responsible for exceptions.

  • Front desk availability24 / 7

    Inbound answering across phone, SMS, WhatsApp, and email.

  • Safety boundaryHuman gate

    Configurable approval gates for exceptions, refunds, and out-of-policy requests.

  • Core design philosophy

    Every conversation should leave the customer with an answer and the business with an accurate record.

    Chronicle operating principle

Next step

See what each plan includes.

Compare capacity, workflows, and organization controls, or review an organization rollout with our team.

Compare plansExplore Enterprise