How to Set Up a Chatbot in 5 Minutes
A practical, no-code guide for small business owners. Six clear steps, real examples, and a checklist — no coding, no developer, no APIs. Just a website and the answers your customers already ask you every day.
Updated 12 min read
Before you start
You don't need much. You need a website (it doesn't matter which platform — WordPress, Wix, Shopify, Squarespace, or hand-written HTML), a few facts about how your business works, and about forty-five minutes of focused time. The "five minutes" in the title is the live-it part — pasting one line of code and watching the chat bubble appear on your site. The rest is the iteration that turns a generic bot into one your customers actually like talking to.
What you do not need:
- A developer
- An API key
- A coding background
- A budget — you can complete every step in this guide on a free account
Have these in front of you before you start:
- The login to your website's admin area (so you can paste the embed code in Step 5)
- A list of the ten most common questions your customers ask you (we'll explain why in Step 1)
- Any PDFs you already use — a menu, a brochure, a price list, a service catalog
- A sense of your business's tone: do you speak to customers casually, formally, with humor?
That's it. Let's begin.
Step 1 — Define your chatbot's purpose
Before you touch any settings, decide what the chatbot is supposed to do. A vague "answer customer questions" produces a vague bot. A specific purpose produces a useful one.
For most small businesses, the chatbot serves one of three goals:
Answer frequently asked questions. Hours, location, prices, delivery zones, return policy, what services you offer. This is the most common purpose and the easiest to set up. The bot becomes a 24/7 receptionist that never gets tired of repeating itself.
Capture qualified leads. Visitors land on your site, browse, then leave. The bot can step in, answer their first question, then offer to take their name and email so you can follow up. Done right, this turns five anonymous visitors a day into one warm lead — which over a year becomes a meaningful pipeline.
Help with bookings or orders. Restaurants take reservations, hair salons schedule appointments, consultants book discovery calls. The bot can collect the basics (date, party size, service) and either save the request or hand off to a real person.
You can do all three at once, but pick a primary purpose. The bot's tone, its welcome message, and the knowledge you give it all flow from that decision.
Step 2 — Choose your knowledge source
A chatbot is only as smart as what it knows. Simple Chat gives you three ways to teach it — pick one or combine them.
Option A — Start from an industry template. Simple Chat ships with templates for 52 industries, from pizzerias to dental clinics to real-estate agencies. Each template includes a starter knowledge base, a tone preset, and a set of suggested questions tailored to that business. If your business fits one of the templates, this is the fastest way in — about thirty seconds to a working draft. You then refine it with your own information. Browse the templates.
Option B — Paste your text directly. If you already have a clean FAQ document, paste it. The knowledge field accepts plain text or simple Markdown. Use H2 headings like ## Hours or ## Returns to keep sections organized — the bot picks up that structure naturally.
Option C — Upload a document. This is for businesses that already have a menu, a brochure, a service catalog, or a price list. Simple Chat accepts PDF, DOCX, TXT, Markdown, plus spreadsheets (XLSX, XLS, CSV) — useful when your prices or inventory live in a sheet. The extractor pulls the text and adds it to the knowledge base. The hard limit is 5 MB per file, which fits most menus, brochures, and short catalogs; longer documents you'll want to split into separate uploads by topic.
Recommended: combine. Start with a template for the structure and tone, paste your FAQs for current info (hours, prices), upload your menu or catalog for product detail. Three sources, layered, give the bot enough to answer almost any question without inventing facts.
| Source | Speed | Best for | Maintenance |
|---|---|---|---|
| Template | ~30 sec | Trying it out, generic starter | Replace with your own copy |
| Paste text | 2 min | Tight FAQ, short knowledge base | Edit in place |
| PDF / DOCX upload | 1 min | Menus, catalogs, brochures | Re-upload when the product changes |
| Combined | 5 min | Production-ready bots | Update each piece independently |
What to avoid in your knowledge base:
- Outdated info. Old prices, removed services, expired offers. The bot doesn't know these are stale; it'll cheerfully tell a visitor your gym was open at 6 a.m. in 2019.
- Internal jargon. Codes, SKUs, system names your customers wouldn't recognize. The bot will quote them.
- Contradictions. If two sections say different things ("delivery free above €30" and "delivery always €4.90"), the bot may pick either. Read the knowledge top-to-bottom once and resolve conflicts before you publish.
Step 3 — Configure personality and tone
A chatbot has a voice whether you choose one or not. Defaults sound generic and forgettable. Two minutes spent picking a tone is the difference between a bot visitors talk to and a bot they ignore.
Match your business. A pizzeria doesn't sound like a notary's office:
- Pizzeria: "Ciao! 🍕 What can I get you tonight?" — friendly, casual, a single tasteful emoji
- Law firm: "Good afternoon. I can help you find information about our practice areas or schedule a consultation." — formal, professional, complete sentences
- E-commerce: "Hey, looking for something specific? I can find it or help you compare." — direct, helpful, sales-aware
- Pediatric clinic: "Hi! I can help with appointments, vaccinations, and our usual visit hours. For emergencies please call our line." — warm but cautious, with a clear escalation note
In Simple Chat, you customize the bot's display name, its avatar, the brand color (this drives the chat bubble, header, and suggested-question pills), the chat-bubble position (bottom-right or bottom-left), the welcome message, three suggested questions visitors can tap, and a fallback message for when the bot doesn't have an answer.
Welcome message templates that work:
"Hi! I'm Tessa, the bot for {your business}. I can help with orders, returns, or finding the right product. What are you looking for today?"
"Welcome! Ask me anything about our menu, our hours, or booking a table. I'm here 24/7."
"Hello — I'm here to answer the quick questions. If I can't help, I'll connect you to {owner name} within a business day."
The fallback message — don't skip this. When your bot doesn't know the answer, it shouldn't guess. Give it a graceful fallback like: "I don't have that one. Want me to pass you to {your team / owner / email}? Tap Talk to a human in the chat menu." In Simple Chat, on Advanced and Ultra tiers an inline handoff chip appears under that reply automatically — the visitor taps it and fills a short form that lands in your inbox.
Step 4 — Test with real questions
The temptation is to set the bot live, see how it does with real visitors, and fix as you go. Don't do this. Real visitors are not patient. A bot that hallucinates an answer in its first week loses trust you don't get back easily.
Simple Chat has a sandbox built into the dashboard. You get fifteen test chats per bot per day — free, without burning your credit balance. Use them.
The ten-question test framework. Run these through the sandbox before you embed:
- Easy: "What are your opening hours?" — should be exact
- Easy: "Where are you located?" — should give the address
- Medium: "Do you deliver to {nearby neighborhood}?" — should know the zone or politely admit it doesn't
- Medium: "How much is a {your second-most-popular product}?" — should be exact
- Hard: "I have an allergy to {ingredient/material}, what can I order/buy?" — should answer carefully or escalate
- Hard: "Can I cancel my booking the day before?" — needs the policy
- Off-topic: "What's the weather today?" — should decline gracefully, not pretend to know
- Off-topic: "Tell me a joke." — should stay in character (or play along briefly and return to topic)
- Emotional: "I had a bad experience yesterday." — should acknowledge, then offer the handoff
- Stress test: a long, multi-part question — "I want to know if you're open on Sunday AND if you deliver to {zone} AND what the smallest pizza costs." — should answer all three parts
What a good answer looks like. Short. Direct. Quotes your knowledge base, doesn't invent. Switches to "I'm not sure — let me connect you" when uncertain. Sticks to the tone you set in Step 3.
What to fix before going live:
- Any wrong fact — track it back to the knowledge base and correct it
- Any hallucination — add a clear "I don't know" rule to the instructions
- Any tone slip (the law-firm bot saying "no worries!") — refine the personality prompt
- Any off-topic answer the bot actually tried — strengthen the boundary rule
Two iterations through this framework usually get a bot from "alpha" to "production-ready."
Step 5 — Embed on your website (the five-minute part)
This is the part the title promises. One line of JavaScript, pasted in one place on your site.
In Simple Chat, the Install tab gives you the snippet — it looks roughly like this:
<script src="…" data-bot-id="…" async></script>
You paste it once. The script asynchronously loads a small loader (under 5 KB compressed), which mounts the chat bubble in the corner of your site. No layout shift, no slowdown, no impact on your SEO.
Where to paste: right before the closing </body> tag of every page where you want the bot to appear. Most websites let you add this once and it propagates site-wide.
- WordPress — Appearance → Theme File Editor →
footer.php, just before</body>. Or, if you don't want to edit theme files, install a free "Header & Footer Code" plugin and paste it in the "Before </body>" field. On block themes, use the Site Editor → Footer template part. - Wix — Settings → Custom Code → Add Custom Code → choose "Body — end" location. Apply to all pages.
- Shopify — Online Store → Themes → Edit Code →
theme.liquid, find</body>near the bottom of the file, paste your snippet just above it. - Squarespace — Settings → Advanced → Code Injection → Footer. Paste there; it applies site-wide.
- Webflow — Site Settings → Custom Code → Footer Code. Paste, then publish.
- Plain HTML site — open each page's HTML and paste before
</body>. If you use a shared include file, paste it there once.
Verify the install: open your site in a private/incognito window (so cached versions don't fool you). You should see the chat bubble appear in the corner within a second of the page loading. Click it. Send a test message. If it answers, you're live.
Step 6 — Monitor and improve
Going live is the start, not the finish. Your bot will answer beautifully ninety percent of the time and oddly the other ten — and the only way to fix the ten is to look at what visitors actually asked.
First week — check daily. In the Simple Chat dashboard, the Conversations tab shows every chat. Skim them. Look for:
- Knowledge gaps — questions the bot couldn't answer. These are gold. Add the answer to the knowledge base; the bot is one upload away from being smarter.
- Wrong answers — rarer if your Step 4 test was thorough. When you spot one, trace it to the knowledge source and fix it there.
- Off-topic visitors — people asking things you don't want the bot to handle. Strengthen the bot's instructions to deflect politely.
- Lead opportunities — visitors who showed buying signals but didn't book. Consider enabling lead capture if you haven't already.
First month — weekly review. Same checks, less frequent. By week four, the bot should answer 70–80% of questions correctly.
After that — monthly check. Open the Analytics tab. Track:
- Conversations per week — is the bot getting traffic?
- Average messages per conversation — five to eight is healthy; under three and visitors are bouncing, over fifteen and the bot may be confusing them
- Lead capture rate — leads ÷ conversations (typical: 8–15% for B2B, 3–8% for B2C)
- Escalation rate — handoffs ÷ conversations (typical: 5–10%; if it climbs, your knowledge has gaps)
The bot gets better the more you look at it. Five minutes a week, every week, for the first three months. Then ten minutes a month forever after.
Common mistakes to avoid
After looking at hundreds of small-business chatbots, three mistakes show up over and over.
Mistake 1 — A generic welcome message. "Hi, how can I help you?" is the chatbot equivalent of a sales clerk staring at the floor. Visitors freeze; they don't know what the bot can do, so they don't try. A specific welcome — "Ask me about our menu, our hours, or booking a table" — gets visitors past the first message and into a real conversation.
Mistake 2 — No fallback or no handoff. Every bot will, eventually, hit a question it can't answer. The bots that lose visitors say "I'm sorry, I don't understand" and stop. The bots that keep visitors say "I'm not sure — let me connect you to someone who knows." Enable the handoff (it's one toggle in the Behavior tab) and write a fallback message you'd be happy to read yourself.
Mistake 3 — Never reviewing conversation logs. This is the silent killer. The bot drifts; the business changes (new hours, new prices, new services); the knowledge base goes stale. Owners who don't look at their conversations find out months later that the bot has been giving wrong answers — usually when a customer mentions it. Set a calendar reminder for the first month.
When to upgrade beyond basic setup
A simple FAQ bot on a clear-cut business is fine for years. But three signals tell you it's time to scale up.
You have international visitors. Simple Chat detects the visitor's language automatically and replies in it — turn on "Reply in the visitor's language" in the Behavior tab. The bot handles all the major business languages the underlying AI model supports. No extra setup; the same knowledge base in English serves visitors who write in French, German, Portuguese, and so on.
Your product is complex. Pizzerias do well on the Smart tier. A SaaS company explaining tiered pricing, integrations, and edge cases probably needs Advanced or Ultra. Simple Chat has four model tiers — Simple, Smart, Advanced, Ultra — that you can switch on a single dropdown. Heavier reasoning costs more credits per chat but answers harder questions more reliably. See the credit cost per tier.
You're running more than one bot. Multi-site businesses, agencies, or franchises usually want a bot per location or per brand. Simple Chat supports up to three bots on every paid plan. Need more domains for the same bot? The Extra Domain add-on lets a single bot serve multiple sites.
You want to remove our branding. The free "Powered by getsimplechat.com" footer in the chat goes away with the White-label add-on. Useful if you're embedding on a client's site and don't want a vendor reference.
These are not "you must upgrade" moments. They are "you can." The basic setup is enough for many years of operation, especially if your bot's main job is answering FAQs.
Recap and next step
Six steps. Five minutes to live, an hour or so to iterate, and a sustainable bot for the years after that. To recap:
- Define the purpose. FAQs, leads, or bookings. Write your top ten questions.
- Pick a knowledge source. Template, paste, upload, or combine.
- Set the tone. Match your brand voice; write a specific welcome.
- Test with the ten-question framework. Sandbox is free.
- Embed one line of JavaScript before
</body>. - Review conversations weekly for the first month.
You can do every step on a free Simple Chat account. You get fifty credits when you sign up — no credit card needed — which is plenty to launch the bot, test it, and run real conversations for the first week.
Want to try as you read?
Simple Chat gives you 50 credits free, no credit card required. Enough to launch and run real conversations for your first week.
Frequently asked questions
Can I set up a chatbot without coding?
Yes. Every step in this guide is no-code. You configure the bot in a dashboard, then paste a single line of JavaScript on your site (and even pasting is optional — most CMSes have a "custom code" or "footer code" field where you do not touch the HTML at all). No APIs, no developer, no command line.
How long does it really take?
Five minutes to get the bot live with default settings. Another twenty to thirty to test, refine the tone, and patch obvious knowledge gaps. After that, a few minutes a week reviewing what visitors actually asked.
Will the bot understand my customers' questions?
For most everyday business questions, yes — modern AI chatbots understand natural language, including typos, slang, and questions phrased indirectly. The bot will struggle with topics it has no knowledge about (questions outside your knowledge base, niche industry jargon you have not taught it). That is why the ten-question test framework in Step 4 matters: it surfaces the gaps before visitors do.
What if my chatbot answers something wrong?
You fix the knowledge base, not the bot. Open the Conversations tab, find the wrong answer, trace it to the source content, correct it, save. The next time a visitor asks the same question, the bot answers correctly. Keep an eye on the first week; after that, wrong answers become rare.
Do I need to pay before I can try Simple Chat?
No. Sign up and you get fifty credits free — enough to test the sandbox and run real conversations on your live site. No credit card on file. Paid plans start at $20/month and only kick in when you have outgrown the free trial.