THE DAILY AI INTELLIGENCE BRIEFING
Briefing ID: 26-127
Status: Confidential
I have sat through enough post-incident conversations on both sides of the table to recognize the moment when a technical problem becomes a communication problem.
All of the teams on the vendor side are looking at the issue from different angles:
The engineering team is talking about failover behavior, dependency chains, and recovery windows.
Customer Success wants to know what to tell a very unhappy client.
Sales is worried about a renewal.
An executive asks when the written explanation will be ready.
And suddenly six people are trying to turn an incident log into something a customer can actually understand. That translation work is harder than it looks.
A customer affected by an SLA breach usually needs several things at once. They need acknowledgment that the disruption mattered, a factual explanation of what happened, confidence that the immediate problem has been contained, and enough detail about corrective action to believe the organization learned something.
Unfortunately, those needs pull the message in different directions.
Engineering may want precision, legal may want restraint, Customer Success may want warmth, and leadership may want reassurance. Meanwhile, the customer wants someone to explain what happened without hiding behind technical language or vague promises.
AI can be very useful here because much of the work involves organizing, translating, comparing, and drafting. Give it the verified incident facts, customer impact, contractual context, mitigation steps, and communication requirements, and it can create a strong first draft much faster than a committee writing sentence by sentence.
You still confirm every factual claim, remove speculation, check contractual language, validate technical explanations with engineering, and make sure future commitments are actually approved. During an outage recovery, the polished sentence that happens to be wrong is far more dangerous than the awkward sentence you catch before sending.
The best use of AI in this scenario is to give your team a structured starting point that forces the right questions before anyone writes the apology.
Let's go raise your AIQ.
THE MASTER PROMPT
📄 SLA Breach Recovery Builder
INTEL FROM Q:
Use this after the incident team has established a verified set of facts. The prompt helps you turn technical incident information into a customer-ready recovery package while keeping assumptions, commitments, and unverified claims visible for human review.
ROLE
Act as a senior incident communications advisor with experience in B2B technology, customer success, service reliability, executive communications, and post-incident reviews.
REQUEST
Create a complete SLA breach recovery communication package following an unexpected service outage.
GOAL
Help us communicate with affected customers clearly, empathetically, and ... 
NON-SUBSCRIBERS
🔒 RESTRICTED: INSIDE THE FULL BRIEFING
The Master Prompt is just the beginning of what you are missing as a free, non-subscriber.
AIQ with Paul™ subscribers are currently reading the rest of today's intelligence brief, which includes:
⚙️ The Logic: The psychological and technical breakdown of why this specific prompt structure works, so you can learn to build your own.
🛠️ The Turbo Boost: Advanced modifiers and parameters to take the baseline prompt and make it 10x more powerful.
📑 Applied Intelligence: 3-5 specific, real-world business scenarios where you can deploy this strategy today.
⚠️ Glitch Watch: The common issues and errors AI will make when executing this task, and how to build guardrails against them.
📖 AIQ Vocabulary: One new term demystified so you can speak about AI with absolute confidence.
🗺️ The Community Challenge: A weekly mission to test your new skills and raise your baseline AIQ.
Don't operate with half the intel.
> Join the network of everyday people raising their AIQ. And even better: It’s completely free!
Click the button below to get tomorrow's brief delivered straight to your inbox.
Oh, and you will be able to see this and all of the previous Daily AI Intelligence Briefings here on the website!
Let's raise your AIQ.
Until next time,
