Automated Medallia Response Coverage Checks
Every Monday, WebRun opens Medallia, reads how many survey invitations went out and how many responses came back for each location and team, compares that against the previous month, posts the units collecting less than they should to Microsoft Teams, and alerts you on Telegram about any location that has gone quiet.
How do I find locations whose survey response rate has dropped?
WebRun checks your Medallia response coverage every Monday. It reads invitations sent and responses received for each location and team, compares them against the previous month, and posts the under-collecting units to Microsoft Teams worst drop first. Telegram gets an alert when a location goes silent, so a broken survey trigger is fixed in days.
- A broken survey trigger is caught in days, not at quarter end
- Every location is compared against its own last month, not an average
- Silent units are escalated separately from merely soft ones
Built for CX leads · customer insight teams · multi-location retailers · operations managers
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
www.medallia.comin a real browser with your saved login - no setup, no API keys. -
1
Medallia - compare response volume by location
WebRun opens Medallia to compare response volume by location. - Open Medallia and select the surveys and reporting period you asked it to cover
- For each location and team, read the invitations sent and the responses received
- Work out the response rate and compare it against the previous month
- Flag units whose response volume has dropped past the threshold you set
- Flag any unit with no responses at all this period
Done when Every location has a response rate and a month over month change.
-
2
Microsoft Teams - post the coverage gaps
WebRun opens Microsoft Teams to post the coverage gaps. - Post the coverage report to your CX channel, worst drop first
- For each unit show invitations, responses, the rate, and the change since last month
- Separate units that are collecting less from units that have stopped entirely
- Note the total responses lost against the previous period so the cost is visible
Done when The coverage report is posted in Teams, ranked by drop.
-
3
Telegram - alert you when a unit goes silent
WebRun opens Telegram to alert you when a unit goes silent. - Alert your Telegram channel when a location records no responses at all
- Name the location, the survey, and how long it has been silent
- Suggest checking the invitation trigger for that unit as the first thing to look at
- Never edit a survey, resend an invitation, or contact a customer
Done when Every silent location has been raised in Telegram.
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 send surveys or contact customers?
No. WebRun never sends an invitation, resends a survey, or messages a customer. It reads the volumes already recorded and reports where collection has dropped.
How does it tell a quiet week from a broken survey?
It compares against the same unit's previous month rather than a fixed number, and separates a drop from a total stop. A location with zero responses is escalated on its own.
Does it change anything in Medallia?
No. It is read-only. Fixing a broken invitation trigger or adjusting a survey stays with your CX team, which is why the alert names the unit and the survey involved.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.