About Plum
Plum is one of India's leading employee benefits platforms. They help companies offer health insurance and other coverage to their employees, handling everything from onboarding and policy issuance to claims and renewals.
For Plum, almost every important conversation happens on WhatsApp. Be it sales cycles, client relationships, or claims queries.
Two teams at Plum run completely different workflows on WhatsApp, and as the business grew, both hit the same ceiling. The tools weren't keeping up.
Challenge 1: The Sales Team
- 25 agents, 20,000+ clients, and no way to see what was happening across any of it
The Personal Insurance Sales team, led by Atul and Dhairya, runs a high-intent pipeline of clients who come in through the Plum app already interested in term insurance or other personal insurance products.
The sales cycle is structured: send a quote, follow up, close the payment. All of it happens over WhatsApp over the course of roughly a month.
The problem wasn't the clients or the process. It was the tooling. The team was running on a WhatsApp Business API platform that had started to buckle under the volume. Three issues in particular were creating real friction:
The 24-hour messaging window was a persistent blocker. If a client went quiet for a day, agents couldn't send a regular follow-up. They were forced to use pre-approved templates, which felt impersonal and, worse, often didn't deliver reliably. In a sales cycle where a warm follow-up can be the difference between a conversion and a dropped lead, this was costly.
Broadcast campaigns were unreliable. Reaching clients at scale for offers, reminders, or product updates was inconsistent. Some messages would land, others wouldn't. The team couldn't trust the channel for any kind of coordinated outreach.
The biggest operational gap: every agent was operating off a shared number. Managers had no way to see individual conversations. There was no audit trail, no way to review how a specific agent had handled a client, and no accountability mechanism.
"Everyone was on the same number. Managers couldn't see what individual agents were doing, and there was no way to review conversations or hold the team accountable. At our scale, that wasn't something we could keep ignoring."
— Atul, Personal Insurance Sales Lead, Plum
Challenge 2: The Customer Success Team
- 15 people, 5,000+ groups, and no way to know what was falling through the cracks
Plum's Customer Success team manages the company's relationships with the HR departments of its corporate clients. Each client gets a dedicated WhatsApp group — one group per company, containing the HR contact and the relevant Plum CS team members.
That's where all the work happens: onboarding new employees onto insurance plans, answering claims queries, managing renewals, and resolving policy questions. It's live, ongoing, and relationship-critical.
15 people managing 5,000+ active groups. At any given moment, messages are landing across hundreds of those groups simultaneously. Before Periskope, the team was managing this entirely through native WhatsApp, which meant no central view, no ownership model, and no way to enforce response times.
The failure mode was predictable:
- A message would land in a group, and because nobody had explicit ownership of it, it would sit there. Maybe it would get picked up in a few hours.
- Maybe it would get missed entirely. For small clients, delayed responses are friction. For large enterprise clients, they're a churn risk.
"With 15 people across 5,000 groups, things were inevitably falling through. There was no central view, no way to assign ownership, and no escalation path when something sat unanswered. We needed a system, not just an app."
— Customer Success Team, Plum
The Sales Team
Dedicated agent numbers, shared visibility, and broadcasts that actually work
Plum moved the Personal Insurance Sales team to Periskope, and the operational changes were immediate and structural.
Each of the 25 agents now has their own dedicated WhatsApp number. Those numbers all connect to a single shared dashboard, which means managers can see every conversation across every agent in real time. The audit trail that didn’t exist before is now automatic.
The 24-hour window problem is gone. Agents can send regular, conversational follow-ups without being forced into templates. The quality of client communication improved overnight.
Broadcasts, meanwhile, now work reliably — the team can reach their entire client base with consistent messaging when needed, whether that’s for product launches, reminders, or campaign activity.

We need each sales agent to have their own WhatsApp number, and for managers to easily track conversations — but Business API’s chat window & template restrictions made it hard. Periskope made the whole setup effortless to scale.

Dhairya T.
Lead, Product
Key Periskope features powering this team:
✦ Dedicated per-agent numbers
✦ Unified shared dashboard
✦ Reliable broadcast messaging
✦ Full conversation audit trail
Customer Success
One inbox to run it all with tickets, assignments, and automatic escalation
Periskope became the Customer Success team’s operating system for WhatsApp. The entire team now works from a single shared inbox that aggregates messages from all 5,000+ corporate groups. Nobody is working out of their personal phone or a split-view interface. Everything is in one place.
When a message comes in, it can be flagged as urgent and converted into a ticket, which is then assigned to a specific team member. Ownership is explicit. The person responsible for resolving a query knows it’s theirs, and managers can see the status of every open item across the team.
Automation handles the escalation layer. If a message sits unanswered beyond a defined threshold, it’s automatically surfaced for intervention, no manual monitoring required.
The team consistently hits a sub-10-minute response SLA now, something that simply wasn’t achievable with native WhatsApp at this scale.
Key Periskope features powering this team:
✦ Unified inbox across 5,000+ groups
✦ AI-powered message flagging
✦ Ticket creation & agent assignment
✦ Automated SLA escalation
20,000+ | Insurance clients actively managed on WhatsApp |
5,000+ | Corporate groups managed from one inbox |
Sub-10 min | Response SLA maintained by the CS team |
Full visibility | Managers can see every agent conversation in real time |
The sales team now operates with the accountability and structure it always needed. The CS team responds faster, misses less, and gives enterprise clients the reliability they expect.
Plum has a single platform powering two completely different WhatsApp workflows, without compromise on either side.
What began as fixing a broken workflow has become the foundation for how the entire sales and customer success function operates on WhatsApp.
Ready to see what this looks like for your team?
If your team is managing client relationships on WhatsApp and things are starting to slip through, you already know the cost of that. Book a demo, and we'll show you exactly how Plum’s setup would map to your workflow.
More case studies

Financial Services
How Alegra's Customer Success Team Connects WhatsApp Conversations to HubSpot Workflows

Marketing
How Motion Society Coordinates Creators, Clients and Delivery Teams across WhatsApp Groups

Healthcare







