The Insights Hub: Converting Raw Feedback into Deliverables
Collecting feedback is easy. Converting it into deliverables without drowning is the hard part. This is a triage playbook for the Insights Hub, and a clear explanation of the two email pipelines that feed it.
The Customer Insights hub is a project inbox for customer feedback. Emails with the Customer Insights token become classified insights; the Internal Secret Token turns team emails into tasks, notes, budget entries, events or activities. Triage weekly: review, classify, convert, acknowledge, resolve.
- Two pipelines, two tokens: the Customer Insights token files messages as insights; the Internal Secret Token turns team emails into tasks, notes, budget entries, events or activities.
- A weekly triage rhythm: review New, classify, convert, acknowledge, resolve.
- Conversion targets: task, note, change request and more, each created from the insight's subject and content.
- Safe by design: customer input is evaluated, never obeyed as a command.
Two Email Pipelines on One Address
Each project has one inbound address, and a secret token in the message body decides what happens to the email. This is easy to confuse, so here it is plainly:
| Token | Who gets it | What the email becomes |
|---|---|---|
| Customer Insights token | Customers and partners (safe to share) | An insight in the Customer Insights inbox, classified by AI |
| Internal Secret Token | Trusted team members and tools only | A task, note, budget entry, calendar event or activity |
Because the internal token can create project data, treat it like a password. Every inbound email, and what it became, is visible in the admin-only Internal Email Inbox, where you can also convert any email by hand.
The Weekly Triage Playbook
Review New
Open the inbox filtered to New. The badge in the sidebar counts them.
Check the classification
Skim the AI-assigned intent and correct anything ambiguous. Spot-check new customers more closely.
Decide the target
Bug and small requests become tasks; larger requests or anything that moves scope become change requests; context-only items become notes.
Convert
Use Convert to project object. Task conversions add an AI-suggested due date, type and tags.
Update status
Move the insight to Acknowledged, In Progress or Resolved so the state is visible.
From Insight to Deliverable
A conversion fills the new object from the insight's subject and content, and for tasks the AI enriches it. You can convert the same insight more than once, for example first to a note for context and later to a task; each conversion creates a new object and the latest is shown on the insight. For decisions with consequences, the AI-drafted change request carries a full impact assessment, so the discussion starts from facts about schedule, budget and scope.
Customers Inform; They Do Not Command
A customer email is input to evaluate, never an instruction to execute. That is why the change request conversion explicitly treats the insight as customer input, and why scope-changing items go through approval. See Change Request Impact Assessment. ARI can also convert an insight or an inbox email into a task, note, budget item or change request using the same logic as the manual button.
- Feedback triaged ad hoc by whoever noticed
- Customer requests treated as commitments
- No view of what is waiting
- A weekly rhythm with counts by status
- Requests evaluated through change requests
- Status Summary bar and filters
About CoMng.AI
CoMng.AI is an AI-native project management platform that generates a project's plan, tasks, risks and budget from a description or document, monitors project health in real time, and gives both human teams and AI coding agents live access to the same project data, with a person approving every AI-generated change.
Turn the next customer email into a task in two clicks
Create a project, copy its inbound address and token, and let customer feedback arrive classified and ready to convert.
Frequently Asked Questions
What is the Customer Insights hub?
A project inbox where all customer feedback lands: complaints, bug reports, feature requests, questions, praise and suggestions. Messages arrive by email or manual entry and are classified by AI.
What is the difference between the two tokens?
The Customer Insights token files an email as an insight and is safe to share with customers. The Internal Secret Token turns an email into a task, note, budget entry, calendar event or activity and should be shared only with trusted people and tools.
How many insight types are there?
The AI chooses among eight intent types and you can override its choice at any time.
Can ARI help with triage?
Yes. ARI can update an insight's status and notes, and convert an insight or inbox email into a task, note, budget item or AI-drafted change request.
Where can I see all inbound emails?
In the admin-only Internal Email Inbox, which shows every inbound email routed to the project and what it became.
Related reading
See the full guide: Planning, Scope & Change Control Guide