Straight answers to the questions people ask first

No. You connect your own Meta WhatsApp account and add a payment method there, so Meta charges you directly at their own rates. We never sit in the middle of that, which is why our plans are as cheap as they are.

The software — the inbox, CRM, campaigns, chatbots, automations, email and ad tools, and the people who keep them running. That is a flat monthly fee that does not change with how much you send.

Meta charges per conversation and the rate depends on the country and the type of conversation. Service conversations started by the customer are free within a 24-hour window. Meta publishes the current rates and you can see your own usage in your Meta account at any time.

No. Connecting your WhatsApp number takes a few minutes through Meta's own sign-up flow, and everything after that is done in the panel.

Yes, provided it is not currently active on the normal WhatsApp or WhatsApp Business app. Meta requires a number to be on one or the other, not both.

It is yours. Contacts, conversations and CRM records can be exported, and because your WhatsApp and ad accounts are your own, they simply carry on without us.

No. One business number, as many agents as your plan allows — everyone works the same inbox from their own login.

They can, but assignment exists so they do not. An assigned chat shows who owns it, presence shows who is typing, and taking it over is a deliberate action.

Nothing is lost. Conversations belong to the workspace; you deactivate the login and reassign their open chats in bulk.

Not for the same number. Meta requires a number to be on either the app or the API, not both. Most businesses move the business number across and keep a personal number on the app.

Only if you tell it to. Set business hours and the clock pauses outside them, so an overnight message is not counted as a breach at 9am.

Meta requires them for any message you start. We help you write and submit them; approval usually takes minutes to a few hours.

Our plan fee, plus Meta’s conversation charge billed straight to you. There is no per-message markup here.

Meta sets a messaging limit per number, which rises as your number builds a good quality rating. We pace inside that limit deliberately — sending faster than it is how numbers get restricted.

Meta gives a reason and you edit and resubmit from the same screen. Promotional wording inside a utility category is the usual cause.

Yes, and they must be able to. Opt-outs are recorded against the contact and honoured on every future campaign without you doing anything.

Yes. Access is per CRM and per agent, so a salesperson sees their pipeline and not the whole company’s.

Yes, from a spreadsheet, with your own fields mapped across. Duplicates are matched on phone number rather than blindly added.

Yes. Separate lines of business usually want separate stages, and each pipeline can have its own agents.

It does — but the point of it is that leads arrive already filled in from conversations, so most people connect a number first.

Yes, through the developer API or an automation, and the contact is matched to an existing one if the number already exists.

That is up to your copy. You write every message it sends — nothing is generated behind your back.

Any agent can take over mid-conversation, and the bot stands down for that chat immediately.

No. It is a drag-and-drop canvas, and a useful first bot usually takes under half an hour.

Yes. Trigger it outside business hours and daytime conversations go straight to a person as normal.

It is saved to the contact and, if you want, opened as a CRM deal — so the answers are usable rather than buried in a transcript.

No. Every rule has a frequency guard, and the defaults are conservative on purpose.

It fails quietly and is recorded. A broken automation never blocks a customer’s message from arriving.

They run in order and each records what it did, so a conflict is visible in the log rather than mysterious. Rules cannot trigger each other in a loop.

Yes — dry run it against a real recent conversation. It tells you what it would have done and does none of it.

Through webhook actions and the developer API, yes. Anything we do not do natively, you can hand to your own endpoint.

No. Almost every hosting plan already includes mailboxes. We detect your provider from your domain and use it.

Not if you clean the list and warm up — both of which are enforced here rather than suggested.

You do not need to. The check tells you what is wrong, gives you the exact record to paste into your DNS, and explains in one line what it does.

Two to four weeks for a new domain. An established domain that already sends normally starts much higher.

Yes, and that is the point of having both here. A segment of people who clicked an email can be the audience for a WhatsApp campaign the next day.

No. You connect your own MSG91 or Fast2SMS account and they bill you at their rate — roughly ₹0.11 to ₹0.25 an SMS depending on volume. We charge for the software only.

MSG91 if you also want RCS or send at volume: one key covers both channels. Fast2SMS if you want the cheapest possible start — ₹100, no monthly plan.

TRAI requires every business SMS in India to come from a registered entity, under a registered sender id, using a registered template. Without it operators drop the message. Registration is done once on an operator's DLT portal; your vendor will walk you through it.

Nothing. The campaign is a queue on the server and keeps sending at the pace you set. If the server itself restarts, it resumes where it stopped, without sending anyone twice.

The report groups failures by reason — DND, invalid number, template mismatch — with counts. Numbers that are dead or on DND are added to your do-not-message list so you do not pay for them again.

No. It needs Android with Google Messages, or an iPhone on a network that supports it — in India that is currently Jio. That is exactly why SMS fallback exists: phones without RCS get the SMS.

MSG91 bills you directly: roughly ₹0.12 for a transactional message and ₹0.32 for a promotional one, with a monthly plan per bot from ₹2,000 that becomes wallet credit. We charge for the software, not the messages.

Indian operators only deliver RCS templates they have approved. You create and submit them in your vendor's panel, and import them here.

Bot verification by Google and the operators takes 2 to 6 weeks the first time. You can use Bulk SMS from day one while you wait.

Not for RCS itself. You do need it for the SMS fallback, because that is an ordinary SMS.

Yes, your own — which means the spend, the invoice and the data stay yours.

Yes. One campaign runs across both, and you can see which is earning its share.

No. Meta charges your card directly. Our fee is the software fee and nothing else.

Small and short. A few hundred rupees a day for a week on one audience tells you more than a big launch, because you can still tell what caused what.

Meta’s reason is shown in the panel and you edit and resubmit from the same screen, exactly as you would in Ads Manager.

No — it complements it. Most customers here sell in the chat because that is where the conversation already is.

Payment is taken the way you take it today — a link, a transfer, or on delivery. The order record holds what was agreed either way.

Metered by plan, and counted live. Most small catalogues are well under any plan’s limit.

The reason is shown in the panel. It is usually an image or a restricted category, and you fix and resubmit from the same screen.

Through the developer API and webhooks, yes. Natively, stock lives here and decrements when an order is confirmed.