// case study · lekta ai · voice ai demo campaign
NPS Campaign
Turning a voicebot demo from slides into something you test live — and get a personalized report by email.
- role
- Product Designer · UX & conversation flow
- scope
- 0→1 — concept to public launch
- timeline
- ~6 months
- team
- PM · junior designer · developers
- platform
- Lekta — voice AI
// problem
The company had no independent demo of its voicebot. Showing bots on slides didn't reflect what they could actually do.
// approach
An interactive landing page where anyone could test the voicebot live — language → call → email → report — with a conversation script and microcopy tuned for trust.
// outcome
A working proof of concept that let users test the bot in real time with no setup. Plus honest lessons about cross-team alignment when leads came in lower than hoped.
fig. 01
context
To promote Lekta's voice AI, we built an interactive NPS campaign where prospects could test a voicebot straight from a landing page — turning a marketing initiative into a real product experience that generated leads and validated the format for future self-service tools.
// who it served
prospective clients
test the voicebot directly, no setup — hands-on proof of the platform
marketing
drive traffic, capture leads, demo the product interactively
sales
use collected data and conversations to qualify and follow up
fig. 02
problem
A voicebot on slides.
A bot you test live from a landing page.
// constraints
- ~6 months, concept to public launch
- bot: no visible response length
- static language selection
- recognition limited to predefined edge cases
- ship fast — pave the way for a self-service NPS tool
- balance transparency about limits with a simple experience
fig. 03
process
// reasoning trace — each step follows from the one before
Market analysis & workshops
Internal workshops to define key user needs and the campaign's positioning. A mind map of value drivers, conversion points and the product signals worth highlighting in the demo.
The conversation script
Designed the dialogue to feel natural while showcasing the real capabilities of Lekta's voice engine — not a scripted happy path that hides the edges.
A focused user flow
One clear path optimized for engagement: language selection → voicebot interaction → email collection → report delivery. Every step earns the next.
Landing architecture & prototype
Designed the page architecture, layout and an interactive prototype — built with a quick launch in mind, since the campaign had to ship fast.
Microcopy, testing & analysis
Co-wrote microcopy to build trust and drive conversion, aligning tone with the brand. Supported implementation, tested the live version, and analyzed results to inform future experiments.
// the interactive demo — test the bot in three steps
01 · set up
enter your name, pick a language, start a live call
02 · live call
the bot calls you — connect and answer the NPS survey
03 · report
get a personalized report and full transcript by email
// process artifacts — from research to solution
click any frame to open it full-size
// positioning — where the demo fits
// insights → problems
// research & conclusions
// developing a solution — value & conversion map
// flow & information architecture
// positioning — where the demo fits
// insights → problems
// research & conclusions
// developing a solution — value & conversion map
// flow & information architecture
// key insight
The best pitch for a voicebot is letting people talk to it.
fig. 04
outcome
A demo that runs itself
Users tested the NPS voicebot in real time and received a personalized report — no setup, no sales involvement.
// the bot sold itself by talking
Honest lessons on leads
Leads came in lower than hoped. The main issue: email copy written outside the product team, lacking clarity and credibility.
// the product worked — the message around it didn't
Trust under real constraints
With real bot limitations, the flow balanced transparency about what the bot can and can't do with a simple, confident experience.
// honesty about limits builds more trust than hiding them
fig. 05
reflections
What cross-team alignment really means
The campaign proved that in growth work, the message and tone of voice matter as much as the product. A strong demo with weak surrounding copy underperforms — messaging alignment isn't a nice-to-have.
What it sharpened for me
Designing conversion-focused flows and content across touchpoints — landing, microcopy, conversation UX — and balancing user trust, business goals and technical constraints. It shaped my later growth-related work.
Have a complex product that needs clarity?
Open to a long-term B2B contract, a freelance project, or a one-off consultation.
or reach me directly: