Questions dispatchers, managers, and owners actually ask.

RunSheets is a dispatch, ticketing, and billing platform for field service businesses. It covers the full loop — a ticket comes in, gets dispatched to a technician, gets tracked against its SLA, gets resolved, and gets billed — all from one dashboard.

No. RunSheets provisions and manages the underlying Google Sheet and API layer for you — you don't need your own Google account or Workspace subscription. Your customer, ticket, invoice, and technician records live in a real Google Sheet rather than a proprietary database, which is what keeps the data open and exportable; RunSheets just handles running that infrastructure so your team never has to.

RunSheets ships with configured templates for roofers, plumbers, electricians, towing and emergency roadside services, and HVAC and general contracting — and its ticket categories, dispatch rules, and billing can be configured for other trades too. See the Industries page for a breakdown of each template.

No — RunSheets runs for field service teams anywhere in the world. It was built for a Middle Georgia field service business first — Perry, Warner Robins, Macon, and Houston County — so that's where it's most battle-tested, but nothing about it is regional. Any trade, in any state or country, can run on it today.

Request a demo from the About page and we'll walk through your team's workflow, set up your Google Sheet, and configure the ticket categories and dispatch rules for your trade.

New tickets land in an unassigned "Needs Dispatch" tray. From there you drag a ticket onto a technician on the Dispatch Board, which is split into a Business Hours section and an After-Hours section — or switch to the Day Timeline for an hourly, Gantt-style view of exactly who's booked and when.

Marking a ticket Emergency or dispatching it after hours automatically routes it to whoever's on call, with instant email and text notification. No one has to be staring at the dashboard for it to reach them.

Yes. Every open ticket with a resolvable address gets a pin on an interactive map, color-coded by priority and labeled with the ticket number, customer, and assigned technician — so you can see the whole day's workload geographically.

No. You can add a new customer or household right from the New Ticket screen, and everything else you've already typed — priority, category, description — stays exactly where you left it once the new customer is saved.

Customers with multiple properties — landlords, property managers, multi-building accounts — get a Service Locations list on their profile, each with its own address. Pick the right location per ticket and it flows through to the Customer card, the Dispatch board, and the Map automatically.

The Upcoming Installs calendar shows every ticket categorized as an installation on a month view, with any that don't have a scheduled time yet collected into an Unscheduled Installs list underneath — so nothing sits in limbo between quoting and the calendar.

Yes. Scheduled Reports can send a daily or weekly email summarizing SLA performance, ticket throughput, labor hours logged, and overdue invoices, with a test-send button so you can confirm delivery before relying on the schedule.

Every create, update, and delete is recorded in the Audit Log under the real name of whoever did it, pulled from the login screen — never just "anonymous."

Yes. A Module and Feature Management setting lets you hide entire sections — Live Chat, Map View, Scheduled Reports, Billing, On-Call/After-Hours — for your whole team instantly, without deleting any of the underlying data.

No. Technician logins are scoped to their own tickets and hide office-only tools like the Internal Job Tracking Sheet, so field staff get a focused view instead of the full back office.

No. RunSheets generates its own itemized customer invoices — viewable and downloadable as a PDF with no extra setup — and separately, an internal, non-QuickBooks job tracking sheet lets office staff log true job cost (labor hours, parts, notes) that never touches the customer-facing invoice.

A signed-token client self-service portal is built into RunSheets for exactly that, and is being rolled out to customer-facing deployments — ask about it when you request a demo.

Yes. A lightweight, dependency-free chat widget can be pasted onto your own public website; conversations land in a Live Chats inbox where you can reply, convert a chat to a ticket, or generate an invoice from it directly.

Not built directly into RunSheets, but it connects to one: Nagoh's AI Receptionist is a separate add-on that answers every call 24/7 in English or Spanish and feeds straight into RunSheets' existing on-call routing — a ticket gets created and the right technician gets notified automatically, even with nobody at a desk. See nagoh.us/ai-receptionist for setup and current pricing.

Yes. Push Notifications can alert a dispatcher's or technician's device the moment a ticket becomes an emergency or goes after-hours, through real browser push or a webhook relay to a service like ntfy.sh — no RunSheets tab needs to be open.

No artificial seat limits — since your records live in a Google Sheet RunSheets provisions and manages for your account, RunSheets scales with however large that sheet grows.