AI AGENTS
Nightly batch: convert the day's resolved tickets into a callback voicemail run
On a schedule, reads all of the day's resolved support threads from Postgres, generates one spoken follow-up script per customer with ElevenLabs.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule after end of business
- ActionQuery Postgres for tickets resolved in last 24hPostgres
- LogicDedupe by customer, drop callback opt-outs
- ActionAgent drafts one follow-up script per customer
- ActionBatch-render scripts to audioElevenLabs
- OutputWrite deduped voicemail batch into callback queuePostgres
What it does
Runs once a night to sweep every conversation resolved that day, produce a personalized callback voicemail for each unique customer, and stage the whole batch for the morning calling shift — one customer, one voicemail, no duplicates.
When to use it
For higher-volume teams who prefer a single predictable nightly run over per-ticket triggers. It gives the calling team a clean, ready-to-dial list each morning with audio already rendered.
How it works
- 1A schedule fires after end of business.
- 2The flow queries Postgres for conversations resolved in the last 24 hours.
- 3A logic step dedupes by customer and drops opt-outs, keeping the most recent thread per person.
- 4For each, the agent writes a concise spoken follow-up script.
- 5ElevenLabs renders each script to audio in batch.
- 6The voicemails are written into the callback_queue table dated for the next morning, forming the day's run.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect ElevenLabsText-to-speech, voice cloning.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.