Launching an AI website assistant is not a single step but a short project: gather content, connect an AI provider, test, configure booking and handover, install the widget and watch the first weeks. Done in order, it takes an afternoon of work and a few minutes a week afterwards. Done out of order, you launch an assistant that guesses. This guide is a complete runbook, with the exact stages, the checks at each one and the mistakes that cause most bad launches. Where steps are specific to Crescelo we say so; the plan applies to any product.
Overview: seven stages
| Fase | Goal | Typical time |
|---|---|---|
| 1. Prepare content | Documents that answer real questions | 1 to 2 hours |
| 2. Create the assistant and add knowledge | Assistant reading your content | 20 minutes |
| 3. Connect an AI provider | Model that writes replies | 10 minutes |
| 4. Test in a private area | Confidence that answers are right | 1 hour |
| 5. Configure booking, leads and handover | Actions that turn chats into business | 30 to 60 minutes |
| 6. Install the widget | Assistant live on your site | 10 minutes |
| 7. Review and improve | Accuracy that grows | 15 minutes a week |
Stage 1: Prepare your content
Content decides quality more than any setting. Gather what you already use to answer customers, then improve it.
- Collect your price list, service descriptions, policies, opening hours, FAQ and terms.
- Read each document critically: remove anything out of date, resolve conflicts between documents and make sure each service has a name, a price or range and what is included.
- List the ten questions your team answers most often and check each is answered in writing.
- Write down what the assistant must never say: advice you are not qualified to give, discounts you have not approved, guarantees.
- Split large documents into short, clearly titled pages.
More detail on writing for retrieval is in preparing your service menu and pricing documents and document chunking strategies.
Stage 2: Create the assistant and add knowledge
In Crescelo, start a free trial, then open the dashboard. In the Knowledge Base you can upload files, paste text or add your website address. Give the assistant a name, a greeting and a tone. Keep the greeting short and specific to the job, for example 'Ask about our services or book a time'. If you offer bookings, say so.
- Upload documents one topic at a time so you can see each was read.
- Add your website address if your site already holds the answers; check that the pages were read correctly.
- Note which sources you added and when, so you know what to refresh later.
Stage 3: Connect an AI provider
Crescelo uses a bring-your-own-key model: paste a key from a provider such as OpenAI, Anthropic, Google, Groq or DeepSeek, and the provider bills you directly, with no markup. A free engine is available to start and test. If you connect your own, create a dedicated key for this assistant, set a spending limit with the provider and store the key only in the assistant's AI settings. See which AI model to connect and BYOK versus bundled pricing.
Stage 4: Test before anyone else sees it
Use the Testing Studio, the private area inside the dashboard. Treat it as a customer would.
| Test | What to check |
|---|---|
| Ten common questions, in different words and with typos | Correct, complete answers |
| Three questions your content cannot answer | It says it does not know and offers a person or a form |
| A request for a discount or guarantee | It declines and does not promise |
| A booking | Real times, confirmation and email |
| A request for a person | Your team is notified |
| A question in another language you serve | Understandable and correct answer |
| A rude or off-topic message | Polite, brief, back on topic |
Fix each failure by improving the source content, not by piling instructions on the assistant. Retest after each change. See how to stop a chatbot from making things up and the ten questions every service business chatbot should answer well.
Stage 5: Configure the actions
Prenotazione di appuntamenti
On the Growth plan and above, turn on booking, set your opening hours and slot length, or choose Calendly or Cal.com if you need more complex scheduling, and subscribe to the calendar feed so bookings appear in your own calendar. Test two people choosing the same slot. See AI appointment booking and configuring calendar sync and availability rules.
Acquisizione di lead
Decide what you need from a lead: usually a name, a way to reach them and what they want. Turn on instant email alerts, and, if you use them, webhooks or CRM delivery. See conversational lead capture.
Handover
Set who is notified when a visitor asks for a person, and how. Decide which topics always hand over: complaints, emergencies, anything about money or safety. See live human handover flow design.
Honesty and privacy
Make sure the chat says it is an AI assistant and links to your privacy policy. See the GDPR checklist for website chatbots if you serve people in Europe.
Stage 6: Install the widget
Copy the embed snippet from the Overview page (Add to website) or the Deploy button in the top bar, and paste it just before the closing body tag of your site. Platform-specific steps are in the guides for WordPress and Webflow, Squarespace and Wix, and the general version is in how to add an AI chatbot to your website.
- Publish the change.
- Open the live site in a private window.
- Ask two questions and try a booking.
- Check on a phone.
- Check page speed before and after.
Stage 7: The first 30 days
| Quando | What to do |
|---|---|
| Day 1 | Read every conversation; fix errors immediately |
| Days 2 to 7 | Read conversations daily; add answers for unanswered questions |
| Week 2 | Check bookings and leads; confirm emails and alerts work |
| Week 3 | Review handover requests; adjust rules |
| Week 4 | Compare with your baseline; decide what to improve next |
Set a recurring ten-minute weekly review. See how to review your chatbot's conversations each week.
Go-live checklist
- Content reviewed and current.
- Ten common questions tested; three unanswerable questions tested.
- Discount and guarantee requests declined.
- Booking tested end to end, including a clash.
- Confirmation emails arrive.
- Handover notifies the right person.
- AI disclosure and privacy link visible.
- Tested on phone and desktop.
- Page speed checked.
- Weekly review scheduled.
Common launch mistakes
- Skipping content preparation.
- Testing only the questions you expect.
- Forgetting to test booking failures.
- Not telling anyone on your team how handover works.
- Hiding the widget on mobile by accident.
- Launching on every page without checking the main ones.
- Never reading conversations.
If something goes wrong
Removing the snippet from your site removes the assistant instantly, and your content and conversations stay in your dashboard. Keep a note of what you changed so you can undo it. If answers are wrong, correct the source content and retest before restoring.
A sample test script you can copy
Print this and tick each line as you test. It takes about forty minutes.
| # | Test | Pass if |
|---|---|---|
| 1 | Ask 'How much is [your main service]?' | Correct price and what is included |
| 2 | Ask the same in different words with a typo | Same correct answer |
| 3 | Ask about your opening hours on a holiday | Correct, or says it does not know |
| 4 | Ask something your content never mentions | Admits it does not know and offers a route |
| 5 | Ask for a discount | Declines politely |
| 6 | Ask it to confirm you a same-day appointment when none exists | Does not promise; offers real times |
| 7 | Book two appointments at the same time from two windows | Only one succeeds |
| 8 | Ask for a person | Team notified with the conversation |
| 9 | Type an angry message | Calm reply and a route to a person |
| 10 | Open the site on a phone | Chat fits and is usable |
Who should own the assistant
Name one person as owner. Their job is small but important: read the weekly conversations, keep the documents current, answer handovers quickly and decide when to change rules. Without an owner, an assistant slowly goes stale. In a small business the owner is often the same person who wrote the price list. Give them ten minutes in their calendar every week.
What to tell your team
- What the assistant will and will not do.
- How they will be notified when a visitor wants a person.
- Where to see conversations and bookings.
- How to correct a wrong answer.
- What to do in an emergency message.
A short briefing prevents confusion and makes staff allies of the assistant instead of skeptics.
Five days instead of one afternoon
If you prefer to spread the work, this schedule keeps each day light and gives you time to think between steps.
| Giorno | Work |
|---|---|
| Monday | Collect and clean your documents; write the ten common questions |
| Tuesday | Create the assistant, load content and connect the AI provider |
| Wednesday | Test with the script and fix content gaps |
| Thursday | Configure booking, lead alerts and handover; brief your team |
| Friday | Install the widget, run the live checks and watch the first conversations |
A staged launch also gives you a natural stopping point: if Wednesday's tests fail, delay Friday. There is no prize for launching early with wrong answers.
Frequently asked questions
How long does it take to deploy an AI website assistant?
A small business can be live in an afternoon: an hour or two for content, an hour for testing and configuration and minutes for installation.
Do I need a developer?
Not for a standard site. You paste one snippet into your site's settings or footer.
What should I test before going live?
Common questions, questions your content cannot answer, discount and guarantee requests, a booking, a handover and the mobile view.
What happens if the assistant gives a wrong answer?
Find the source passage or missing document, correct it and retest. Weekly review catches these early.
Can I turn it off quickly?
Yes. Remove the snippet and it disappears from your site at once; your data stays in the dashboard.
How much time does it need after launch?
About ten to fifteen minutes a week to review conversations and update content.
Rehearse the first stages in the playground without an account, then start a free trial. The help centre has product guides for each step.
Further reading
- Google Search Central: creating helpful, people-first content: What Google looks for in useful pages.
RISPONDI A OGNI VISITATORE. PRENOTA CHI È PRONTO.
Installa Crescelo sul tuo sito in 15 minuti
Addestra il tuo assistente sui tuoi listini, documenti e condizioni di servizio. Attiva risposte fondate sulle tue fonti 24 ore su 24 e prenotazioni in chat senza sovrapposizioni.