Callout

A maintenance plan is a promise. This is the system that keeps it.

Callout runs subscription-based home and property maintenance end to end: plans and tiers with explicit inclusion rules, properties and units under contract, job requests validated against entitlement, technicians dispatched by zone and shift with live location, quotes for anything outside the plan, and SLA events recorded against every job.

  • Subscription plans
  • Entitlement rules
  • Zone dispatch
  • Live technician tracking
  • SLA events
  • Quotes & invoicing

Pilot deployment Subscription field-service platform with SLA tracking built in.

45entities

modelling plans, contracts, jobs, technicians and billing

SLAtracked

as first-class events, not a report written afterwards

Zonebased

dispatch with technician shifts and live location

Multiproperty

organisations, properties and units under one contract

01 / The problem

Every field service business drowns in the same three questions.

Is this covered? Who is nearest? Are we still inside the response time we sold?

Answering those from a WhatsApp group and a technician’s memory is how maintenance businesses lose money on their best contracts and their reputation on their worst jobs.

Callout answers all three structurally: entitlement is a rule attached to the plan, dispatch is a function of zone and shift and live position, and the SLA clock is an event stream that does not depend on anyone remembering to look at it.

02 / In operation

What the team actually looks at.

The shape below is true to the real product. The numbers are not — these are illustrative values, never customer data.

03 / Capabilities

What it does, in detail.

10 capability areas, each built because the operation breaks without it.

01

Plans and tiers

Subscription plans with explicit rules defining which service categories and templates are included at each tier, and what falls outside.

02

Contracts and scope

Contracts bind an organisation, its properties and its units to a plan, with the service scope recorded per contract rather than remembered.

03

Entitlement checking

A job request is checked against the contract before it is dispatched, so the conversation about who pays happens first, not after the van arrives.

04

Zone-based dispatch

Technicians are assigned to zones and shifts; jobs route to whoever is actually on duty and in range.

05

Live technician tracking

Technician location feeds dispatch decisions and gives the customer a credible arrival estimate.

06

Quotes for out-of-scope work

Line-item quotes for anything outside the plan, approved by the customer in-app before work begins.

07

SLA events

Response and resolution milestones recorded as events against the job, producing real performance data against the promise you sold.

08

Job evidence

Photos, messages, status history and customer ratings attached to every job — the record that settles a dispute.

09

Billing and invoicing

Subscription billing, invoices with lines, payment methods and payment capture against the billing account.

10

Audit and access control

Roles, audit logging, OTP authentication, device tokens and login-attempt monitoring across customer and technician apps.

04 / Surface area

25 modules, one system.

Breadth is only an asset when the parts share a data model. Every module here reads and writes the same records — there is no export step between them.

  • Plans
  • Plan rules
  • Tier inclusions
  • Subscriptions
  • Contracts
  • Service scope
  • Organisations
  • Properties
  • Units
  • Job requests
  • Jobs
  • Job status history
  • Job media
  • Job messages
  • Quotes
  • Ratings
  • Technicians
  • Zones
  • Shifts
  • Technician location
  • SLA events
  • Billing accounts
  • Invoices
  • Payments
  • Audit log

05 / Architecture

Policy is configuration, not code.

A Laravel application where plan rules, tier inclusions and policy configuration are data — so a commercial decision to change what a tier includes is an administrative action, not a release. Customer and technician clients run against the same API with separate identity and device handling.

  1. L1 Customer app Request jobs, approve quotes, track arrival, rate the work.
  2. L2 Technician app Assigned jobs, status updates, evidence capture, location and shift handling.
  3. L3 Dispatch core Entitlement, zone, shift and availability resolution.
  4. L4 Policy layer Plans, plan rules and tier inclusions held as configuration.
  5. L5 Billing Subscriptions, invoices, payment methods and capture.

06 / Integrations

Built to connect, not to be a silo.

Third parties are first-class parts of the architecture, isolated behind stable internal contracts so any one of them can be replaced without touching the core.

Payments

Card and mobile money for subscriptions and out-of-scope invoices.

Messaging

OTP authentication, job notifications and arrival alerts by SMS and push.

Location

Technician location streaming to power dispatch and arrival estimates.

Next platform Threshold Rooms, reservations, guest folios, housekeeping and restaurant point of sale on one guest account. Read on

Field service

Want Callout for your operation?

We can walk you through the live platform, talk about how it maps onto how you work today, and be honest about where it does not fit.

Request a walkthrough See all platforms