How brands scale personalized video with first-party customer data: one template, a customer table, and delivery on WhatsApp, email, apps and RCS.
Brands scale personalized video by building one brand-safe template and connecting their first-party customer data, so each record renders as its own 1:1 video. Whilter.AI’s Snype does this through an API in real time or in scheduled batches, and delivers on WhatsApp, Instagram, RCS, mobile app and email.
The old ceiling was the studio. Hand-crafting caps personalized video at whatever a studio can produce. Once a video is generated from a template and a row of data, the limit moves to the quality of the data and the discipline of the template, and that’s where most of the work now sits.
One finished video per row. Snype merges each recipient’s name, language, offers, product recommendations and calls to action into a single dynamic template and generates a 1:1 personalized video and image for that person. Nobody records a separate video per customer. Brand-safe templates hold your look and tone fixed, so the data varies and the brand doesn’t.
The published numbers show what that looks like at volume. Snype delivered 100M+ personalized creatives for PolicyBazaar across seven languages, with +40% CTR and +10% conversions (PolicyBazaar case study). For Bajaj Pulsar’s “Chala Apni” campaign, one selfie per rider became one film each: 160K personalized videos, 30M+ impressions and 70% click-to-conversion (Bajaj Pulsar case study). The Bajaj input was a selfie rather than a CRM row, so the per-person input isn’t always a table row.
The ones that change what a customer does next. A first name makes a video feel addressed. Language, offer and product recommendation decide whether it works. Those are also the merge fields Snype documents: name, language, offers, product recommendations and CTAs. You connect a CRM, CDP, spreadsheet or product database with merge fields and segments, and you choose which fields drive the personalization.
PolicyBazaar’s case file describes the pattern. Snype read each person’s first-party data to decide which message and which offer they saw, then generated the matching creative in all seven languages. ABHI shows the other half of the design: keep the ask fixed. Every video pointed at one action, download the app and register the same day, while the message adapted to the person. That campaign ran 500K+ personalized videos for +44% app-download conversions and 10× same-day registrations (ABHI case study).
The data work sits on your side of the table, and it decides more than the template does. Dedupe before you render. Decide in advance what a video says when a field is empty, because a greeting that reads “Hello ,” is worse than a generic one. Use only fields you could explain to the customer, and check the consent behind each one. Snype’s FAQ says no third-party or PII data is required and that your first-party data stays yours.
Snype, Whilter.AI’s enterprise video platform, is built for this. It’s API-ready and aimed at retention at scale: you build one dynamic, brand-safe template and Snype generates the 1:1 variants automatically. The documented capabilities go past a name swap. Face replacement and virtual try-on work from a single source asset, one template localizes across 7+ languages, and generation runs in real time through the API or as scheduled batches.
The use cases Whilter lists are lifecycle ones: cross-sell and upsell, renewal and retention, cart abandonment, lead conversion and dormant cohorts. MakeMyTrip is the volume example outside insurance. Snype rendered 1.5M+ personalized traveler videos on demand, for 3× CTR and a 90% conversion uplift (MakeMyTrip case study).
Whatever platform you shortlist, ask three things. Is the template one object, or a copy per variant? Does it take your fields directly from the system where they live? And what does it measure after someone presses play?
On Snype, through a four-phase engagement with Whilter.AI. Growth Assessment maps your lifecycle and the cohorts where personalized video moves the number. System Design sets the data connections, templates and channels. Deployment puts real-time and batch generation live. Optimization feeds plays, watch time, drop-off and conversions back, so each cohort gets sharper.
Measurement comes with the platform. Snype tracks plays, watch time, drop-off, CTA clicks and conversions, so you can tie each cohort’s videos to what people did after they saw them.
For regulated buyers the checklist usually starts with security. Whilter maintains an ISO 27001, SOC 2 and GDPR security posture, and the videos and images it generates are yours. The BFSI page collects the PolicyBazaar and ABHI results in one place.
Snype delivers across WhatsApp, Instagram, RCS, mobile app and email, so each recipient gets a video in the channel they already use. That covers all four in the question, plus Instagram.
The case record shows WhatsApp most directly. W for Woman ran a virtual try-on entirely inside WhatsApp: Snype generated a personalized on-brand image per shopper on demand, for a 4× engagement uplift and 65% WhatsApp engagement (W for Woman case study). Bajaj Pulsar’s case page also carries a demo of a personalized film delivered over WhatsApp. For the other channels, the mix gets decided in System Design, next to the data connections and templates.
Two practical points. Consent usually attaches to a channel, so a customer who agreed to email hasn’t necessarily agreed to WhatsApp, and your table needs a column for that before any send. And pick the generation mode by when the video has to exist: real time through the API when it must be ready the moment someone needs it, batch for a scheduled campaign to a whole cohort.
To see your own customer data mapped onto a template, book a personalization assessment.
Published 2026-10-06 · Whilter.AI
