Solutions · Business software

WhatsApp inbox & CRM: what to decide, build and test.

Planning one? Here's what to settle before you brief anyone, what goes in the first version, how the build runs week by week, how the beta is tested with real people, and the numbers that show it's working.

Decisions to make before you brief a shared WhatsApp inbox

A shared inbox looks like a chat screen, but the expensive decisions sit behind it. Make these before you write a brief.

  • Internal tool or a product you sell. An internal tool has one workspace and your own rules. A product needs separate workspaces, per-customer data, billing and onboarding, and costs a lot more. If you might sell it later, say so now, because tenancy is hard to retrofit.
  • Direct platform access or through a provider. Going direct to Meta's platform gives control but you handle webhooks, retries and number setup. A provider shortens setup but adds a fee and a dependency, and your chat history may sit with them.
  • One number or several. One number is simple. Several (sales, support, a clinic per branch) need routing by number and per-team permissions.
  • Routing by fairness, skill or ownership. Round-robin is fair but ignores language and past relationships. Routing a returning customer to the same agent feels better but leaves chats waiting when that agent is off.
  • Support-only or also broadcasts. Broadcasts bring in opt-in tracking, template approval, segments and a policy risk, so they are a second product.

Bring these to the first call:

  • Number of agents, teams and WhatsApp numbers
  • Where orders and customers live today
  • The response time you want to hold agents to
  • Languages your customers write in
  • Whether broadcasts are in version 1
  • Who owns the Meta business account

What goes in version 1 and what waits

A single-team inbox with window handling and an SLA timer is a complete first release.
ModuleFirst versionAdd laterWhy
Number setupOne verified number on the platformSeveral numbers, per-team numbersVerification takes time on your side
InboxShared list, assign, resolve, private notesLabels, saved filters, merge contactsThe daily core
RoutingRound-robin and manual transferSkill, language and owner-based rulesRules need real chat data to tune
Window handlingShow when the 24-hour window closes; template-only afterAuto-prompts to re-engagePrevents failed sends
Quick repliesSlash shortcuts with name and order fieldsTemplate builder with approval statusSaves the most typing
Customer contextContact, past chats, one store or CRM connectionSeveral integrations, actions like refundsEach integration is its own project
SLAFirst-response timer with a warning stateBusiness hours, escalation chainsNeeds clear hours first
ReportsFirst response time, volume by hour, per agentFunnels, custom dashboardsStart with three numbers people act on
BroadcastsOptional: one template, one list, delivery statusSegments, scheduling, A/B testsBrings policy and opt-in risk
AdminRoles, audit log, exportWorkspaces and billingOnly needed if you sell it

Our concept build Replyvo implements the window clock, a five-minute first-response target with a warning at three minutes, round-robin assignment and a broadcast funnel, all on sample data. Those figures are its demo settings, not a standard.

How the 8 to 12 weeks run, and what you supply

Template approval and number verification run on Meta's schedule, so start them in week 1.
WeeksWhat we buildWhat you supply
1Scope, roles, routing rules, data modelSample chats, order data export, list of quick replies
1–3Platform connection and webhooks, message storage, inboxMeta business account, verified business details, a number not already used on the regular app
3–5Assignment, notes, quick replies, window rulesTemplate text for approval; agent names and teams
5–7Store or CRM integration, customer panelAPI access to your store or CRM, a test account
6–9SLA timers, reportsTarget response times and business hours
8–10Broadcasts if includedOpt-in records and a clean contact list
10–12Pilot with a few agents, load test, launchAgents for training; a rollback plan to the phone

Read the WhatsApp for business apps guide for the account setup steps.

How we work with you each week

The same rhythm runs from week 1 to launch, so you always know what's happening and what we need from you.

  • Friday: a demo link and a 30-minute call. You open the latest build on your own phone and try it yourself, rather than watching our screen.
  • Within 48 hours: your feedback, in writing. In one shared doc, next to the screen it's about. Written feedback is clear, dated and doesn't get lost between calls.
  • Monday: triage. Every comment goes into fix now, next week or later. Anything that changes the agreed scope gets a written quote before we touch it.
  • Each milestone: two revision rounds, then your sign-off. Sign-off is against the scope we agreed, so it's clear what done means.
  • One decision-maker on your side. Most delays aren't build time. They're feedback waiting on several people who disagree.

The full version, including how the beta and user testing work across every kind of project, is on our process page.

The beta: one team on the real number, the old phone on standby

The beta is the pilot in weeks 10 to 12. It starts once messages arrive in the inbox, can be assigned and answered, and the window clock and first-response timer work on live chats. Customers don't install anything: they keep messaging your number on ordinary WhatsApp, so this is real support from the first hour.

  • What's in it. The shared inbox, round-robin and manual transfer, notes, quick replies, window handling with templates, the customer panel with your store or CRM connection, the SLA timer and the three basic reports.
  • What stays out. Skill and language routing, extra numbers, business-hour escalation chains and extra integrations. If broadcasts are in version 1, the beta sends one template to a small opted-in list only.
  • Who uses it. One team: three to five agents on their normal shifts, the team lead who watches the timers, and the admin who manages roles. The customers are whoever messages that number during the pilot. You pick the team; a keen, quiet team tells you less than a busy one.
  • How they get it. A browser link on the computers and phones agents already use, each with their own login and role. No app store step.
  • What stays as backup. The phone that handled chats before stays charged and logged in, with the rollback plan written down, so the team can switch back in minutes if a webhook stops.
  • How long. Two weeks, covering at least one sale day or month-end rush if your business has one. Agents flag problems from a button in the inbox that captures the chat ID.

What we test with real people, and the tasks we set

We give each agent a realistic chat to handle on the device they work on, typing the way they normally type, Hinglish included. We watch, we don't coach, and we note every pause. Around five sessions per role surfaces the problems worth fixing. After the fixes, we run the tasks again with different agents.

Agent sessions run at a busy hour, with the real queue behind them.
WhoThe taskWhat we watch for
Agent"A customer sends a voice note: 'mera order abhi tak nahi aaya'. Find the order and send the tracking link."Does the voice note play? Do they find the order from the customer panel without opening the store admin?
Agent"Reply to this customer. Their last message was 26 hours ago."Do they notice the window has closed before typing? Can they find and send the right utility template?
Agent"This customer writes in Tamil. Hand the chat to a colleague who reads it, with a note."Does the transfer keep the history and the note? Does the customer get a reply, or fall into a gap?
Team lead"It's 7 pm and four chats show the first-response warning. Clear them."Can they see who is overloaded and reassign from one screen?
Admin"An agent left today. Remove her access and reassign her open chats."Is it done in a minute? Does the audit log show who did it?
CustomerReal customers asking things like "Can I exchange the kurta I bought last week for a size L?"We read the logs, not the person: was the first reply on time, correct, and free of duplicate or failed sends?

The numbers that say it's working

In week 1 we choose two or three of these with you. If chats were on a phone before, we pull what figures we can from it as a starting point. The tracking is in place before the pilot, and we report at launch and again after 30 days. We don't promise the numbers will move; we make sure you can see them.

GoalWhat we measureWhere it comes from
Customers hear back quicklyFirst response time, by hour of day and by agentInbox reports
Problems actually get solvedChats resolved without the customer coming back within seven daysInbox chat history
Messages don't failFailed sends, and sends attempted after the window closedPlatform delivery status webhooks
No chat is left ownerlessChats still unassigned or unanswered at end of dayInbox queue
The team moves off personal phonesShare of customer chats handled in the inbox rather than on a staff phoneInbox counts against the old phone's chat log
Broadcasts don't hurt the numberOpt-outs and blocks per broadcast, and the number's quality ratingPlatform reports

What a shared inbox costs, and what pushes it up

A team inbox with integrations and reports is data-heavy business software. In our app development cost guide that band is ₹12–35 lakh as a small-studio ballpark. A single-team inbox with no integrations sits at the lower end. A multi-tenant product sits at the top or above. These are ballparks, not a quote.

  • Multi-tenancy. Workspaces, data isolation and billing add substantial back-end work.
  • Integrations. Each store, CRM or billing tool has its own data and failure modes.
  • Routing and SLA rules. Business hours, escalation and skills multiply the cases to test.
  • Broadcasts. Segments, scheduling and delivery tracking add a second product.

Platform charges for messages are separate from build cost and are paid to Meta or your provider. They are billed per delivered message by category, and the rates change, so check the current price list.

India rules and habits for a WhatsApp inbox

  • The 24-hour window. Free-form replies are possible for 24 hours after the customer's last message. After that only approved templates can be sent. Build the window into the inbox so agents see it.
  • Opt-in. Meta requires opt-in before template messages, and it must name your business. Record when and how each customer agreed, and honour opt-outs. Repeated violations can lead to limits or a disabled account.
  • Template categories. Templates are marketing, utility or authentication, with different charges. Order updates are utility. Offers are marketing. Do not slip promotions into a utility template.
  • Chat data. Chats hold names, phone numbers, addresses and sometimes health or payment details. Under the DPDP Act you need purpose-limited consent, a notice in English or an Eighth Schedule language, and a way to erase on request. Most obligations are reportedly phased in about 18 months after the November 2025 Rules. See the DPDP checklist.
  • Languages. Customers write in Hinglish and regional scripts. Search and routing should cope with mixed language.
  • Habits. Customers expect an answer in minutes. They also send voice notes and photos, so the inbox must play and store them.

This is general information, not legal advice. Platform policies and prices change, so check Meta's current terms, and ask a lawyer about data retention.

Common WhatsApp inbox mistakes and what to do instead

  • Using one agent's phone. Chats vanish when they leave. Move to the platform with a number owned by the company.
  • Importing a purchased contact list for broadcasts. It breaks the opt-in rule and risks the number. Message only people who agreed.
  • Ignoring the window. Agents type replies that fail to send. Show the countdown and switch to templates when it closes.
  • Over-automating. Bots that trap customers lose goodwill. Always offer a person.
  • Measuring only speed. A fast useless reply passes an SLA. Track resolution and re-opens too.
  • Integrating everything at once. Connect the store first and add the rest after agents use it.
  • No roles. Everyone seeing every chat and every phone number is a privacy risk. Set roles and keep an audit log.
  • Unclear ownership of the Meta account. Register it in the company's name, with two admins, so a resignation does not lock you out.

Cost and timeline

8–12 weeks for a first version.

Fixed quote within 48 hours of your brief: scope, timeline and price in writing before we start. These are what move the number.

  • Number of teams, numbers and routing rules
  • Integrations with your store, CRM or billing
  • Broadcast volume and segmentation
  • Reports and dashboards
  • Whether it is an internal tool or a product you sell

How app costs work in India →

Questions

About your whatsapp inbox & crm.

What does a custom WhatsApp inbox cost?

It depends on routing rules, integrations and reports. Every project gets a fixed quote within 48 hours of your brief. Our guide to app development cost in India explains typical ranges. WhatsApp's own per-conversation charges are separate and paid to the platform or your provider.

Do we need the WhatsApp Business Platform?

Yes. A shared inbox needs the official platform, accessed directly or through an approved provider, and your business must be verified. The regular WhatsApp Business app on a phone can't be shared safely across a team. Our guide to WhatsApp for business apps explains the setup.

Can it connect to our store or CRM?

Usually, yes. We connect to your store, billing or CRM so agents see orders and history beside the chat, and actions like refunds can start from the inbox. We check what your current tools support before quoting, so there are no surprises mid-build.

Can we turn it into a product to sell?

Yes. We have designed it as a multi-team SaaS in our concept build, and the code is yours to extend with billing, workspaces and onboarding. If you plan to sell it, we design for many businesses from the start, with separate workspaces and data for each customer.

Who owns the code and the chat data?

You do. The code is handed over in full and chats live in your own database, not ours. That matters for customer trust and for data protection: you decide how long chats are kept and who can see them. Nothing stays locked in our accounts.

Start a project

Tell us how your business runs. We'll build what it runs on.

Four taps, about a minute. Fixed quote within 48 hours.

Menu

Read

Ask an expert Ask an expertFree, real peopleHub
Ask an expert