What contact is for
Contact is for useful context and routing, not a generic inbox. Customers should understand what to send and what kind of response to expect.
- Question
- Support request
- Handoff request
- Route clarification
Contact X-ITM
Start with enough context to be useful
Give enough context for a technical conversation. X-ITM routes the request without making external commitments from the form.
Guided request
Share enough context.
This form routes the request. It does not create a quote, order, payment, provider submission or external commitment.
Page detail
Useful detail before the next step.
How to get a better response
The more clearly a customer describes outcome, systems and urgency, the faster the request can move to assessment or workspace.
- Describe outcome
- Name systems
- Explain urgency
What happens next
The request is reviewed and routed. If work requires access, the next step should be workspace/control-centre based, not silent action.
- Review
- Route safely
- Move to workspace if needed
Customer route
Useful contact, not a generic inbox
The contact route gathers context and sends the customer to the right next step.
1. Ask question2. Share context3. Route safely
Linked customer routesStart an EngagementBegin the commercial and technical conversation.Captures enough context to avoid generic consultancy.Start X-ITM SupportGet help without losing journey context.Routes questions back into the right workspace or next step.Get support Customer Feature MapSee all public/customer routes and how they connect.Helps a customer choose the right starting point.View map 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.