Feature area
Stories group related work. POVs are the angles inside a story, each with its own questions, audience, and outreach. This is the structural layer the rest of the workflow builds on.
Features/Story and POV operations
A story holds shared context—headline, description, languages, tags, and section assignment. POVs break that story into operational angles. Each POV can carry its own headline fields, questions, and send configuration.
Stories are created and browsed on the Stories page. POVs appear on the POV list and are authored in depth from the POV panel when preparing outreach.
Operators define how many angles a story needs and how each POV is worded before any send happens.
How desks and campaigns move from container to angles.
Step 1
Define the shared container with title, description, tags, and section scope.
Step 2
Create one or more POVs with targeted questions rather than one generic prompt for the whole story.
Step 3
Configure story and question text across the languages your audience and templates require.
Step 4
Move to the POV panel to attach recipients, templates, and sends to specific question sets.
Build multiple story angles from one editorial brief.
POV = one focused angle with its own audience and ask.
Yes. That is the default model. Each POV represents a distinct angle with its own questions and outreach context.
POV records are saved from the POV panel question workflow and managed on the POVs page. The create tile on the POV list is intentionally disabled in favor of panel-based creation.
Definitions used on this page.
A specific angle inside one story or campaign, with its own question set, audience, and outreach message.
Read in glossaryThe higher-level container that groups one or more POVs around a shared editorial or campaign objective.
Read in glossaryWe can walk through setup, approval, and reply handling using your story format.
