Operating pattern
External
Customer-facing follow-up, CRM, and outbound actions are grouped into one pattern with approvals where needed.
Workspace
Advocacy Nomination
Trace the exact path from input signal to workflow execution, approvals, files, and roadmap outcomes.
Signals ingesting
Agents reasoning
Actions queued
RunPausedExternal
Advocacy Nomination
Positive customer outcomes were detected, but external reference promotion is paused pending legal-safe review.
Customer advocacy agent
Trigger: Positive outcome call detected
Last run: Yesterday
Linked meetings
1
The run record should collect every internal or external meeting that contributed to this workflow.
Generated outputs
0
Actions, approvals, and files remain attached to the same execution object instead of being scattered.
Architecture View
How this run moves through the platform architecture
This is the systems view: source inputs, run core, specialist outputs, and the tracking layer that explains what happened.
01Inputs
External pattern
This run is consolidated around customer-facing meeting activity.
Meetings attached
Every transcript that contributed to this run is collected here.
Trigger source
Positive outcome call detected
02Run Core
Run record
Owns the lifecycle, status, and linked entities for this workflow execution.
Step graph
Tracks the consolidated stages instead of treating every action as a separate run.
Risk gating
Approvals stay attached to this run so governance is visible in context.
03Outputs
Action previews
Generated actions remain attached as explainable outputs from the run.
Files
Artifacts from the run inherit lineage and stay discoverable in the file workspace.
Roadmap links
Product demand and feature work stay stitched to the same execution chain.
04Tracking
Owner
This operating pattern is explicitly assigned so work does not disappear between teams.
Status
The run carries its own health and pause state instead of being inferred from unrelated screens.
Lineage
Inputs, approvals, files, and roadmap outcomes are all explainable from one record.
Execution
Step-by-step run history
01Completed
Detect proof points
Outcome language and measurable impact were found in the customer conversation.
02Completed
Create advocacy record
Reference nomination package was drafted with evidence.
03Awaiting Approval
Wait for approval
1 approval decision are still gating risky work.
Source Meetings
Generated Outputs
Files
Approvals
Promote Acme as a reference candidate
PendingRequires advocacy and legal review
Approver: Customer success director
Roadmap Links