Before we start

Be honest. Have you ever passed
a problem on — before you'd really tried?

You don't need to know any system to do this well. You just need to think.

A ticket comes in. A call lands. The answer isn't immediately obvious — so it gets passed to another team, left for someone else, or escalated up the chain.

And somewhere in the back of your mind, a thought: I probably could have figured that out.

This isn't a criticism. It's one of the most natural responses in the world. But it's also exactly the habit that PRISM is here to change — not by telling you what to do, but by changing how you think.

"Not knowing the answer isn't the problem.
Not trying to find it is."
The Escalation Habit

A ticket comes in. You don't immediately know the answer. What do you do first?

A
Escalate it — someone else will know
B
Ask the customer for more info
C
Look around the system to understand what's happening
D
Check internal docs or knowledge base
The reframe

Not knowing is where
everyone starts.

Think about something you're genuinely good at — anything. A sport, a skill, a hobby. Nobody sat you down and explained every instinct you'd eventually develop. You just did it, repeatedly, until the thinking stopped feeling like thinking. You figured out where you add value, what decisions make sense in the moment — and it became second nature.

Support work is no different. The agents who grow fastest aren't the ones who know the most — they're the ones who are most willing to go and find out.

The good news? Logical thinking isn't a personality trait you either have or don't. It's a skill. And like any skill — it gets sharper every time you use it. Even the most technical-looking problems have a logical reason behind them. A system error, a permission issue, a wrong code — they all follow a trail. Your job is to follow it.

The Assumption Trap

A user says: "The system isn't saving my changes." What's your first thought?

A
The system is broken
B
It's probably user error
C
Something specific is failing — I need to find where
D
I've seen this before — I know the fix
The three questions

Every answer starts with
three simple questions.

Not frameworks. Not flowcharts. Just three things a curious person naturally asks.

WHAT
What is actually happening here? Not what the customer thinks is happening — what does the data show?
WHY
Why is this happening? What caused it? A symptom always has a root cause. Find that.
HOW
How do we fix it — or at least help right now? What's the next step the customer can take?
The Investigation Depth

You find something that might explain the issue. What do you do next?

A
Go with it — it's probably the cause
B
Fix it and move on
C
Check if it explains everything you're seeing
D
Escalate to confirm
A real example

Curiosity over panic.

Two agents. Same ticket.0:00
Two agents. Same ticket. Very different outcomes.
Click to watch
The ticket
"Hi, I've just been charged twice on my account this month. I have no idea why. Can someone look into this please? — Sarah"
The Resolution Mindset

You've identified the issue, but the full fix requires another team. What do you do?

A
Escalate it to the right team
B
Tell the customer to wait
C
Provide a workaround or clear next step while it's being fixed
D
Close the ticket — it's out of your hands
The bottom line

The answer is almost always
already there.

In every system, every platform, every tool you'll ever support — data exists for a reason. Logs, records, histories, permissions — they tell a story. Your job is to read it.

The agents who progress fastest aren't the ones who know every answer. They're the ones who back themselves to find it — calmly, methodically, every single time.

"Calm. Curious. Methodical.
That's all this takes."
The Ownership Test

Be honest. When something isn't obvious… what usually happens?

A
I pass it on
B
I try a bit, then pass it on
C
I keep digging until I understand it
D
Depends on time and pressure