Reply triage routes messages. Read each one for intent, decide the outcome, then place it where the right person can act without rereading the thread. When reply work shares a campaign queue, a higher priority setting does not guarantee that its calls happen before lower-priority work.1 Use priority as a capacity control and decide what each message needs. Finish with a disposition: mark it done, remind it for later, or respond immediately.2 A label without an action leaves the next person to reread the message.
Run the triage
Use the same short sequence for every reply. Move on once the message has an intent and an action, checking the queue when work competes for shared capacity.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Scan | whether the message asks for action | What does the sender want to happen? |
| Classify | whether it fits interested, objection, referral, unsubscribe, out of office, or ambiguous3 | Which intent is present? |
| Disposition | what should happen to the message next | Should I act now, set a reminder, or close it? |
| Queue check | whether a shared queue requires one campaign to take priority over another4 | Which work should this reply displace? |
Classify intent
Start with what the sender wants to happen. Read the whole reply before assigning a label because the last sentence can change the meaning of the opening line.
Use explicit intent labels for interested, objection, referral, unsubscribe, out of office, and ambiguous replies.3 Keep the ambiguous class when the message does not provide enough information to decide. Ask the smallest clarification question that will determine the next action, then move the reply forward once you have the answer.
A reply can show interest while raising an objection, or provide a referral while asking for more information. Record the signals that affect the next action instead of forcing the message into one interpretation. Stop reading once the intended action is clear.
Choose the disposition
After identifying intent, choose what to do with the message before opening another reply.
Respond immediately when the sender asks for information, a decision, or a next step that you can provide. Set a reminder when the reply gives you a timing condition or when the next move depends on something that has not happened yet. Mark the message done when it closes the loop and leaves no action for your team.
Write the action in plain language before moving on. A useful reminder says what you are waiting for and why the reply should return to the queue. An immediate response should answer the request or state the next step. A completed message should give someone else enough context to understand why no further action remains.
If you cannot choose an outcome, return to the reply and identify the missing intent. Ask a focused question before assigning priority.
Set priority when work competes
Choose priority after disposition, when you need to decide which live work gets capacity first. This applies when reply handling shares people or queue capacity with outbound campaigns.
A campaign priority control sets a campaign's importance relative to other campaigns using the same group of agents.5 If your setup exposes that control, assign an integer between 1 and 5 inclusive.6 The scale runs from 1 as the lowest priority to 5 as the highest.7
Use the setting as a capacity rule around the reply queue. It helps outbound dialing determine how many calls to place for each campaign for each agent.8 That can change which work competes for attention, while the intent and disposition still belong to the individual reply.
Before relying on the setting, check how the queue is staffed and what work shares it. If reply handling has its own capacity, campaign priority may have no bearing on message order. If the same people handle both, use the setting to make the tradeoff visible and review the result against actual response needs.
What not to do
- Do not force a reply into one label; labels are not mutually exclusive.9
- Do not assume a priority setting applies when the same agents are not assigned to at least two campaigns being compared.10
- Do not treat a default priority of 5 as a deliberate decision about your queue.11
- Do not let campaign priority decide the reply's intent or disposition. Those decisions belong to the message itself.
- Do not leave an ambiguous reply in the general queue without a question that could resolve it.