The Tier 1 Trap: Why Your EPM Support Contract Probably Isn't What You Think

EPM Support · April 16, 2026 · 6 min read

Here's a scene we've walked into more times than we can count.

A finance team has an Oracle EPM or NetSuite Planning system. They have a "support contract" with a vendor. Month 3 of the fiscal year, a forecasting rule breaks. The close is on Friday. They open a ticket.

Twenty-four hours later, someone responds asking them to restart the application and confirm the browser they're using.

"I thought we had managed services. What are we actually paying for?"

They were paying for Tier 1. They needed Tier 2. And nobody had ever walked them through the difference.

What Tier 1 actually is

Tier 1 is the front door. It's the first human — or bot — who touches your ticket. Their job is triage: confirm the issue, rule out the easy stuff, and either resolve it or escalate it.

Tier 1 is good at:
- Password resets and access issues
- "Is the system down?" questions
- Running through a checklist of known fixes
- Logging the ticket cleanly for whoever picks it up next

Tier 1 was never designed for:
- Diagnosing why your Workforce cube won't aggregate
- Tracing a rule break to a metadata change three sprints ago
- Knowing if a dataset issue is a dimension conflict or user error
- Anything requiring knowledge of your specific implementation

If your EPM system is genuinely broken — not "I forgot my password" broken, but "the forecast is wrong and the board meeting is Tuesday" broken — Tier 1 cannot help you. It was never meant to.

Here's the thing: modern AI is exceptional at Tier 1. It's patient, available 24/7, and can triage a ticket in seconds. The industry is moving in that direction fast. That's a good thing. But it also means the human work in EPM support has to shift up the stack — which is exactly where most vendors have been quietly understaffed for years.

What Tier 2+ actually is

Tier 2 is where someone who understands EPM — as a discipline, not just as software — actually touches your system.

In the EPM world, Tier 2+ usually means a consultant who can read your rules, calc scripts, or automations and understand why something behaves the way it does. Someone who knows your metadata, your data loads, your integrations, and your close cycle. The ability to make controlled changes in your environment — not just explain what might be wrong.

If Tier 1 is "did you try turning it off and on again," Tier 2+ is: "Your July forecast scenario is pulling from a substitution variable that got overwritten during your last metadata refresh — and here's how we fix it without breaking the August close."

Those are not the same job. They shouldn't be priced the same. And they definitely shouldn't be sold as the same thing.

How to tell what you're actually paying for

This is the uncomfortable part. Most finance leaders we talk to genuinely don't know which tier their contract covers. The word "support" is doing a lot of hidden work on those SOWs.

Signs you're on a Tier 1 contract being marketed as something more:
- Your first response almost always comes from a generalist, not an EPM specialist
- Tickets that require real investigation get bounced back with "please provide more information"
- You've never had the same person work two of your tickets in a row
- There's no named resource — you're in a queue
- When something complex breaks, you end up calling your original implementation partner anyway

None of those are bad in themselves. A well-run Tier 1 layer is valuable. The problem is when it's the only layer, and you thought you were buying more.

Five questions to ask before you sign (or renew)

Save this list. Send it to your controller. Ask these directly to the vendor:

1. What percentage of tickets do you resolve at Tier 1 vs. escalate to a senior EPM resource? (If they can't tell you, that's your answer.)
2. Who specifically will touch our environment, and what's their EPM background? (You want roles and experience — not a team name on a slide.)
3. What's the SLA for Tier 2 response — not just first response? (First response is often a form reply. Tier 2 response is when a real expert engages. Those are very different clocks.)
4. Can we see a sample ticket resolution from the last 90 days for a client on our platform? (Redacted is fine. You're looking for depth of analysis, not names.)
5. If we need a change that goes beyond support — like adding a complex new set of rules — is that in scope, or does it become a separate project? (The answer is almost always "separate project." Know that before you're mid-crisis.)

The honest takeaway

Tier 1 support is useful. AI is going to make it better and cheaper. That's the easy part.

The hard part — the part that actually keeps your close on track, your forecast trustworthy, and your team out of panic mode — is Tier 2+. Senior people who know EPM, know your environment, and can actually fix things.

If you don't know which one you're paying for, you probably aren't getting enough of the one that matters. Ask the questions. Read the SOW. And if the answers are vague, keep shopping.