Codex
Claude
GeminiWhat you do
- Choose the approved source-to-Slack route and the canonical support destination.
- Set privacy, redaction, media retention, and task-creation policy.
- Send feedback through an approved surface or provide safe message and media refs.
Support and product teams receiving feedback across communication channels / communications
Customer Feedback Intake
One route-approved Slack thread containing the complete feedback packet and safe refs for investigation.
From request to resultA complete plan you can follow.
Visible planThe problem
Customer feedback arriving across chat or email can lose media, privacy context, and ownership before anyone investigates it.
AI can normalize several communication formats and preserve context, while StackOS enforces the configured route and delivery boundary.
What the agent does
- Verify the source, route, destination, media inventory, and data-sharing boundary.
- Normalize the report without diagnosing it or dropping allowed media.
- Create one complete Slack handoff, add the intake signal, and preserve investigation refs.
When this workflow helps
A reusable method, adapted to the request.
- Customer feedback or a support symptom arrives outside the canonical Slack support thread.
- A project needs a single Slack thread before support investigation starts.
- Source media, reporter context, route context, and safe message refs must be preserved for later agents.
Before it starts
Depends on the selected path
- A named source surface and message or media refs
- An approved cross-surface route and Slack target
- Privacy, redaction, retention, and media policy
What proves it worked
Evidence, not a success claim.
- Complete media inventory
- Route and target resolution
- Slack message or upload receipts
- Linked canonical thread ref
Workflow path
The reusable stages of the work.
A real run expands these stages around the request, context, selected tools, approvals, and dependencies.
- 01Passes to next stage
Capture Feedback
Read the inbound request and source refs, including media inventory and route hints.
- 02Passes to next stage
Establish Canonical Thread
Reuse a Slack-origin thread or create one route-approved Slack handoff that preserves source context and media.
- 03Passes to next stage
Add Intake Reaction
Mark the canonical Slack message with a reaction that indicates support intake has started.
- 04Verified outcome
Prepare Investigation Handoff
Return the refs and concise support context needed to start support.issue-investigation without re-discovering the source message.
Safe stopping and recovery
Useful even when the whole path cannot run.
- Stop with a missing-route or privacy question before copying customer content.
- Stop before sending if any required media cannot be forwarded safely.
- On partial provider failure, avoid duplicate sends and resume from the stored delivery receipt.
Documented follow-on work
The next workflow is conditional, not hidden.
Specialists inside this workflow
Clear roles for each part of the job.
Connected work