What support handles
Support should help customers get unstuck while preserving journey context. It should not be a dead-end page with a generic message.
- Account/workspace questions
- Route confusion
- Evidence or approval questions
- Technical handoff
Help and handoff
Get help without losing context
Support routes customer questions into workspace context, evidence and approval-safe next steps rather than a disconnected help page.
Page detail
Useful detail before the next step.
How support stays useful
Support should connect back to customer routes and evidence so the customer does not have to repeat context across every page.
- Keep context
- Link to workspace
- Escalate exact blocker
What happens next
The issue is routed to the right customer path, workspace, trust page or contact route.
- Clarify
- Route
- Resolve or escalate
Customer route
Support should connect back to the journey
Customers need help, but the answer should still link to diagnostic, assessment, workspace, trust or capability status.
1. Ask question2. Open route3. Resolve blocker
Linked customer routesContactAsk a question or request a handoff.A safe fallback when the right route is unclear.Contact X-ITM Customer Workspace / Work PanelOpen the governed workspace for authorised projects, sources and approvals.Use when real work needs controlled context.Open work panel Customer Feature MapSee all public/customer routes and how they connect.Helps a customer choose the right starting point.View map Capability StatusSee what is live, guarded, blocked or waiting.Makes readiness visible before relying on a capability.Check status Trust CentrePrivacy, approval gates and evidence requirements.Explains how protected actions stay approval-led.Review trust
Everything stays connected.
These are live customer-facing entry points. Each card explains what the route is for, what the customer gets, and the next safe action.