Field visit request: a known appointment, a prepared technician, a signed report
A customer in Jeddah requests AC maintenance for their office. It needs a visit, and the customer has a visit-based contract. This journey shows how the right technician is scheduled, the customer knows the appointment, and the report comes out signed and deducted from the contract.
The journey, step by step
Click any step or use the buttons to see the ticket status.
- Request
From the customer portal: location, preferred time, asset.
Customer - Contract check
Active contract, 5 of 12 visits left, asset covered.
System - Scheduling
HVAC technician in Jeddah available Monday morning.
Coordinator - Appointment notice
To the customer: Monday 9:30, technician Sami.
System - Arrival
Check-in from the technician app.
Sami - Work
Before/after photos, filters cleaned, one unit recharged.
Sami - Signature
Customer signs on mobile.
Customer - Report & contract
Visit report sent, one visit deducted (4 left).
System
Before and after
| Aspect | Without a system | With TixDesk |
|---|---|---|
| Appointment | Back-and-forth calls | Confirmed time and technician |
| Contract | Checked manually | Checked automatically |
| Documentation | Paper that gets lost | Photos and digital signature |
| Parts | Not charged | Recorded |
| Contract balance | Unknown | Updated automatically |
Features used in this journey
Field service
The visit.
Contracts
The balance.
Customer portal
The request.
Notifications
The appointment.
Locations
The city.
Assets
The AC units.
Questions about this case
Can the customer choose the time?
Available slots can be shown, or a preferred time confirmed by the coordinator.
What if a part is not available?
The ticket moves to "waiting for part" and a second visit is scheduled.
See the journey on your requests
We apply this case with your details in a live demo.
- A scenario from your reality
- Your teams and policies
- Direct answers