Back to workflows
SalesEnrich and routeSmall business

Missed call to booked visit

Identify the caller, understand the request, and prepare an available appointment for approval.

What this workflow does

Identify the caller, understand the request, and prepare an available appointment for approval. It resolves identity, enriches the case with approved evidence, and shows why the proposed route is appropriate before anything is assigned.

What you gain

Fewer valuable calls disappear after business hours.

What the AI agent changes

How this worked before

Rule-based routing handled only clean, predefined fields and broke when the request was incomplete or written in natural language.

What the AI agent changes

The agent can interpret unstructured context, gather missing evidence, explain its recommendation, and pause when confidence is low.

Agent trigger

A business call is missed or reaches voicemail.

Inputs

  • Process context: caller, voicemail, service area, service type, urgency, and calendar
  • Approved policies, ownership, and exception rules

Agent flow

  1. 1

    Resolve the case identity and validate source freshness.

  2. 2

    Enrich the case with approved context and show every scoring signal.

  3. 3

    Prepare a qualified callback or available appointment option with confidence and exceptions.

  4. 4

    Create the approved assignment and notify its owner.

Human decisions

After step 3

The accountable process owner approves a qualified callback or available appointment option.

Outcome

  • Approved callback task or booking
  • Evidence, exceptions, and audit trail

Guardrails

  • Do not route low-confidence identity matches automatically.
  • Use an allowlist of destinations and writable fields.

Risks and mitigations

A wrong identity match can send a case to the wrong owner.

Require deterministic identifiers and expose the routing rationale.

Sources and evidence