Automated Voiceflow Escalation Alerts
Every hour, WebRun opens Voiceflow, reviews recent transcripts from your conversational agent, flags any marked unresolved or handed off for a human, posts the conversation summary to Slack, and mirrors anything still unclaimed to Telegram so support never misses a handoff.
How do I get alerted when a Voiceflow conversation needs a human?
WebRun reviews your Voiceflow agent's transcripts every hour, flags conversations marked unresolved or handed off for a human, and posts the user's question and the bot's last response to Slack. If an escalation sits unclaimed for 15 minutes it mirrors to Telegram too, so a stuck customer conversation never waits on someone noticing a busy channel.
- Escalated conversations reach a human within the hour, not the next day
- Unclaimed handoffs get a second alert instead of going quiet
- Every escalation includes the full context, not just a link
Built for Customer support teams · chatbot operators · product support leads · small support teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
creator.voiceflow.comin a real browser with your saved login - no setup, no API keys. -
1
Voiceflow - check transcripts for escalations
WebRun checks transcripts for escalations in Voiceflow. - Open the transcripts view for your agent
- Filter to conversations marked unresolved or escalated
- Capture the user's question and where the bot got stuck
Done when Every escalated conversation from the window is captured.
-
2
Slack - post the escalation summary
WebRun posts the escalation summary in Slack. - Post each escalated conversation to the support channel
- Include the user's question and the bot's last response
- Tag whoever is on support duty
Done when Every escalation is posted to Slack for a human to pick up.
-
3
Telegram - mirror unclaimed handoffs
WebRun mirrors unclaimed handoffs to Telegram. - Mirror any escalation still unclaimed after 15 minutes to Telegram
- Keep the message short: the question and how long it's waited
- Stay quiet once a Slack reply claims it
Done when Telegram only pings for escalations nobody has picked up yet.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it reply to the customer for me?
No. WebRun only surfaces the escalated conversation to your team. Replying to the customer stays a human step, wherever you handle support.
What counts as escalated?
Any conversation Voiceflow marks unresolved or hands off for a human, based on how you've configured the agent.
What if support already replied in Slack?
It's treated as claimed and the Telegram mirror never fires for that conversation.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.