Support
Getting help
Identity breaks at inconvenient moments. When it does, you should reach somebody who knows your deployment — not a queue that asks you to describe it again.
Something is broken now
Use the channel agreed in your contract. It reaches an engineer, not a triage desk, and response targets are written into your agreement rather than implied on a web page.
A question, not an emergency
Your named contact is the fastest route. Most questions in the first quarter are about what a role should mean — which is a conversation, not a ticket.
You run it yourself
Then some of this is genuinely yours: your maintenance windows, your recovery targets, your upgrade timing. We support the product; you control the schedule. That is the trade you chose, and we will not pretend otherwise.
You found something
Responsible disclosure, and we would rather hear it from you than read it later. How that works.
Beyond breaking
The help that actually matters
Most identity programmes do not fail because the software broke. They fail in month seven, when the reviews come round again and nobody has the time.
The first review
We sit with you through the first recertification campaign end to end. Not a training session — your actual review, finished.
Before the audit
Bring us the questions your auditor asked last time. If the evidence pack does not answer them, we would rather find out before they do.
Before you expand
We will tell you when we think the next capability is a bad idea this quarter. A customer who expands too early is a customer who churns.