How long does it take to get an AI support agent running?
Answering from your documentation is a matter of hours, not weeks: what you already publish gets indexed and it starts replying. What takes time is the other half — connecting the reads against your API so it can check the account of whoever is asking — and that depends on your product team, not the vendor. One to two weeks is an honest estimate for having both.
Short answer
Answering from your documentation is a matter of hours, not weeks: what you already publish gets indexed and it starts replying. What takes time is the other half — connecting the reads against your API so it can check the account of whoever is asking — and that depends on your product team, not the vendor. One to two weeks is an honest estimate for having both.
In detail
What happens on day one
Indexing the documentation, deciding the tone and the limits, and putting it to answer on one bounded channel. That already covers the group of questions whose answer is the same for everybody, which in a clear product is not a small share.
What the second week takes
The reads against your API: plan, usage, subscription state, recent orders. It is work on your side and it is where the expensive half of the volume sits. It is worth starting with two or three queries rather than all of them: plan and usage alone resolve more than you would think.
What never finishes
The documentation. Weak agent answers point at one specific article almost every time, so the first weeks generate a documentation to-do list with the diagnosis already done. That is not a launch problem: that is the work.
The way it gets delayed
Trying to make it resolve everything from day one. A bounded launch resolving 30% well beats a broad one resolving 60% indifferently, because the second has to be undone and the first gets extended.
Terms that come up here
Other questions in this thread
Do I need to integrate all my tools before starting?
No, and it is better not to. With the documentation indexed you already resolve the group of questions that do not depend on the account, and that works on day one with nothing connected. Integrations get added in order of what gets asked most, and normally two or three cover the bulk: subscription state, usage, and the last order or invoice.
Do I need a help centre already to use an AI knowledge base?
No. The articles can live anywhere readable — a portal, a docs repository, even internal documents — and the system indexes them the same. What is required is that they exist in writing: if the answer is nowhere, there is nothing to index, and that is the only real prerequisite.
Do I need the official WhatsApp Business API to support customers there?
Yes, if you want to handle it with a team or with an automated system. The normal app and WhatsApp Business do not allow tools to be connected in any supported way, and the workarounds that manage it risk having Meta shut the number down. The official API is contracted through an authorised provider, who handles the verification.
Where this question comes from
Intake pricing →