NivoDesk Pro / Operations
Planned module · illustrative sample dataField work, from enquiry to handoff.
A planned field-service workflow that keeps an enquiry, an agreed job, the next owner and the meaning of “done” clearly separate, so nobody has to guess between conversations.
Concept page. No live tool, account or contact intake is offered.
How it works
Four clear states for every service job
Each state answers one question, so an enquiry never quietly becomes a promise of attendance, scope or price.
- Step 1
Record the enquiry
Capture the problem as described, without treating it as agreed work.
- Step 2
Clarify the scope
The general task, location needs and whether an assessment is required.
- Step 3
Name the next owner
Context travels with the job to the person who plans or performs it.
- Step 4
Confirm completion
Agree what “done” means: task addressed, issue explained or follow-up arranged.
01 · Enquiry
Separate an enquiry from an agreed job
A service request may describe a problem without establishing the work required. Before treating it as a job, consider what needs clarification: the general task, the location requirements and whether an assessment is necessary.
This distinction matters when comparing field service management software. A recorded enquiry should not quietly become a promise of attendance, a fixed scope or a price that nobody has reviewed or confirmed.
Enquiry
- Problem as described
- Location still unclear
- No price or date agreed
Agreed job
- Reviewed scope
- Confirmed location needs
- Accepted through your real process
02 · Handoff
Make the next owner easy to identify
Operational confusion often appears at a handoff. Someone may have spoken with the customer, while another person needs to plan the work and a third must confirm completion.
A useful job card would carry the accepted quote version, assigned person, arrival window, required equipment and escalation contact. Changes after acceptance should be visible and confirmed through the business's real process.
| Field | Value | State |
|---|---|---|
| Quote version | v2 (accepted) | Confirmed |
| Assigned person | Example technician | Named |
| Arrival window | 10:00–12:00 | Planned |
| Equipment | Example ladder kit | Check |
| Escalation contact | Example supervisor | Named |
03 · Completion
Define what completion would mean
Completion can involve more than changing a status. Depending on the business, it may require confirming the agreed task was addressed, explaining a remaining issue or arranging a further conversation.
These are evaluation questions for your own process, not functions available on this website.
04 · Assistance
Suggested assistance, bounded first pilot
Suggested assistance would include draft summaries and missing-information prompts. Automatic dispatch, customer messaging, invoice preparation and integrations remain planned capabilities with implementation and testing dependencies.
A first pilot would use one defined job type, an agreed data source and a small set of staff roles. It would establish which actions require approval, what happens when information is missing and how an incorrect draft is stopped.
- One job type: a narrow, defined starting point
- Approval points: which actions need a person
- Missing information: what happens when data is incomplete
- Stop control: how an incorrect draft is halted
FAQ
Questions you might have
Can I book or dispatch a job here?
No. This page describes a planned workflow. There is no job board, dispatch or field-worker app.
Is the job card real?
No. It is illustrative sample data used to explain which details a handoff could carry.
Where can I start today?
The quote-to-job guide offers a manual checklist you can use before deciding what to automate.
Map your field workflow first
Read the practical guides, including the quote-to-job checklist.