VAPI · IN DEVELOPMENT · early access

Vapi callbacks, automated.

Same callback layer we built for Retell — adapted for Vapi's webhook + Calls API shape. Sub-processor list, encryption posture, retry policy, and TCPA defaults all carry over. Early access while we close on parity.

STATUS In development PROVIDER vapi.ai ↗ EARLY ACCESS via /contact

Same engine, Vapi-shaped. The scheduling, retry, quiet-hours, and PII-encryption machinery is provider-agnostic. We're building the Vapi adapter (webhook ingest + outbound call API) on top of it. Early-access slots open as we close on parity with the live Retell flow.

EARLY ACCESS Get on the list The Vapi adapter is the next provider on our build list. Drop your name and we'll bring you in as soon as the integration is ready. Open contact HOW IT WORKS Read the Retell guide Vapi will follow the same pattern. The Retell guide is the easiest way to understand what we'll do for you. Open docs

WHY REDIALER.IO · for Vapi

Your Vapi agent handles the call. We handle the callback.

Vapi is great at the call. Scheduling a reliable callback when your agent promises one — webhook ingestion, time-zone math, retry policy across providers, audit logs, quiet hours, consent-aware exemptions — is a separate system. We are that system.

Same encryption: Every PII field (phone numbers, dynamic variables, metadata, captured call payloads) is encrypted at rest with AES-256-GCM under a per-tenant key wrapped in HashiCorp Vault. Vapi never sees plaintext from us; we never see plaintext after the first decrypt.
Same retry logic: Voicemail / no-answer / busy / technical-error / inactivity groups each with their own toggle + delay. Per-workspace tuning. Per-agent overrides on Pro and Scale. Quiet-hours shift retries forward; explicit caller requests are exempt under TCPA's consent carve-out.
Same dashboard: Dashboard, agents page, activity feed, audit log, REST API — all provider-agnostic. Switch between Vapi and any other connected workspace from the topbar without losing context.
Same compliance posture: TCPA-friendly defaults (no automated calls 19:00–10:00 local). 24h soft-delete grace on workspace disconnects. 30-day data export window on cancellation. Audit log on every mutation.

HOW IT WIRES · Vapi side

What you do in Vapi.

When Vapi support lands, the steps will mirror the existing Retell flow with provider-specific field names. Sketch below; the live version will live in /docs.

01
Paste your Vapi API key

In our setup flow, paste a Vapi API key with read access to your agents and permission to use the Calls API. We encrypt it at rest with your tenant DEK; it never lives in app memory longer than a single decrypt operation.
02
Paste our webhook URL into your agent

For each agent you connect we mint a unique webhook URL of the form https://redialer.io/api/webhooks/vapi/wh_…. Drop it into your Vapi agent's Server URL. One URL per agent. Rotatable any time with a 24h grace window.
03
Add one Boolean to your post-call extraction

We watch for a single Boolean named redialer.io_callback in the post-call analysis output. When your agent flips it to true after a caller asks for a callback, we extract the requested time from the transcript tail and schedule the redial — respecting your quiet hours and retry policy.

Voicemail, no-answer, busy, and technical-error retries are handled separately from the operator-facing Boolean. They're driven by Vapi's disconnection_reason (or the provider's equivalent field), so your agent doesn't need any extra prompting for them.

EARLY ACCESS · Vapi

Get notified when Vapi support lands.

The Vapi adapter is the next provider on our build list. Drop your name and we'll bring you in as soon as the integration is ready. Your interest helps us prioritize which provider integrates next.

Reach out via contact or skim the Retell guide