OpenClaw · Open source
Sort a shared support inbox into a simple ticket workflow
The team behind Linkedmash connected OpenClaw to its support inboxes, and it designed status folders and mail rules that move each ticket along as replies go out.
What they did
A member of the Linkedmash team ran OpenClaw on a local machine, connected it to the company's support and hello mailboxes, and used the ChatGPT model they already paid for. It proposed four folders: new, waiting on customer, waiting on internal, and done. It then set up incoming filters, applied the rules to existing mail, and added an outgoing filter so every reply the team sends moves the thread to waiting on customer.
How it went
The poster says the outgoing-mail rule closed a gap they had never handled and removed a lot of mental load, and that it also suggested a manual flow for edge cases like internal blockers and feedback emails.
Worth knowing
It was not fully autonomous: the poster hit model rate limits and waited about three hours, and a mail interface glitch meant one step had to be done by hand. These were first impressions after one day.
Try it with OpenClaw
Connect to <your support mailbox> and look at the last <number> weeks of support email. Propose a small set of status folders that match how we actually work, then show me the filter rules you would create, including one that moves a thread to a waiting on customer folder whenever we reply. Wait for my approval before creating any folders or rules, and do not reply to or delete any email.
We wrote this prompt from the case. Replace the parts in angle brackets with your own details.
What this label means: User reports
Someone using it at work posted about it. Any numbers are theirs, so we write "the poster says".
Real cases of AI agents at work, from every major agent, each linked to where it was first reported. Rewritten in our own words, most with a prompt you can try. These are not Wize customers.