Choose
Pick a supported use case and name the playbook. Handshake owns the approved call configuration.
AI-powered outreach for insurance teams
Every conversation should lead somewhere human.
Handshake turns carefully planned playbooks into compliant, AI-guided conversations—and qualified interest into a verified warm handoff. Start with CSV, or connect your systems through scoped API keys and signed webhooks.
Purpose-built for controlled, reviewable outreach
Conversation live02:14
AI
Handshake agent
“I can connect you with Maya now. She already has the details we discussed.”
M
ConnectedWarm transfer readyMaya Chen · Licensed advisor
One clear path
Draft. Prepare. Start calling.
No preflight maze or separate approval step. Handshake gives operations teams one place to see what is ready, what is blocked, and exactly what needs attention.
Connect
Send current customer and policy events from your system. Handshake maps them to the matching playbook.
Run
Each enrollment revalidates source state, permission, routing, and suppression before a call is placed.
Purpose-built conversations
Start with the reason for the call.
Each available use case has server-owned context, disclosure, and conversation boundaries. Additional informational and triggered workflows remain visible in the workspace as they are developed.
Claim status update
Share a factual update about an existing claim.
Missing document request
Request documents for an existing policy, claim, or transaction.
Appointment reminder
Remind a customer about an appointment already scheduled.
Coverage review
Discuss a coverage opportunity and offer a licensed handoff.
Renewal outreach
Invite an existing customer to review an upcoming renewal.
Meet your systems where they are
One readiness model, however customers arrive.
Mapped imports and API events feed the same enrollment model. Handshake validates source state, permission, routing, suppression, and provider readiness before delivery.
Mapped imports
Use a guided mapping for one-time and early-stage data while keeping source identifiers intact.
Integration API
Send idempotent customer events from your CRM or agency system. Newer state supersedes older state explicitly.
Signed events
Receive durable lifecycle and outcome webhooks with bounded retries, delivery health, and one-time signing secrets.
Version 1
Read the API docs Build against a small, explicit playbook API.
Create a playbook, send customer events, inspect structured enrollment blockers, and let Handshake schedule only ready deliveries. No inferred routing or partial event ingestion.
Guardrails before growth
Automation your team can answer for.
Every playbook runs through explicit controls before a call is placed. If a required provider, credential, or safety check fails, Handshake stops and tells you why.
- Agency approval before activation
- Pre-dial eligibility checks
- Organization-level suppression
- No transcript or call recording stored
playbook readiness4 / 4
Customer list loaded 2,418 valid
Permissions matched Current
Call routes ready 12 members
Calling services ready Verified
Ready to launchReview playbook
Make outreach feel personal again