The complete business process
Click a stage to see what the office or field user sees, what they do next and why that handoff matters.
14 connected stages
This is a guided explanation of the current product workflow. Jobs can skip quotation, delivery or collection when those steps do not apply.
Stage 01
A daily view of the service work that needs attention.
The owner or admin opens the workspace and chooses the queue to review.
The day starts from shared work, not a round of status calls.
Stage 02
Customer context and available service information before the new call is logged.
Office staff search or select the customer and confirm the record.
The next complaint starts with the right context.
Stage 03
A service call with problem, priority, category and status fields.
The office captures what the customer needs and the next action.
A complaint becomes an owned work item instead of a loose message.
Stage 04
Engineer assignment and the open-work queue.
An Admin assigns one or multiple engineers or lets eligible city-based work be claimed.
Responsibility is visible before the customer has to call again.
Stage 05
The assigned work queue in the engineer web/PWA experience.
The engineer opens the supported browser or installed PWA and reviews the call.
Field work begins with the same job record as the office.
Stage 06
Customer, problem and service context on the engineer’s device.
The engineer checks the job before travelling or starting work.
The field team can act without waiting for another phone explanation.
Stage 07
A service status and work update attached to the call.
The engineer records progress, a hold reason or completion context.
The office can see why work is still open.
Stage 08
Material used in the service record.
The engineer or office adds the part or material consumed on the job.
The handover and later review have a more complete operational trail.
Stage 09
The dashboard and filtered calls after the field update.
The office reviews the changed status and chooses the next action.
The owner can manage by exception instead of chasing every engineer.
Stage 10
A quotation with items, GST mode, terms or alternative options.
Office staff create, edit, copy or revise the quote.
The commercial decision is connected to the service work.
Stage 11
The quote’s next action and decision status.
The team records replies and moves the follow-up to Won or Lost.
Approved work does not disappear into a private reminder.
Stage 12
A Delivery Challan built from eligible work or quotation items.
The office reviews quantities, status and partial delivery options.
Handover stays connected to the decision that created it.
Stage 13
Operational collection, payment method and settlement context.
Staff record the available collection and review the operational ledger.
The owner can see what happened at handover without calling the counter.
Stage 14
A completed call and its available customer/service context.
The team closes with remarks, then uses filters and reports on the next job.
Each completed job makes the next customer conversation easier.
Office ↔ engineer
The office creates context and assigns responsibility. The engineer updates from the site. The office sees progress and can move into quote, follow-up, handover or closure without rebuilding the story.
See the screens in sequence
Sixteen steps add the product screen, action and business reason at each point.