Guides
How to triage customer signals (November 2026)
For owners who get messages from several channels and answer them late. After reading, you can sort every incoming signal in one short pass and know what needs a reply today.
In short
- Triage means deciding what happens to each signal, not answering all of them.
- Use few categories, define each in one line, and let nothing sit without a category.
- An AI can sort and draft; a person should approve anything that is sent.
What it is
A customer signal is any message that carries information about what a customer wants or feels: an email, a review, a chat message, a refund request, a question under a post. Triage is the first pass over these signals that decides the next step for each one before anyone spends time writing a reply.
How to do it
- Pick three outcomes. Act now, schedule, and no action. More categories slow you down, and the reason for a category is to make the next move obvious.
- Define each outcome in one line. For example: act now means a customer is waiting and the answer changes a sale or a refund. Written definitions make your choices repeatable and let an AI apply them the same way.
- Bring the channels into one view. A signal in a channel you forgot to open is a signal you ignored. One list per day is enough.
- Sort by the customer's wait, then by value. The oldest waiting question usually costs the most trust. Value breaks ties.
- Draft in batches. Writing similar replies together is faster and keeps the tone consistent.
- Review the "no action" pile weekly. Patterns appear there: the same question five times is a missing page, not five questions.
How Growth OX helps
Growth OX applies signal triage inside the Today view. For Gmail it reads through the claude.ai Gmail connector, read only, twice a day, and waiting replies appear in Today. Other tools such as Outlook, WhatsApp or Google Drive are read through your own signed-in browser (see connector). Each item shows where it came from.
When a reply is needed, the assistant can prepare it, but posts, replies and e-mails wait for your approval; you can approve, edit or refuse (see approval card).
Limits: Gmail for Codex is not supported yet. The sorting follows the rules and goals you set, so a vague goal gives vague triage. Growth OX does not send anything without you.
Other ways to do it
| Option | Good for | Limit |
|---|---|---|
| Shared inbox with labels | Teams that already live in mail | Labels are manual; other channels stay separate |
| Rules and filters in a mail client | Predictable senders and subjects | Cannot judge urgency from meaning |
| Helpdesk ticket queue | Support-heavy businesses | Setup and cost; focused on support, not sales signals |
| Chat assistant with pasted messages | Occasional batches | Manual copying; no standing view |
| Growth OX Today view | Mixed channels for one owner or small team | Limited to connectors it supports; needs your review |
Where to go next
Run the three-outcome sort for one week and count how many signals landed in each. If "act now" is always full, the cause may be slow replies upstream, which measuring a growth task can reveal. Before letting any tool send replies for you, read how to approve AI actions safely.
FAQ
Can AI triage replace reading the messages?
No. It can order and summarise them, but you should read the ones marked act now before replying, because a wrong category costs a customer.
What if a message fits two categories?
Choose the stricter one. A message that could be act now is treated as act now until you have read it.
How often should I triage?
Pick a rhythm you can keep, such as twice a day. Consistency matters more than frequency.