Make a Chatbot by Picking Its First Job: Four Bot Recipes for Small Businesses, From Job Sentence to Test Questions (Free Recipe Builder)

Make a chatbot that does one job well before you ask it to do ten, and you will have something useful live by this evening. Most first bots fail because they try to answer everything, book everything and sell everything on day one. This guide gives you four recipes, one per job: answering common questions, catching enquiries when nobody is free, collecting booking requests and helping visitors choose. Each recipe has a job sentence, a welcome line, the first answers to write, a handover list, a Flow and a test script. A free tool writes the recipe for your business type.

4recipes, one per job
1job per bot to start
5–6answers to write first
90 min+typical first build

⚡ In short

  • Give your first bot one job. Write it as a single sentence before you touch any settings.
  • Pick from four jobs: answer common questions, catch enquiries, collect bookings or guide choices.
  • Each job needs a different welcome line, different first answers and a different Flow.
  • Every recipe ends the same way: a list of things the bot always hands to a person, and a test script.
Make a chatbot in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them
How it looks in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them.

Why one job

The bot that tries to do everything does nothing well

Picture a small clinic owner on a Sunday afternoon. She signs up for a chatbot tool, opens the builder and starts typing. Timings. Prices for twelve services. A booking flow. A section on insurance. A product recommender for the skincare range. A feedback survey. By evening she has forty half-finished answers, three flows that overlap, and a bot that greets visitors with a menu of nine buttons. Nobody uses it, and by Wednesday she has switched it off.

The problem wasn’t the tool or her effort. It was scope. A bot with no clear job can’t decide what to say first, which questions matter, or when to step aside. Visitors feel that. A menu of nine options asks them to do the sorting work the bot was meant to do.

Compare that with a bot built around one sentence: “This bot will collect booking requests with the date, time and contact needed to confirm them.” Every decision follows from it. The welcome line invites a booking. The first answers cover what people ask before booking: timings, prices, location. Anything else, like a medical question or a complaint, goes to a person. The test script checks that bookings come through complete.

That bot is smaller, but it works on day one. Once it does, adding a second job is easy, because you’re extending something that works instead of fixing something that doesn’t.

So before you open any builder, decide the first job. The rest of this guide shows how to choose it, then gives you a recipe for each of the four jobs most small businesses start with.

The four jobs

Which first job fits your business?

Most small-business bots start with one of these. Pick the one that solves your biggest daily headache.

💬

Answer common questions

Best when the same five or six questions arrive every day: timings, prices, delivery, location. The bot saves your team from typing the same replies.

📥

Catch enquiries when nobody is free

Best when you lose leads after hours or while busy with customers. The bot’s job is to make sure nobody leaves without leaving a contact.

📅

Collect booking requests

Best for clinics, salons, tutors and service businesses. The bot gathers service, day, time and phone so you can confirm in one call.

🧭

Help visitors choose

Best when you sell several similar options and visitors get stuck. The bot asks two or three questions and points to the right one.

Step 1

Before you make a chatbot, write its job sentence

Open a notes app and write one sentence that starts with “This bot will”. It should name one job, for one kind of visitor, and say what happens to everything else.

Good job sentences are specific:

  • “This bot will answer delivery, COD and return questions for shoppers, and pass order problems to our team.”
  • “This bot will take down every enquiry after 7 pm, so nobody leaves without a reply by 11 am next day.”
  • “This bot will collect hair and skin appointment requests with day, time and phone.”
  • “This bot will ask budget and location, then point buyers to the right three listings.”

Weak job sentences are vague: “This bot will help customers” or “This bot will improve engagement.” They don’t tell you what to write first or when to hand over.

The job sentence does three things for you. It decides the welcome line: a bot that collects bookings should invite a booking, not ask “How can I help?” It decides your first answers: only the questions that sit on the path to that job. And it decides what the bot refuses: anything outside the job goes to a person or the away form.

Keep the sentence somewhere you’ll see it while building. Whenever you’re tempted to add something, check it against the sentence. If it doesn’t serve the job, write it on a “later” list instead.

If you’re not sure which job to pick, look at last week’s messages on WhatsApp, email and phone. Our guide to building a chatbot from questions you already get shows how to group them; the biggest group usually points to the first job.

Free tool

Write your bot’s build recipe

Choose your business type, the first job and your team’s hours. You’ll get a job sentence, welcome line, first answers, handover list, Flow and a test script to adapt.

Pick your business, the one job you want the bot to do first, and when your team is around. The tool writes a one-page build recipe: the bot’s job sentence, a welcome line, the first answers to write, what to hand to a person, the Flow to set and the questions to test with.

Business type

The bot’s first job

When someone from your team can reply

Runs only in your browser; nothing is sent or saved. Example wording is illustrative: replace it with your real prices, hours and policies.

Recipe 1

Make a chatbot that answers your top questions

This is the most common first job, and the easiest to get right, because you already know the answers.

Job sentence: “This bot will answer the questions customers ask most, and pass everything else to a person.”

Welcome line: name the two most-asked topics so visitors know what to type. For a shop: “Hi! Ask me about delivery, returns or anything else. I answer straight away, and our team picks up anything I can’t.” Naming topics works better than a blank “How can I help?” because it shows the bot is useful before the visitor commits.

First answers: five or six, no more. For each, write one to three sentences with the key fact first. “We deliver across India in 3 to 6 working days. Orders above ₹999 ship free.” (Illustrative figures.) Use your customers’ words, including Hinglish if that’s how they write.

Hand over: anything about a specific order, payment, or complaint. These need someone to look something up.

Flow: a proactive message on your two busiest pages after about 20 seconds, asking about the top topic.

Where answers go in LiveChatBot: put them in the AI Agent’s knowledge so it can answer in its own words, and save the same text as saved replies so the free keyword bot can still answer when AI replies aren’t available. Our guide to training your AI chatbot covers writing knowledge it can use.

You’re done when every one of your top questions gets the right answer in a test, and order questions hand over cleanly.

Recipe 2

The enquiry catcher

Many small businesses don’t need a bot that answers much at all. They need one that makes sure nobody leaves without leaving a way to reach them. If you’ve ever opened your phone at 9 am to find a “hello?” from 11 pm with no number, this is your recipe.

Job sentence: “This bot will take down every enquiry while the team is busy or away, so nobody leaves without a reply.”

Welcome line: be honest about timing. “Hi! Tell us what you need and leave your phone or email. We’ll reply as soon as we’re back.” Don’t pretend someone is about to answer if they aren’t.

First answers: fewer than Recipe 1. The most important one is when you reply: “We reply to messages left after 7 pm by 11 am the next working day.” Add two or three quick facts people ask before leaving a contact, such as your area or starting price.

Hand over: almost everything. The bot’s skill here is collecting, not answering.

Settings that matter: opening hours with the away form switched on, so visitors outside hours are asked for an email or phone. Offline messages can become tickets, so they don’t get lost in a busy inbox; see turning a chat into a ticket.

Flow: a proactive message on your contact or pricing page, where people are closest to asking.

You’re done when you leave a test message after hours from your own phone, and it arrives with a contact attached and lands where your team will see it first thing.

Recipe 3

The booking collector

Clinics, salons, tutors, repair services and restaurants all share one pattern: a visitor wants a slot, and you need four facts to confirm it. The bot’s job is to collect those facts in a friendly way, so your team can confirm in one call instead of five messages.

Job sentence: “This bot will collect booking requests with the service, day, time and contact needed to confirm them.”

Welcome line: invite the booking directly. “Hi! Want to book? Tell me the service and the day you prefer, and we’ll confirm by phone.”

First answers: the questions people ask just before booking. Timings and days open. Services and starting prices. How far ahead to book. Location and parking. What to bring. One more answer is unique to this recipe: what details you need to confirm, so the bot can ask for them in one go.

Hand over: rescheduling an existing booking, complaints, and anything needing professional judgement. A clinic bot must never answer a question about symptoms; it should pass it to the clinic.

Be honest about confirmation. Unless your booking system is connected, the bot collects a request, not a confirmed slot. Say so: “We’ll call to confirm your time.” Promising a slot you can’t guarantee causes more trouble than it saves.

Flow: a proactive message on your services or booking page.

You’re done when a test booking arrives with all four facts, and a medical or complaint question goes straight to a person.

Example

One booking chat, before and after the recipe

👤 What the visitor seesBooking collector (illustrative salon)
hi can i book for tomorrow
🤖 AI AgentSure! Which service would you like, and do you prefer morning or evening?
hair spa evening
🤖 AI AgentHair spa starts at ₹1,200 and takes about an hour. Is 5 pm or 6 pm better for you?
6
🤖 AI AgentGreat. Please share your phone number and we’ll call to confirm 6 pm tomorrow.
98xxxxxx10
Request saved: hair spa · tomorrow · 6 pm · phone shared

Four short turns and the team has everything needed to confirm. Prices and times are illustrative.

Recipe 4

The option guide

This recipe suits businesses with several similar products, plans or courses, where visitors get stuck choosing. A coaching institute with six batches. A shop with four mattress types. A builder with three projects in different budgets.

Job sentence: “This bot will ask two or three questions and point visitors to the option that fits them.”

Welcome line: offer the help explicitly. “Hi! Not sure which one is right for you? Answer two quick questions and I’ll suggest one.”

First answers: start with the questions that split your options. Usually two are enough: budget and purpose, or class and subject, or location and size. Then write one short summary per option: who it’s for, the price, and one reason to pick it. Keep it to the options you actually want to recommend.

Hand over: price negotiation, special cases and anyone who has answered the questions but still isn’t sure. A person can close those far better than a bot.

Keep it short. More than three questions and people drop off. If you need more detail, the person who picks up the chat can ask.

Flow: target visitors who look undecided, for example those viewing several product or course pages in one visit. Our guide to creating a chat flow explains page and visit conditions.

You’re done when a test visitor who answers both questions lands on the right option every time, and anyone asking to negotiate goes to a person.

Compare

The four recipes side by side

Question answererEnquiry catcherBooking collectorOption guide
Main settingAI Agent knowledge and saved repliesOpening hours and away formAnswers plus contact requestTwo splitting questions
First answers5–6 top questions2–3 facts plus reply timePre-booking factsOne summary per option
Hands overOrder and payment issuesAlmost everythingReschedules, complaints, adviceNegotiation, special cases
Success checkRight answer to every top questionEvery after-hours message has a contactRequests arrive with all 4 factsRight option every time

Step 2

Test, launch, then add the second job

Whichever recipe you follow, testing works the same way. Use the exact messages from the test script, typos included, from your phone and a laptop. Then try three messages that should hand over, such as “real person please” and a complaint. Fix any wrong answer before you fix a missing one, because a confident wrong answer hurts more than “Let me get someone for you.”

Launch quietly. Put the bot live, tell your team, and read every chat for the first week. You’ll spot wording customers use that you didn’t expect, and questions the bot should hand over sooner.

After a week or two of the first job working, add the second. A question answerer can grow into a booking collector. An enquiry catcher can start answering the two questions people ask before leaving a contact. Each new job gets its own job sentence, answers and test script, and the old test script stays, so you know nothing broke. Our simple chatbot guide shows how small a useful bot can be, and the chatbot builder targeting guide explains how to show different messages to different visitors once you have more than one job.

One rule doesn’t change as the bot grows: it should always be easy to reach a person. Keep that path open at every stage, and keep each new job small enough to test in an afternoon. If you want to make a chatbot that keeps working a year from now, that habit matters more than any feature.

Checklist

Before you switch it on

Recipe progress

Getting started

Choose your recipe and build it today

Run the recipe builder above, copy the result into your notes, and edit the wording until it sounds like you. Then sign up, paste the chat code on your site and add your answers.

LiveChatBot’s free plan includes the AI Agent with a small free monthly allowance, a free keyword bot that answers from saved replies, Flows, opening hours with an away form, tickets, the team inbox and the Android app, for two websites with 100 visitors per website each month. See pricing, or start at livechatbot.in.

Frequently asked questions

How long does it take to make a chatbot with one of these recipes?

About 90 minutes for the enquiry catcher or booking collector, around two hours for a question answerer and about three for an option guide. Most of the time goes into writing short, accurate answers.

Can one bot do more than one job?

Yes, later. Start with one job, get it working and tested, then add a second with its own answers and test script. Starting with several at once is the most common reason first bots fail.

Do I need to write code?

No. You paste one chat code snippet on your site, or install the WordPress plugin, then set everything else in the dashboard: answers, saved replies, Flows and opening hours.

What if the bot can’t answer something?

It should hand over to a person during your hours, or collect a phone or email through the away form when nobody is online. Keep that path easy to find.

Can the bot confirm bookings automatically?

Not on its own. Unless a booking system is connected, the bot collects a request with the details and your team confirms it. Tell visitors that, so expectations are clear.

Build your first bot around one job

Pick a recipe, write the answers, and switch on a bot that does one thing well. Start free on livechatbot.in.