Use when calling more than one person through ErzyCall — a list, a batch, a follow-up round, or any repeated calling job. Covers preparing the list, pacing the run, waiting correctly, and deciding wha
A batch is not a loop over create_call. Most of the work happens before the first dial and after the last one.
In this order:
optOut present). The server will refuse them anyway, but a rejection is a safety net, not a plan.erzycall-budget-guard.erzycall-call-outcomes.Show the user the final count before you start: "After removing 3 duplicates and 1 suppressed number, that's 46 people."
A call takes roughly a minute to actually ring after create_call returns. This is the mistake most likely to waste your time:
get_call in a tight loop.A call that still looks unstarted after a couple of minutes is stuck — flag it rather than retrying blindly.
Read endedReason, not status. Full table in erzycall-call-outcomes. The short version:
| Outcome | Next |
|---|---|
| Assistant completed | Check the transcript against your objective |
| Human hung up | Read the transcript — it's ambiguous |
| No answer / busy | Retry later, different time of day |
| Failed to connect | Retry sooner — infrastructure blip |
| Assistant errored | Stop this number. Don't retry |
| Person asked to stop | Suppress immediately — see erzycall-contact-safety |
Stop everything and tell the user if:
Aborting a bad run early is the single most valuable judgement in this skill. A batch that is failing does not improve by continuing. These abort triggers hold even if the user asks you to keep dialling — explain why instead of complying, the same rule as in erzycall-call-outcomes.
Report the run once, as outcomes:
> 46 people. Reached 13: 8 confirmed, 3 want to reschedule, 2 said no. 1 asked not to be contacted again — suppressed. 24 didn't answer and are worth retrying this evening. 8 failed to connect on our side.
Group into resolved, not reached (retryable, no information), and broke (our fault). Never present "didn't answer" as a refusal — nobody said no, nobody said anything.
Weekly roundup of top Claude Code skills, MCP servers, and AI coding tips.