A customer buys a chimney, hob or water heater from a dealer, marketplace or your own store. When they need installation or repair, connect their request to the right service centre, a scheduled technician, the parts used and the final bill.
Online marketplace · INV-7841
Bengaluru East service centre
Approved on site by the customer
Before tax · from approved lines
The same record follows the appliance from purchase to bill.
The appliance was bought from a marketplace, a dealer or a store. By the time it needs service, the invoice and serial number live in someone’s inbox.
The purchase channel, invoice and serial stay on the service ticket from the first call.
The visit is booked, but the part is missing, the slot was never confirmed or the coverage is unclear until the technician is at the door.
Dispatch confirms the slot, the skills and the parts before the visit is promised.
A duct kit or extra fitting is added on site, agreed verbally and forgotten by the time finance raises the invoice.
Every addition becomes an approved line item that flows into billing as-is.
Each stage hands its work to the next on the same record. Select any module to see what it does.
Give the service desk the purchase context and the dispatcher the information needed to send a prepared technician.
Let the technician act on the same job record: arrive, diagnose, add parts or services, obtain approval and record the outcome.
Close the customer issue, reconcile the technician’s parts and give finance a bill it can trace back to approved work.
Illustrative workflow · sample records
The purchase can happen anywhere. The service record stays together.
Every installation, demonstration, breakdown or maintenance request becomes one ticket that carries the appliance’s purchase story, so nobody has to ask for it again.
Follow an installation request from the first customer call to a signed job sheet. The same record supports repairs, chargeable work and return visits.
Capture the installation or repair request, wherever the appliance was bought.
Read the purchase evidence and the timeline that turned a call into this ticket.
Bengaluru service network
SR-24081 · Installation request
Product bought through an online marketplace.
Invoice, serial number and address attached.
Anita Rao assigned to the customer’s slot.
Illustrative policy, configured by product
The customer does not have to repeat their purchase story when the technician takes over.
Operational changes, not promised percentages. We size the impact with you against your own baseline.
Each role sees its own queue, its own actions and the same underlying record.
Registers the appliance and request, verifies purchase evidence and keeps the customer informed.
Configured to your process, brand, roles and integrations. The layer underneath is shared, so adding another product extends what you already run.
Each phase is usable on its own. Configuration follows your process, not a fixed template.
Configure product categories, serviceable areas, centres, ticket types and warranty evidence.
Set up roles, appointment slots, app checklists, parts catalogues and approval rules.
Connect stock locations, invoice rules, collections, accounting and service reporting.
Capture the original purchase channel and invoice against the customer’s appliance. Service intake can begin independently of the sales channel; warranty eligibility is checked against your policy and evidence.
The customer care agent routes the ticket to a service centre. The dispatcher assigns a suitable technician and confirms an appointment with the customer. Routing rules can assist while retaining manual control.
Yes. The technician selects a part or service from the configured catalogue, adds the quantity and records whether it is covered or chargeable. Chargeable additions follow customer approval before they flow into billing.
Keep the job in an awaiting-parts state, raise a linked stock request and set the next follow-up. The original diagnosis, estimate and customer history carry into the return visit.
No. Service completion, customer acknowledgement, invoice approval and payment are separate records. This lets finance follow outstanding payments without hiding completed field work.
The app queues supported field updates for sync. Dispatchers see the last received status and location timestamp, rather than an apparently live location. Location sharing requires device permission.
We’ll walk it from intake to the technician’s job sheet and the final bill, configured to your service centres on the call.