When your trading bot spots something real, your phone rings.
A Slack ping from your bot at 3 AM either wakes you up when it shouldn’t, or doesn’t wake you up when it should. AgentPing is the escalation layer that calls you only when it actually matters.
Voice call with retries, critical-severity bypass for quiet hours, DTMF acknowledgement. One API call from your bot.
Why voice for a trading bot
For a trading system, a missed alert is directional loss.
Voice-first
A phone call, not another Slack ping
Chat apps batch, mute, and swipe. A trading halt or drawdown breach belongs on your phone — loud, interruptive, impossible to miss.
Severity-aware
Critical alerts bypass quiet hours
Ambient fills and PnL snapshots stay in chat. Real incidents — halts, risk breaches, stale data feeds — ring through at 3 AM. You decide what's which.
Acknowledge from the keypad
Halt, resume, or snooze without a laptop
Press 0 to acknowledge, 1 to snooze 5 minutes, or enter a custom snooze up to 120 minutes. Your bot knows the outcome and acts on it.
What gets escalated
Halts, anomalies, and risk limits — not heartbeats and fills.
Three buckets: ambient events go to a dashboard, informational events go to chat, escalation events ring your phone. You decide what crosses each threshold.
Bot halted
“Exchange API returning 5xx on order placement for 4 minutes. Strategy paused.”
Anomaly needs judgment
“Slippage 3σ above expected on BTC/USD. Position opened 40% larger than model target.”
Drawdown breach
“Daily drawdown crossed -2.5%. Live strategies disabled, pending manual review.”
Data feed stale
“Market data stream frozen for 90 seconds. Bot refusing to trade on stale book.”
Opportunity window
“Funding rate divergence on ETH perps exceeded threshold — human confirmation before entry.”
Silence fallback
“Posted in chat 15 minutes ago, no acknowledgement. Escalating to phone.”
One API call
Wire escalation into your strategy in three lines.
Send a message and a severity. AgentPing handles delivery, retries, quiet-hour policy, and keypad acknowledgement — so your bot gets the outcome and can act on it.
pip install agentping-sdknpm install agentping-sdkcurl -X POST api.agentping.me/v1/alertsBridge from any existing alerting pipelinefrom agentping import AgentPingClient
client = AgentPingClient(api_key="ap_sk_...")
# Wake me up — exchange halted
client.send_alert(
title="Bot halted",
message="Exchange API 5xx on order placement "
"for 4 minutes. Strategy paused.",
severity="critical",
)Your phone rings. Press 0 to acknowledge — your bot sees the ack and can resume, halt, or wait for you to reach a laptop.
Pricing
Start free. Scale when your bot runs hotter.
A well-tuned bot usually fires a handful of escalations per week. Free plan is enough to validate the workflow; Starter covers most solo setups.
Starter
Most popular$9/mo
300 alerts / month
120 call minutes
3 verified phones
5 retries per alert
All plans include voice calls, keypad acknowledgement, quiet hours, and full API access. Compare plans in detail
Further reading
Why traders end up on voice escalation
A longer walk-through of the three-bucket severity model, the four escalation patterns traders use in practice, and why sleep is the real benefit.
Read: Your Trading Bot Shouldn’t DM You at 3 AMTry it now
Your bot already knows. Make sure the signal reaches you.
Create a free account, verify your phone number, and test the full call flow in under two minutes. No credit card required.