A QR code, a counter, and the customer’s own phone.
The journey opens in the customer’s own browser, on the programme’s mobile background — no queue at the till.
Experience
Recording and playback run in the browser, on whatever phone, tablet or computer people have to hand. No app to install.


Someone tucked a voice into your bouquet.
Press play to hear it.

Where it acts
A gift rarely waits for a desk: scanned at a counter, opened on the way home, revealed on a sofa — a different screen each time.
Fullscreen on a phone, or a hand-off to the device camera.
Every message plays in the browser, whatever the screen.
Background and logo carry their own mobile values.
Each event carries its device, so the funnel splits in two.
How it works
Add your voice to the gift.

One link opens the journey in the browser. No app, no account.

Fullscreen in the page, or handed to the phone’s own camera.
A message for you.

Every message plays in the browser, on any screen.
Good to know
“Any device” is easy to write. Here is where the split actually falls.
One setting decides: the recorder takes over the page, or the phone’s own camera opens.
Background, background position and logo width each have a mobile value next to the desktop one.
No separate tablet treatment: a tablet is handled as a phone or a desktop, by width and pointer.
Which recording mode your integration starts with depends on the widget generation you embed.
Settled at scopingThe journey opens in the customer’s own browser, on the programme’s mobile background — no queue at the till.
One colleague records from a narrow intranet column; another opens the link that evening, on a phone. The funnel is read per device.
Example brands and messages, for illustration.























FAQ
No. Recording and viewing run in the browser, from a link. Even when a phone hands capture to its own camera, it returns to the same web journey.
That’s a setting you choose at integration time: one records inside the page in fullscreen, the other opens the device camera. Importing an existing video stays available in both.
Yes. Background, background position and logo width each have their own mobile value, and the back office previews that rendering before you publish.
Yes. It measures its own container rather than the screen, and goes compact when that container gets narrow. A sidebar embed behaves like a phone on a desktop.
Yes. Every journey event carries a device-aware flow — mobile, desktop, and the same split for the embedded widget. No breakdown by device model or operating system.