Field Service Yoke
The flagship board for this vertical. Every job moves New → Dispatched → On-site → Invoiced. Dispatcher sees the queue; tech sees their day on their phone.
Field service / HVAC
Operational software for field-service contractors
Dispatch boards, on-site state tracking, invoicing the moment the work is done, and an audit trail every operator can read. Single-tenant-multi-facility or one-tenant-per-location — both shapes ship.
Who this is for
HVAC contractors, electricians, plumbers, locksmiths, appliance-repair operators, and multi-trade shops with 5-50 field technicians across one or more locations. You have a dispatcher, an office team, and a customer base that mixes residential maintenance contracts, commercial service calls, and the occasional install. Your current stack is some combination of ServiceTitan, Housecall Pro, a homegrown spreadsheet, a separate accounting package, and a lot of Slack messages.
This page is for the moment you're evaluating a replacement for that stack or looking for the back-of- house operations layer underneath it.
What ships today
- What's currently shipped
The field-service stack on FastYoke is a combination of marketplace apps plus the free Logistics core. Six apps cover intake-to-invoice end-to-end.
CRM Suite
Customers, equipment-on-site, contract status, service history. Linked to the job entities so a dispatcher opening a job sees the full equipment history without a context switch.
Yoke Ledger + GL Pack
AR / AP, invoicing, payment capture, GL posting. When a job moves to Invoiced, the invoice posts to the ledger automatically. Month-end close runs against the same ledger.
Inventory
Truck stock, parts on hand, reorder points. When a tech uses a part on a job, the inventory deducts. The GL Pack posts COGS on issue if you flip the toggle.
Logistics core (free)
Facilities, bins, zones, movements, immutable event log. Free with every tenant — the shared substrate every field-service multi-location operation builds on.
Forms — free
Public maintenance-request forms, online quote requests, contact forms. Cloudflare Turnstile + PDF copy on submit. Free forever; you don't pay extra for intake.
Extend without code
- How to extend with low-code
Field-service operations are full of small per-shop quirks — the pricing book, the truck-stock policy, the maintenance-contract billing cadence. Most don't require an engineer:
- Pricing-book authoring in the schema (one afternoon). Use the entity-schema layer to model your specific line-item catalog with optional add-ons, regional pricing, and maintenance-contract discounts. The catalog flows into the Field Service Yoke's line-item picker and the Yoke Ledger's invoicing.
- A custom approval step for jobs over a threshold
(one hour). Add an
AwaitingApprovalstate betweenOn-siteandInvoicedfor jobs over a dollar threshold. The FSM Designer adds the guard ({">": [{"var": "total"}, 1000]}). No code change. - Maintenance-contract auto-scheduling (an afternoon). Use the FSM scheduler to spawn next- visit jobs on a contract anniversary. The audit log proves the maintenance was scheduled when contracted.
- Equipment-warranty lookups (one day). The WASM scripting tier (TypeScript on QuickJS in wasmtime) lets you call out to the manufacturer's warranty API on a job-creation transition. Returns get stored on the equipment entity, surfaced in the tech's mobile view.
The low-code surface is bounded by what the schema can express. When the customization is broader than schema-shape, you're in customization territory — covered next.
Customize deeply
- How to make major customizations
In-house engineering
FastYoke ships a typed SDK (@fastyoke/sdk-next,
@fastyoke/sdk-vue, plus a Rust crate for the kernel).
For field-service contractors with engineering bench
(usually rare in this vertical), the SDK enables:
- Custom tech-facing mobile experiences (the platform ships a responsive web UI; a native React Native app is a project, not a config).
- Direct integrations with non-marketplace vendors (parts distributors, equipment-warranty APIs, specific accounting packages beyond Yoke Ledger).
- The ejection clause — take your compiled rules and per-tenant databases with you whenever you want. Useful if your operation grows into a private-equity rollup with its own platform.
FastYoke Partner engagement
For most field-service operations, the right shape is a Strategic Partner engagement:
- iNetko — our first named Strategic Partner — handles schema authoring, FSM design for your specific service-call flow, integration wiring (payment processor, parts- distributor import, equipment-warranty API), and the first 60-90 days of operator onboarding. One iNetko SE for the first three weeks is enough for most single-location pilots.
- See the Multi-location HVAC guide for the realistic pilot path.
Most field-service prospects engage iNetko before they engage their own engineering team. The math usually wins on the partner side — iNetko has done this enough times to make scoping mistakes that you'd otherwise make yourself.
Honest tradeoffs
What FastYoke isn't for field service
- No built-in pricing-book module. Field Service Yoke ships a generic line-item flow. If you're used to ServiceTitan's built-in pricing-book authoring UI, you'll author one in the entity schema layer instead. Real but unfamiliar.
- No native dispatch optimization. You see the queue and you assign manually (or via a simple rules-based workflow). Native vehicle-routing optimization isn't yet generalized from the Bus Routing / Convention Rideshare apps to field service.
- No native mobile app for techs (yet). Techs use the web console on their phone. It's responsive and it works, but it's not a native iOS / Android app. Native field-tech mobile is on the roadmap.
If those tradeoffs are deal-breakers — stay on ServiceTitan. The vertical SaaS has those features because the vertical SaaS is built only for HVAC. FastYoke gives you the operational substrate, the workflow engine, and the multi-app integration story for the cases where the vertical SaaS is overkill or doesn't fit your specific shape.
Next step
Request early access
Talk to iNetko
Already in retail / POS / food service paired with field service? See Pay n Go Systems — our first named Channel Partner — for the integrated storefront-plus-field-tech shape.