What this page should answer
Customers need to know what X-ITM can do now, what is guarded, and what still depends on provider, legal, account or customer access. This page makes capability readiness visible instead of hiding uncertainty.
- Ready capabilities
- Guarded capabilities
- Waiting on provider/customer gates
- Evidence needed before claims
How to use capability status
Use it before relying on an automation, integration or service route. It explains whether a feature is ready for customer work, safe but approval-led, or still waiting on an external requirement.
- Check readiness before starting
- Avoid unsupported promises
- Route blockers to the right next action
What happens next
If a capability is ready, move to the relevant route. If it is guarded or blocked, use the linked customer route or support path so the blocker is visible and not hidden in the process.
- Proceed
- Request evidence
- Escalate blocker