Automated Computrition Meal Satisfaction Survey Drafts
Every morning, WebRun opens Computrition, finds patients on day 3 or later of their stay who have not already been surveyed this admission, drafts a short meal satisfaction text through Twilio for your patient experience team to review and send, logs every response received to a Google Sheet, and posts a weekly satisfaction summary to the food service director in Slack.
How do I collect meal satisfaction feedback without texting patients unsupervised?
WebRun finds patients on day 3 or later of their stay in Computrition who have not yet been surveyed, and drafts a short meal satisfaction text through Twilio for your patient experience team to review and send. It logs every response to a Google Sheet and posts a weekly Slack summary to the food service director, so feedback keeps flowing without a single unsupervised text going out.
- Every satisfaction text is reviewed by a person before it reaches a patient
- Feedback gets collected continuously instead of only during a periodic survey push
- The food service director sees a weekly pattern by unit and diet type, not raw responses
Built for patient experience teams · food service directors · hospital nutrition services · hospitality and dietary 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.computrition.comin a real browser with your saved login - no setup, no API keys. -
1
Computrition - find patients eligible for a check-in
computrition.com
WebRun opens Computrition to find patients eligible for a check-in. - Open Computrition and pull patients on day 3 or later of their current stay
- Exclude anyone already surveyed this admission or currently NPO
- Note each patient's room, unit, and diet type for context
Done when Every eligible, not-yet-surveyed patient has been listed with their room and unit.
-
2
Twilio - draft the satisfaction text for review
twilio.com
WebRun opens Twilio to draft the satisfaction text for review. - Draft a short meal satisfaction text for each eligible patient asking about their last two meals
- Queue every draft in the patient experience team's Twilio approval inbox
- Leave every message unsent. A person on the patient experience team reviews and sends each one
Done when A draft text is queued for every eligible patient, with none sent without a person's approval.
-
3
Google Sheets - log every response received
google.com
WebRun opens Google Sheets to log every response received. - Log every satisfaction response received back to the Survey Response tracker
- Tag each response by diet type and unit
- Carry forward the running response count for the week
Done when Every response received this week is logged with its diet type and unit.
-
4
Slack - summarize results for the food service director
slack.com
WebRun opens Slack to summarize results for the food service director. - Post a weekly summary of satisfaction responses to the food service director in Slack
- Break results out by diet type and unit so a pattern is visible
- Flag any unit or diet type trending below your satisfaction target
Done when The food service director has a weekly satisfaction summary in Slack, broken out by unit and diet type.
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 text patients without anyone reviewing the message first?
No. Every satisfaction text is drafted and queued in Twilio for your patient experience team to review. Nothing sends to a patient without a person approving it first.
How does it pick which patients to survey?
It looks for patients on day 3 or later of their current stay in Computrition who have not already been surveyed this admission, so nobody gets asked twice or too early in their stay.
Where do the survey responses go?
Every response is logged to a Google Sheet, and the food service director gets a weekly Slack summary broken out by unit and diet type, so a pattern is visible without reading every response.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.