Who this is for: Product teams preparing a timed storyboard for an original launch asset.
What to prepare
- Verified new integration scope
- Approved source and destination identities
- One supplied example transfer
- Eligibility and current release status
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
State the user task
Show an illustrative event and the task it needs to inform.
On screen:Bring the relevant event into the task.
- 02
5–10s
Announce the new scope
Reveal approved identities with a one-way relationship unless two-way behavior is verified.
On screen:A new connection is available within the stated scope.
- 03
10–18s
Show one handoff
Track the same labeled example event from source to its supplied destination state.
On screen:The supplied event reaches the task record.
- 04
18–23s
Hold the useful result
Keep the destination record and exact transferred field readable.
On screen:See the relevant context beside the task.
- 05
23–27s
Name access conditions
Display verified eligibility and any consequential release limit.
On screen:Check the supported scope and eligibility.
- 06
27–30s
Offer the next step
Show the actual setup or access destination.
On screen:Read the current connection details.
Make it your own
- New scope
- State exactly what has become available.
- Example item
- Track one approved field or object.
- Eligibility
- Keep current release conditions visible.
Announce scope rather than every setup step
The event-to-task scenario is illustrative. The launch should identify exactly what is newly supported and why that matters for one task. It should not imply universal synchronization, automatic setup or instant transfer.
A separate source-to-destination walkthrough can explain mapping and verification. This announcement gives viewers enough information to decide whether that detail is relevant.
Adapt the evidence
Use supplied product states when available. If the only approved material is a flow diagram, label it as an explanatory diagram rather than a recorded transfer.
For a 60-second version, explain the most consequential eligibility condition and one boundary. For a 15-second version, retain the new scope, source-destination direction and current access status.
Review the relationship
Check arrows, logos and status labels as carefully as copy. A bidirectional arrow can expand the claim even when the script is precise.
This template describes the reader's integration announcement, not an Animro integration. Use only approved partner assets and the actual release facts.
Review checklist
- The announcement distinguishes new scope from setup instructions.
- Transfer direction is accurate.
- Example content remains consistent.
- Partner imagery introduces no broader claim.