Practical technology in action
From service request to follow-through.
See how a team can organize requests, assign work, and keep customers informed.
Fictional demonstration — Red Maple HVAC. All names, requests, and activity below are made up. Changes stay in this page and reset when you reload. No real messages, emails, appointments, or backend updates are sent.
Red Maple HVAC · fictional business
Service requests
Choose a request, then try a status. Each change adds a simulated customer confirmation and staff notification.
Request queue
Simulated confirmations & staff notifications
How the work moves
One clear path from request to completion.
1. New
A customer submits a service request. They receive a confirmation and the office sees the details.
2. Assigned
The dispatcher assigns the request. A staff notification keeps the next step clear.
3. In Progress
The technician starts work. The team sees progress and the customer receives an update.
4. Done
The team marks work complete and sends a completion message. Open requests stay visible for follow-up.
In a tailored implementation, reminders and escalation rules can help the team follow up on unattended requests. This standalone demo only simulates the workflow shown above.
Discuss your workflow with PKS