Redialer · Built for Retell · Voice & SMS chat agents · Vapi & Bland coming soon

Voice & SMS callbacks,
automated.

Your Retell agent handles the conversation — voice call or SMS chat. redialer.io handles the callback. When your agent promises to follow up, we schedule it and place the outbound call (or send the outbound SMS) at the requested time — automatically, on time, every time.

LIVE · 3 AGENTS REDIALING · 247 CALLBACKS THIS WEEK
Retell ships callbacks as a DIY assignment

Building callbacks is the project.
Using redialer.io is three steps.

Retell handles the call. What it doesn't do is call someone back at a future time. Building that yourself is custom webhooks, scheduling, retries, timezone math, and persistence. Or you point redialer.io at your agent — three steps, done.

Build it yourself build once, maintain forever
0+ things you'd own
  • A new service in your codebase to own
  • A real backend service to design, ship, and run
  • Architecture you'd have to design from scratch
  • A system that knows when to call each person back
  • State that holds every callback from request to delivery
  • Time zones, DST, and quiet hours to get right
  • Visibility across every callback in flight
  • A way for your team to manage scheduled calls
  • Logic for the dials that don't connect cleanly
  • A path for forwarding events to your existing tools
  • Other headaches of building it
Use redialer.io ~5 minutes per agent
0 things to wire
  • Paste your Retell API key read-only
  • Paste our webhook URL into your Retell agent
  • Add one Boolean to Post-Call Extraction
+ your automations keep working

Already piping Retell events somewhere? Drop your existing webhook URL into redialer.io and we'll forward every payload there — same structure, your fields untouched. We add a few of our own alongside (attempt number, chain context) but never modify or drop yours. Plug us in without rewriting anything downstream.

Setup · ~5 minutes per agent

Three things to wire up.
Two more — only if you want them.

Required · 3 steps Without these, nothing fires.
  1. 1

    Paste your Retell API key

    Read-only. We use it to list your agents so you can pick which one to wire up. We never write back to your Retell account.

    retell_… · read-only
  2. 2

    Paste our webhook URL into your Retell agent

    We generate one URL per agent. You drop it into the agent's webhook field in the Retell dashboard. That's how we receive call events.

    https://redialer.io/hooks/agent_…
  3. 3

    Add one Boolean to Post-Call Extraction

    Your Retell agent flips it true when a caller asks for a callback. That's our signal to schedule the redial.

    redialer.io_callback : boolean
Optional · Polish · 2 steps Skip these and we still work.
  1. 4

    Forward call events to your own webhook

    So your downstream systems — CRM, Slack, internal flows — get the same call data we receive. Pass-through only; we don't change anything you send.

    your-webhook.example.com
  2. 5

    Add the callback-time prompt snippet

    So your agent captures callback times consistently — E.164 phone numbers, ISO timestamps, global callers. We provide the snippet; you paste it into your agent prompt.

    prompt snippet · global
~5 min per agent 0 writes to your Retell account cancel anytime from Settings
How redialer works · start to finish in four events

Marcus calls at 8:42 PM.
He gets called back at 10 AM tomorrow.

R Retell agent · 8:42 PM

Caller asks to be called back at 10 AM tomorrow.

Marcus calls into your Retell agent after-hours. Your agent listens, captures the requested time, and ends the call gracefully. Post-Call Extraction runs immediately.

caller=+1 306•••2014 requested=10:00 AM PT duration=1m 12s
R Retell agent · 8:42 PM · Post-call extraction

Your agent flips one Boolean. That's it.

You add a single Post-Call Extraction variable to your Retell agent: redialer.io_callback. Your agent sets it to true when a caller asks for a callback. Nothing else changes about your setup.

redialer.io_callback=true agent=A_8f3c…d12a
Redialer · 8:42 PM · Webhook

Redialer schedules the dial-back — timezone aware.

Retell fires its Post-Call webhook to a URL we generate for that specific agent. We compute the correct dial-back time (timezone, DST, business hours, quiet hours) and queue the outbound call.

webhook=200 OK scheduled=10:00 AM PT tz=America/Vancouver
Redialer · 10:00 AM tomorrow · Outbound dial

Marcus' phone rings. Your agent picks up where it left off.

At 10:00 AM, Redialer fires the outbound call through your same Retell agent. Marcus answers — your agent is already on the line, with the original conversation context.

ring=9.8s connected=true ✓ duration=3m 41s
The deal

Read-only. We never modify your Retell account.

Redialer uses your Retell API key to read your agents — names, IDs, and configuration metadata — so we can show you which agents are wired up and which still need a Boolean field. We don't write anything back. The Boolean and the webhook URL — those you add yourself. That's the deal.

  • Your API key is encrypted at rest and only used to list and read agent metadata.
  • No writes to prompts, tools, voices, custom functions, or any agent setting.
  • You can rotate or disconnect your key at any time from Settings — we drop all derived state.
  • Webhook deliveries are signature-verified. Per-agent webhook URLs, never shared.
Read the full security note