Who this is for: Product marketers and partner teams announcing a verified software connection.
What to prepare
- Approved integration relationship and scope
- Exact source, transferred item and destination
- Supplied product evidence or a labeled explanatory diagram
- Current eligibility, status and follow-up route
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Illustrative brief: announce a fictional connection that places one supported event into a task record. Open with the user's need for relevant context, introduce the approved source and destination, and follow the same example event into the supplied result. Use a one-way path unless the verified scope supports another direction. Hold the transferred field so viewers can inspect what arrived. State eligibility and current release status. Do not invent automatic setup, instantaneous timing, additional supported fields or partner endorsements. End with the actual connection-details or access destination. This brief describes the reader's product integration and does not imply an Animro integration.
Define the announcement job
The launch asset should help viewers recognize whether the new connection is relevant. It can lead to a detailed setup walkthrough, but its primary job is announcing scope, task value and availability.
Choose one concrete transfer rather than showing a network of logos. A simple source-item-destination story is more inspectable than a broad claim that everything is connected.
Select suitable evidence
Good inputs identify the exact object or field, direction, prerequisites and resulting state. Use consistent example values so the viewer can track the handoff. If only a diagram is approved, label it as an explanation rather than a recorded transfer.
Unsuitable inputs include unapproved partner marks, contradictory field lists, a mock destination that invents data or an old release note whose availability has changed.
- Scope decision: identify what is newly supported and what remains excluded.
- Evidence decision: distinguish actual source states from illustrative diagrams.
- Access decision: state who can use the connection and where details are available.
Build the story and boundaries
Start with the user task, announce the new scope, show one handoff and hold the result. Keep configuration detail in a separate resource unless it is necessary to interpret the announcement.
Review arrows and visual timing as claims. A two-way arrow implies reciprocal behavior; an instant flash between systems can suggest performance the evidence does not establish. Use neutral transitions when timing is not the subject.
Confirm the relationship wording, partner assets and destination before publication. The creative plan is not a test of the integration and should never be presented as proof that a transfer ran successfully without actual evidence.
Review checklist
- The newly available scope is exact.
- The transfer direction and example item are consistent.
- Diagrams are distinguished from recorded evidence.
- Eligibility and partner wording are approved.
- No automatic setup, timing or broad compatibility claim is invented.