A video can arrive with immaculate product footage and still tell the customer something untrue: “You’ve just received your new device.” If the delivery event reached marketing several days late, production quality will not rescue the sentence.
For an overseas brand coordinating a China-based production team, relative-time language deserves its own brief. Decide what must be known when the customer sees the message before recording “today” into the only available voice track.
The documented mechanism is narrower than the implication
Braze’s current Create a Canvas documentation explains that action-based delays use the submitted custom-event timestamp. A backdated timestamp beyond the waiting window can make the delay count as elapsed and the message send immediately. The passage was checked on October 25, 2026.
That describes one product’s mechanism, not every automation platform or a newly announced feature. The production implication is an ONCE inference: a configured wait need not start at data receipt, and an immediate trigger does not establish a recent customer action.
The question here is not whether to build a lifecycle content library. It is which meaning of “now” a particular script assumes.
ONCE’s three timing questions
First, when did the business event occur? Order placement, dispatch, delivery and device activation are different events. An order record cannot establish possession of the product. Identify the relevant order or item and the event’s actual meaning.
Second, when did marketing learn about it? Investigate batch imports, offline reporting or historical backfills. Do not rewrite a genuine historical occurrence as current merely to make a campaign run conveniently. Preserve the factual record; the operational team must separately design delivery behavior for its actual tools.
Third, is the customer still in the assumed state at send time? They may have completed setup, cancelled the order or entered a support process. A true past event does not establish that its original message remains suitable. Uncertainty needs an explicit neutral-content or hold decision, not a default send.
This is a proposed ONCE briefing method, not a platform feature. It does not require a production supplier to take over the customer database. It requires the brand to distinguish confirmed states from creative assumptions.
Record the demonstration separately from the time claim
Consider a hypothetical smart-home device, not an ONCE client. “You’ve just received it—let’s make your first connection today” assumes a recent delivery, the right recipient and no completed setup. Do not make it the only opening if those facts cannot be established reliably.
A more durable opening is: “When you’re ready to connect this device, check these two conditions first.” The shared demonstration can still show the correct model, connection entry point and success state without declaring what the viewer has just done. Whether someone who already completed setup should receive it remains a separate decision. Neutral wording is not permission to send indefinitely.
Capture the opening, core demonstration and closing as separable elements, with clean picture and separated audio. This does not mean commissioning a new film for every hour. It prevents one time-dependent line from stranding otherwise useful footage. Content that never depended on individual timing may need no extra version at all.
“Tomorrow” adds a promise
“Arrives tomorrow,” “last chance today” and “replace it in two days” depend on delivery commitments, offer validity or usage conditions. Purchase history alone does not establish any of those.
Where the relevant information is unavailable, keep such claims out of a general-purpose master. Place necessary changing details in a maintained destination or message field, and check consistency with the video before release. If the channel cannot support a safe update, use a version without the promise or hold the send. Small print beside a video does not automatically undo an incorrect spoken assertion.
Rehearse timing without messaging real customers
In an authorized test environment, the brand can review three scenarios: an event arriving promptly, the same type arriving late, and an event arriving after the customer’s relevant state changed. Retain the expected content choice and observed path, not just a “sent successfully” screenshot.
Check that the time-sensitive opening is restricted to its agreed conditions, that the neutral version can actually be selected, and that unsuitable messages are held or rerouted. With several orders or devices per customer, verify item-level relevance rather than treating one person’s overall status as the answer for everything. Available controls and testing scope depend on the brand’s tools and permissions.
No customer system was accessed or tested for this article. These are proposed checks, not a claim that every latency problem can be detected.
Buy a defined handover, not unlimited versions
The business owner approves event meaning, state and promises. CRM or data operations confirms time sources and invocation. The production partner identifies copy dependencies and delivers replaceable sections and clearly mapped files. Together they decide which sentences are unavailable unless their conditions hold.
Scope the sensitive opening, neutral opening, shared demonstration, handover notes and any test support explicitly. Do not promise an unmeasured conversion lift or bury unlimited system maintenance in editing fees.
Before the next shoot, circle every “just,” “now,” “today” and “tomorrow” in the script. Ask who can establish that it will still be true when viewed. Where there is no answer, change the copy first.
Source and interpretation
Braze, Create a Canvas, Step 2 custom-event timestamp guidance; no revision date shown for the cited passage, checked October 25, 2026. This is evergreen production analysis, not a recommendation to migrate platforms. The three timing questions, scripts and rehearsal are ONCE proposals; the device example is hypothetical.
