Pilot ready Template ready outbound

Service window / arrival

Field and home services: arrival window updates for customers who already booked.

service_window_consented

One of our most popular starters—not the only shape we support. For production, we customize the agent (open, intents, tools, guardrails, CRM hooks) to your exact specifications.

Sample open

Hello, this is an AI assistant calling about your scheduled service visit. I can share the arrival window, note a change request, opt you out of these calls, or have someone call you back.

Identity required: yes
AI disclosure: yes
Paid-for-by flag: no

Lawful basis tags

{
  "type": "CONSENT_PEC",
  "consentArtifactRequired": true,
  "consentMustCover": [
    "artificial_or_prerecorded_voice",
    "ai_generated_voice",
    "voice_calls",
    "service_scheduling_updates"
  ]
}

Agent

{
  "intentsAllowed": [
    "confirm_window",
    "request_reschedule",
    "gate_code_parking"
  ],
  "intentsBlocked": [
    "upsell",
    "billing_collections",
    "new_sales"
  ],
  "tools": [
    "opt_out",
    "escalate_human",
    "end_call"
  ]
}

Destinations & frequency

Classes: wireless, residential_landline

Purpose: service_window_update · Default enabled on seed: no (enable in Campaigns)

{
  "maxAttemptsPerNumberPer30d": 8,
  "minHoursBetweenAttempts": 4
}

Customize to your program

Opens, disclosures, intents, tools, CRM fields, and escalation rules are configured to your scripts and ops process. If your use case isn’t listed, we still build it—starters are shortcuts, not a ceiling.

→ Dispatch / ETA data available to the agent when you pilot
→ Staff callback path when the customer needs to reschedule
→ Purpose-bound script only — no upsell spray
→ You own lists/consent (outbound) or knowledge + recording policy (inbound)

Open campaigns Start a pilot Product