About Services

The office, creating a service that did not come through a quote: a call-out, warranty work, a customer who just wants it fixed.

A repair booked by phone lands in the field as a name and an address. What is to be done, what it will cost and what was actually performed get written down afterwards, if at all.

The job form for a service, in tabs: Details (customer and building, service type, assigned office, priority, difficulty, estimated duration and days, number of techs, anticipated start, due date, scheduled date and time, working window, reference, contract and PO numbers), Items (the service items to perform, priced from the catalog), Attachments, Related, History and Documents. New customer, building and contact can be added from inside the form. Edit Service is the same form on an existing job.

• Scope and price before the visit. Items are on the job when it is created, so the technician knows what to do and the office knows what to bill.
• The same form as an inspection. One shape for both job types; only the middle tab changes.
• Working windows and difficulty travel with the job into every scheduling view and the Routing Workbench.

The service manager and whoever bills the work.

Margin on a service is known when the invoice is reconciled, weeks later. Which quote a service came from, and which inspection that quote came from, is a paper trail.

The job grid narrowed to services, with the same search, filters and Actions as All Jobs. The Service Dashboard mirrors the inspection one: a header card, the Lineage rail, KPIs (Items Performed, Total Sell, Margin, Hours Logged, Days Open), Work Breakdown, Outputs, Scheduled Days, the Source Service Quote, and the Service Items grid with type, description, quantity and unit cost.

• Margin on the dashboard. Total Sell and Margin are on the service the day it is done, not when the invoice closes.
• The source quote is one click away. What was promised sits beside what was performed.
• Hours against sell. Hours Logged beside Total Sell is the number that says whether this kind of work pays.

The service manager or estimator pricing a repair.

A repair estimate is a document written outside the system, so its items are not priced from the catalog, its acceptance is an email, and the service it becomes has no link back to it.

A short form: customer and building, optional national account, title, quote type, assigned office, reference and PO numbers, and scope of work. It creates the quote and opens the edit page, where the estimate is built: the header card with total and stage, the Lineage rail, a Workflow Status banner and a Rejection banner with a Resubmit action, quote info, the customer contact with an Add Contact modal, Outstanding Deficiencies when the quote came from an inspection, Scope of Work, and the Estimates section where items are searched from the catalog and priced.

• Priced from the catalog. Items carry the catalog's cost and sell, so margin is on the quote before it is sent.
• The findings are on the quote. When it came from an inspection, Outstanding Deficiencies lists what still needs a line.
• A rejection is a step, not an end. The Rejection banner carries a Resubmit action, so the revised quote keeps its history.

The service manager watching what is out and what has been answered.

Quotes sent and never answered are forgotten. The acceptance rate is a guess, and a customer's PO number for a quote is in someone's inbox.

The service quote grid. Search by title, customer, building, address, reference or PO. Rows show the quote, its status, who created it, and actions into the edit page. The edit page is where a quote is sent, accepted or rejected and, once accepted, becomes a service.

• The awaiting-answer list. Sent quotes with no response are the follow-up calls for the week.
• Find it by the customer's number. Reference and PO search means a customer quoting their own number gets an answer.
• The stage is on the row. Pending, Sent, Accepted or Rejected, without opening each quote.

The service manager, and the technician who flagged a finding as worth quoting.

An inspection finds six things; the office quotes two and forgets four. The unquoted findings are revenue nobody asked for and liability nobody addressed.

Inspections whose deficiencies still need a quote. Search by job number, customer or building. The grid shows each inspection's deficiency count and a Needed / Created pair, so the office can see which inspections are fully quoted and which are not. Actions create the service quote from the inspection, or remove the inspection from the queue.

• The loop is closed on screen. Needed / Created moving to equal is the proof that every finding was priced.
• Create from the queue. The quote is created from the inspection, so it arrives with the findings already attached.
• Deliberate removal. An inspection that will not be quoted is removed on purpose, not forgotten.