Turn scattered feedback into a weekly evidence packet.
Group recurring customer feedback, compare it with product behavior, and prepare a source-linked brief without overstating anecdotal evidence.
How this composition works
This workflow combines approved support discussion with product analytics to identify patterns worth investigating. It preserves the distinction between qualitative reports and measured behavior, cites representative evidence, and records uncertainty so product teams can decide what deserves follow-up.
Collect support themes
Find recurring approved feedback and retain links to representative reports.
Check observed behavior
Compare reported friction with relevant product events and funnels.
Validate the pattern
Use a second authorized analytics view where the question requires it.
Update the evidence register
Record themes, strength, owners, and unresolved questions.
Connected systems
These are the real product connectors composed for this example, each scoped to the credential permissions your workspace approves.
Slack
Read channels and messages, post messages, and upload files as your Slack bot.
Explore connectorPostHog
Query PostHog analytics, generate HogQL from questions, and manage insights.
Explore connectorMixpanel
Access Mixpanel projects to query events and properties, edit them, and create tags.
Explore connectorAirtable
Query and create Airtable tables, fields, and records.
Explore connectorOptional skills
Where relevant, skills add reusable method and verification. The connectors and agent instructions remain the primary building blocks.
Ticket Triage
Summarize and classify a support issue, suggest priority and routing, and identify missing evidence. Use for new tickets, duplicate checks, escalation intake, or queue review.
See the playbookData Validation
Validate an analysis before sharing by checking lineage, methodology, calculations, bias, visualizations, and whether conclusions follow. Use for SQL, spreadsheets, dashboards, or reports.
See the playbookTry asking
More examples for Customer support
Build a governed workflow like customer feedback brief.
Tell us what your team repeats today. We will map the systems, approval boundaries, and first governed run with you.