Autopilot struggles to extract ideas from multi-topic Slack feedback
F
Front Partridge
In cases where a single message contains:
A clear feature request
Supporting context (training notes, stakeholder alignment)
Multiple related pain points
Autopilot frequently routes these to “Low confidence” instead of:
Extracting the primary idea, and
Splitting secondary themes into separate ideas or insights
Example pattern:
Core request: Display program descriptions in the daily print calendar
Supporting pain point: Duplicate manual work (re-entering descriptions via text boxes)
Even though both signals are clear, Autopilot struggles when they are embedded in narrative context.
Expectation:
For Ideas to be the primary workflow, Autopilot should be able to:
Identify the dominant request in a message
Separate secondary but distinct problems
Ignore internal context (e.g., “no action needed”, stakeholder decisions)
Right now, this creates friction because:
We need to manually restructure messages before sending, or
We risk losing signal in Low confidence
Sarah Hum
Thanks for sharing this, Front Partridge. This is really helpful feedback.
Totally makes sense that when a Slack message mixes a clear request with narrative context and a couple related pain points, you still want Autopilot to pull out the dominant idea and split the secondary themes instead of dropping it into Low confidence.
We will share this with the team and we will let you know if we have an update.