Workflows reference

Use this when a customer asks "why did it answer like that?". Each workflow lists example triggers, the reply, and what to watch.

Diagnose: quiet partners

Triggers: "which partners are dormant?", "which partners went quiet?", "which partners need attention?"
Reply: "Dormant partners (no qualifying activity for 90 days or more):", one line per partner with name, category and last activity date, up to 25, then a count of the rest. Empty: "No dormant partners in the last 90 days."
Watch: Slack never saves a diagnosis today, because record_diagnosis is not an allowed Slack write. The reply ends "This result was not saved: saving a diagnosis needs write access." Recommended next actions only appear on saved diagnoses, so customers normally see the list without them.

Query: rankings and briefs

Triggers: "Tell me my top 10 partners", "top partners by leads this month", "find briefs", "review brief" plus an ID.
Reply: active partners ranked by attributed revenue (or the requested metric), with period, currency and total; or a brief list with status and IDs.

Prove: performance and company revenue

One partner: "How did Acme do last month?". Asks for the partner and month if missing. Replies with attributed revenue from PartnerStack, leads, trials and activations. Partner figures are read-only.
Company revenue read: "Show September revenue". Four channels (Sales, Marketing, Product-led, Partnerships), total, partner channel mix and gap to the Anchor target.
Company revenue log: "Log September revenue: sales 4.7M, marketing 2.1M, product-led 1.15M, partnerships 3.9M". Asks for missing channels, and whether figures are in thousands when unclear. Confirmation shows the new figures and any existing figures it will replace. Only customer users can log.

Activate: briefs

Create: "Create a webinar brief for Acme about onboarding automation". Story and Social take one partner; Webinar and Event take a host and promoting partners. Confirm saves a draft only.
Setup: the draft message shows filled fields and the next question with Answer question, Change and Refresh review. Answers use the Brief setup modal and each save is its own Confirm.
Generate: Review generation, then Confirm. "This starts metered generation." Event registration stays closed.
Delivery: results post into the same private thread when generation finishes. See Delivery, Stop and recovery.

Decide: existing briefs

Approve: "approve brief" plus ID or exact title. Event approval warns that it opens the public registration page.
Regenerate: must name the Story, Social or Webinar asset.
Dispatch: proposes dispatch with a strategy choice. Dispatch does not generate or make the brief live; approval does.
Publish Riley / programme go-live: always refused as staff actions.

Mode matters

In a read-only environment, Diagnose, rankings, performance, revenue reads and brief reads work. Revenue logging, brief creation, setup, decisions and dispatch need the confirmed-writes mode, and generation also needs paid generation. App Home tells the person which mode they are in.