Skip to content
Request a demoDemo

Signature feature · Delivery & Sharing

Choose exactly when the message arrives.

Set the day and time, then deliver by email, SMS or a QR code printed with the gift.

See how a message travels Discuss your delivery flow
  • Email or SMS
  • Printed QR & PDF card
  • You trigger delivery
  • Download on or off
A man opens a gift box while the video message plays on his phone
One channel per messageemail or SMS, never both
Delivery Birthday gift · Julie
  • Scheduled for 14 June · 08:00
  • Channel Email
  • Delivery call notify
  • Stays available 90 days

Queued for 08:00

Example order, for illustration.

01 — What it changes

The gift has a moment. So does the message.

Not a checkbox at the end: three decisions — the moment, the channel, and what remains.

Tap an act. Each number is a decision you take.

Example brand

Schedule the delivery For Julie · Birthday
Queued for 14 June · 08:00

The moment — when it leaves

Chosen while recording, not on the day.

  1. A day and an hour Platform switchPlatform With scheduling on, the sender picks the date and hour before submitting.
  2. Any future moment, by API API callAPI Your integration can pass any future timestamp, straight from your own rules.
  3. Queued, not instant Platform switchPlatform Triggering a delivery queues the notification; a platform delay can push it further on purpose.
  4. The sender’s clock Message fieldMessage The hour is read in the browser’s time zone, then stored in UTC.

Julie, Marc and MAISON LUNE are illustrative.

For people
  • It arrives on the day it was meant for.
  • It comes through the channel they actually read.
  • They are told how long it stays.
For the brand
  • A day and an hour, set at recording time.
  • Email or SMS, from templates that are yours.
  • A QR code for whatever you print.
A woman records a message on her phone at her desk, a wrapped gift beside her laptop A woman records a message on her phone, a wrapped gift beside her laptop 14 June · 08:00

Recorded on a Tuesday. Delivered on the fourteenth, at eight.

02 — How a message travels

Three acts: the moment, the channel, and what comes after.

Each act is settled somewhere different — a platform switch, a message field, or your own call.

  • The moment

    When it leaves
    14 June · 08:00, chosen while recording
    • A day and an hourWith scheduling on, the sender picks the date and hour before submitting.
    • Any future moment, by APIYour integration can pass any future timestamp, straight from your own rules.
    • Or the moment you say goOne call notifies the recipient, the other opens access when your channel did.

  • The channel

    How it reaches someone
    • One channel, never twoEmail or SMS, asked for explicitly — never both, never a fallback.
    • Emails and SMS that are yoursSubject, layout and sender come from your own templates, one per language.
    • A QR for whatever you printEach container hands you a QR image and a card your printer can use.

  • After the play

    What stays
    Reachable 90 days by default, up to a year
    • Keeping the video is your callSwitch download on and the recipient keeps the file, exactly as encoded.
    • A window you set yourselfThe hosted link lasts as long as you decide, and can warn before closing.
    • A link that arrives dressedPasted into a chat, it opens a preview carrying your own wording and the message’s image.
The rules 1channel per message 90days by default, up to a year Any future timestamp by API QR as an image, card as a PDF Scheduling, download and the expiry warning are platform switches. The two delivery calls are API-key scopes.

03 — What it produces

The date, the route, and the afterwards.

Three gains, one per act — rarely for the same team.

Timing

The message lands on the date that carries it

A birthday at eight, a Christmas dinner at seven: chosen while recording, not on the day.

  • A day and an hour, set ahead
  • Any future timestamp, by API
  • No ceiling on the horizon
Channels

The delivery can be yours rather than ours

Some want us to send the email. Others already own the card, the parcel or the channel.

  • Email or SMS, from your templates
  • A QR image and a printable card
  • Trigger the send, or open access
Afterwards

After the first play is still a decision

Whether they keep the file, how long the link stays up, whether they are warned.

  • Download on or off, per platform
  • Retention from a day to a year
  • A shared link that previews itself

Not every delivery needs an inbox. Some travel with the gift.

  • A QR image per container
  • A ready-to-print PDF card
  • Unlocked when the courier leaves
Colleagues hand over a wrapped gift in an office lounge, one of them filming it Colleagues hand over a wrapped gift, one of them filming it Scan · one call opens it

04 — Why activate it

Everything before this can be redone. The delivery cannot.

Four reasons teams give us, and the two things we don’t claim.

  1. A gift has a date you did not choose

    The occasion sets the hour. Delivery is the only part that can be late.

  2. An inbox is not a guarantee

    An address can be mistyped, filtered or never opened. SMS exists for that, explicitly.

  3. Not every programme wants us to send anything

    A florist prints the code on the card; a retailer hands it over.

  4. How long it stays is a setting

    Too short disappoints. Forever is a question your legal team will eventually ask.

Two things we don’t claim With API v3, nothing is pushed to your systems; webhooks come with API v3.1 or 2.1. A forward from the recipient’s own inbox is counted nowhere.

05 — Where it shows

Three programmes, three ways in.

Main case

A florist whose delivery is the bouquet itself

The QR — or the branded card — is printed with the delivery note when the order is packed. Livstick sends nothing: when the courier leaves, one call opens the message.

A birthday, scheduled for eight

The sender records a week early and picks the day and the hour. One channel, chosen, never inferred.

Your own transactional email

The team owns its sending platform and wants no second sender in the inbox. Livstick only opens access.

Also: Midnight birthday messages Christmas orders shipped weeks ahead In-store cards scanned at the counter

FAQ

Eight questions we get about the last mile.

Can a message be scheduled for a future date?

Yes, once scheduling is switched on for your platform: the sender picks a day and a whole hour before submitting. Through the API, any future timestamp works.

Which clock does the chosen hour follow?

The sender’s: the date is read in the browser’s time zone, then stored in UTC. There is no time-zone field, so check a programme that spans several markets.

Can a message go out by email and SMS at the same time?

No. Each message carries one channel, and a number alone is never enough: SMS is asked for explicitly, in international format — plus sign, eight to fifteen digits.

Do we write the email and the SMS ourselves?

They are templates on your platform — subject, layout, content and sender — one per language. A channel with no template sends nothing at all, and SMS routing is arranged programme by programme, market by market.

Can we deliver through our own channel instead of Livstick’s?

Yes. Two calls, two roles: notify asks Livstick to send the message, unlock opens access when your own email, card or parcel already delivered it. Contacts can be prefilled or replaced.

Is the send immediate?

Triggering a delivery queues the notification rather than sending it synchronously. A platform delay can push it further on purpose, and a batch can override it.

Can the message be printed on a card or a parcel insert?

Each container exposes a QR image, and a batch export ships a whole print run. A PDF template adds a ready-to-print card. The QR opens a web page, so playing needs a connection.

Can the recipient keep the video?

Download is a platform switch. When it is on, the recipient saves the file and keeps it; the hosted link follows your retention — ninety days by default, up to a year.

A woman and a man exchange a video message on their phones in a living room

What needs to reach someone?

A gift you couldn’t deliver on the day is a gift you delivered late.

Discuss your delivery flow

One message, one channel, one moment — and a link that lasts as long as you decide.