Skip to main content

Agent Recipes

Common multi-step workflows your agent can run. Each is 2 to 4 API calls in sequence. Copy the prompt into your agent; the endpoint sequence below it is what the agent should execute.

Recipe 1: Book a meeting from a missed call​

Prompt: "Find missed calls from today and text the callers a booking link."

  1. GET /api/v1/receptionists. Pick a receptionist.
  2. GET /api/v1/receptionists/:id/calls?direction=inbound&date_from=<today>
  3. Filter for outcome = no_answer or abandoned, extract the from phones.
  4. POST /api/v1/receptionists/:id/sms with an Idempotency-Key. Text each caller a booking link.
  5. When they reply (handled via the sms.received webhook on your side), update your CRM.

Valid call outcome values: completed, failed, abandoned, no_answer, busy, booked, handoff, unknown.

Recipe 2: Weekly revenue digest​

Prompt: "Summarize this week's call activity in 4 bullets."

  1. GET /api/v1/account. Plan and period stats.
  2. GET /api/v1/receptionists. Each active receptionist.
  3. GET /api/v1/receptionists/:id/calls?date_from=<7d ago> per receptionist (paginate).
  4. Aggregate: total calls, bookings, outbound SMS, minutes used. Format as prose.

Recipe 3: Nurture a stale lead​

Prompt: "Call back everyone who didn't answer last week."

  1. GET /api/v1/receptionists/:id/calls?date_from=<7d ago>
  2. Filter outcome = no_answer, deduplicate by from.
  3. POST /api/v1/receptionists/:id/calls with an Idempotency-Key, customer_name, purpose: "follow_up", and an optional system_prompt referencing the prior call.

Always pass an Idempotency-Key to prevent duplicate outreach on retry. Your agent is responsible for TCPA compliance on cold outbound at the REST layer: the MCP tool layer enforces prior-contact, REST does not. See TCPA rules for agents.

Recipe 4: Onboard a new customer​

Prompt: "Set up a new HVAC receptionist named 'Acme HVAC' with my Cal.com calendar."

  1. POST /api/v1/receptionists with an Idempotency-Key and a body like { "business_name": "Acme HVAC", "industry": "hvac" }.
  2. Poll GET /api/v1/receptionists/:id until status is active (typically 10-30 seconds).
  3. PATCH /api/v1/receptionists/:id with the calendar config.
  4. POST /api/v1/receptionists/:id/calls to a test number to verify.