WhatsApp Chatbot for Business in 2026: Build One on Your Own Number, No Code

Customers ask the same questions on WhatsApp every day: opening hours, the price of a service, whether you can fit them in on Thursday. A WhatsApp chatbot takes that first reply, so the question does not sit unread while you serve someone else. Most guides assume you have a developer, a platform contract, or a spreadsheet of canned replies. You need none of those to start.

What is a WhatsApp chatbot for business, and what can it do on your own number?

A WhatsApp chatbot for business is software that reads a message sent to your number and replies without you typing it. It can follow a fixed script, answer from text you provide, or pass the chat to a person. On Blueticks it works with the WhatsApp number your customers already use, through WhatsApp Web, so there is no separate number to set up.

Three things it does well:

• Answers repeated questions from your own text, such as hours, prices, and directions.
• Follows a fixed path, such as asking for a name, then a date, then writing the answer to a Google Sheet.
• Stops and hands the chat to you when a customer asks for something you did not authorise.

The no-code side of this is covered in more depth in our guide to building a WhatsApp agent without code. The rest of this article focuses on the decisions that matter before you switch it on.

Should you use a fixed-script chatbot or an AI agent?

Use a fixed script when every answer is one of a few options. Use an AI agent when customers ask in their own words and the answer lives in the text you wrote. Blueticks gives you both, and a single flow can mix them.

The flow builder can also call a webhook, write to Google Sheets, or drop in an LLM or agent node. That means a flow can collect a booking through fixed questions, then let an agent answer a follow-up. For the API side of webhook replies, see WhatsApp API webhooks for auto-reply. For the wider agent question, see our WhatsApp AI agent comparison.

Can you build a WhatsApp chatbot without code?

Yes. The no-code paths are a visual flow, where you connect steps on a canvas, or an agent you describe in plain words. Neither path asks you to write code. The catch is that no-code removes the setup work, not the thinking. You still decide the answers, the order of the questions, and the moment a person takes over.

Plan the flow on paper before you open the builder. List the questions in the order a customer would ask them, write the answer for each, and mark the three or four questions that need a human. Then build exactly that list. A builder makes it easy to add steps, and that is how bots end up with twelve branches nobody tests.

How do you set up a WhatsApp chatbot on your own number?

Setup is four steps: connect the number, choose which chats it may answer, write the instructions, and turn it on. Keep the first version small. You can widen it once it has handled real questions for a week.

1. Connect the WhatsApp number your customers already message. Basic and Standard run in your browser through WhatsApp Web, so the browser has to stay open for the bot to reply.
2. Choose which chats it may answer. The "Respond to new incoming chats" toggle controls new chats. The allow list is the default, and a block list is available for chats you want excluded. Sending is limited to the chat that triggered it unless you widen the lists.
3. Write the instructions in plain words. Say who the bot speaks for, which facts it can use, and what it must not promise.
4. Turn it on. New agents start paused. Nothing goes out until you press Turn it on.

Failure mode: the browser is closed. The agent replies to inbound messages that a live engine receives. On Basic and Standard, that engine is your browser. If you close the tab, do not expect replies. Check the plan table below before you rely on a browser plan for evening or weekend traffic.

How do you test it from a second phone before a customer sees it?

Test on a second phone with a short list of questions before any real customer writes in. Send one question the bot should answer from your text, one it should not answer, and one off-topic message. Compare each reply against your instructions line by line. Only open the allow list to real chats after all three behave.

1. Restrict the allow list to your test phone. Sending is limited to the triggering chat, so this keeps everyone else out of the test.
2. Send the three questions. One answerable from your text, one with an answer you did not write down, and one off-topic.
3. Check each reply against your text. Any detail that is not in your instructions is a gap. Add it, or add a rule that stops the bot guessing.
4. Widen the allow list only after a clean run.

Failure mode: a test that passes once. One good reply proves little. Run the same three questions the next morning, then again after every edit to the instructions. Bots often pass on Monday and drift after a price change on Friday.

When should the chatbot hand the chat to a person?

Hand the chat to a person when the question involves money, a complaint, a deadline, or anything you did not write down. Blueticks makes that handoff by default: when you write in a chat yourself, the agent stays quiet in that chat until you release it. There is no timer, so the agent does not return on its own.

1. List the handoff triggers. Refunds, complaints, pricing disputes, and anything with a deadline.
2. Write the handoff line into the instructions. For example: "If the customer asks for anything not in this list, say you will pass it to the team."
3. Reply yourself when the chat needs you. Writing in the chat is what pauses the agent.
4. Release the chat when you are done. Type "continue" in your operator chat (the chat where the agent sends you its notices, not the customer's chat) or release it from Conversations, and the agent resumes.

Failure mode: the silent chat. You answer a customer once, forget to release it, and the agent stays silent for that customer until you do. Check your Conversations list at the end of each working day, the same way you check your inbox.

For a related pattern where the agent asks you before it acts, see human-in-the-loop WhatsApp approvals.

What does a WhatsApp chatbot cost per month in 2026?

Blueticks meters AI use in credits. Each plan includes a monthly allowance per user: 250 credits on Basic, 500 on Standard, and 1,000 on Pro. Credits are a shared team balance that renews monthly, and you can buy extra credits at any time. A typical agent reply uses about 2 to 4 credits, so the table below shows a rough reply count, not a guarantee.

Check the Blueticks pricing page for the current plan prices, because those change. The pricing page lists AI credits for Basic, Standard and Pro only, so plan on one of those for the chatbot.

Ready to try it on your own number? Sign up for Blueticks, start with one chatbot, and pick the plan that matches the hours your customers write. It needs no developer setup, and it runs on the number your customers already use.

Where does a WhatsApp chatbot on your own number fall short?

It falls short in three places: browser uptime, account risk, and consent. Basic and Standard need an open browser. Automated messaging is something WhatsApp's own terms restrict, and no setup can promise your number will never be restricted. You also own the consent question for every person you message.

• Uptime. Basic and Standard reply only while the browser is open. Pro runs in the cloud and keeps working when WhatsApp Web is closed.
• Terms. WhatsApp's Terms of Service list auto-messaging among impermissible communications, and they restrict automated access to the Services. Read them before you automate outbound messages.
• Account risk. Blueticks cannot promise that your number will never be restricted. Keep volumes modest, and keep your replies relevant to what the customer asked.
• Consent. The sender is responsible for consent. Only let the bot reply to people who contacted you, and only send outbound messages to people who agreed to hear from you.

Failure mode: a bot that messages people who never asked. Automated outreach to a cold list is the fastest route to a restricted number. Keep the chatbot on inbound replies at first.

What a chatbot can't do natively, and how Blueticks adds it

A stock chatbot answers and stops. It cannot tell when a message needs a person, and it cannot keep running when your laptop sleeps. Blueticks adds handoff controls and cloud hosting on Pro. It does not remove the limits. Credits still run out in a busy month, and the browser plans still depend on an open browser.

Work out the hours your customers actually write before you choose. If most questions arrive in the evening, the browser plans leave those messages waiting. If the team writes in the morning and you can watch the inbox, a browser plan with a clear handoff rule can be enough.

FAQ

Do I need to write code to build a WhatsApp chatbot?

No. Blueticks offers a visual flow builder for fixed scripts and an agent you describe in plain words. Test the bot from a second phone before you open it to real customers.

Will the chatbot reply when my computer is closed?

Basic and Standard reply only while the browser is open, because they run through WhatsApp Web in your browser. Pro runs in the cloud and keeps replying when WhatsApp Web is closed.

How many replies do the AI credits cover?

Basic includes 250 credits per user per month, Standard 500, and Pro 1,000. A typical agent reply uses about 2 to 4 credits, so Basic covers roughly 60 to 125 replies. Credits are shared across the team and renew monthly.

Can I take a chat back from the bot?

Yes. Write in the chat yourself and the agent pauses for that chat. Release it by typing "continue" in your operator chat, not the customer's chat, or from Conversations. There is no timer, so the agent stays paused until you release it.