Field Service Management
Crescove FSM covers the whole path a service business actually walks: an enquiry becomes a customer with a property, an estimate becomes approved work, work becomes a scheduled visit with a technician who has the checklist and the access details, and the visit becomes an invoice that gets paid.
Crescove FSM is available in our staging environment and verified there. It is not production-verified, live card payments and SMS are not enabled, and we do not publish customer logos, testimonials, savings figures, or comparisons with other vendors.
Each step hands the next one its context. Nothing here asks the office to re-key a customer, and nothing asks a technician to phone in for an address.
Lead
A call, a public quote request, or an import arrives as a lead with its source recorded.
Customer and property
The lead becomes a customer with the address you serve and the equipment at it.
Estimate
Priced from your price book, with good/better/best options where a choice helps the customer decide.
Approval
The customer approves an option — with a signature — and the approved amounts are what carry forward.
Job
Approved work becomes a job with its lines, required checklists, and skill requirements.
Schedule
Visits get an arrival window in the property's own timezone, not the dispatcher's.
Dispatch
Assign technicians against availability, skills, and service zones.
Field work
The technician has the property, access details, checklist, photos, notes, and time tracking — offline included.
Invoice
Invoiced from what was actually done, including change orders and material usage.
Payment
Payment recorded and allocated to invoices, with allocation as its own explicit step.
Follow-up
Callbacks, notes, and equipment history stay on the record.
Recurring service
Service agreements generate the visits a maintenance plan owes.
FSM is a module of Crescove, not a separate product with its own database. The customer, contacts, notes, tags, and communication history are the same records Crescove CRM manages — so a business running content or commerce alongside service work has one customer, not three.
The workflows here were shaped with input from a service-business design partner rather than assembled from a feature list. We do not name design partners publicly or present them as launched customers.
Each area carries a label. Where something is a data model waiting for a screen, it says foundation only. Where something needs a paid provider connected, it says so. Nothing is described as active because it is nearly finished.
Every query, job, export, and file path is scoped to an Organization and a Brand on the server. Access details and internal notes are gated by capability, so what a technician's phone shows is a deliberate decision.
Tell us how your business runs today and we will walk through what is available now, what is still being built, and what would need to be connected for you.
