Skip to main content
Documentation

Service and repair

The module for repair and maintenance: requests by stage, item intake with photos, history for every customer, warranty and handover with a document. It fits workshops, car services, field crews and companies that service equipment under a contract.

The «Deals» section: a funnel by stage and a table of requests with customer, owner and amountThe «Deals» section: a funnel by stage and a table of requests with customer, owner and amount
Every request is a deal moving from intake to handover

What is included

Core components

  • Deals — the request with stages, an owner, a deadline, works and parts.
  • Clients — enquiry history, the customer's equipment, warranty.
  • Point of sale — payment at handover, prepayment, refunds.

Optional components

  • Inventory — parts and supplies written off to a request.
  • Scheduling — booking a field job or a master's time.
  • Field service — work at the customer's address.
  • Work planning — a task board and a schedule when a repair waits weeks for parts.
  • Payroll — a master's percentage for completed work.
  • Finance — expenses, profit and customer debts.

Catalog, reports, calendar, messenger, integrations and the AI assistant are available right away.

Five scenarios

ScenarioThe processWhat it adds
🛠 WorkshopThe item stays with youIntake form, a "Warranty until" field, a printable work order
🚗 Car serviceRepair with parts from stockSwitches on inventory, "Plate number" and "Mileage" fields, history per vehicle
🚐 On-site repairThe master travels to the customerSwitches on scheduling, "Field address", "Entry code", "Type of work" fields, an act of completed work
🧰 Workshop + field + salesAll of it at onceThree deal types: intake, field job and product sales
📋 Contract maintenanceScheduled visits on a planPlanned visits, "Serviced object", "Frequency", "Contract response" fields, service reminders

The field scenarios bring address fields and an act. Ready customer texts by stage — "The master is on the way", "Work completed" — come with the Field services module. In the service scenario the "Notify the customer about stage changes" toggle sends a general message on every transition.

How a request goes

  1. Intake. The master records the request: customer, device, the reported fault, what came with it, photos. The customer receives a receipt with a number and a QR code.
  2. Diagnostics. The request moves to the next stage, and works and parts with prices are added.
  3. Approval. The amount is agreed with the customer — by phone, in a messenger or through a status link.
  4. Repair. Parts are written off from stock when the request reaches the work stage, so stock stays accurate.
  5. Handover. The request is closed with a POS receipt, a work order is printed and the warranty period starts.
The «Field» section: requests with addresses, times and assigned executorsThe «Field» section: requests with addresses, times and assigned executors
The field scenario: requests with an address and an assigned master

Intake: what is recorded

Intake is the most disputed moment of a repair, so it is recorded separately.

What we recordWhat it is for
Device and its markingsSo two identical items are not mixed up
The fault as reportedThis is the customer's claim, not your diagnosis
What came with itWhat exactly was accepted: a case, a charger, keys
Condition and photosThe answer to "did you scratch this here"
Agreed amount or ceilingA costlier repair is approved separately

The customer gets a receipt with a number and a QR code. For small items there is a smaller label that goes straight onto the bag with the device.

The customer follows the repair

The link from the receipt leads to a status page: the customer sees which stage their item is at. No registration and no call to the front desk, which noticeably reduces "how is mine going" calls.

The page shows only the stage of that specific repair: your internal comments and other customers' data are not there.

Contract maintenance

  1. Create a serviced object for the customer: an air conditioner, a machine, a vehicle.
  2. Describe the contract: what is serviced and how often.
  3. Planned visits are created on schedule.
  4. A reminder goes to the customer before a visit.
  5. Each visit prints an act, and the work lands in the object history.

At the next enquiry you can see what was done before.

What to set up after connecting

  • Request stages — bring the funnel to your process: diagnostics, approval, repair, handover.
  • Make and model reference books — they fill in during intake and remove the "Samsung / samsung" mess.
  • A price list of works — add services to the catalog so you do not type them in every time.
  • The receipt template — check it and add your warranty terms.
  • Service reminders — for the contract maintenance scenario.

What to look at in reports

  • How many requests are in progress and how many are overdue.
  • Average repair check and profit with parts taken into account.
  • Master output — how many requests each of them closed.
  • Repeat warranty enquiries.

In short

  • A request is run as a deal and moves through stages from intake to handover.
  • Intake records the condition and contents of an item with photos.
  • Parts are written off at the work stage rather than at payment.
  • The customer follows the repair through the link from the receipt.

Similar modules