For anyone who sells something and has to support it
A support desk that already knows who bought what.
Every ticket arrives with the customer and their purchase attached — checked against Envato, against your own store, or approved by you. Replies are drafted from your own documentation. Your customers stop explaining who they are, and you stop asking.
Nothing charged for 14 days · Full data export on every plan · Free tier that stays free
The problem
Most of a support day is not support.
Supporting people who bought something has a shape that general help desks were never built for — so a person ends up doing that shape by hand, every time.
Three messages before the question
Who are you, did you buy this, is your support still valid. By the time the actual problem arrives you have lost the thread and half the morning.
The same answer, again
On a mature product most tickets have been answered before — often by the person answering them again, in slightly different words each time.
Nobody knows what is slipping
Somebody has been waiting two days and nothing says so. You find out when they write again, less politely.
Five messages in, and nobody has looked at the slider yet.
Multiply by every ticket, every week.
How it works
What happens between their problem and your reply.
Three things happen before a ticket reaches a person, and none of them need one.
Deflect
Matching articles are shown before they can submit.
The cheapest ticket is the one nobody needed to send.
Ticket avoided
Verify
The purchase code is checked against Envato as it arrives.
Licence, buyer and support window land on the ticket. Envato down? It is accepted anyway and re-checked later.
Nothing to ask
Draft
A reply is written from your own articles and documentation.
With a confidence label, for an agent to read, edit and send. Nothing goes out on its own.
Answer ready
So the ticket from a moment ago arrives like this instead.
Customer
Jamie Rowe
Licence
Regular
Purchased
14 Mar 2026
Support until
14 Sep 2026
“The slider stopped working after I updated to 4.2. It shows the first image and then nothing.”
Draft reply high confidence from “Slider & jQuery conflicts” · your docs
“Thanks Jamie — 4.2 moved the slider to jQuery 3, and an older plugin on the page is usually what stops it after the first slide. Open Appearance → Theme Options → …”
Read it, edit it, send it. First message, and it is about the slider.
Features
Everything it does, and why each part is there.
Built for one job: answering people who bought something from you on a marketplace. That narrowness is the point — a general help desk has to be told what a purchase code is, and by then you have already done the work.
Fewer tickets, and the ones you get are complete
Purchase verification, your way
A code checked against Envato or against your own store at submission, with the licence, buyer and support window attached. Whichever is down, the ticket is still accepted and re-checked in the background.
Or approve people yourself
No API to point us at? A customer asks, you say yes once, and they are set. Right for an agency that already knows its clients. Set per product, so an open product and a client-only one can sit side by side.
Support periods, handled
When a support window ends it can block a new ticket or just show a banner — your choice. Either way they keep reading everything they already have, and see your renewal link.
Knowledge base, shown first
Matching articles are offered before the submit button. Every article that answers a common question is a ticket you never receive.
Ask what you need up front
Custom fields on the submit form — WordPress version, staging URL, whatever your second reply always asks for.
Drafts written from your documentation, not the internet
A draft on every ticket
With a confidence label. High means the sources clearly answer it; low means the model is telling you it is guessing.
It reads your docs
Point a product at its documentation URL and it is read — same domain only, robots.txt respected. Republish an article and the answers update.
Automatic replies, if you want them
Off by default, paid plans only. Fires only on tickets your knowledge base fully answers, always labelled, always offering a human.
Metered, and it fails quiet
A monthly allowance per plan. At the limit drafting stops and everything else carries on exactly as before.
A support desk that looks like your company
Your own domain
support.yourbrand.com, certificate issued and renewed automatically. Your logo, your colours, your wording.
Email in and out
Customers reply by email and it lands on the right ticket. Bounces are detected, so a dead address stops being retried silently.
Routing rules
Send anything about one product, or one category, to the agent who knows it. Bulk-assign the whole catalogue in one sitting.
Response targets
Set what you promise, per priority and per customer group. The inbox shows what is past it.
Knowing whether it is actually working
A health check, not another chart
Eleven checks that each say what is wrong and where to fix it — who is waiting and for how long, replies that never reached a customer.
Your team, your rules
Agents can be limited to their own tickets, kept out of the customer directory, or shown a ticket without what the customer paid.
Notifications that mean something
Nobody is told what they just did, and four replies in a minute leave one badge rather than four.
Your data, any day
Every ticket, message, customer and article as JSON, CSV and Markdown. One click, on every plan including Free.
Who it is for
Three people we built this for.
The independent maker
One or two products, a few hundred customers, support squeezed between builds. ThemeForest, CodeCanyon, your own checkout, or all three.
Who is asking is settled before the ticket reaches you, and the knowledge base answers the repeats. What is left is real work.
Free covers one product
The software company
A catalogue, two to five people answering, docs that already exist.
Point us at Envato or at your own store and every code is checked as it arrives. The AI drafts from your documentation, so a new agent answers like the person who wrote it.
Author or Studio
The agency
You did not write it, you support it, and the client sees the desk. You know exactly who your clients are and have no API to prove it with.
Approve each client by hand, once — no codes, no integration. Your own domain and your client's brand on top, and agents can be shown a ticket with the purchase details hidden.
Studio, for the domain
Comparison
Already using something else?
We checked six well-known help desks — the big omnichannel names, an all-in-one business suite, and the closest thing to our niche for online sellers. Not one of them makes proof of purchase a condition of opening a ticket. The best of them can show you what somebody ordered; none of them can turn a stranger away until they prove who they are.
| Capability | A general help desk | A marketplace or all-in-one desk | TicketModules |
|---|---|---|---|
| Blocks a ticket until ownership is proven | No | No — shows order data, does not gate | Yes, per product |
| Checks a purchase against your own store | No | No | Yes, one signed webhook |
| Approve customers by hand, with no integration | No | No | Yes |
| Works without buying a whole other business suite | Yes | No — tied to their CRM/invoicing | Yes |
| Support periods, and what happens when one ends | No | Partial | Yes, your choice per workspace |
| AI drafts from your own documentation | Add-on | No | Included, with a confidence label |
| Knowledge base shown before they can submit | Yes | Yes | Yes — and it grounds the AI |
| Email in and out with correct threading | Yes | Partial | Yes |
| Priced per workspace, not per agent | No | Varies | Yes |
| One-click full data export | Partial | No | Yes, on every plan |
| Your own domain | Yes | Varies | Yes |
Six competitors checked, none of them built for a seller with no system to ask. We are betting on one thing the big desks leave to you entirely: knowing who bought what, before anybody reads the ticket. Plus data you can walk away with.
Setting up
Nothing to connect, unless you want to.
Most support tools hand you a list of accounts to open before anything works. You can be answering tickets here without connecting anything at all — and when you do want purchases checked, you pick how, per product.
Three answers, and you choose per product
Nothing at all, for a free tool or a desk where everybody is already known. A code we check for you, against Envato or against your own store. Or you approve each customer by hand — no integration, no API, right for an agency that simply knows its clients.
Connect a source, if you have one
Envato — supported in full
Paste a token and purchase codes, licences, buyer names and support windows all arrive on their own. Envato sign-in too, so a buyer never types a code at all.
Your own store
One signed webhook. We ask, you answer, and every order code is checked as it arrives — WooCommerce, WHMCS, Paddle, whatever you run.
Nothing at all
Approve customers yourself, or ask for no proof. No integration, no API, and you can change your mind per product later.
Your own domain
support.yourbrand.com, on Studio. The certificate is issued and renewed for you.
Included in every plan
Configured once, by us, for the whole platform. No accounts to open, no keys to paste, and no separate bills.
Email delivery
support.yourbrand.com, on Studio. The certificate is issued and renewed for you.
The AI
support.yourbrand.com, on Studio. The certificate is issued and renewed for you.
Virus scanning
support.yourbrand.com, on Studio. The certificate is issued and renewed for you.
Storage and backups
support.yourbrand.com, on Studio. The certificate is issued and renewed for you.
Sign-in for your team
support.yourbrand.com, on Studio. The certificate is issued and renewed for you.
Need something we do not talk to yet? Tell us which and why — that is how we decide what to build next.
Pricing
Priced per workspace, not per agent.
Charging per seat makes you think twice about letting a colleague help with a backlog, which is the opposite of what a support desk should encourage.
Free
$0
Free, and it stays free
- 1 product
- 1 agent
- 50 tickets a month
- No AI drafts
- Envato purchase verification
- Email in and out
- Full data export
Author
$15 $12 /month
or $144 a year — save $36 $144 billed once a year
Everything in Free, plus:
- 3 products
- 3 agents
- Unlimited tickets a month
- 100 AI drafts a month
- Automatic first replies
Studio
$39 $31 /month
or $374 a year — save $94 $374 billed once a year
Everything in Author, plus:
- Unlimited products
- 10 agents
- Unlimited tickets a month
- 2,000 AI drafts a month
- Automatic first replies
- Your own domain
Cancel any time
From your own billing screen. No email, no retention call.
Leave with everything
One-click export of every ticket, customer and article — on every plan, including Free.
Add your whole team
Priced per workspace, so an extra agent costs nothing.
Every plan starts with the same 14-day trial. Picking a paid one takes you to checkout after signup so your card is on file — the first charge falls on day fifteen, and cancelling before then costs nothing. Nothing is deleted when a trial ends: you drop to Free and anything over its limits becomes read-only rather than disappearing.
Questions
The things people ask before paying.
Getting started
How long does it take to set up?
About ten minutes, and you can connect nothing at all. Add a product and your portal is live on a subdomain with email already working — sending, receiving and bounce handling are ours to run, not yours to configure. Your own domain, your logo and routing rules can all wait until you have answered a few tickets.
Do I have to sell on a marketplace to use it?
No. Sell wherever you like, or nowhere in particular. Each product decides for itself how a customer proves they own it: nothing at all, a code we check for you, or your own approval. An Envato token is one option among those, not a requirement.
I have no way to verify my customers. Can I still use this?
Yes, and this is the common case. Either set a product to need no proof, so anyone signed in can ask — or set it to need your approval, and add each customer yourself with a note of their order. No API, no integration, and you can change your mind per product later.
I sell on Envato. Is this still built for me?
Yes — nothing has been taken away. Purchase-code verification, licences, buyer names, support windows, expired-support renewal prompts and Envato sign-in are all here and all first-class. The difference is that they are now one option among three rather than the only way in, so you can put a non-Envato product on the same desk without pretending it is one.
What do I have to set up or pay for separately?
Nothing. Email delivery, the AI, virus scanning, storage and backups are configured once by us for the whole platform and are included in every plan, including Free. You will not be asked for a Mailgun account or an OpenAI key.
Can I move my existing tickets in?
Not automatically today. Most people run both for a fortnight, point new tickets here, and let the old desk drain. Your knowledge base can be pasted in article by article; there is no import for it yet.
Purchase verification
Can different products be verified in different ways?
Yes, and this is the point of it. Proof is a setting on each product: an Envato item checked against Envato, a plugin checked against your own store, a client project you approve by hand, and a free tool that asks for nothing — all in one workspace, all on one desk.
How do I check purchases against my own store?
One signed webhook. We POST the code to a URL you choose with an HMAC signature, and read one field of your reply — your own database already has the answer, so we ask it rather than integrating with every marketplace in existence.
What happens if the check is down when a customer writes in?
The ticket is accepted and marked unverified, then re-checked in the background. That holds whether it is Envato or your own store: a customer with a real problem is never turned away because an API had a bad afternoon, and your shop going down must not take your support desk with it. Your health check tells you if verifications start piling up.
Can a customer open a ticket after their support period ends?
Your choice, per workspace. Either it blocks a new ticket and shows your renewal link, or it lets them through with a banner. Either way they keep reading every ticket and article they already had — taking away access to their own history is not a way to sell a renewal.
The AI
Does the AI reply to my customers by itself?
Not unless you switch it on, and it is off by default. Normally it writes a draft, an agent reads and edits it, and the agent sends. Automatic replies are a separate switch, on paid plans, and only fire when your knowledge base fully answers the question.
Where does the AI get its answers?
Only from your own content — your knowledge base articles and any product documentation you point it at. It is instructed to answer from those and to say so when they do not cover the question, which is why an unusual question comes back marked low confidence rather than confidently wrong.
Is my ticket content used to train a model?
No. Your content is sent to Anthropic to generate your reply and is not used to train anything. Optionally your own resolved tickets can be made searchable for your own future drafts — that is off by default and stays inside your workspace.
What happens when I run out of AI drafts?
Drafting stops for the rest of the month. Tickets, email, the portal and everything else carry on exactly as before. It fails quiet rather than breaking your desk.
Plans and billing
What happens at the end of the trial?
You drop to Free. Nothing is deleted. If you are over the Free limits — more products than it allows, say — those become read-only rather than disappearing, and everything comes back the moment you subscribe.
Can I take my data with me?
Yes, on every plan including Free, and without asking us. One click gives you every ticket, message, customer, product and article as JSON, CSV and Markdown. We would rather be the tool you stay with because it works.
Why is it priced per workspace and not per agent?
Because charging per seat makes you think twice about letting a colleague help with a backlog, and a support desk that discourages help is working against you.
Running it
Can I use my own domain?
Yes, on Studio. Point a subdomain at us and the certificate is issued and renewed automatically. Your subdomain here keeps working either way, so no link ever breaks.
Can I stop agents seeing what customers paid?
Yes. Agents can be limited to tickets assigned to them, kept out of the customer directory, or shown a ticket with the purchase details hidden. Useful when the person fixing the bug is a contractor.
Do you have an API?
Not a public one yet. Webhooks exist for inbound mail and payments. If an API would decide it for you, say so below — that is how we work out what to build next.
Still deciding
Ask us anything.
Questions before you sign up, or a feature that would decide it. We answer in our own TicketModules workspace — the product we are asking you to buy.
This becomes a ticket in our own desk
Not a mailbox somebody remembers to check. We answer you inside the product we are asking you to buy, which means we read the same screens you would — and notice the same things.
A person, not an autoresponder
Every reply here is written by somebody who works on the product.
support@ticketmodules.com
If you would rather just write an email.
Already using it? Sign in first
A ticket from your own desk reaches us with your workspace attached, which saves a round trip.
Try it on your own tickets.
14 days of Author features. No card required, nothing to cancel if you stop, and your data is exportable from day one.
Questions first? Ask us.