Short answer
One to two weeks to have it fully running. Answering from your documentation takes a few hours. What you already publish gets indexed and it starts replying. What takes longer is connecting the queries to your API so it can check the account of the person asking, and that depends on your engineering team more than on the vendor.
In detail
Day one
You index the documentation, decide the tone and the limits, and put it to work on one channel. That already covers the questions whose answer is the same for everyone, and in a well-explained product there are plenty.
The second week
You connect the queries to your API, such as plan, usage, subscription status or recent orders. It’s work on your side, and it’s where the most time-consuming half of the volume sits. Start with two or three queries. Plan and usage alone resolve more than you’d expect.
What never ends
The documentation. When the agent gives a weak answer, it’s almost always because a specific article is missing or wrong, so the first weeks leave you a list of articles to write or fix, each with its reason. That work continues after launch.
How it gets delayed
By trying to make it handle everything from day one. Starting narrow and resolving 30% well beats going broad and resolving 60% poorly, because the first can be expanded, the second has to be undone.