The service desk that already knows what's covered.
Service ERP is the operational core of BusinessOps360. Every request is attached to a real serial-numbered machine, so coverage, history and billing stop being something a person has to look up โ or guess.
Every request lands on a real machine
A request isn't a free-text ticket with a customer name on it. It's attached to the exact serial-numbered unit you installed, which is how the system can answer the coverage question before a human has to.
- Raised from BO360 Care, from a phone call, or by the sales team
- Linked to the specific asset โ not just the customer account
- Billing type resolved on creation: warranty, AMC or chargeable
- Priority and SLA clock applied from the contract terms
- Full thread of updates, attachments and site notes on the request
UPS not switching to battery
SR-2291 ยท Apollo Tyres, PuneQuarterly PM visit due
SR-2288 ยท Sunrise HospitalDisplay panel replacement
SR-2284 ยท Vertex FoodsBattery bank health check
SR-2279 ยท Meridian TextilesA light installed base, not a warehouse
We track what you sold, where it sits and what covers it โ and deliberately stop there. No stock ledgers, no bin locations, none of the inventory apparatus you already have somewhere else.
- Serial-tracked assets created automatically from the sales invoice
- Warranty start and end derived from the installation date
- Contracts, PM schedule and full service history on every asset
- Site and location detail, so the engineer knows where to go
- Documents and photos attached to the unit, permanently
Galaxy VS 40 kVA UPS
SN-UPS-40-118824See the whole day before it goes wrong
One board with every engineer, every job and every unassigned request on it โ so the coordinator can move work around at nine in the morning rather than apologising for it at five.
- Live board of engineers, jobs and today's open requests
- Assign, reassign and reschedule without leaving the screen
- Unassigned and SLA-at-risk requests surfaced, not buried
- The engineer sees the change on their phone immediately
- Visit history per engineer for utilisation and load balancing
R. Kulkarni
4 jobs ยท Pune WestS. Nair
3 jobs ยท PimpriA. Deshmukh
2 jobs ยท ChakanThe job closes on site, not that evening
The engineer records the work where the work happened โ fault, parts, labour, readings, photos โ and both signatures are captured on the device before they leave. Offline the whole time, if that's what the site gives you.
- Fault found, action taken, parts consumed and labour hours
- Meter readings and photographs captured against the asset
- Engineer signature, then customer signature, on the phone
- A reason captured when the customer can't sign, instead of a blank
- Works fully offline and syncs the moment signal returns
Chargeable work stops leaking
The most expensive thing in a service business is work that got done and never got billed. When the FSR closes, the parts and labour on it are already priced and waiting โ nobody has to remember.
- Closed chargeable jobs arrive at invoicing on their own
- Parts and labour priced straight from the FSR lines
- Warranty and AMC jobs marked covered, so they're never billed twice
- Invoice visible to the customer inside BO360 Care
- Every step attributable, with a full audit trail behind it
Job closed on site
FSR submitted with parts and labourCoverage checked
No AMC, warranty expired โ chargeableInvoice drafted
Parts and labour priced from the FSRApproved & sent
Visible to the customer in BO360 CareFour people, four different screens
The same service request looks different depending on whose job it is. Pick a role to see what they actually work with.
Runs the day
Opens on the dispatch board, not an inbox. Every incoming request already carries its asset, its coverage and its SLA clock, so the only decision left is who goes and when.
What they get
- Today's board with every engineer and every open job
- New requests with billing type already resolved
- One-click assign, reassign and reschedule
- SLA-at-risk jobs flagged before they breach
Works the site
Lives in BO360 Field. Today's jobs, the route and the full history of the machine are on the phone before they leave โ and the report is finished before they get back in the van.
What they get
- Assigned jobs with customer, site and asset history
- Offline capture of parts, labour, readings and photos
- Engineer and customer signature on the device
- Job closed on site โ nothing to type up later
Watches the trend
Cares about throughput and exposure rather than individual tickets: what's breaching, who's overloaded, which assets keep coming back, and what it's costing.
What they get
- Open load, breaches and closure rates at a glance
- Engineer utilisation across the week
- Repeat-failure assets surfaced from service history
- Chargeable versus covered work, by customer
Stops phoning
Sees their own equipment through BO360 Care โ what's covered, what's been done to it, where the current job has got to โ without going through your coordinator to find out.
What they get
- Raise a request against a specific machine
- Live status of every open job
- Downloadable Field Service Reports and invoices
- Warranty and AMC status per unit
Everything in Service ERP
The full list, grouped the way the work actually breaks down.
Service requests
- Multi-channel intake (portal, phone, sales)
- Asset-linked, not just customer-linked
- Automatic warranty / AMC / chargeable resolution
- Priority and SLA clock from contract terms
- Update thread with attachments
- Full status history per request
Installed base
- Serial-number tracking per unit
- Auto-created from the sales invoice
- Warranty dates derived from installation
- Contracts and PM schedule per asset
- Complete service history
- Site, location and document storage
Scheduling & dispatch
- Live dispatch board
- Assign, reassign, reschedule
- Unassigned and at-risk queues
- Push to the engineer's phone
- Per-engineer visit history
- Utilisation view across the week
Field execution
- BO360 Field on Android
- Full offline capture with sync
- Parts, labour and meter readings
- Photo capture against the asset
- Dual signature on device
- Cannot-sign reason capture
Billing
- Chargeable jobs routed to invoicing
- Parts and labour priced from the FSR
- Covered work marked, never double-billed
- GST tax invoice generation
- Invoice visible in BO360 Care
- Full audit trail on every step
Control
- Eleven role definitions across the business
- Role-based access to every screen
- Attributable record changes
- Configurable per tenant
- Your own branded subdomain
- Exports for finance and reporting
Straight answers
Do we need CRM Sales to use Service ERP?
No. Service ERP runs on its own โ you can import your existing customers, products and serial numbers and start dispatching straight away. What you gain by adding CRM Sales is that new installations create their own asset records instead of being keyed in.
What if a machine wasn't sold through the system?
Import it. Most teams start with a spreadsheet of what's already out in the field โ customer, model, serial, install date, warranty end โ and that becomes the installed base on day one. Nothing has to have been sold through BusinessOps360 to be serviced through it.
How does it know whether a job is chargeable?
From the asset, not from a human. When a request is raised the system checks that unit's warranty dates and any active contract covering it, and resolves the billing type at that moment โ warranty, AMC or chargeable โ so the decision is made once and consistently.
Does the engineer's app really work with no signal?
Yes. BO360 Field holds the assigned jobs on the device, and parts, labour, readings, photos and both signatures are all captured locally. When the phone reconnects everything syncs and the job closes properly on the server.
Can customers raise their own requests?
Through BO360 Care, yes โ against a specific machine from their own equipment list, with live status afterwards. In practice that's where most of the status-chasing phone calls go.
What sits either side of it
See Service ERP on your own jobs
Bring a real service request and a real machine. We'll run it through the module end to end rather than showing you a scripted demo.
sales@businessops360.com ยท Typically replies the same working day
BusinessOps360