How Long Does It Take to Set Up an AI Chatbot? A Realistic Timeline

You have probably seen the promise on a chatbot vendor's homepage: set up in minutes, live today. For one part of the job it is true. Importing a website and pasting a script tag take little hands-on time on every tool in this guide. What the promise leaves out is everything between the first good answer in a test window and the day you let every visitor talk to the bot.

This guide is for the person who will do the setup themselves: a store owner, a salon or studio manager, a coach, or a support lead at a small company choosing an AI support agent. It sets out what eight tools' own documentation says setup involves, a stage-by-stage time budget with honest ranges, which stages the "minutes" claims leave out, and a day-by-day plan for the first week.

PepoChat is our product. Its setup path below comes from its documentation and code, read on 22 October 2026, and every other vendor's from that vendor's own site on the same day. We did not create accounts or time anyone's setup, so each duration below is either a vendor's own words, quoted, or our estimate, labelled as one.

How long does it take to set up an AI chatbot?

Setting up an AI chatbot takes 30 minutes to 2 hours of hands-on work for the mechanical stages and about 4 to 13 hours in total before it is ready for every visitor, usually spread over a week.

Two finish lines hide inside the question. Time to first answer is the time from sign-up until the bot answers a question from your own content in a test window. Time to launch is the time until you would let every visitor use it without reading each conversation first. Vendor claims measure the first; your customers live with the second.

The range is wide because businesses differ. A 15-page site with prices written on the pages, run by one person who can edit the footer, sits near the bottom. A store with policies buried in PDFs, a developer who controls the site and an order lookup to connect sits near the top. The budget below assumes a small business site of about 40 pages, three PDFs, one person doing the work and one integration.

What do AI chatbot vendors say about setup time?

AI chatbot vendors' own setup claims run from "in under 5 minutes" at Chatbase to "Set up in under an hour" for Intercom Fin, and each one covers part of signing up, adding content and going live, never testing or handoff.

Claims quoted from each vendor's own site on 22 October 2026.

Read the table as a measure of the mechanics, which is all a one-line claim can describe. Chatbase's quick start does include a test step in its Playground, and says training "typically takes 2-5 minutes depending on the amount of data". What none of the eight pages promises is that the answers are right, that a request for a person reaches someone, or that an order lookup works.

The vendors with the biggest crawlers word their estimates most carefully. Intercom's website sync guide says an initial sync "can take anywhere from a few minutes to over an hour", and HubSpot makes no time claim for its Breeze Customer Agent at all. PepoChat's own docs FAQ claim belongs in the same column, with the same limits.

What does each AI chatbot's documented setup path look like?

Each AI chatbot's documented setup path follows the same four steps (sign up, add content, test in a preview, paste a script), but the eight tools differ in card requirements, page limits and the plan the agent needs.

Plans, limits and install steps from each vendor's pricing page, docs or help center, checked 22 October 2026. "Not stated" means the pages we could open were silent; Tidio's help center blocked automated reading, so its row relies on Tidio's pricing page, product page and blog.

Three gates cost more calendar time than any import. The first is paying before testing. SiteGPT's pricing page says its 7-day trial needs a card ("credit card required, cancel anytime before it ends"), Chatbase lists no free plan, only 7-day trials of its paid plans, and HubSpot's agent needs a Professional or Enterprise seat, which starts at $90 a seat a month on the Service Hub pricing page plus a required one-time onboarding fee of $1,500. If a purchase needs approval at your company, that stage takes days.

The second gate is a prerequisite you may not have. Intercom's guide to deploying Fin over chat says "To set Fin live, you must have at least 10 public articles live in your Help Center", and the Messenger must be installed first. HubSpot's customer agent overview lists a live chat channel connected to the conversations inbox, the tracking code on sites HubSpot does not host, AI settings switched on and an assigned seat. Teams already running Intercom or HubSpot have most of this in place; teams starting from nothing have articles to write and settings to find.

The third gate is the crawler. Page limits decide whether one import covers your site: Intercom syncs up to 4,000 pages per source and HubSpot up to 5,000 URLs per domain, Chatling's crawler takes up to 1,000 pages, and SiteGPT's Starter plan holds 1,000 pages, where a page means 2,500 cleaned characters, while a PepoChat crawl stops at 200 pages. Crisp's training guide adds two warnings: its crawler needs content "available statically", and it does not refresh crawled pages on its own, so a price change means a manual refresh.

How much time does each AI chatbot setup stage take?

Each AI chatbot setup stage takes between a few minutes and a few hours of hands-on work, and the nine stages together come to about 4 to 13 hours for a 40-page small business site.

Estimates for a site of about 40 pages with three PDFs, one person and one integration, made on 22 October 2026 from each vendor's documented steps; they are not measurements.

Stages 1 to 4 are what the "minutes" claims describe, and even here they come to 30 minutes to 2 hours, because choosing what the bot should read takes longer than clicking Import. Stages 5 to 9 add about 4 to 11 hours, and they decide whether the bot is any good. If you are costing the work for a business case, budget the top of the range: the first week nearly always turns up a page that needs rewriting.

The waiting column matters too: start the slow things, such as a purchase approval or a first sync, before the hands-on stages.

Why does adding content take longer than the import?

Adding content takes longer than the import because the slow part is deciding what the chatbot should read: excluding stale pages, adding the PDFs that hold prices and policies, and writing answers your site never states.

A whole-site crawl brings in everything it can reach, including a 2023 promotion and last year's shipping policy. Twenty minutes comparing the import list with your sitemap saves hours of testing later, because two pages that disagree produce answers that flip between them. The guide to training a chatbot on your website and PDFs covers each source type and its traps.

Then you wait, and how long depends on page count and on how politely the crawler fetches. PepoChat's crawler, for example, works through pages in batches of three, pausing half a second after each page and a second between batches, so in a full 200-page crawl the pauses alone add almost three minutes, on top of the time it takes to download and index each page. That is a floor read from the code, not a measured time, and larger sites take longer on every tool.

The wait costs nothing if you use it. Chatbase, SiteGPT and PepoChat all document that an import keeps running when you leave the page, so start it first, then write your greeting and instructions while it works.

How long does installing a chatbot widget take?

Installing a chatbot widget takes 5 to 30 minutes when you can edit your site's code settings yourself, and as long as someone else's queue when a developer or agency controls the site.

Every tool in this guide installs the same way: copy a script from a setup page and paste it into the page head or before the closing </body> tag, or install a plugin. Intercom's install guide says "It only takes a few minutes to install the Messenger on your website", and a Tidio guide to Squarespace says you can "add the plugin in just 3 minutes"; both are fair for the paste itself. HubSpot adds a step, because its agent answers through a live chat channel, which needs the HubSpot tracking code on sites HubSpot does not host.

The 30-minute end of the range comes from the checks around the paste: whether your website builder's plan runs custom code at all, a page cache that keeps serving the old footer, an allowed-domains setting that leaves out your preview domain, and a look on a real phone. The one-script-tag install guide has the snippets and the checks for each platform.

Install late in the week, not first. Seven of the eight tools document a test window or playground (Tidio's help center could not be read), so you can test answers long before visitors can see the launcher.

Which setup stages do "set up in minutes" claims leave out?

The "set up in minutes" claims leave out five stages: writing instructions, testing about 40 questions, configuring human handoff, connecting an integration and running a soft launch, which together take about 4 to 11 hours.

Instructions and greeting: 30 to 90 minutes

Agent instructions are the written rules for tone, scope and refusals that a bot follows on top of your content. A first draft takes half an hour. The rest goes on a greeting that says what the bot can do, a few suggested questions it answers well, and "never" rules for discounts, legal questions and promises you do not make. The 12 instruction examples are a faster start than an empty box.

Testing: 2 to 4 hours

Testing takes longest because it is where content problems surface. Our 40-question test script takes 60 to 90 minutes a run; add an hour or two to fix what fails, mostly by correcting or adding content, and about ten minutes for a regression rerun. Skipping the test does not save the time; it moves it to the week your customers find the problems.

Human handoff: 20 to 60 minutes

Human handoff is the transfer of a conversation from the bot to a person, with the transcript attached. The settings take minutes: who is notified, what the bot promises outside your hours, and where the conversation lands. The time goes on the test, because an alert that lands in an inbox nobody reads only shows up when you send a real "I want to talk to a person" and wait for it.

One integration: 15 minutes to 2 hours

Connecting a store, helpdesk or billing tool is quick when you hold the admin keys and slow when someone else has to approve access. PepoChat's docs FAQ says integrations "take a few minutes each", which matches the connect step. The rest of the two hours goes on creating a test order or ticket and checking what the bot says about it, because a test that triggers an action usually does the real thing.

Soft launch: 15 to 30 minutes a day

A soft launch puts the bot on a few pages before the whole site. Two pages where visitors already ask questions, such as pricing and contact, give you real conversations at low risk. The cost is reading every conversation for three to five days and fixing the content behind each miss.

What does a realistic first week of chatbot setup look like?

A realistic first week of chatbot setup is five working sessions of 30 minutes to 3 hours, ending in a soft launch on two pages, followed by two days of short daily reviews.

Our estimate for a 40-page site, 22 October 2026: about 6 to 10 hours across the week.

The order matters more than the dates. Content comes first because every later stage tests it. Testing comes before the install because a bot you have not tested should not meet customers, and handoff gets its own day because it involves other people's inboxes and phones. If you only have an hour on day 5, the AI chatbot launch checklist names the five checks not to skip.

If the week has to shrink, shorten the soft launch, never the testing day.

What slows AI chatbot setup down the most?

The things that slow AI chatbot setup down most sit outside the chatbot: a purchase approval or card wall, a website only a developer can edit, policies that live in PDFs or people's heads, and nobody owning the handoff.

• Paying before testing. A card at sign-up or a seat purchase turns a quick trial into a buying decision. Start with a free plan or a no-card trial if you can.
• Content that is not on the site. Refund exceptions, delivery cut-offs and a price list in a PDF are exactly what customers ask about. Write them down as text before you test.
• Contradictions. An old page and a new page that disagree cost more testing time than a missing page, because the bot answers both ways.
• Site access. If an agency controls your footer, send the request on day 1, not day 5.
• An unowned handoff. Decide before launch who answers when the bot hands over, and when.

How long does PepoChat take to set up?

PepoChat's docs FAQ says setup takes "About ten minutes for account, knowledge, customization and install", and that claim has the same blind spot as everyone else's: it stops before testing, handoff and a soft launch.

The documented path in the PepoChat quickstart has six steps:

1. Sign up with email and a password, confirming the code sent to you, or with Google, then name your workspace. No credit card is needed, and the Free plan includes 200 AI replies a month and 5 knowledge sources.
2. Add your website under Knowledge Base, Add New. A crawl takes up to 200 pages, 3 levels deep, and a sitemap import up to 200 URLs; either counts as one knowledge source and runs in the background with a running page count.
3. Shape the widget in Widget Customization: greeting, up to three suggested questions, brand colour and agent instructions.
4. Test the agent in a drawer that opens your real widget under a "Test mode" banner. Test chats are free and stay out of analytics and the team inbox, but bookings, integration actions and emails still run for real.
5. Install by pasting one script tag before </body>, or install the WordPress plugin and paste your Organization ID.
6. Ask for a person on your live site and check that the conversation turns escalated and an email titled "A visitor needs a person" arrives.

Three limits shape the PepoChat timeline. A crawl or sitemap import stops at 200 pages, so a bigger site needs a second import that starts at the missing section; it still counts as the same knowledge source. The importer reads published HTML without running scripts, so text that only appears after JavaScript runs must be uploaded or added as Q&A pairs. And the Free plan has one member, so a team sharing the inbox needs Starter, with 3 members, or Growth, with 10. PepoChat is also a web widget and hosted chat page only; if your customers write on WhatsApp or Instagram, a tool with those channels will save you more time than any setup shortcut.

What to do next

• Put five sessions in your calendar for next week using the day-by-day plan above, and keep day 3 for the full test script.
• Before day 4, read how human handoff should actually work, so the handover carries the context a person needs.
• To follow the plan on PepoChat, create a free workspace: no credit card, and the test drawer, human handoff and integrations are on every plan, including Free.