White-Label Research Delivery Over WhatsApp: How It Works
Most SEBI Research Analysts already send client notes over WhatsApp. The question is how. A broadcast list from a personal number leaves no record and reaches every contact regardless of what they hold. White-label delivery over the WhatsApp Business API does the opposite: notes go out under your own firm branding, to the clients who hold the relevant ticker, with every send logged for your Regulation 25 audit trail. Here is how the mechanism works.
Note: This describes how a delivery mechanism works, not legal or compliance advice. SEBI rules and Meta's WhatsApp policies change. Verify current requirements against SEBI's circulars and the Research Analyst Regulations 2014 as amended, and consult a compliance professional for your situation.
What "white-label" means here
White-label delivery means the client never sees the software vendor. The research note arrives on WhatsApp showing your firm name, your SEBI RA registration number, and your disclaimer. The client experiences your practice as the source. The platform that runs the API connection, the targeting, and the logging stays invisible in the background.
This matters for an RA practice for a simple reason: trust is the product. A client who pays โน30,000 to โน80,000 a year for your coverage is paying for your judgment and your name. A note that arrives branded as some generic broadcast tool dilutes that. A note that arrives as "Acme Research, SEBI RA INH000XXXXXX" reinforces it.
WhatsApp Business API: the basics
There are two WhatsApp products that matter for an RA. The standard app on your phone, including its broadcast-list feature, is one. The WhatsApp Business API is the other, and it is a different thing entirely.
The API is a server-to-server channel. Messages are sent programmatically over an official Meta connection, not tapped out by hand. Each outgoing message is logged at source with the recipient, the timestamp, the content, and the delivery status. The log is cloud-hosted, not stored only on your device. You reach the API either directly through Meta Business Manager or through a solution provider that handles the provisioning and the verified business number for you.
That server-side log is the whole point for a SEBI RA. Personal WhatsApp keeps no retrievable record once a message leaves your phone. If SEBI asks for your communication records, a personal-app broadcast cannot produce them. The API can.
How the delivery actually works
White-label WhatsApp delivery for an RA rests on five components. Each one maps to a specific compliance or targeting need.
A verified WhatsApp Business API number
The number is registered to your RA practice through Meta Business Manager, directly or via a solution provider. Your display name and firm branding are approved by Meta, so the client sees your practice as the sender, not a third-party app.
Client opt-in captured and logged
Before any research goes out, the client opts in. The opt-in is timestamped and tied to your written client agreement. This one consent record satisfies both Meta's messaging policy and the SEBI requirement for client consent before research delivery.
A symbol-to-client map
You record which clients hold each NSE or BSE ticker. This map is the targeting layer. It turns "send to everyone" into "send to the three clients who actually hold RELIANCE".
A note template with your branding and disclaimer
Each research note carries your firm name, SEBI RA registration number, and the standard disclaimer at a fixed position. The branding and disclaimer are part of the template, so they go out on every message without you retyping them.
A server-side log of every send
When a note goes out, the platform writes the send to a log: client, ticker, channel, timestamp, full message text. The log is cloud-hosted and retrievable, which is the core of a Regulation 25 audit trail.
What a white-label note looks like to the client
Example white-label WhatsApp note
ACME RESEARCH ยท SEBI RA: INH000012345 9 June 2026 ยท 11:18 IST RELIANCE (RELIANCE) ยท Filing Alert Board outcome: buyback of โน9,300 Cr approved. Record date and tendering window to follow. Analyst view: Capital return positive for holders. Not a call to action. Analyst or associates may hold RELIANCE. For informational purposes only. Not investment advice.
The firm name and RA number are part of the template, so they appear on every send. The same note is logged server-side against the client and ticker.
Targeting: only the clients who hold the ticker
The targeting layer is what separates white-label delivery from a blast. It runs off a symbol-to-client map: for each NSE or BSE ticker, a record of which clients hold it. When a filing lands for RELIANCE, the platform looks up RELIANCE in the map and finds the clients who hold it. The note goes to those clients and no one else.
A solo RA with 20 clients holding 15 stocks each is watching 300 stock-client pairs. NSE and BSE publish 300 to 800 filings on a normal trading day. Without targeting, every material filing becomes a choice between blasting all 20 clients or skipping it. With the map, a RELIANCE board outcome is simply "3 clients affected", and you send to those three.
This is better research practice, not just less spam. A client who holds RELIANCE at 25% of their portfolio reads a RELIANCE note differently from one who holds none. Sending the note only to holders keeps every message relevant, and it means each send is documented against a specific client holding for your records.
Opt-in and consent
Two consent requirements line up here, and the convenient part is that one action satisfies both.
Meta's WhatsApp Business policy requires that a client opts in before you can message them through the API. Separately, SEBI rules require a written or electronically acknowledged client agreement authorizing you to send research communications. When a client opts in, the platform timestamps and logs that consent and ties it to your client agreement. One record, two obligations covered.
The practical effect: you cannot accidentally send white-label research to a number that never agreed to receive it. The opt-in gate is built into the channel. A broadcast list from a personal phone has no such gate, which is one of the ways it drifts into non-compliant territory.
How this differs from a broadcast list or a personal number
The distinction is not cosmetic. A broadcast list and the API produce different artifacts, and only one of them survives a SEBI inspection.
The broadcast list looks similar from the sender's side: you type once, many people receive it. The difference is everything you cannot see. No per-recipient log. No targeting by holding. No opt-in record. No export. Under SEBI Regulation 25, a research communication must be recorded and retrievable for at least 5 years. A broadcast list gives you none of that.
The Regulation 25 audit trail
Regulation 25 of the SEBI Research Analyst Regulations 2014 requires an RA to maintain records of research and recommendations, retrievable for inspection. A WhatsApp message containing a stock view is a research communication, so it falls inside that record-keeping duty exactly like a formal report.
White-label delivery over the API builds that record as a side effect of sending. Every note written to a client produces a log entry with the client, the ticker, the channel, the timestamp, and the full message text, held for at least 5 years. Many platforms also store a hash of each sent note, which proves the content was not altered after the fact. When SEBI asks what you sent, to whom, and when, the answer is a CSV export, not a scramble through phone backups.
The mechanism supports compliance; it does not do your compliance for you. The registration number and disclaimer still have to be in the note, the client consent record still has to exist, and the conflict-of-interest check before each send is still your responsibility. White-label delivery makes those steps repeatable and logged, which is the part that breaks down when an RA is copy-pasting from a personal phone under time pressure.
How Aktai does white-label WhatsApp delivery
Aktai sends client research over the WhatsApp Business Cloud API under your firm branding. You add your client portfolios once. Aktai ingests the BSE and NSE filing feeds, matches each filing to the clients who hold the ticker, and shows you who is affected. You write the note, hit send, and it goes out white-labelled to those clients with the audit log written automatically.
Aktai for Research Analysts
White-label WhatsApp delivery, BSE and NSE filing alerts targeted to the clients who hold each ticker, and a Regulation 25 audit log on every send. Request access at aktai.app/for-research-analysts or email [email protected].
FAQ
What is white-label research delivery over WhatsApp?
White-label research delivery means your client notes go out over the WhatsApp Business API under your own firm name and SEBI RA registration number, not under the software vendor's brand. The client sees your research practice as the sender. The platform runs the plumbing (API connection, message logging, ticker-to-client targeting) in the background, but the message reads as if it came directly from your desk.
How is the WhatsApp Business API different from a broadcast list?
A broadcast list sends one message to many contacts from your personal phone, with no server-side record and no per-recipient log. The WhatsApp Business API is a server-to-server channel: each message is sent programmatically to a named client, logged at source with the timestamp, ticker, and full text, and retrievable on demand. For Regulation 25 record-keeping, the API produces an audit trail; a broadcast list does not.
Do clients need to opt in before I send research over WhatsApp?
Yes. The WhatsApp Business API requires opt-in before you can message a client, and SEBI rules require a written or electronically acknowledged client agreement before you send research communications. The two line up: the client consents once, the consent is timestamped and logged, and that record supports both Meta's policy and your SEBI Regulation 25 file. Sending research to a number with no opt-in is non-compliant on both counts.
Can I target a research note to only the clients who hold a specific stock?
Yes, when delivery runs off a symbol-to-client map. You record which clients hold each ticker. When a filing lands for that ticker, the platform identifies the affected clients and sends the note to those clients only. A client who does not hold the stock gets nothing. This keeps inboxes relevant and means each send is documented against a specific holding for your audit trail.
Is white-label WhatsApp delivery compliant with SEBI Regulation 25?
The delivery mechanism supports compliance; it does not replace your own duties. WhatsApp Business API delivery logs every message server-side with the client, ticker, timestamp, and full text, retained for at least 5 years, which is what Regulation 25 asks for. You still need the registration number and disclaimer in each note, a client consent record, and a conflict-of-interest check. Verify the current rules against SEBI circulars.