How do I stop the same question arriving by email?
You stop the same question arriving by email by answering it before the customer reaches for email: a chat widget on the site that quotes your published article. The emails that still come in become tickets in one inbox, the AI drafts the reply from the same article, and you approve it instead of typing it again.
Last updated: October 2026 · View as Markdown
Why does this keep happening?
Email is the slowest place to answer a fast question. The customer writes, waits, and often writes again. Then the reply is typed by hand for the fortieth time. A benchmark of 1,000 companies found the average reply takes over twelve hours, and 62% never replied at all.
The question usually started on your site. They looked, did not find it, and fell back to the support address in the footer. Each email is a page that did not answer.
So the fix is in two places: on the site, so the question gets answered there, and in the inbox, so the ones that still arrive cost a click rather than a paragraph.
How do I fix it, step by step?
Find the five emails you keep writing
Search your sent folder for the reply you paste most. Those five are the articles.
Publish them and put the widget on the site
The widget answers from the articles on the page where the question starts. Many of those emails stop before they are written.
Turn the support address into tickets
On Pro, email to your support address becomes a ticket with the customer and the thread attached. Replies go back as email from your own domain.
Let the AI draft from the same articles
For a ticket covered by an article, a draft waits in the approval queue. Read, edit if needed, send. The paragraph you used to type is now a click.
Add a line to the article each time one slips through
A question that still arrives by email is a sentence the article is missing. Add it. The next one gets answered on the site.
What is true about this today?
| Fact | Value | Source |
|---|---|---|
| Companies that never answered a customer service email, in a test of 1,000 | 62% | SuperOffice customer service benchmark, updated March 2023 |
| Average reply time among the companies that did answer | 12 hours 10 minutes | SuperOffice customer service benchmark, updated March 2023 |
| Customers who rate an immediate response as important or very important | 90% | HubSpot Research, updated May 2025 |
| DeskCrew Pro | $29 a month flat for the workspace: email-to-ticket, 150 AI answers, white-label | DeskCrew pricing, October 2026 |
What changes, and what does not?
Email-to-ticket is on Pro
The widget, ticketing and the public board are free. Turning an email address into tickets is a paid feature, at $29 a month for the workspace. If email is your main channel, that is the plan; if the widget alone stops most of the emails, the free plan may be enough.
Drafts still need a read
The AI drafts; you approve. That is a click, not a paragraph, but it is not zero. You can let a workspace send drafts on its own later, once they have earned it.
Some emails should stay human
Complaints, refunds and anything with an account number. The articles answer the easy ones so you have time for these.
What else do people ask?
Can the AI reply to emails on its own?
By default it drafts and you approve, which is the right setting for anything you have not watched it do. Once the drafts for a type of question are consistently right, you can let that workspace send them without approval. Every reply, approved or automatic, is grounded in your published articles and nothing else.
Does the customer get the reply as a normal email?
Yes. On Pro, replies go out as email from your own domain, in the same thread the customer started, so it looks like any other reply from your company. If the customer started in the chat widget and left, the reply also goes by email, and their whole history stays on one ticket.
What happens to the emails that are not questions, like receipts and newsletters?
They should not reach the support address at all, and a dedicated support address is the first step. Anything that does arrive and is not a support request can be closed or marked as spam in one click, and the sender is not emailed back. The queue stays the questions, which is the whole point of having one.
How quickly will the emails drop?
Most people see the first fall within two weeks of the widget going live with the five articles, because the question is answered on the page before the email is written. The rest of the drop comes from adding a line to an article each time a question still arrives. Count a month before and a month after.
Is there a free way to do this?
The widget, the articles and the ticket inbox are free, with no card, and they stop the emails at the source. What is paid is turning the support address itself into tickets, which is Pro at $29 a month flat. Many small sites run free until the email volume justifies the upgrade.
Email to ticket · AI support widget · Stop answering the same five questions · Pricing · All how-to guides