Service connects telemetry, dispatch decisions, territory, SLA, technician work and material. Review configuration across the complete ticket lifecycle.
Before you begin
- First confirm the correct company and location.
- Prepare a real operating scenario for validation.
- Confirm permission for the intended change, not only read access.
What to enter
Add exact device position, service hours, entry instructions, parking, restrictions, access code, GPS and one current orientation photo.
Who can see it
Administrators or dispatchers manage the card. A technician sees it only in a ticket assigned directly to them. The photo is never served as a public file.
Regular review
Re-verify after changes to tenant, reception, opening hours or access code. The verification date tells the technician whether instructions are current.
- Test changes on one controlled case first.
- Add a clear audit note to important decisions.
- After saving, verify the result from the operating role’s perspective.
- Bulk changes without testing can affect many devices or tickets.
- Overly broad access hides a problem but does not create a sound process.
- An unverified change may behave differently in downstream workflow.
The result should be one clear flow: the right signal creates one actionable case with correct SLA and an eligible technician.
Still need help? Contact support.