Role clarity
The provider company—not ClueXP—is the physical service provider. The customer sees that relationship before any dispatch authorization.
Trust & safety
Trust starts with knowing who does what.
ClueXP coordinates the request. Independent participating provider companies and their technicians perform the physical service.
Explicit authorization
A coverage check is not a dispatch. Consequential authorization is presented separately with the applicable disclosures.
Data restraint
Addresses, phone numbers, tracking tokens, technician locations, and customer notes do not belong in URLs, analytics, or ad platforms.
Honest status
Unsupported, uncertain, delayed, and unavailable are valid outcomes. The site does not replace them with invented availability, ETAs, prices, or ratings.
Safety comes before service
For immediate threats to life, suspected break-ins, children or vulnerable people in danger, or a person or animal trapped in a vehicle, contact local emergency services. ClueXP is not an emergency-response service.
What a coverage check can actually tell you
Every outcome is shown honestly, not smoothed over
- Supported. The Platform confirmed the request can proceed. This is still not a dispatch — separate authorization comes next.
- Unsupported. The Platform determined this request cannot be served for this location or service today. No provider, price, or timing is implied.
- Uncertain. The Platform could not give a definite answer yet. The honest response is 'not yet known,' not a guess.
- Unavailable. The coverage or transaction step could not be completed — for example a connection or configuration issue. This is a system state, not a coverage answer.
If the online step cannot complete a real check today, the site says so and points to the phone option — it never substitutes a guess for a Platform answer.
Your information
What stays out of URLs, analytics, and ad platforms
Service location, contact details, request identifiers, and tracking tokens are used only to complete the step you asked for. They are not appended to page URLs, sent to analytics as event properties, or shared with advertising platforms. Acquisition context (like which page you arrived from) is captured separately from request data and is never treated as proof that a job happened.
Before service
Questions a customer should be able to answer
- Which independent company is expected to perform the work?
- What is known—and not yet known—about timing and price?
- What action authorizes dispatch?
- Which cancellation terms apply?
- How can the request be tracked, cancelled, or escalated?
The final wording and policies must come from the Platform contract and approved legal policy. Until then, this site will stop at an unavailable state.
Read frequently asked questions