WABA and number access
WhatsApp chatbot development
Turn WhatsApp messages into support, leads, bookings, and sales.
TUNDRÄ builds WhatsApp chatbots on the official Business API for teams that need fast replies, AI support, lead qualification, order updates, booking flows, and human handoff.
- Official API planning
- AI replies
- Lead capture
- CRM and human handoff
WhatsApp Business API Readiness map
Template copy and categories
Opt-in and stop path
CRM route and human handoff
Scope
Your customers already use WhatsApp. The question is whether your business can keep up.
WhatsApp is where many customers ask for prices, availability, delivery updates, appointments, and support. A chatbot can answer immediately, collect the right details, and escalate when the conversation needs judgment.
- Fast replies for after-hours and high-volume questions.
- Lead capture, booking, reminders, and order updates inside a familiar channel.
- Human handoff with conversation history when automation should stop.
Use cases
WhatsApp chatbot workflows TUNDRÄ builds
WhatsApp is strongest when the conversation should continue after the first message: support, sales, reminders, bookings, or order follow-up.
AI support bot
Answer repetitive questions from policies, service details, product pages, and help content. Escalate uncertain conversations.
- FAQs
- Policies
- Guardrails
- Handoff
Lead qualification bot
Ask qualifying questions, collect contact details, understand urgency, and send hot leads to sales with a summary.
- Qualification
- Contact capture
- Urgency
- Sales summary
Booking bot
Collect service type, preferred time, location, customer details, and route the request to staff or a calendar.
- Service type
- Preferred slot
- Location
- Calendar route
E-commerce assistant
Answer product questions, recommend options, send catalog or checkout links, confirm orders, and provide delivery updates.
- Product Q&A
- Catalog
- Checkout links
- Order updates
API reality
WhatsApp bots need more planning than Telegram bots.
A production WhatsApp chatbot is not just a script connected to a phone. Serious automation usually needs the official Business API, message templates, opt-in handling, and a clear handoff process.
Business API readiness
Check business verification, WhatsApp Business Account state, phone number setup, and provider path before setting a timeline.
- WABA
- Number
- Verification
- Provider
Outbound message planning
Business-initiated notifications usually need approved template messages and category-aware copy.
- Utility
- Marketing
- Authentication
- Approval
Opt-in and opt-out
The flow should show how users opted in, how they can stop messages, and when a human takes over.
- Opt-in source
- Stop path
- Support contact
- Escalation
Actual WhatsApp costs depend on provider, country, volume, message category, and current Meta pricing.
API readiness map
WhatsApp scope depends on account, templates, consent, and handoff.
A WhatsApp bot estimate is cleaner when platform readiness is checked before conversation design starts.
WhatsApp platform costs and rules can change by provider, country, volume, category, and current Meta policy.
| Area | What to confirm | Why it matters |
|---|---|---|
| Business account | WABA state, business verification, number ownership, provider route | Determines whether launch can start immediately or needs setup first |
| Message direction | User-initiated replies vs business-initiated template messages | Changes copy rules, testing, and cost planning |
| Templates | Utility, marketing, or authentication use cases and approval path | Outbound follow-up usually depends on approved templates |
| Opt-in and stop path | Where consent is collected and how users can stop messages | Protects the channel and reduces complaint risk |
| Human handoff | Agent destination, working hours, transcript summary, escalation triggers | Prevents automation from trapping high-risk conversations |
| Connected systems | CRM, booking, catalog, order, payment, support inbox, analytics | Adds mapping, retries, data ownership, and QA work |
Channel choice
Choose WhatsApp when continuity matters more than setup speed.
Telegram, WhatsApp, and website chat can all automate messages, but they solve different commercial problems.
| Channel | Best for | Tradeoff | Typical first workflow |
|---|---|---|---|
| Consumer reach, follow-up, reminders, booking, order updates, personal sales conversations | More planning around API access, templates, consent, providers, and cost | Lead qualification with human handoff or appointment intake | |
| Telegram | Communities, SaaS users, digital products, internal workflows, paid access, technical audiences | Audience fit depends on whether customers already use Telegram | FAQ, lead capture, alerting, subscription, or AI support bot |
| Website chat | Visitors already browsing the site, low-friction testing, top-of-funnel questions | Conversation often ends when the visitor leaves unless follow-up is captured | FAQ, lead form, routing, or AI support entry point |
Estimate inputs
Send these details to avoid a vague WhatsApp quote.
The fastest estimate names the business case, platform state, message direction, systems, and expected handoff.
| Question | Good answer example | Scope impact |
|---|---|---|
| What should the bot do first? | Qualify inbound leads and route high-intent chats to sales | Defines the main workflow and acceptance checks |
| Is API access ready? | WABA verified, number available, BSP selected | Separates setup work from bot development |
| Do you need outbound messages? | Yes, appointment reminders and follow-up after opt-in | Requires template planning and approval time |
| Where should data go? | A CRM lead, staff WhatsApp inbox, booking calendar, analytics event | Adds integrations, retries, and data mapping |
| When should a human take over? | Pricing dispute, angry user, legal question, high-value lead | Defines escalation rules and transcript summaries |
Packages
Choose the WhatsApp package by API readiness.
The same business flow can be a simple build or a larger launch depending on Business API access, templates, provider route, and handoff requirements.
WhatsApp FAQ or lead bot
For basic support, first response, lead intake, and routing when API access is ready.
USD 1,000-2,500 2-5 days
- Structured flow
- Quick replies
- Lead capture
- Admin alert
- Handoff
AI-powered WhatsApp bot
For support, product questions, qualification, summaries, and escalation based on business content.
USD 2,000-4,000 3-7 days
- AI answers
- Knowledge prep
- Guardrails
- Conversation logs
- Escalation
Booking, CRM, or e-commerce workflow
For workflows that need Business API setup, templates, CRM, booking, catalog, payments, or multi-agent handoff.
USD 2,500-7,000+ 1-3+ weeks
- API setup
- Templates
- CRM sync
- Booking or catalog
- Analytics
WhatsApp vs web chat
Why not just use a website chatbot?
Website chat is useful when visitors are already on your site. WhatsApp is useful when the conversation needs to continue after the visit, include reminders, or happen where customers already talk to businesses.
Good for site visitors
Lower platform friction, easier testing, and useful for answering questions while the visitor is already browsing.
- Website visitors
- Low setup friction
- Easy testing
- On-site conversion
Good for continuity
Better for follow-up, reminders, personal replies, sales conversations, and support that continues after the site visit.
- Follow-up
- Reminders
- Personal chat
- Sales routing
Use the site to start WhatsApp conversations
Website, ads, QR codes, and social profiles can bring users into WhatsApp when the conversation should continue.
- Click-to-chat
- QR code
- Ads
- Social profiles
Capabilities
What TUNDRÄ can include
A WhatsApp bot can be the front door for support, sales, booking, order updates, and CRM routing.
Business-trained answers
AI replies from your service content, product information, policies, and approved source material.
- Source content
- Tone rules
- Fallbacks
- Review
Lead and support handoff
Collect data, qualify intent, send summaries, and route important conversations to the right person.
- Lead fields
- Intent
- Summary
- Agent route
Cost-aware analytics
Track topics, handoffs, conversions, unresolved questions, and cost assumptions for API and AI usage.
- Topics
- Handoffs
- Conversions
- Cost assumptions
Comparison
WhatsApp route options
The right route depends on whether you need a communication platform, a custom workflow, or a phased test.
| Option | Best for | Risk | TUNDRÄ view |
|---|---|---|---|
| BSP platform | Shared inbox, campaigns, templates, multi-agent support | Monthly fees, workflow limits, add-ons, and platform lock-in | Good if the primary need is inbox and broadcast tooling |
| No-code automation | Simple marketing flows and quick tests | Custom CRM, booking, payments, and AI can get fragile | Good when the team accepts platform limits |
| Custom WhatsApp bot | Specific intake, routing, CRM sync, support, and commerce workflows | Needs API readiness and policy-aware design | Best fit when the flow must match your business process |
Process
WhatsApp chatbot development process
We check API readiness first, then design the flow around WhatsApp rules instead of discovering platform constraints late.
Scope and channel check
Confirm business goal, volume, number status, API path, templates, and connected systems.
Conversation design
Map the main flow, quick replies, fallback behavior, opt-in language, handoff, and notification triggers.
API and bot setup
Configure webhook handling, bot logic, data storage, AI, CRM, booking, or e-commerce integration.
Launch and monitor
Test user-initiated chats, templates, handoff, errors, and early real conversations.
FAQ
WhatsApp API questions that affect scope and budget.
Do I need the official WhatsApp Business API?
For serious automation, usually yes. The normal WhatsApp Business app is limited. The Business API is the right path for scalable automation, integrations, templates, multiple agents, and production workflows.
Can a WhatsApp bot use AI?
Yes. AI can answer common questions, qualify leads, and summarize conversations. It still needs guardrails, fallback logic, and human handoff.
Can the bot send messages first?
Usually through approved templates and opt-in rules. This is one of the main differences between WhatsApp and Telegram, and it should be planned before launch.
Is WhatsApp more expensive than Telegram?
Usually yes. Telegram has no standard Bot API fee. WhatsApp can justify the extra cost when customer reach and behavior make it the stronger channel.
Next step