First, the honest version. Waveloom is not a helpdesk. It has no ticket queue, no shared inbox, no agents, no SLAs, no macros. If you have a support team, you need a support tool, and this is not it.
Waveloom is for the stage before that. You are the founder. Customers email you directly. They message you in Slack. You answer them yourself, between everything else, and the good ones sit unanswered for two days because they landed in the same inbox as the newsletters.
What happens to a support message
A customer writes in through Gmail or a Slack DM. Waveloom reads it in the background, alongside the channels and everything else it watches.
Most messages get dropped. Automated receipts, notifications, a thread that someone else already answered. Waveloom does not create a card for these. That is the default outcome, and it is the one that keeps your feed usable.
When a message needs you, you get one card. It has:
- The context. The message, plus what Waveloom already knows about this customer from your feed.
- Why this matters. One line. "Paying customer, second time asking about export, tone is patient but tired." Not a summary of the email. A reason to open it.
- An editable draft. Written from the message, the context it has, and what you have told it. You can send it as is, change three words, or rewrite it.
Approval is the whole design
Nothing goes out on its own. Waveloom can execute exactly two background actions, reply by email and reply to a Slack DM, and both require you to approve the draft first. This is enforced in code. There is no setting that turns it off.
If you dismiss a card instead, Waveloom remembers that too. Over time it gets a better sense of which customer messages you want to see and which you handle some other way.
Where it fits
Early-stage founders. Solo operators with a small customer base. Anyone whose "support" is a Gmail label and a #customers channel. If that is you, the value is simple: the customer message that matters shows up with a draft attached where a reply is supported, and the rest stays out of your way.
When you hire your first support person, you will outgrow this. That is fine. It was never meant to replace them.