Ask to see the same job from three sides.

A mobile screen can look convincing while the office still has to reconstruct the visit. Compare providers using one complete fictional job and the people who depend on its result.

Prepare one shared demonstration brief

Describe the visit type, dispatcher, technician and receiving office role. List the intended devices and connection conditions, required notes or photos, completion decision and the next office task. Provide fictional addresses and harmless sample files. Keep customer records, signatures and access instructions out of a public inquiry.

Ask each provider to separate demonstrated behavior from a mock-up, planned feature or provider dependency. Use the same ordinary case and interruption so the comparison reflects work rather than the size of a feature catalog.

Dispatcher: assign and then change the job

Have the dispatcher assign a visit with the information the technician needs. Change an instruction or reassign the job after it has been opened. Ask what the original and new technicians see, when the change is acknowledged and whether the office can distinguish an assignment from an accepted one.

Include an unavailable technician or missing required detail. Identify who owns the exception and where it waits. An invisible unassigned job is a different result from a clear queue requiring a decision.

Technician: finish on a representative device

Ask the technician to find the current job, enter a note, attach a harmless photo and attempt completion. Interrupt the connection in an approved test environment. The demonstration should distinguish a local draft, queued material and a server-confirmed result. Reconnect and check that the material reaches the correct job once.

Ask about rejected or oversized files, a device change and a job updated by someone else. Offline operation must be explicitly designed and tested; a cached page does not prove the visit can be completed without a connection.

Office: use the resulting record

Have the office find the current visit, review the evidence and explain what remains missing. Correct a fictional mistake under ordinary permissions. If invoicing or another system is in scope, inspect that destination or clearly label its demonstration as a substitute. A completed field screen alone does not establish the office handoff.

Keep a useful comparison sheet

For each role record: expected task, observed result, unresolved assumption, responsible owner and acceptance example. Add device limits, available exports, access administration, source/configuration ownership and the support route. Separate initial delivery, vendor subscriptions and continued maintenance.

Use the findings to choose a first job type, not to demand every possible feature at launch. Read the offline field-work guide or discuss a field-to-office workflow. Live notifications or production changes need their own agreed scope and recipients.