Browse the docs
Plans
What counts as an answer
How ASDK counts the answers in your plan: one agent reply to one visitor message, what doesn't count, when the count resets and how to estimate your needs.
Last updated
On this page
Every plan includes a number of answers a month. This page explains exactly what one answer is, what doesn't count, and how to estimate what your site needs.
One reply, one answer
An answer is one reply an ASDK agent writes to a visitor's message. A conversation in which a visitor asks five questions uses five answers.
| Plan | Answers a month |
|---|---|
| Free | 50 |
| Starter | 1,000 |
| Pro | 5,000 |
| Business | 20,000 |
| Agency | 50,000 |
| Trial (14 days) | 500 in total |
Answers are counted for the whole workspace: all its sites share the plan's answers.
What counts
- Every reply to a visitor's message, whatever its length. A short reply to "hi" or "thanks" counts too.
- Replies that say the agent doesn't know. The agent still searched your knowledge and wrote a reply, often with an offer to leave contact details.
- Answers to suggested questions. Clicking a suggested question sends it as a message, and the reply counts.
- Questions you ask in the dashboard, in Try it during setup or Try the real widget on the Agents page. They use the same agent as your site. They're left out of your conversation statistics, but not out of the count.
What doesn't count
- The greeting and the suggested question buttons themselves.
- Contact forms, whether offered by the agent or opened by the visitor, and the leads they create.
- Opening the widget, page views and other events.
- Visitor feedback with Helpful or Not helpful.
- A reply that is resent after a network problem: when a visitor's connection drops and the widget sends the same message again, it is answered and counted once.
- The fixed reply after your monthly answers run out. See What happens at a limit.
- AI assistants reading your hosted llms.txt, published by the Agent-Ready agent.
When the count starts again
During early access, answers are counted per calendar month in UTC, and the count starts again at 00:00 UTC on the first day of each month. Unused answers don't carry over. When billing launches, the count follows your billing month, as the pricing page describes.
Estimate what you need
A rough estimate from numbers you probably have:
- Monthly visitors of the pages where the widget appears.
- Share who open the chat. This varies widely by site and audience; measure your own after the first weeks rather than relying on an industry figure.
- Questions per conversation. Most visitors ask one to three.
For example, 10,000 visitors a month, 2% of whom open the chat and ask two questions on average, use about 400 answers. That fits the Starter plan's 1,000 with room to spare. After two or three weeks, the real numbers in your weekly report or the Inbox are a better guide than any estimate.
Keep answers working for you
You don't need to ration answers: a visitor who gets a good answer is the point of ASDK. But a few habits keep the count meaningful:
- Give suggested questions that lead somewhere, so clicks turn into useful conversations. See Suggested questions.
- Keep test sessions short. Questions you ask in the dashboard count.
- Fix knowledge gaps. Visitors who get "I don't know" often rephrase and ask again, using two or three answers for one question. A Q&A pair answers it the first time.
See your usage
During early access, the dashboard doesn't show an answer counter yet: usage against your plan's limits will appear on the Billing page with billing. Until then, we let workspace owners know by email when the workspace reaches its monthly answers, and the weekly report shows the week's answers once it reaches your workspace.
Related: Plans and limits, What happens at a limit.