Catch MAX messages nobody has answered
Twice a day, WebRun opens MAX, scans your business chats for messages that came in and never got a reply, records each one with its waiting time in a Notion tracker, and posts a short chase list to your Microsoft Teams channel so nothing sits unanswered.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I make sure no MAX message goes unanswered?
WebRun watches your MAX inbox twice a day and finds every conversation where a customer message sits without a reply. It logs each one in a Notion tracker with its waiting time and posts an ordered chase list to Microsoft Teams with owners named, so no MAX chat goes quietly unanswered.
- No customer message sits waiting past your response target
- Every waiting chat has a named owner in Teams
- The Notion tracker shows response times without anyone counting by hand
Built for support teams · small business owners · community managers · sales 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
max.ruin a real browser with your saved login - no setup, no API keys. -
1
MAX - find chats with no reply
WebRun opens MAX to find chats with no reply. - Open MAX and go through your business conversations
- Find every chat where the last message is from the other person
- Record who sent it, the first line of the message, and how long it has been waiting
- Ignore chats already marked resolved or muted
Done when Every conversation waiting on your side is listed with its waiting time.
-
2
Notion - log each waiting conversation
WebRun opens Notion to log each waiting conversation. - Open your Notion chase tracker database
- Add a row for each waiting conversation with the contact, the waiting time, and the first line
- Update rows that already exist instead of creating a second one
- Close out rows for chats that have since been answered
Done when The Notion tracker matches the live state of your MAX inbox.
-
3
Microsoft Teams - post the chase list
WebRun opens Microsoft Teams to post the chase list. - Post the chase list to your support channel, longest wait first
- Mention the teammate who owns each conversation
- Say plainly which chats have crossed your response-time target
- Leave replying to the team. WebRun never answers the customer itself
Done when The team has an ordered chase list in Teams with owners named.
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 people in MAX for me?
No. WebRun only reads which chats are waiting and reports them internally to Notion and Teams. Every reply is written and sent by a human, so no customer ever receives a message WebRun wrote.
How does it decide a chat is unanswered?
It checks whether the last message in the thread came from the other person. If it did, the chat counts as waiting, and the clock starts from that message's timestamp.
What if someone answers between runs?
The chat drops off the next list automatically. WebRun re-reads live MAX state each run and closes the matching Notion row rather than chasing something already handled.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.