
Requests, Jobs, and Dispatch in One Place for Vancouver Trades
If you run HVAC, plumbing, electrical, cleaning, landscaping, or another on-site service business in Metro Vancouver, your day rarely fits a simple “calendar appointment.” Work starts as a request. It becomes a quote. It turns into a job at a customer address. That job may need one visit or several. Someone has to dispatch the right tech, watch drive time across the Lower Mainland, and still get an invoice out when the work is done.
Modern client systems now include dedicated field-service workflows for that lifecycle. Some features may still be rolling out or in limited release. This post explains the concepts in plain language for BC trades owners, how AI receptionist and booking can feed the front of that funnel, and how SMA Ventures can help you evaluate and set it up when access makes sense. We help local teams put these systems to work — we did not invent them.
Why “appointments” fall short for field work
A haircut or a coaching call is usually one person, one slot, one location. A furnace call in Surrey or a panel upgrade in Burnaby is different:
- The address and travel time matter as much as the clock
- The scope can change after someone is on site
- One customer job may need multiple visits (diagnose → parts → install)
- Office staff, dispatchers, and techs need the same live picture of the day
- Money sits in estimates, invoices, and outstanding balances, not just a booked meeting
Spreadsheets, group texts, and a generic calendar can limp along — until volume grows or a storm week hits.

The field-service lifecycle in plain language
A solid field module is built around requests → jobs → visits, then billing — not only “book a meeting.”
Requests
A request is the inbound ask: online booking page, request form, phone/chat intake, or something your office creates manually. It captures who needs help, where, what kind of service, and enough detail to quote or schedule.
For Vancouver trades, this is where service-area rules matter (North Shore vs. Langley vs. downtown condos with parking constraints). Clear intake early saves a wasted drive.
Jobs
A job ties together one customer, one address, and the work — services and products, pricing, checklists, notes, invoices, and payments. Status moves as visits and billing progress. Think of the job as the folder for everything related to that work order.
Visits
A visit is a scheduled trip with assigned staff (one or more techs), a time or time window, and field execution details — checklists, notes, timers, status updates from mobile. Complex jobs often need more than one visit.
Estimates, invoices, and getting paid
Good field workflows carry the commercial side in the same place: estimates awaiting response, jobs awaiting invoices, invoices awaiting payment. Owners get a home-style overview of money and work that needs attention — not just a calendar grid.
Scheduling, dispatch, and routes
Look for scheduling tools aimed at field reality:
- Find availability that considers staff working hours, services, service areas, existing bookings, and drive time
- Schedule views as list, calendar (day / timeline / week / month), and map
- Dispatch visibility for unassigned visits and visits by status
- Route optimization you can review (including drive-time impact) before you apply — with the ability to lock visits that must stay put
For Metro Vancouver, drive time is not a footnote. Bridge traffic, ferry-adjacent jobs, and dense strata buildings all punish a naive “next open slot” approach. Tools that surface travel and service areas help; they still need your real rules and a human who knows the city.
Crews should use a mobile app with the same login so status, checklists, and notes sync with the office view.
How AI receptionist and booking connect
Field workflows are not only a back-office module. In the systems we configure for clients, a practical front door often includes:
- A branded online booking / request path for customers
- AI receptionist patterns that can answer service, coverage, and pricing questions you allow — and take requests
- Ties to Google booking for businesses that want search demand to land in the same system
That pairs naturally with what many SMA clients already care about: an AI phone or chat agent that qualifies after hours, then writes a clean request or booking into CRM — instead of a voicemail that dies overnight.
A practical front-door design for a Lower Mainland trade shop:
- Missed or after-hours call / chat → AI intake (service type, address/area, urgency)
- In-area + bookable → request or visit path per your rules
- Edge cases (emergencies, warranty disputes, complex quotes) → human callback with full notes in the contact and job record
Privacy still matters in Canada. Be clear with callers when AI is involved, escalate sensitive issues to people, and ask how voice/chat data is stored under PIPEDA and BC’s PIPA expectations.
Set expectations on new field modules
Important framing:
- Some field-service features may be in limited release or private beta. Screens and capabilities can change.
- These modules are aimed at on-location work (HVAC, plumbing, electrical, cleaning, landscaping, and similar) — distinct from a generic calendar-only workflow.
- Availability and exact feature gates depend on your account. This article does not invent access guarantees or dollar figures.
If you are evaluating it, ask what mobile your techs will use, and how you will migrate services, staff hours, and service areas without freezing dispatch for a week.
What “good setup” looks like (SMA’s implementation lens)
Whether you use a dedicated field module or a tighter calendar + CRM pattern today, trades that win on operations usually nail:
- Service catalog — clear offerings and add-ons techs and the website both understand
- Service areas and travel rules — who you serve, when you charge travel, when you decline
- Staff skills and hours — who can run which job types
- Intake scripts — phone, chat, and web forms asking the same core questions
- Dispatch ownership — one person accountable for unassigned visits each morning
- Customer messaging — confirmations, on-the-way texts, and invoice follow-up that do not rely on memory
SMA Ventures helps Vancouver-area businesses design that stack — CRM pipelines, booking, AI phone and chat reception, and field-service configuration where access exists. We frame field modules as an emerging capability we can help you set up, not as something we invented or can promise on every account tomorrow.
Is this relevant to your shop?
Worth a conversation if:
- You regularly lose leads after hours or while crews are on site
- Dispatch lives in texts and whiteboards
- Jobs span multiple visits and the paperwork trails behind
- You already use (or are adopting) a CRM for pipelines, funnels, or AI intake
It may be early if you have a single tech, almost no inbound volume, or no one to own scheduling rules — fix intake and calendar hygiene first, then layer field-specific tools.
Next step
If this is something you want to simplify, send me a message and we’ll map out what makes sense for your business.
— Simon, SMA Ventures

