Interaction Mode 4 — Autonomous
The agent calls them. You don't queue it.
When a call ends, a form is submitted, or a prescription is ready, WFW agents initiate the follow-up call automatically — triggered by the event, not by a human adding a task to a list.
TCPA-compliant calling hours enforced by policy. Opt-out handled automatically.
85%
contact rate on same-day follow-up calls.
vs. 23% when the same call happens the next business day — manually. The window closes faster than your staff can open it.
Event → Policy → Call
What Breaks Without It
Follow-up calls that depend on humans don't happen.
Not because your team doesn't care — because the volume exceeds the bandwidth, every time.
Problem
Follow-up calls that never happen
Your staff intends to follow up after every appointment, every form fill, every procedure completion. In practice, it happens when there's time — which is rarely the same day.
Problem
Contact rate collapses after 24 hours
A lead who filled out a form at 11am and gets a callback at 10am the next day is half as likely to convert as one who gets called within the hour. The window closes fast.
Problem
Manual outbound doesn't scale with volume
Your recall list has 400 patients. Your front desk has 6 working hours. The math doesn't work — and the patients who don't get called don't rebook.
How It Works
Event fires. Policy clears. Call goes out.
The autonomous calling pipeline is deterministic: a triggering event, a policy check, an async initiation, and a webhook-delivered result. No human in the loop unless the policy routes it for review.
An event fires in the pipeline
Any event can trigger an autonomous call: call.completed (follow-up), a scheduled cron (recall batch), a form submission webhook, a status change in your PMS, or a custom event you define via the WFW Event API.
Policy evaluates whether to call
Before dialing, the policy layer checks: calling hours (TCPA compliance), opt-out status, existing scheduled callback, and any rate limits you've configured. If all checks pass, the call is queued.
POST /v2/calls fires (async 202)
The call is initiated asynchronously. Your system receives a 202 Accepted with a call_id immediately — the actual call connects in the background. No blocking, no timeout risk on your end.
Agent executes the task, result delivered via webhook
The agent completes its task — confirmation, reminder, lead qualification. When the call ends, call.completed fires with disposition, and call.extractions_ready delivers the structured outcome for your CRM or downstream flow.
Real Scenarios
What autonomous agents call about.
These are the follow-up calls your team means to make — and doesn't.
48 hours before every appointment, the WFW agent calls the patient to confirm. If they can't make it, it reschedules in real time and fills the slot from your waitlist. Staff sees the updated schedule — no manual effort required.
Your pharmacy integration fires an event when a prescription is filled. Within minutes, the patient receives a call from your practice's WFW agent: their prescription is ready, here are the pickup instructions. 100% same-day reach.
A prospect submits a contact form on your website at 2pm on a Saturday. Within 5 minutes, your WFW agent calls them, qualifies their interest, and books a consultation — before your office opens Monday.
4 hours after a car service is completed, the WFW agent calls the customer, confirms satisfaction, and invites a Google review. If they mention a problem, the call is flagged for manager review. Not 3 days later — that day.
API Surface
Trigger autonomous calls from anywhere.
Any system that can fire an HTTP request can trigger a WFW autonomous call — your CRM, your EHR, your n8n workflow, your custom application. The API is identical regardless of the trigger source.
POST /v2/calls returns a 202 Accepted immediately. Your system doesn't wait for the call to complete. When it does, the result arrives via webhook.
Full API reference →Relevant Endpoints
/v2/callsTrigger an outbound call. Async 202 response with call_id. Accepts task context and caller instructions.
/v2/calls/batchQueue a batch of outbound calls (recall lists, confirmation batches). Policy checks applied per call. (Coming in Sprint 9)
/v2/calls/{id}Check call status, disposition, and outcome for an initiated call.
/v2/webhooksRegister your endpoint to receive call.completed and call.extractions_ready events.
Compliance Built In
TCPA, opt-outs, and calling hours — handled by policy, not your code.
WFW autonomous calls run through a policy layer before every dial. You configure the rules once — the platform enforces them on every single call, automatically.
TCPA Calling Hours
Calls blocked outside 8am–9pm local time by default. Configurable per agent or per contact.
Opt-Out Enforcement
Any caller who says 'stop calling' or 'remove me' is flagged and suppressed immediately — no re-queue.
Consent Verification
API accepts a consent_given flag per call. Calls without verified consent are blocked at the policy layer.
Contact Rate Benchmark
85%
Same-day
WFW autonomous call
23%
Next-day
Manual staff follow-up
The contact rate gap between same-day and next-day follow-up is not marginal. For appointment confirmations, lead follow-up, and prescription alerts, timing is the entire variable.
Get Started
Let the event stream make the calls.
Connect your event source to POST /v2/calls. Receive results via webhook. The follow-up calls happen the same day — every time, for every customer.
TCPA compliance and opt-out management built in.