Automatic StreamElements Redemption Queue
Every few minutes while you are live, WebRun opens StreamElements, reads the loyalty store for redemptions still waiting to be delivered, notes the viewer, the item and how long it has been pending, texts your moderator through Twilio when something has waited too long, and keeps a running fulfilment queue in Microsoft Teams.
How do I keep loyalty point redemptions fulfilled during a live stream?
WebRun keeps your StreamElements loyalty store moving while you are live. Every few minutes it reads pending redemptions with the viewer, item and waiting time, texts your moderator through Twilio when one waits too long, and keeps the fulfilment queue posted in Microsoft Teams for the crew.
- Viewers get what they redeemed in the same session
- Moderators are told the moment something waits too long
- The crew sees one live queue instead of refreshing a dashboard
Built for streamers · stream moderators · esports teams · creator support crews
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
streamelements.comin a real browser with your saved login - no setup, no API keys. -
1
StreamElements - read pending store redemptions
WebRun opens StreamElements to read pending store redemptions. - Open StreamElements and go to the loyalty store redemption list
- Collect redemptions still marked pending with the viewer name and item
- Note how long each one has been waiting and the points spent
- Check the chat bot is responding so redemptions can still be made
- Do not approve, complete or refund a redemption. Fulfilment stays with a moderator
Done when Every pending redemption is listed with its viewer, item and waiting time.
-
2
Twilio - text the moderator on duty
WebRun opens Twilio to text the moderator on duty. - Text the moderator on duty when a redemption has waited past your limit
- Include the viewer, the item and the minutes waiting in the message
- Send at most one text per cycle so a busy stream does not spam the phone
- Only message your own moderator numbers, never a viewer
Done when The moderator has been told about anything waiting too long.
-
3
Microsoft Teams - keep the fulfilment queue visible
WebRun opens Microsoft Teams to keep the fulfilment queue visible. - Post the current fulfilment queue to your stream crew channel in Microsoft Teams
- List oldest pending redemptions first with the viewer and item
- Update the running message rather than starting a new thread every few minutes
- Note when the queue is empty so the crew knows it is clear
Done when The crew channel shows the live fulfilment queue.
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 mark redemptions as fulfilled by itself?
No. WebRun only reads the pending list and shows it to your crew. Approving, completing or refunding a redemption is always done by a moderator in StreamElements.
Does it message viewers?
No. The Twilio text goes to your own moderator numbers only, and the queue is posted to a private Teams channel. Viewers are never contacted by the automation.
Will it text me constantly on a busy stream?
No. It sends at most one text per cycle and only when a redemption passes the waiting limit you set, so a busy store does not turn into a stream of alerts.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.