A website with real content
The main input is your existing pages — products, services, FAQs, policies. If your site is thin on content, the chatbot will only be as good as what it can read, so a quick content review is worth doing first: are your pricing, hours, and policies actually written down clearly anywhere, or do they only exist in your head or in past email replies?
This audit alone is often useful independent of the chatbot project — it frequently surfaces gaps in your site content that were worth fixing regardless.
Permission to add the snippet
You'll need whatever access lets you paste a snippet into your site — a theme editor, a header/footer plugin, or your CMS's custom-code settings. If that's not you personally, it's a five-minute favor from whoever does have that access, not a development task requiring a project brief.
A short list of your top visitor questions
Even a rough mental list of the five questions you get asked most is enough to know what to test once the bot is live, and where to add FAQ entries if the automatic crawl misses anything. You probably already know this list without writing it down — it's whatever you find yourself explaining to customers over and over.
A little time in the first week for review
Not a large time commitment, but plan to spend fifteen or twenty minutes sometime in the first week reading through early conversations. This is where most of the genuine 'setup' value happens — not in the initial installation, which takes minutes, but in the light-touch refinement afterward.
That's genuinely it
No developer, no multi-week implementation project, and no dedicated project manager are required to get started — you can use the one-time trial shown at checkout and decide from real usage whether a paid package fits.
