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.
- First reported
- x.com · 26 Jan 2026
- Added
- 13 Oct 2026
- Source checked
- 13 Oct 2026
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.
What happened
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.
Keep in mind
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 your agent
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.
Replace the <angle brackets> with your own details.
Original source
x.comUser storySomeone who uses the agent described their own setup. Figures are theirs.
Tools for this kind of work
The whole toolkit →
