Support email from all your products lands in one place, sorted in under a second. Spam and link sellers never reach you. Every real question comes with a reply drafted from your own help center, ready to approve.
Stop checking five support addresses. Every product, one queue.
Answers written from your help center, waiting for one click.
Spam is filtered. Link sellers get your standard reply.
What you ship each week becomes draft help articles and release notes.
Add a product by adding its support address or domain. Its email starts landing in one inbox, threaded by conversation.
Each email is classified in under a second: support, bug, feature request, refund, link seller, partnership or spam. Spam never reaches you.
Per product rules answer link sellers, check refunds against your policy, and forward bugs and requests to your team with context.
Every ticket comes with a draft. Approve, edit or decline it. Replies go out in the same thread, from that product’s own address.
Pick a type to see what Kamaan does with it.
I added the record twice and the domain check still fails. What am I missing?
Support questionHi Maya, that check usually fails while the old record is still cached. Remove the old CNAME, wait ten minutes, then press Verify again.
Kamaan finds the help articles that answer the question and drafts the reply from them. You approve it, edit it or decline it.
Every ticket arrives with a draft. Nothing goes to a customer until you say so, and every reply looks like it came from you, because it did.
Your blog and help center live in Kamaan, and they are what the drafts and the widget answer from. Each week, merged work turns into draft help articles and release notes for you to review.
mergedAdd CSV export to reportsmergedFix time zones on scheduled postsmergedNew Viewer role for teamsAdd one script tag and every page gets a contact form and a search across your help center. It is served from support.yourdomain.com through a CNAME, so customers see your brand, not ours.
<!-- one line, before </body> -->
<script src="https://support.yourdomain.com/api/hc/loader.js" defer></script>Pick a plan by how many products you run. Your team is included.
Prefer to use your own AI? Translate through the MCP or the ChatGPT and Claude integrations and it runs on your account, using zero translation credits.
Lifetime plans have the same limits as the matching subscription plan. Translation credits are a one-time grant that never expires.
API calls are requests your server makes to Kamaan's REST API, not page views on your blog. You host your own frontend, so visitors hit your infrastructure, not ours.
Add your first product, and the next support email arrives sorted, with a reply ready.