Workforce Wave Workflows
Every conversation
triggers a workflow.
Automatically.
When a call ends, extracted data activates multi-step chains - CRM updates, confirmation SMS, calendar bookings, task creation - all without a human touching a keyboard.
The difference
Manual processes are why leads go cold.
Without Workforce Wave
With Workforce Wave
Extraction examples
Every call produces structured data.
The extraction layer reads the transcript and outputs typed JSON - ready for any downstream system without any parsing on your end.
Sample transcript
"Hi, I need to schedule an appointment for my knee pain. It started about a week ago and is getting worse. I have Blue Cross insurance. I can come in Thursday afternoon."
Extracted fields
Actions fired
- 1Email to front desk with extracted intake summary and urgency flag
- 2Calendar blocked for Thursday 1pm, 2pm, or 3pm pending confirmation
- 3SMS sent to caller with intake form link and appointment confirmation options
Trigger types
Four ways to start a workflow.
After call ends
The most common trigger. When the call disconnects, extraction runs and the workflow fires within seconds. No polling, no delay.
Mid-call (real-time tool)
The AI agent can call a workflow step during a live call - look up inventory, check availability, or fetch a customer record while the caller waits.
After SMS reply
When a contact replies to an outbound SMS, the reply triggers a workflow. Confirm appointments, collect intake answers, or re-engage lapsed leads via text.
On schedule (cron)
Run a workflow at a set time or on a recurring schedule. Daily summaries, weekly lead digests, monthly re-engagement campaigns - all automatic.
Action library
12 actions. More coming every sprint.
Mix and match these in any order to build the exact automation your business needs.
Real workflow examples
End-to-end flows, step by step.
Click any card to expand the full workflow. These run live in production for Workforce Wave customers today.
Everything included
Production-grade from day one.
No-code builder (coming soon)
Drag-and-drop workflow editor coming in Q3. Today, workflows are configured via dashboard forms and API.
Structured JSON outputs
Every conversation produces a typed JSON payload - caller name, intent, entities, urgency. Downstream systems get clean data.
Conditional logic
If-this-then-that branching based on extracted field values. Different paths for qualified vs. unqualified, urgent vs. routine.
Multi-step chains
Chain up to 20 actions per workflow. Each step can use outputs from prior steps - no separate orchestration layer needed.
Webhook in and out
Trigger workflows from external events via inbound webhook. Fire outbound webhooks to any URL as a workflow step.
Full audit log
Every workflow run is logged with inputs, step outputs, and errors. Searchable, exportable, and HIPAA-compliant.
Retry and dead-letter
Failed steps retry with exponential backoff. Permanently failed jobs land in a dead-letter queue for manual review.
Real-time and batch
Most workflows fire within seconds of the trigger. Batch mode for high-volume outbound campaigns with rate limiting.
How we compare
Why not just use Zapier?
Workflows are included in all Workforce Wave plans. Execution volume limits vary by tier - see pricing for details.
FAQ
Common questions
What triggers a workflow?
Workflows trigger after a call ends, during a call in real time when a specific intent is detected, when an inbound SMS reply arrives, or on a cron schedule. You assign a trigger when you create the workflow.
How does the extraction work - can it get things wrong?
Extraction uses a structured prompting layer on top of the transcript. For high-stakes fields like dates and names it performs a second-pass verification step. You can also flag specific fields as required - if the model is uncertain, it marks the field as null rather than guessing.
Can I see when a workflow fails?
Yes. Every workflow run appears in the audit log with status (succeeded, failed, retrying), timestamps for each step, and the exact error message if a step failed. You can replay any failed run manually from the log.
Does this replace Zapier or Make?
For conversation-triggered automations, yes - and it is simpler because the extraction is built in. For unrelated automations (e.g., syncing two SaaS tools that have nothing to do with calls or SMS), Zapier or Make are still the right tool. The two systems complement each other via the webhook action.
How many workflows can I have?
Unlimited workflow definitions on all plans. Execution volume is metered by the number of workflow runs per month, with generous limits on each tier. See the pricing page for the exact caps per plan.
Get started
Stop doing manually
what workflows do for free.
Every call already produces a transcript. Workflows turn that transcript into action - automatically, reliably, and without you lifting a finger.
Already a customer? Workflows are in your dashboard under Automation.