Start with an audit

Let’s talk.

Tell us what you’re working on. A person from the team replies to every enquiry, with a time for a 30-minute call.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.
Specialist service · WhatsApp chatbot development

WhatsApp chatbot

Both, in most production bots: buttons, list messages and WhatsApp Flows for structured tasks like booking or order tracking, free-text AI for open questions. Users can then tap or type.

AI & Automation practice: abstract red and ink artwork from the Red Balloon reel

When staff spend the day answering the same questions about prices, documents, EMI dates or order status, WhatsApp chatbot development gives customers instant answers and frees people for the conversations that need them. Red Balloon builds chatbots for travel agencies, NBFCs, clinics, retailers and education businesses, designed around the handful of tasks customers come to WhatsApp for. Bots collect details after hours, send payment links and booking confirmations, and hand over to an agent with the conversation attached. An unanswered-question log shows what to add next, and a short satisfaction survey keeps quality honest. WhatsApp chatbot development cost depends on flows, integrations, languages and AI use, and the bot runs on your own account.

What drives WhatsApp chatbot development cost

The number of tasks the bot handles is the first driver. A bot that answers timings and sends a catalogue is a small build; one that books tables, collects payments, verifies borrowers and logs service requests is several. Each integration, whether a POS, loan management system, booking calendar or CRM, needs design and testing. Every language adds copy and review, and AI answers add an evaluation set built from your approved content.

Ongoing costs sit beside the build: Meta's message charges, your BSP's plan, any AI model usage, and the time someone on your side spends keeping prices, policies and FAQs current. WhatsApp chatbot development is quoted after the journey design phase, when we know which flows matter most, so you can launch with the highest-volume tasks and add the rest once usage data shows what customers actually ask for.

Writing bot copy people will reply to

Chatbot copy fails when it reads like a form. Each message should ask one thing, in plain words, and tell the customer what happens next. We keep messages short enough to read without scrolling, put the action in a button where possible, and confirm every booking or payment back in a single clear summary. The bot introduces itself as automated and offers a human from the first message.

Language is chosen by the customer, not assumed. The first message offers English and Hindi, or the regional language your customers use, and the choice is remembered for later chats. Copy is written by native speakers in the register your customers actually use, which for many brands means everyday Hinglish rather than formal Hindi. Tone stays consistent with your brand, and staff can edit replies without a developer.

Connecting the bot to payments, bookings and records

A bot saves time only when it can finish the task. That means reading and writing live data: available slots from your booking system, EMI dates from your loan system, order status from your store, and stock from your POS. Payment links from Razorpay, Cashfree or PayU can be generated inside the chat and confirmed back to the customer once payment succeeds, without anyone checking a dashboard by hand.

Every completed task is written back to the system of record, so staff see bookings, payments and requests where they already work. For sensitive data, such as loan balances or test reports, the bot verifies the customer first and shows only what the policy allows. We log each step, which gives you the drop-off report and an audit trail for disputes.

Where this works

Real-world situations we're built for

Illustrative · not a client
Delhi travel agency

Same questions about visa documents and package prices all day

What we'd do
Button-led bot for packages and visa checklists, AI answers from approved FAQs, agent handover for bookings
What moves
Agent chat load down, share of handovers with complete booking details up
NCR two-wheeler finance NBFC

EMI date and payment link requests swamp branch staff

What we'd do
Bot verifies the customer, shares the EMI date and a UPI payment link, and hands disputes to staff
What moves
Branch queries down, on-time payment share up; tracked as branch EMI queries per month before and after, over a fixed period
How a project runs

3 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Intent and journey design

1–2 weeks

Chat log analysis, flow scripts, button vs AI decisions

You get: Flow diagrams and copy

We need: Past chats, FAQs, policies

Build and test

2–3 weeks

BSP bot builder or custom code, WhatsApp Flows, integrations, handover

You get: Bot on a test number

We need: API access, test users

Launch and tune

Ongoing

Drop-off review, copy changes, new intents

You get: Monthly funnel report

We need: An owner for content updates

A typical engagement

From first call to result

Illustrative · not a client

Gurugram multi-brand restaurant group, 9 outlets, POS with an API, WhatsApp API through a BSP, catering enquiries by phone

Week 1Intent mapClassify 1,000 past chats; rule of thumb: buttons where an intent has under 10 fixed answers, free text with an LLM otherwiseMenu, booking, catering and feedback flows; complaints go to people
Weeks 2–3Build flowsWhatsApp Flows for table booking, list messages for outlets (10 rows max, so group by area), a small LLM layer answering menu questions from approved dataBot running on a test number
Week 3Handover and trackingShared-inbox handover with chat context; drop-off events logged per stepFunnel by step visible
Weeks 4–5Launch and tuneGo live, review drop-offs weekly; most common drop-off: typed date or address questions where a Flow picker would doFlows simplified at the worst drop-off points
Where it starts1,500 chats/week, 70% about menus, timings and table bookings, 20% of chats unanswered after closing time
Where it endsThe group answers routine chats round the clock with clean handovers. Weekly they watch bookings via the bot, drop-off by step and handover rate.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Containment rateChats resolved by the bot ÷ total bot chatsSet from the pilot; raise it without hurting satisfactionBSP analyticsWeekly
Step drop-off rateUsers leaving at a step ÷ users reaching itFix the highest drop-off step firstBot event logsWeekly
Handover wait timeMedian minutes from handover to first human replyWithin your agreed SLAInbox reportsWeekly
Goal completionsBookings, payments or leads completed inside the botRising month on month, with completions per 100 bot chats above your starting baselineBSP plus CRMWeekly
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: Bot cannot match an intentUnanswered question logFallback intent writes questions to a sheet through n8nRemoves: Feeds new FAQs and flows
When: Chat outside working hoursAfter-hours captureBot collects details and creates a CRM ticketRemoves: Prevents lost enquiries overnight
When: Chat closedSatisfaction surveyRating message sent after resolutionRemoves: Compares bot and human satisfaction
Rules we work to

Standards and regulations

MetaWhatsApp Business Messaging Policy

Bots must give a clear route to a human and respect opt-outs

MeitYDPDP Act 2023 and DPDP Rules 2025

Collect only what the bot needs, say why, and delete chat data per your retention policy; main duties apply from 13 May 2027

What's changing

Platform and policy updates that affect this work

We track: Meta for Developers: WhatsApp Flows documentation and changelog, WhatsApp Business Messaging Policy page.

Meta (WhatsApp)Started charging for service replies beyond a monthly free allowance, and for utility messages sent inside an open window

Budget for reply volume as well as templates; the earlier free-reply rules no longer apply

Meta (WhatsApp)Announced terms barring general-purpose AI chatbots on the Business API from January 2026

Keep AI scoped to your business: support, bookings, product questions

Meta (WhatsApp)Made customer-started service conversations free of Meta charges

Bot replies inside the customer service window carry no Meta fee; BSP fees may apply

Before you hire anyone

Questions to ask any agency, including us

Can our staff edit bot replies without a developer?

Why ask

Prices and policies change every week

A good answer

A content editor, preview, version history

How does the bot verify a customer before sharing account details?

Why ask

A phone number alone may not be enough for sensitive data

A good answer

OTP or known-detail checks, limits on what is shown

What does the bot say when it doesn't know?

Why ask

Confident wrong answers cost trust

A good answer

Fallback copy, a handover option, logging of unknown questions

FAQ

Questions buyers ask us

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

Is an AI chatbot on WhatsApp allowed under Meta's current policies?

Yes, for business-specific bots handling support, sales or bookings. Meta's updated WhatsApp Business terms, effective January 2026, bar general-purpose AI assistants whose main purpose is open-ended chat.

  • Scope the bot to your products, services and customer accounts, and test its refusals with off-topic prompts such as homework or coding questions before launch.
  • Meta's commerce policies restrict categories such as prescription drugs, alcohol and real-money gambling; healthcare, lending and insurance bots also follow NMC, RBI or IRDAI rules on advice.
How does the chatbot hand over to a human, and how do you track where users drop off?

On request, after repeated misunderstanding or on a high-value intent, the bot passes the full chat to a human inbox. Every step is logged, which shows drop-off and resolution per flow.

  • Handover goes to the BSP inbox, Freshdesk, Zoho Desk or your CRM with the conversation summary attached.
  • If the customer service window closes before an agent replies, only an approved template can restart the conversation.
  • We report containment rate, handover rate, drop-off per node and a one-tap CSAT at the end of each conversation.
  • Start with the node where most users drop: often it asks for typed input, such as a pincode or order number, that a button or Flow field would capture better.
Can the chatbot answer in Hindi, Hinglish and regional languages?

Yes. Button flows and templates are written separately for each language you choose, and approved in each language Meta supports for templates. AI answers can understand questions typed in Hindi, Hinglish or Roman-script regional languages, but we test them on real customer messages before launch, because accuracy varies by language and model. Where a language tests poorly, the bot routes those chats to a person.

  • Flows written per language, not machine-translated
  • AI answers tested on real messages
  • Weak languages routed to staff
Can we run the same chatbot on our website and Instagram?

Largely, yes. The logic, content and integrations can be shared across WhatsApp, a website chat widget and Instagram messages, through a BSP that supports several channels or a shared backend we build. Each channel keeps its own rules, message formats and response windows, so flows are adapted rather than copied. Reporting combines channels so you can compare where customers prefer to talk.

  • Shared logic and content across channels
  • Each channel's rules respected
  • Combined reporting by channel
Back to the service

WhatsApp automation →

Start with an audit

Ready for
lift?

A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

A person from the team replies to every enquiry.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.