CHATBOTS

After-hours voice IVR with morning callback queue

Lets the ElevenLabs voice agent answer FAQs around the clock, and for calls received outside business hours that need a human.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerwebhook
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerElevenLabs posts call-ended webhookElevenLabsElevenLabs
  • LogicBranch on business hours vs after hours
  • ActionInsert callback request into Postgres queuePostgreSQLPostgres
  • OutputPost pending callback queue to Slack at openSlack

What it does

Keeps your voice line useful overnight: the ElevenLabs agent resolves what it can, and anything needing a person is captured as a callback request rather than dumped to voicemail. The next morning the queue surfaces to your team with full context.

When to use it

Use it when you don't staff phones 24/7 but don't want after-hours callers to churn. The bot deflects routine questions immediately and turns the rest into a tidy, prioritized callback list instead of a pile of voicemails.

How it works

  1. 1The ElevenLabs agent ends a call and posts the transcript plus a needs-human flag via webhook.
  2. 2The flow branches on local business hours.
  3. 3During hours, unresolved calls route straight to a live Zendesk-style escalation path; after hours they take the callback path.
  4. 4After-hours callbacks are inserted into a Postgres queue table with caller number, summary, and priority.
  5. 5At the start of the next business day a Slack message posts the pending callback queue to the support channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ElevenLabsText-to-speech, voice cloning.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.