One consent record, six products, 1.47 billion people. How we made consent the gatekeeper for every promotional call and message in India.
<aside> 🔒
Screens are recreated mocks with dummy data, and client names and internal metrics are left out. I can't include more product shots or details here, but I'm happy to give a walkthrough over a call.
</aside>
Role
Lead UX Designer
Tanla Platforms
Timeline
Oct 2025 – present
Partners
TRAI, Airtel, Jio, BSNL, Vi
Tools
Figma, Figma MCP, Claude, Cursor
<aside> 👥
1.47B
subscribers covered
</aside>
<aside> 🚀
5
product releases
</aside>
<aside> ⚡
~50%
faster design cycles with AI
</aside>
Every day, Indian phone users receive a flood of promotional calls and messages they never agreed to. The rules already exist: the TCCCPR 2018 regulations and the DPDP Act 2023 say brands need a person's consent before contacting them. In practice, though, consent was scattered across brands, their marketing partners and individual operators. There was no single record anyone could trust, check or audit.
DigiConsent is the answer: an AI-native, national consent platform built with the regulator and India's major operators. A promotional message or call only goes through if a valid consent exists for it.
Many actors, one record
Brands, their partners, operators, registrars, the regulator and citizens all touch the same consent, with very different jobs and permissions.
Regulation is a design input
Every flow had to be audit-ready and trace back to specific legal requirements.
National scale
Brands arrive with years of legacy consent data that has to be migrated in, not collected again from scratch.
Our team designed across six connected surfaces, each built for a different user:
| Surface | Who uses it | Core job |
|---|---|---|
| Enterprise Portal | Brands and their compliance teams | Set up brands and lines of business, migrate existing consents, map message templates, track consent health |
| GTM Partner Portal | Aggregators and agencies acting for brands | Manage the enterprises they serve, rate cards and onboarding |
| Channel Owner Portal | Operators | Oversee enterprises, migrations and commercial set-up on their network |
| Registrar Console | Registrar operations | Verify and govern consent records |
| Regulator Console | The regulator | Oversight, audit and compliance reporting |
| Consent Wallet (PWA) | Citizens | See who holds your consent, and grant, change or revoke it in a few taps |
The most important design decision wasn't a screen. Instead of six products with their own data, every surface is a different view of the same consent object:
<aside> 🏢
Brand
</aside>
<aside> 🗂️
Line of business
</aside>
<aside> 📡
Channel
</aside>
<aside> 🎚️
Preference
</aside>
<aside> ✅
Status
</aside>
This gave everyone, from a bank's compliance officer to a citizen, the same vocabulary. A change made in one portal shows up consistently everywhere else. What each role can see or do became a question of permissions, not of separate screens.