Skip to main content

5. Service & Field Operations (FSM)

Purpose — The after-sales engine: complaints, installation/commissioning, AMC, dispatch, and the technician app. Half the business lives here, so it's a first-class module. Includes the notes' cross-vendor intake (we'll service a competitor's product as a paid visit).

Personas served​

Customer, Technician, Service partner, Service head, Dealer (raises on behalf), Manager (scoped).

Key capabilities​

  • Complaint / ticket management — raise via web, app, WhatsApp, call center, IVR; capture what happened, photos, invoice/asset link.
  • Scheduling & dispatch — auto-assign nearest available technician by skill/zone; route optimization (v2); SLA + escalation matrix.
  • Technician app (offline-first) — job list, navigation, customer/product/warranty context, checklists, photo/video, digital signature, parts used, time/expense, on-site close-out. See Apps.
  • AMC management — plans (comprehensive vs non-comprehensive), pricing tiers, multi-year; sell/renew online; auto-reminders for due services + renewals; scheduled preventive-maintenance visit generation; AMC profitability/coverage/SLA.
  • Installation & commissioning — site survey → install → commissioning report → activation (activates warranty start).
  • Warranty decisioning at point of service — in-warranty → free fix; else quote/pay (engine in Warranty).
  • Cross-vendor / external assets — a customer whose non-our-brand product broke (e.g. a ball cracked their Luminous panel) registers an external asset and books a paid visit. Enables the "broken/cracked panel" repair business + marketing campaigns (notes #5).
  • Service history per asset/serial — full lifecycle log.
  • CSAT — feedback after every visit; technician scorecards.
  • Service-partner / franchise management — authorized 3rd-party service orgs and their technicians.
  • Billing at close — AMC vs warranty vs paid decision → invoice (Finance).
  • Testimonial trigger — installation.completed schedules the 7-day testimonial request (Marketing).

Data owned​

Mongo (FSM): ServiceTicket, Job/Visit, AMCContract, ServicePartner, Technician, SLA timers. Money (invoices) → Finance (PG). Asset truth → Warranty (Mongo). See fsm-service-mongo.

Events​

  • Emits: ticket.created, job.assigned, installation.completed, ticket.closed, amc.created, amc.due_soon, visit.completed.
  • Consumes: order.delivered (create install job), claim.approved (repair/replace job), payment.captured (paid-service confirm).

APIs​

  • POST /service/tickets, GET /service/tickets (scoped), POST /service/tickets/:id/assign
  • POST /service/jobs/:id/close (photos, parts, signature)
  • POST /amc/contracts, POST /amc/contracts/:id/renew, GET /amc/due
  • POST /service/external-assets (cross-vendor intake)

Tenant-config knobs​

featureFlags.amc, crossVendorService; service.defaultSlaHours; AMC plan templates; dispatch strategy; CSAT template.

Dependencies​

Orders, Warranty, Inventory (parts), Finance, Notifications, Apps.

Open questions​

  • Route optimization in v1 or v2?
  • Cross-vendor pricing model (flat visit fee vs quote) per tenant.