The Complete WhatsApp Setup and Cost Guide for Businesses (Meta, Twilio and Deimix)
The Complete WhatsApp Setup and Cost Guide for Businesses (Meta, Twilio and Deimix)
Who this guide is for
This is the detailed companion to What Is Deimix and How Does It Work?. That article explains what Deimix is and what you need before starting. This one is for the point after that — when you’ve decided WhatsApp automation is worth doing, and now you want to understand the machinery properly before you commit budget or a phone number to it.
It covers the WhatsApp Business Platform, who owns which account, what happens to your existing number, how Meta’s verification and template review actually work, what the message categories mean, how the 24-hour window affects your bill, what limits apply to broadcasting, and what each of the three parties charges.
Two notes before we start. First, this article deals with a third-party platform whose rules and rates change — Meta updates its pricing on a published calendar, and there are changes scheduled for late 2026 that are covered below. Where something is subject to change, it’s marked as such. Second, we don’t publish per-message rate tables here, because a rate table in a blog post goes stale faster than anyone updates it. We explain the structure and point you at the official rate cards, which are the only version worth budgeting from.
Want this walked through for your specific business? Send “Hi” to +91 96009 59581 on WhatsApp.
The WhatsApp Business Platform, explained properly
There are three WhatsApp products, and they are genuinely different things.
WhatsApp — the consumer app. Your customers use this. Nothing in this guide changes their experience.
WhatsApp Business App — the free business app. A real product with a profile, catalogue, labels, quick replies and away messages. Designed around one business, one phone, one person managing it.
WhatsApp Business Platform — commonly called the WhatsApp Business API. There is no app to download. It’s an interface that software connects to, which is the entire point: it lets a system, rather than a person holding a handset, send and receive messages on a business number.
That difference produces everything else:
| Business App | Business Platform | |
|---|---|---|
| How you access it | Install and log in | Software connects through a provider |
| Who can send | The person with the phone | Any authorised system or team member |
| Business-initiated messages | Type anything | Must use a Meta-approved template |
| Message records | Stored on the device | Logged in the platform |
| Automation | Quick replies, away message | Full conversational flows, scheduling, follow-up |
| Verification | Not required | Meta business verification required to operate at scale |
| Sending limits | Broadcast list caps | Account-level messaging limits set by Meta |
| Cost | Free | Platform + Meta + provider charges |
The Platform is not a premium version of the App. It’s a different product with different obligations. You take on template approval, verification and per-message costs — and in exchange you get software, scale and records. That trade is worth making when your customer communication has become a process rather than a conversation.
For the plain-language comparison: WhatsApp Business App vs Business API.
Account ownership: what you own, what Deimix touches
This is the section most vendors leave vague, and the one you should be clearest on before signing anything.
Your business → Deimix → Twilio → Meta / WhatsApp
(owner) (software) (provider) (the network)
Meta / WhatsApp owns the network. It verifies your business, reviews your templates, sets messaging limits on your account, monitors quality, and charges for messages by category.
Twilio is the provider that carries messages between Deimix and WhatsApp. Meta doesn’t sell API access directly to most businesses — a provider sits in between. Twilio charges its own per-message fee and passes Meta’s charges through.
Deimix is the software layer: automation, guided conversations, campaigns, segmentation, customer records, reporting, and the console your team works in. Deimix builds and operates that layer on top of your accounts.
Your business owns the number, the customer relationships, the content of what gets sent, and the decisions.
Here’s how that translates into practice:
| Asset | Whose name it’s in | What Deimix does with it |
|---|---|---|
| Your business phone number | Yours | Connects it to the Platform, never claims ownership |
| Meta Business account | Your business | Guides setup, works within it |
| WhatsApp Business Account | Your business | Configures messaging and templates |
| Twilio account | Your business | Connects the messaging path |
| Your customer contact data | Yours | Imports, organises, segments — never sells or supplies |
| Approved templates | Submitted under your account | Drafts, structures and submits for your approval |
| The Deimix platform itself | Deimix | Provided under your subscription |
The practical consequence: Meta and Twilio charges land on your own accounts, at their rates, and Deimix takes no margin on them. If you ever stop working with Deimix, the number, the accounts and the verified business status stay with you.
One honest caveat. The exact account structure — particularly how the Twilio account is opened and who holds the payment method on it — is confirmed with you during onboarding, because it depends on your situation and on what the providers require at the time. We’ll tell you exactly how it’s set up for your business before anything is created. What we won’t do is quietly put your business’s messaging infrastructure in someone else’s name.
Your number: new, migrated, or existing
Most businesses want to keep the number their customers already have. That’s usually possible.
Moving an existing number onto the WhatsApp Business Platform is a migration — the number stays the same, but how it connects to WhatsApp changes. It stops being served by the app on a handset and starts being served through the Platform. The exact path depends on how the number is currently set up, which product it’s on now, and what the providers support at the time, so it’s checked case by case before anything is touched. That’s part of onboarding, not something you have to work out yourself.
Three practical considerations:
What you might be giving up. Whatever lives only on the handset — chat history in the app, labels, the app’s own catalogue — belongs to that app installation. Plan for the migration as a fresh start on the record-keeping side, with your contact list carried across deliberately rather than assumed.
Whose SIM it is. A large number of Indian businesses run their “business” WhatsApp on an owner’s or an employee’s personal number. When that person leaves, every customer who saved that contact is now connected to them, not to you. There’s no way to make customers update a saved number. If this describes your setup, migration is the moment to move to a number the business actually owns.
Starting fresh. A new business number avoids all of the above, at the cost of having to tell customers about it. For businesses whose customers mostly arrive through walk-ins, ads or a website rather than a saved contact, this is often the cleaner choice.
There’s no universally right answer. We’ll look at how your customers currently reach you and recommend one.
Meta business setup and verification
Before you can operate at scale, Meta needs to confirm your business is real. This is Meta’s internal process — not a government registration, not something Deimix or any vendor can approve, accelerate or guarantee.
What it involves. A Meta Business account for your business, a business document proving the entity exists (for Indian businesses, the GST certificate is the usual one), a business email on your own domain where possible, a website or landing page that matches your business details, and a phone that can receive the verification code.
What causes most failures. Name mismatches. If the legal name on your GST certificate and the name on your Meta Business account differ — even by a single character, an ampersand instead of “and”, a missing plural — the application fails and you start again. Poor-quality document scans are the second cause. A website whose details don’t match the business is the third.
Timing. Verification is typically measured in weeks, not days, and a rejection means resubmitting and waiting again. Nobody can guarantee a timeline. If you’re working towards a festival season, this is the item that determines whether you make it.
The full document-by-document walkthrough is here: Meta Business Verification for Indian Shops.
Templates: categories, approval and reassignment
Why templates exist. On the Business App you type whatever you like. On the Platform, Meta requires that any message starting a conversation uses a template it has reviewed in advance. It’s Meta’s control against businesses using the network to send unsolicited messages at volume. Under Meta’s current rules, template messages are the only type that can be sent outside an open customer service window.
The three categories.
| Category | What it’s for | Review | Relative cost |
|---|---|---|---|
| Marketing | Promotions, offers, new arrivals, re-engagement, anything not clearly transactional | Strictest | Highest |
| Utility | Order confirmations, appointment reminders, delivery updates, payment reminders — tied to something the customer did | Moderate | Lower |
| Authentication | One-time passwords and verification codes | Narrow and specific | Lowest |
Submission and approval. You choose the category when submitting. Review is a mix of automated checks and, for borderline cases, human reviewers, and typically takes anywhere from a few hours to several days. Rejections come back with a reason, usually a general one. Deimix drafts, structures and submits your templates — but approval is always Meta’s decision.
Category reassignment. This is the part that costs businesses money quietly. If Meta decides the category you chose doesn’t match what the template actually says, it can reassign the template to a different category, and pricing follows the reassigned category. The classic case: a utility template with a promotional line added to the end — “Your order is ready for collection. Do see our new arrivals while you’re here” — gets reclassified as marketing, and every message sent under it is charged at the marketing rate. Meta expects businesses to review the categories assigned to their approved templates.
Why this means writing carefully. Keep transactional templates transactional. If you want to promote something, that’s a second template in the marketing category, sent separately. Avoid unverifiable superlatives — “best prices”, “number one”, “guaranteed lowest” — which are among the most reliable ways to get rejected. Include an opt-out line in marketing templates. Make sure any link works and uses HTTPS.
The full list of rejection causes and how to write around them: Why Your WhatsApp Template Keeps Getting Rejected.
Message categories and when each applies
The category is a property of the template, not of the individual send. Getting your templates into the right categories at setup is a cost decision as much as a compliance one.
| Situation | Category | Notes |
|---|---|---|
| Diwali offer to your customer list | Marketing | Highest rate, strictest review, needs opt-out |
| “Your appointment is confirmed for Saturday 11am” | Utility | Tied to a customer action |
| “Your order is ready for collection” | Utility | Keep it clean of promotion |
| “Your verification code is 4821” | Authentication | Narrow use only |
| Replying to a customer who just messaged you | Service message | Free-form, no template — see the next section |
Under Meta’s current pricing rules, utility and authentication messages carry volume tiers that vary by market and category, so per-message rates can fall as monthly volume rises. Marketing messages have no volume discount at any level. Most businesses send a mix, and the mix is what determines the bill.
The 24-hour customer-service window
This is the most misunderstood mechanic in WhatsApp business messaging, and the one most worth understanding.
How it opens. When a customer sends your business a message, a 24-hour customer service window opens. If a window is already open, a new message from them refreshes it.
What you can send while it’s open. Any message type — free-form replies as well as templates. This is why customer-initiated conversations are so much easier to run than business-initiated ones: your team, or your automation, can simply talk normally.
What happens when it closes. Under Meta’s current rules, once no window is open, an approved template is the only way to reach that customer again. You cannot send a free-form message to someone who hasn’t messaged you recently.
On cost — and this is time-sensitive. Under Meta’s pricing rules as they stand at the time of writing, free-form service replies inside an open window have not attracted a Meta per-message charge, and utility templates sent inside an open window have been treated the same way. Meta has announced changes to this taking effect 1 October 2026, under which service messages become billable and utility templates lose their in-window exemption, with the specific per-market rates due to be published by Meta ahead of that date. Authentication and marketing templates have always been charged inside the window.
What this means practically: if you’re budgeting now for a period that runs past that date, assume replies inside the window become a per-message cost, and check Meta’s published rates when they appear rather than relying on any blog post — including this one. We will keep this section current, but the authoritative source is always Meta’s official WhatsApp pricing documentation.
Twilio’s fee is separate and unaffected. Whatever Meta does or doesn’t charge for a message, Twilio’s own per-message fee applies to messages sent and received. This is why “WhatsApp is free for 24 hours” was never true, and why anyone still saying it in late 2026 isn’t paying attention.
One useful exception. Conversations that begin from a Click-to-WhatsApp advertisement or a Facebook Page call-to-action currently qualify as free entry points, with a 72-hour free window on Meta’s side. Provider fees and your advertising costs still apply. If you run ads, this is worth building your flows around.
Broadcast mechanics, limits and quality
The Platform does not give you unlimited sending. Three separate things govern how much you can send and how well it lands.
Messaging limits. Meta sets a limit on how many unique customers your account can start conversations with in a rolling 24-hour period. New accounts start low. Limits can increase over time based on your sending history and account standing, but increases are Meta’s decision and are not guaranteed, automatic or something a provider can arrange. Plan your first campaigns around a modest limit rather than assuming your whole list can be reached on day one.
Quality rating. Meta monitors how customers respond to your messages — blocks, reports and negative feedback. An account whose quality drops can find its messaging limits reduced. This is the mechanism that makes indiscriminate blasting genuinely expensive: it costs you reach, not just money.
Throughput and delivery. Messages are queued and delivered by Meta’s infrastructure. Nobody — not Deimix, not Twilio — can guarantee delivery, timing or read rates. Messages to numbers not on WhatsApp, or that Meta marks as failed, don’t reach anyone.
What this means for how you should broadcast. Segment rather than send to everyone. Message people who have a reason to hear from you. Give recipients an easy way out. Warm a list up with something useful before you push an offer at it. A list of 800 relevant customers who reply will outperform 8,000 who don’t, and it will also protect your account.
Your existing customer list
Contacts you already hold — billing exports, booking registers, enquiry sheets — can be imported into Deimix, organised and segmented by service, area, last visit, spend, or any distinction that matters to your business. That segmentation is what makes campaigns work: relevance is the difference between a broadcast that generates replies and one that generates blocks.
Two boundaries worth stating plainly. You need the right to contact the people on your list — having a phone number is not the same as having permission. And Deimix does not supply, sell or source customer contact data. The list is yours; so is the responsibility for it.
What Meta charges
Meta charges per delivered template message. The rate depends on two things: the category of the message, and the country code of the recipient — not where your business is located.
The structure, under Meta’s current rules:
- Marketing, utility and authentication templates are each charged at their own per-market rate
- Utility and authentication have volume tiers that can lower the unit rate as monthly volume rises; marketing does not
- Charges apply on delivery, not on sending
- Rates are updated on Meta’s published calendar and do change
- Changes to in-window service and utility message charging take effect 1 October 2026, as described above
We deliberately don’t reproduce Meta’s India rate card here. Rates move, and a stale number in a blog post is worse than no number. Check the current figures at Meta’s official WhatsApp pricing documentation, which carries the live rate cards, or ask us and we’ll pull the current rates for your categories.
GST applies to these charges for Indian businesses. Confirm the treatment with your accountant rather than taking a vendor’s word for it.
What Twilio charges
Twilio’s structure is unusually transparent, which is one reason we use it.
Your Twilio bill is Twilio’s own per-message fee plus Meta’s per-template fee passed through at cost. Per Twilio’s published pricing, the Twilio fee is $0.005 per message, inbound or outbound — note that inbound messages count, so a busy two-way conversation carries a fee on each side. Twilio also applies a small processing fee to messages that end in a failed status, and prices its optional add-ons, such as link shortening and click tracking, separately.
Two practical points. Twilio bills in US dollars, so your rupee cost moves with the exchange rate. And Twilio states its prices may change without notice — the current position is always at Twilio’s WhatsApp pricing page.
What Deimix charges
₹4,999 per month. That is the Deimix platform subscription: the automation and guided conversations, campaign and segment configuration, customer records and reporting, template drafting and submission, the console your team works in, and ongoing support.
It is not a WhatsApp bill. Meta’s charges and Twilio’s charges are separate, sit on your own accounts, and are billed to you directly by them. Deimix takes no per-message margin on either.
We keep the three separate on purpose. Meta and Twilio set their own rates and change them on their own schedules. Folding them into a single Deimix number would hide costs you should be able to see and question, and would leave you unable to tell what you’re paying for software versus what you’re paying for messages.
The Founding Member offer. For the first 10 businesses:
- ₹4,999/month, locked for 12 months
- Setup free — onboarding, Meta and Twilio connection, template preparation, automation build, campaign configuration
- $25/month of Deimix usage credit, issued monthly for 12 months
The credit applies to eligible Deimix-side usage — the per-use platform operations inside your own account. To be precise about what it isn’t: it does not pay Meta, it does not pay Twilio, and it does not reduce the ₹4,999 subscription. Fresh credit is issued each month for twelve months. Unused credit doesn’t roll over and has no cash value. Usage beyond the available credit follows the normal Deimix usage and balance model.
₹4,999 is the base platform subscription. Founding members pay that same subscription with the founding benefits added for twelve months. Terms after that period, and for businesses joining later, are quoted directly.
A worked monthly example
This is an illustration of how the bill is structured, not a quote. The Meta line depends on current rate-card figures for your categories and volumes, which we’ll pull for you.
A clinic with 3,000 contacts. In one month it sends 2,000 appointment reminders (utility), runs one campaign to a 1,200-contact segment (marketing), and handles around 900 inbound customer messages with roughly 1,800 replies.
| Line | What determines it | Amount |
|---|---|---|
| Deimix subscription | Fixed | ₹4,999 |
| Deimix eligible usage | Platform operations in the month | Offset first against the $25 monthly founding credit; any excess follows the normal usage model |
| Meta — utility templates | 2,000 × current India utility rate, tiering applied | Per current rate card |
| Meta — marketing templates | 1,200 × current India marketing rate, no volume discount | Per current rate card |
| Meta — in-window replies | Currently no template charge; billable from 1 October 2026 at rates Meta publishes | Currently nil, changing |
| Twilio | ~5,900 messages in and out × $0.005 | ≈ $29.50 |
| GST | Applies across the above | Confirm treatment with your accountant |
Three things this example is designed to show. The marketing segment of 1,200 costs meaningfully more than the 2,000 utility reminders, because category drives rate. The Twilio line grows with total conversation volume including inbound, so an engaged, chatty audience costs more to serve than a quiet one. And the in-window reply line, currently at nil, is the one to watch as October approaches.
Onboarding, stage by stage
| Stage | Owner | What happens | Typical timing / dependency |
|---|---|---|---|
| 1. Preparation | You | Business name checked for consistency across documents and accounts; GST certificate and business email located; contact list exported | A few days — the more thorough here, the fewer delays later |
| 2. Meta business setup | Deimix, with you | Meta Business account created or reviewed; details aligned to your documents | Depends on what already exists |
| 3. Business verification | Meta | Meta reviews and verifies the business | Typically weeks; Meta’s decision; a rejection restarts the clock |
| 4. Number setup | Deimix, with you | New number provisioned, or existing number migrated onto the Platform after we confirm the path for your setup | After verification; you need the phone for the code |
| 5. Provider setup | Deimix, with you | Twilio account set up in your business’s name and connected | Runs alongside stages 3–4 |
| 6. Templates | Deimix drafts, you approve, Meta decides | Templates written, categorised, submitted | Hours to several days per template; submit early, submit several |
| 7. Deimix configuration | Deimix | Automation flows, buttons, booking paths, reminders, follow-up, handoff rules, contact import, segments | Runs alongside stages 3–6 |
| 8. Testing | Deimix and you | End-to-end tests on real devices; your team walks the flows | A few days |
| 9. Go-live | You | First campaign, live enquiry handling | When verification and templates are both cleared |
The dependency that governs everything is stage 3. Verification is Meta’s process, its timeline and its decision. Everything Deimix builds can proceed in parallel, but nothing can send until Meta clears you. Start earlier than feels necessary — particularly ahead of a festival season, where a single rejection can cost you the window.
Who operates what, day to day
Once you’re live, the division of labour settles like this.
Deimix runs the platform, the automation flows, the campaign configuration, the segments and the technical side of the messaging path. When you want a new flow, a new template, a seasonal campaign or a change to how enquiries are routed, that’s us.
Your team runs the actual conversations. Automation handles enquiries, bookings, reminders and follow-up; when a customer needs a person — a complaint, a negotiation, a question nobody anticipated — the conversation is handed over with its full history attached. Someone on your side needs to be watching that queue during business hours. Deimix is not a call centre and does not answer your customers on your behalf.
You own the decisions. What you offer, what you say, who you contact, how often, and what happens when a customer asks for something unusual. The system executes the process; it doesn’t invent it.
Meta and Twilio bill you directly for their part, on your own accounts.
Common questions
Can Deimix guarantee Meta will approve my verification or templates? No, and neither can anyone else. Both are Meta’s decisions. What we can do is prepare submissions that avoid the common causes of rejection.
What happens if a template gets rejected? We revise and resubmit. Rejections are normal, particularly on first marketing templates. Submitting several templates early, rather than one close to a deadline, is the practical protection.
Can I send to my whole list on day one? Probably not. New accounts start with a modest messaging limit that Meta may raise over time based on your sending history and standing. Plan the first campaigns around a segment.
Does the $25 credit reduce my Meta or Twilio bill? No. It’s a Deimix-side promotional credit for eligible platform usage only. Meta and Twilio bill you separately at their own rates.
What if I use less than $25 of credit in a month? The unused portion doesn’t carry forward and has no cash value. Fresh credit is issued the following month.
What happens after the 12-month founding period? Terms are agreed with you directly. The founding benefits are a twelve-month promotional arrangement, not a permanent entitlement.
Do I need my own Twilio account? The account is set up in your business’s name so charges bill directly to you. The exact structure is confirmed with you during onboarding before anything is created.
What happens to my number and accounts if I stop using Deimix? They’re yours. The number, the Meta Business account, the verified status and the Twilio account stay with your business.
Is GST included in the ₹4,999? Check with us directly when you’re quoted, and confirm the treatment of Meta and Twilio charges with your accountant.
The short version
- The WhatsApp Business Platform is a system interface, not an app. It’s what makes automation, campaigns and team access possible — and it brings verification, templates and per-message costs with it.
- Four parties: your business → Deimix → Twilio → Meta/WhatsApp. The number, the Meta accounts and the Twilio account are in your business’s name.
- An existing number can usually be migrated; the path depends on your current setup and is confirmed before anything moves.
- Meta business verification typically takes weeks, is Meta’s decision, and gates everything else. Name consistency across your documents is the single biggest cause of failure.
- Templates are required for business-initiated messages. Category drives both review strictness and cost, and Meta can reassign a category it thinks is wrong — with pricing following.
- A customer message opens a 24-hour window in which you can reply freely. Outside it, only templates. Meta’s charging inside that window changes on 1 October 2026 — budget accordingly and check Meta’s published rates.
- Meta charges per delivered template by category and recipient country. Twilio charges $0.005 per message, inbound and outbound, plus Meta’s fees passed through at cost.
- Deimix charges ₹4,999/month for the platform. Founding members — the first 10 — get that locked for 12 months, free setup, and $25/month of Deimix-side usage credit that doesn’t pay Meta or Twilio.
- Messaging limits, quality rating and delivery are Meta’s, and nobody can guarantee them.
What happens next
If you’ve read this far, the useful next step is a conversation about your specific numbers — list size, message mix, and which categories your messages fall into. That’s what turns the structure above into a figure you can actually budget.
Send “Hi” to +91 96009 59581 on WhatsApp. Tell us your list size and what you’d want to send, and we’ll walk through what setup and running costs would look like for your business.