Automated imo Chat Request Triage
Every morning, WebRun opens imo, reads the conversations and groups your team uses for customer requests, sorts overnight messages into real requests and chatter, opens a Trello card per request with the sender and what they asked for, and texts you anything that reads urgent.
How do I turn customer chat messages into tracked tasks?
WebRun reads your imo customer conversations every morning and separates real requests from chatter. Each request becomes a labelled Trello card carrying the sender and the message context, and anything urgent or long-waiting is texted to your team through Twilio, so nothing sits unanswered in chat.
- Overnight requests reach the board before the team opens the chat app
- Customers waiting over a day are flagged rather than forgotten
- Every card carries the original message, so nobody has to scroll back
Built for small businesses · service providers · support teams · local shops
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
web.imo.imin a real browser with your saved login - no setup, no API keys. -
1
imo - read overnight conversations
WebRun opens imo to read overnight conversations. - Open imo in the browser and go to the chats and groups your team uses for customer contact
- Read messages received since the last run
- Separate genuine requests from acknowledgements, greetings, and small talk
- Capture the sender, what they asked for, and any date, address, or reference they gave
- Note conversations where the customer has already waited more than a day for a reply
Done when Every overnight message is classified and every real request is captured.
-
2
Trello - card each real request
WebRun opens Trello to card each real request. - Open your request board in Trello
- Create one card per request titled with the sender and what they want
- Paste the relevant message text into the description so the context travels with the card
- Label cards by type, such as booking, quote, complaint, or question
- Skip requests that already have a card from an earlier run
Done when Every overnight request has a labelled Trello card with its context.
-
3
Twilio - text you the urgent ones
WebRun opens Twilio to text you the urgent ones. - Send yourself a Twilio text listing the requests that read urgent or that have waited longest
- Include the sender and a one-line summary of what they need
- Send to your own team numbers only. WebRun never texts the customer
- Never reply inside imo. WebRun reads and sorts, and a person answers
Done when You have been texted this morning's urgent requests.
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 customers in the chat?
No. WebRun reads the conversations and turns them into internal Trello cards. It never sends a message in imo and never texts the customer, so every reply is written by a person on your team.
How does it tell a request from small talk?
It reads each overnight message for an actual ask: a booking, a quote, a question, a complaint, or a change. Greetings, thanks, and acknowledgements are left alone so the board only holds work.
What about messages that need a fast answer?
Anything that reads urgent, or where the customer has already waited more than a day, is texted to your own team number the same morning through Twilio, so it is seen before someone gets to the board.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.