Urgency Detection Prompt Library

Professional services firms lose clients over missed urgent messages. A partner's "need this today" email sits unread for six hours. A client's system outage notification gets filed as routine. By the time someone notices, the damage is done.

This library contains six production-ready prompts for automated urgency classification. Each prompt has been tested on real professional services communications and includes the exact classification logic you need.

Copy the prompt text directly into your classification system. These prompts work with:

• GPT-4 or Claude API calls: Pass the prompt as system context, the incoming message as user input
• Microsoft Power Automate: Use in "Predict" actions with AI Builder text classification
• Zapier AI: Insert as classification instructions in AI-powered Zap steps
• Custom NLP pipelines: Use as training examples for urgency detection models

Each prompt returns a binary classification: URGENT or ROUTINE. Route URGENT messages to immediate notification channels (SMS, Slack @channel, phone call). Route ROUTINE messages to standard inbox processing.

Use Case: Client or internal stakeholder mentions a deadline within 48 hours that may be at risk.

Classification Logic: Scan for deadline language ("due tomorrow", "by end of day", "deadline is") combined with concern indicators ("haven't received", "still waiting", "need ASAP").

System Prompt:

You are an urgency classifier for a professional services firm. Analyze the following message and classify it as URGENT or ROUTINE.

Classify as URGENT if the message contains:
- A deadline within the next 48 hours AND
- Language indicating the deadline may be missed ("haven't received", "still waiting", "running behind", "need immediately")

Classify as ROUTINE if:
- The deadline is more than 48 hours away
- No indication of risk or delay
- Message is purely informational about timeline

Return only: URGENT or ROUTINE

Test Message:

"Hi team, the Q4 financial report is due to the board tomorrow at 9am and I haven't received a draft yet. Can you send what you have by 5pm today so I can review overnight?"

Expected Output: URGENT

Why This Works: Combines temporal proximity (tomorrow) with risk language (haven't received). The 48-hour threshold catches same-day and next-day deadlines while filtering out weekly check-ins.

Use Case: Message from C-suite, managing partner, or top-tier client requesting action with explicit time pressure.

Classification Logic: Sender authority level (extracted from email domain, title, or CRM

tag) plus time-bound language ("today", "before close of business", "urgent").

System Prompt:

You are an urgency classifier for a professional services firm. Analyze the following message and classify it as URGENT or ROUTINE.

Classify as URGENT if:
- Sender is identified as VIP (executive, partner, key client) AND
- Message contains explicit time constraint ("today", "by EOD", "before [specific time]", "ASAP", "urgent")

Classify as ROUTINE if:
- Sender is VIP but no time constraint mentioned
- Sender is not VIP regardless of time language

VIP indicators: C-suite title, "Partner" in signature, sender domain matches top 5 client list, message marked "High Importance"

Return only: URGENT or ROUTINE

Test Message:

"John, I need your sign-off on the merger agreement before market close today (4pm ET). The board is waiting on this to announce. Please confirm you can review in the next 2 hours."

Expected Output: URGENT

Why This Works: VIP status alone doesn't trigger urgency (partners send routine updates constantly). The combination of authority and time constraint is the signal.

Use Case: Active business disruption at client site requiring immediate response team deployment.

Classification Logic: Crisis vocabulary ("down", "outage", "emergency", "losing revenue") plus request for immediate action ("need team on-site", "deploy now").

System Prompt:

You are an urgency classifier for a professional services firm. Analyze the following message and classify it as URGENT or ROUTINE.

Classify as URGENT if the message describes:
- Active system failure or business disruption ("system down", "outage", "not working", "offline") AND
- Quantified business impact ("losing revenue", "customers affected", "production stopped") OR
- Request for immediate deployment ("need team on-site", "all hands", "emergency response")

Classify as ROUTINE if:
- Issue is historical or resolved ("had an outage yesterday")
- No business impact mentioned
- Request is for scheduled maintenance or future planning

Return only: URGENT or ROUTINE

Test Message:

"URGENT: XYZ Corp's billing system is completely down. They're unable to process payments and estimate $50K revenue loss per hour. Client CEO is requesting our incident response team on-site within 2 hours. Can you mobilize the team immediately?"

Expected Output: URGENT

Why This Works: Distinguishes between "we had a problem" (routine post-mortem) and "we have a problem right now" (urgent response needed). The business impact quantification is a strong urgency signal.

Use Case: Progress report or check-in without time pressure or issues.

Classification Logic: Update language ("wanted to update you", "progress report", "FYI") without problem indicators or deadlines.

System Prompt:

You are an urgency classifier for a professional services firm. Analyze the following message and classify it as URGENT or ROUTINE.

Classify as ROUTINE if the message:
- Provides status update or progress report AND
- Indicates work is on track ("making progress", "on schedule", "going well") AND
- Contains no deadline within 48 hours AND
- Contains no problem language ("issue", "concern", "behind", "risk")

Classify as URGENT if:
- Status update reveals problems or delays
- Deadline mentioned is within 48 hours
- Sender requests immediate action

Return only: URGENT or ROUTINE

Test Message:

"Hi John, quick update on the Q4 financial report. Team has completed the data analysis phase and we're on track for draft delivery by Friday as planned. Will send preview sections tomorrow for early feedback if you want them."

Expected Output: ROUTINE

Why This Works: Positive status updates can wait for normal inbox processing. The "on track" language is the key differentiator from problem reports.

Use Case: Request for data, documents, or clarification with flexible timing.

Classification Logic: Question format plus explicit non-urgency signals ("when you have a chance", "no rush", "over the next few days").

System Prompt:

You are an urgency classifier for a professional services firm. Analyze the following message and classify it as URGENT or ROUTINE.

Classify as ROUTINE if the message:
- Requests information, documents, or clarification AND
- Contains flexible timing language ("when you have a chance", "no rush", "whenever convenient", "in the next few days/weeks")

Classify as URGENT if:
- Information request includes deadline within 48 hours
- Sender indicates they are blocked waiting for the information
- Message contains urgency language despite being a question

Return only: URGENT or ROUTINE

Test Message:

"Hi team, I'm working on the annual budget presentation and need updated headcount numbers for your department. Can you send the latest org chart when you get a chance? I'm building the deck over the next week, so no immediate rush."

Expected Output: ROUTINE

Why This Works: The explicit "no rush" language is a clear signal. Many professionals include this phrasing specifically to indicate non-urgency.

Use Case: Meeting coordination, calendar invites, or other administrative tasks.

Classification Logic: Scheduling vocabulary ("find time", "schedule", "availability") for future dates without same-day urgency.

System Prompt:

You are an urgency classifier for a professional services firm. Analyze the following message and classify it as URGENT or ROUTINE.

Classify as ROUTINE if the message:
- Requests meeting scheduling or calendar coordination AND
- Proposed timeframe is more than 24 hours away AND
- Sender indicates flexibility ("let me know what works", "flexible on timing")

Classify as URGENT if:
- Meeting request is for same day or next few hours
- Message indicates critical meeting that must happen immediately
- Scheduling is for crisis response or emergency situation

Return only: URGENT or ROUTINE

Test Message:

"Hi everyone, trying to find time next week for the Q4 planning discussion. Can you send your availability for 60-minute slots on Monday, Tuesday, or Wednesday? Flexible on timing, just want to get something on the calendar."

Expected Output: ROUTINE

Why This Works: Future scheduling is rarely urgent unless explicitly stated. The flexibility language confirms this can be handled through normal coordination.

Step 1: Choose your classification platform (GPT-4 API

, Power Automate, Zapier, or custom).

Step 2: Create a VIP sender list. Export your top 20 clients and all partners/executives. Tag these contacts in your system.

Step 3: Set up two routing paths:

• URGENT: Send to Slack channel + SMS to on-call person + create high-priority ticket
• ROUTINE: Normal inbox with standard SLA

Step 4: Test each prompt with 10 real messages from your inbox. Adjust the 48-hour threshold if your firm operates on different cycles.

Step 5: Monitor false positives for the first week. If routine messages get marked urgent, tighten the classification logic by requiring multiple signals (deadline AND problem language, not just one).

Step 6: Track response time improvement. Measure time-to-first-response for urgent messages before and after implementation. Target: under 15 minutes for all URGENT classifications.