Triaging What Gets Escalated vs. Handled vs. Queued

Triaging What Gets Escalated vs. Handled vs. Queued

A client emails at 4pm asking for something. Does the CMO need to know now, tomorrow morning, or never? That judgment call is one of the most valuable things you do.

Why Triage Is a Skill, Not a Process

Anyone can forward emails. The reason your CMO needs you is that you learn to filter signal from noise. You protect their deep work time, batch the routine stuff, and only interrupt when it genuinely matters. Over time, you'll develop an instinct for this. Until then, here's a framework.

The Three Buckets

Everything that comes in goes into one of three buckets:

The goal is to put 60-70% of incoming items in "Handle," 25-30% in "Queue," and less than 5% in "Escalate." If you're escalating more than that, you're not triaging - you're forwarding.

What You Can Handle Yourself

Before you involve the CMO, check if Armbrain has the answer:

"Switch to Acme Corp"

"What was decided about the Q3 content calendar?"

"What's the status of the website redesign rock?"

If the client is asking a status question, a factual question about what was discussed, or a request for something that was already promised - you can probably answer it. Draft a response, review it for accuracy, and send it.

Things you can handle:

• Status updates on known projects
• Resending documents or links the client already has
• Confirming meeting times and agendas
• Sharing timelines that were already committed
• Scheduling or rescheduling non-strategic meetings
• Acknowledging receipt of something ("Got it, thanks!")

What Gets Queued for Morning

These are things the CMO needs to see but that won't catch fire overnight. Add them to your morning briefing notes:

• A client asking about a new idea or direction
• Requests that require CMO judgment but aren't urgent
• Internal team questions about priorities or approach
• Industry news or competitor moves the CMO should know about
• Meeting prep needs for later in the week

When you queue something, add context so the CMO can decide quickly:

"Acme's marketing director emailed asking if we should pivot the blog strategy to focus on AI topics. Not urgent - their next content review is Thursday. I pulled what we have on their current blog performance:"

"Show me campaign history for Acme blog content"

Include the relevant data so the CMO can make a decision in 30 seconds instead of 10 minutes.

What Interrupts Deep Work

This is the smallest bucket, and you should guard it carefully. Your CMO's deep work time is when they do their best strategic thinking. Every interruption costs more than the interruption itself - it breaks flow and costs 15-20 minutes of recovery time.

Interrupt for:

• An unhappy client (tone matters more than words - "I'm frustrated" is an interrupt)
• Money on the line (a deal at risk, a budget conversation going sideways, a payment issue)
• A deadline that will be missed today without CMO action
• A PR crisis or public-facing problem
• A key stakeholder threatening to leave or escalate

Do not interrupt for:

• "Quick questions" that can wait 2 hours
• FYI emails with no action needed
• Scheduling changes
• Routine deliverable requests
• Someone wanting to "hop on a quick call" about a non-urgent topic

When you do interrupt, lead with the decision needed, not the backstory:

Bad: "Hey, Acme's marketing director just emailed and she seemed kind of upset about the last blog post performance and I think..."

Good: "Acme's marketing director is unhappy with blog performance. She's asking for a call today. Want me to schedule 30 min this afternoon or do you want to call her now?"

Guarding Deep Work Time

Part of triage is managing the people who want access to your CMO's time. When someone asks for a "quick call" or sends a "can we chat?" message:

1. Check if it's truly urgent (use the criteria above)
2. If not, respond warmly: "They're in focused work right now - can I help with anything in the meantime, or should I find time on the calendar for later this week?"
3. Batch non-urgent requests into the next available meeting or check-in

You're not being a gatekeeper to be difficult. You're protecting the time that makes your CMO effective. Most people respect this when it's handled warmly.

Building Trust in Your Triage Judgment

The CMO needs to believe two things: that you'll escalate the right things, and that you won't escalate the wrong things. Both matter equally.

How to build that trust:

• Start conservative. In your first few weeks, escalate more than you think you should. It's better to over-escalate early than to miss something important.
• Ask for feedback. "Was that something you needed to see right away, or could it have waited?" This calibrates your instincts.
• Keep a triage log. Note what you handled, queued, and escalated. Review it weekly with your CMO until you're both confident in your judgment.
• Own your mistakes. If you handle something you should have escalated, say so immediately. "I responded to Acme about X, but I realize you should have weighed in. Here's what I said."

Log your triage decisions so they're visible:

"Quick note: Acme marketing director asked about blog pivot to AI topics. Queued for morning briefing - not urgent, next content review is Thursday."

Tips

• When in doubt, queue it. Queuing is safe. Handling something wrong or escalating unnecessarily both have downsides.
• Read for emotion, not just content. "Can we discuss the timeline?" is a queue item. "I'm concerned about the timeline" might be an escalation.
• Batch your communications. Instead of sending three separate Slack messages, send one morning update with all queued items organized by client.
• Track patterns. If a client escalates the same thing repeatedly, that's a systemic issue worth flagging - not just another follow-up.
• Protect yourself too. If you're drowning in triage volume, tell the CMO. That's a workload problem, not a you problem.

Related Guides

• Morning Routine - where queued items get delivered
• Following Up - what happens after triage identifies a follow-up need
• When a Client Emails 'Where Are We on X?' - handling the most common type of client request