# WhatsApp AI chatbot development

> Customers already answer on WhatsApp. The difficulty is not the AI, it is Meta's messaging rules, which decide what your bot may send and when.

- Page: https://liftup.tech/platforms/whatsapp-ai-chatbot/
- Type: Platform
- Updated: 2026-11-20

## In short

A WhatsApp AI chatbot runs on the WhatsApp Business Platform, usually through the Cloud API or a business solution provider. It can answer freely for 24 hours after a customer writes, then needs pre-approved templates. Setup involves business verification, an opted-in contact list, template approval, a human handoff route and tested AI answers.

## The rule that shapes everything: the service window

When a customer sends you a message, a 24-hour customer service window opens. Inside it, your bot can reply with free-form text, which is where the AI is useful. Outside it, you can only send a message template that Meta has approved in advance. Each new customer message restarts the clock.

| Situation | What you may send | What this means for the bot |
|---|---|---|
| Customer wrote 2 hours ago | Free-form AI replies | Full conversation allowed |
| Customer wrote 30 hours ago | Approved template only | The bot cannot continue the chat without a template |
| Customer never wrote, opted in on your website | Approved template only | First message must be a template, such as an order update |
| Customer tapped a button in your ad or site link | Free-form for the window that opens | Good entry point for lead conversations |
| Customer has not opted in | Nothing | Do not message them |

Templates fall into categories such as utility, marketing and authentication, and the category affects what Meta charges per message. Charges are per message under the current model and change over time, so we model your expected volume against the current rate card when we quote.

## What the setup involves

1. **Business verification**: Your business is verified inside Meta Business Manager, which needs legal documents and can take days. Start this first.
2. **Number and provider choice**: A phone number is registered to the API. We decide between going direct on the Cloud API or using a provider, based on the inbox and reporting features you need.
3. **Opt-in capture**: A clear checkbox or click-to-chat entry that records who agreed, when and to what. Consent evidence matters under GDPR in the EU and UK.
4. **Templates**: We write and submit the templates you need, such as order confirmation or appointment reminder, and plan for rejections.
5. **Bot and knowledge**: The AI answers from your approved content, with fixed flows for sensitive tasks like payments or cancellations.
6. **Human handoff**: A shared inbox where staff take over, with the transcript attached.

We have no published case study on WhatsApp bots, so this is the shape of the work, not a client story. The AI layer follows the same approach as [AI chatbot development](https://liftup.tech/services/ai-chatbot-development/), and the knowledge layer is covered under [RAG chatbot development](https://liftup.tech/services/rag-chatbot-development/).

## Gotchas

- Policy on general-purpose AI. Meta's business terms have restricted bots whose main purpose is to act as a general AI assistant. A bot that serves your own customers about your own business is the intended use. Read the current terms before scoping anything broader.
- Number conflicts. A number used on the regular WhatsApp Business app historically could not also be on the API. Newer coexistence options exist, so confirm what your setup supports.
- Template rejections. Vague wording, missing variables or promotional language in a utility template are common reasons. We allow a revision round.
- Quality rating. Many blocks or reports lower your messaging limits. Send only to people who asked.
- Messaging limits. New numbers start with a daily cap on unique contacts that rises with good quality and volume.
- Voice notes and images. Customers send them. Decide whether the bot transcribes, reads or refuses them.
- Language. Test each language you serve. Mixed-language messages are common.

## Local rules to settle before launch

- EU and UK: consent for marketing messages, a clear way to stop, and a privacy notice that says an automated system answers first. Under GDPR, document your lawful basis.
- Australia: the Spam Act requires consent, identification of the sender and an unsubscribe route for commercial messages.
- United States: marketing messages call for clear consent, and state rules vary. Get your own counsel to review the opt-in wording.
- Time zones: our team works from India, so your human handoff hours should be set by your staff, not ours. We can build an out-of-hours message that tells people when someone will reply.

## Timeline

| Stage | Planning estimate | Note |
|---|---|---|
| Business verification | Several days, outside our control | Start before development |
| Templates approved | Usually within a day, allow a week for revisions | Depends on Meta review |
| Bot build and testing | 2 to 4 weeks | Longer with payment or CRM actions |
| Pilot with real customers | 2 weeks | Daily review of transcripts |

Overall, plan on five to seven weeks from kickoff to a live pilot for a typical support or lead bot.

## Questions, answered

### Can the bot start conversations by itself?

Only with an approved template, and only to people who have opted in. After the customer replies, the 24-hour window opens and the AI can answer freely.

### Do we need a provider or can we use the Cloud API directly?

Going direct gives more control and fewer fees but needs more engineering. A provider adds an inbox and reporting. We compare both against your needs.

### Can the AI take orders or payments?

It can collect details and hand over to a checkout link or a person. We keep payments in fixed flows rather than letting the model improvise.

### Will customers know they are talking to AI?

We recommend saying so in the first message and offering a human option. Some jurisdictions require disclosure, and trust improves when you are open.

### Can we reuse the same bot on our website chat?

Yes, the knowledge and logic can be shared across channels. The channel rules, such as the 24-hour window, stay specific to WhatsApp.

### Can you set up a WhatsApp Business API provider for a business in Pune?

Yes. Our head office is in Pune. We compare providers against the Cloud API for your needs, prepare business verification and templates, and build the bot. Our [WhatsApp Business API guide for Pune](https://liftup.tech/blog/whatsapp-business-api-for-pune-businesses-what-it-is-and-who-needs-it/) lists what to ask a provider before you sign.

## Related

- [AI chatbot development that answers from your content and knows when to stop](https://liftup.tech/services/ai-chatbot-development/)
- [AI chatbot cost calculator](https://liftup.tech/tools/ai-chatbot-cost-calculator/)
- [Zendesk AI chatbot setup](https://liftup.tech/platforms/zendesk-ai-chatbot/)

---

Get a fixed quote: https://liftup.tech/contact/ · email rohit@liftup.tech · WhatsApp +91 77689 10234 (https://wa.me/917768910234) · reply within one working day.
Source page: https://liftup.tech/platforms/whatsapp-ai-chatbot/ (Liftup Technologies)
