Everything between the phone call and the payment
Most field service teams run four tools that each know a quarter of the story. Elevate Team keeps one thread per job, carrying the request, the quote, the visits, the time, the parts and the invoice. Every screen is a view of that same thread.
Request to quote
Nothing retyped between the two
Quote to job
Approval creates the work
Job to invoice
Hours and parts already on it
Requests & inbox
One queue for every way work arrives
Email to your service address, the form on your website, a phone note from the office or a message forwarded by a property manager. All of it lands in the same queue, threaded per client, with nothing sitting unclaimed in a personal inbox.
- Inbound email parsed into site, contact, asset and requested window
- New messages matched to existing clients and properties automatically
- Assignment and ownership, so a request cannot go quiet unnoticed
- Replies send from your own domain and thread correctly
“The rooftop unit over the east wing is short-cycling again. We’re open till 6, can someone come Thursday?”
Pulled from the message
- Site
- Northline Depot, east wing
- Asset
- RTU-3 · Carrier 48TC
- Window
- Thu 17 · after 6:00 pm
- Type
- Callback, under warranty
Quotes & approvals
Priced from your catalogue, signed on a phone
Build a quote from your own price book: flat-rate tasks, hourly labour, materials at your markup, taxes by jurisdiction. Send a link, not a PDF. The customer picks their option, signs, and the job is created the moment they accept.
- Optional and alternative line items for good / better / best
- Deposits collected at approval, balance at completion
- E-signature captured with the timestamp and the version signed
- Approved quotes convert into a job without re-entry
Schedule & dispatch
A board that knows what is possible
Drag a visit onto a crew and the board checks drive time, certifications, working hours and what is already booked. Recurring maintenance holds its slot for the length of the contract, and moving a day moves everything that depends on it.
- Day, week and map views of the same schedule
- Recurring visits generated for the whole agreement
- Drive time between consecutive stops factored into the plan
- Customer notifications sent when a window changes
Jobs & visits
One job, as many visits as the work takes
A job is the thread: the original request, the approved quote, each visit with its own crew and checklist, the parts consumed, the photos, and the invoice at the end. Diagnosis today and a return with the part next Tuesday are the same job, not two unrelated tickets.
- Checklists per job type, completed from the phone
- Photos and notes attached to the visit and the site
- Equipment and asset history kept on the property
- Offline capture that syncs when signal returns
Time tracking
Hours that match what you billed
Crews clock in against a visit, not a day, so drive time, on-site hours and overtime attach to the work the customer is paying for. One set of hours feeds both payroll and the invoice, which means they cannot disagree.
- Clock in and out from the mobile app, on or offline
- Approvals before hours are locked for payroll
- Labour cost per job, visible next to what was charged
- Timesheet export for whatever runs your payroll
A. Diaz
Northline Depot · 7:02 → now
R. Whitfield
Ridgeway Plaza · 7:15 → 15:48
J. Osei
Harbour Lofts · 8:00 → 16:12
P. Vance
Drive time · 6:40 → 7:02
Invoices & payments
Billed before the truck is back
Labour comes off the clock, parts come off van inventory, and the invoice is ready when the tech closes the visit. Card and ACH are collected through Stripe on the same link the customer already has, and the money is reconciled back to the job.
- Card and ACH, with the fee handling you choose
- Deposits, progress billing and retainage
- Automatic reminders on overdue balances
- Every payment tied to a job, not only to a customer
Bridgeport HOA
$1,240.00
Average time from last visit to payment: 19 hours
The account is addressable by AI, on purpose
The assistant inside Elevate Team can move a visit, draft a quote or chase an unpaid invoice. The MCP server exposes the same tools to Claude or any other MCP client, scoped by an API key you issue and revoke, with every call written to an audit log.
Crew B finishes Ridgeway at 13:40, eleven minutes from Riverside. Crew C is booked through Friday.
Book Crew B, 14:00–16:00, and notify Marla?
tools used: schedule.find_gap · crew.availability · client.lookup
And the rest of it
The parts nobody demos, that decide whether you stay
Client portal
Customers approve quotes, watch the visit status, read their service reports and pay, without an account and without calling the office to ask where things stand.
Reports
Revenue and margin by job, crew, service and client. Response time, quote acceptance rate, callback rate, and the gap between hours worked and hours billed.
QuickBooks sync
One-way and auditable: invoices, payments and customers push to QuickBooks as clean entries, and every sync writes a record you can inspect when the books disagree.
Inventory & van stock
Stock per location, including each van. Parts consumed on a visit leave the van and land on the invoice, and low stock is visible before a tech discovers it on a driveway.
Mobile app
The crew's whole day on a phone: route, checklists, photos, time, quotes and signatures. Built to work in a basement with no signal and catch up later.
Calendar feeds
A private ICS feed per person or crew, so the schedule shows up in Google Calendar, Outlook or Apple Calendar without anyone copying dates across.
Roles & permissions
Office, dispatcher, crew lead and tech see different things. Discount limits, cost visibility and client data access are permissions, not conventions.
Your own domain
Quotes, invoices and the client portal served from your domain with your branding, so the customer never sees a tool they did not hire.
See it with your own price book.
Import a catalogue, book a job, send an invoice. Free for one crew, no card.