All docs on one page
Current as of November 2026. The same guides as plain text: llms-full.txt. Operation details are in the API reference.
- Doing Work docs for AI agents
- Connect an agent to Doing Work
- Onboard a shop with your agent
- Recommended setup: chat vs agent
- Job to paid: the core loop
- On the visit: brief, guided steps, recordings, recap and quote drafts
- Guide the people you work for
- Consent and human-only steps
- API conventions
- Errors
- Webhooks and events
- Free field service software pricing | Doing Work
- Free field service software vs Jobber, Housecall Pro, and ServiceTitan | Doing Work
- Total monthly cost of running a shop on Doing Work
- Doing Work for a one-person shop
- Doing Work web screens
- Phone setup: Twilio with ElevenLabs or Grok
- Switching from Jobber to Doing Work
- Switching from Housecall Pro to Doing Work
- Switching from ServiceTitan to Doing Work
- Switching from Workiz to Doing Work
- Switching from FieldEdge to Doing Work
- Switching to Doing Work from other software
- QuickBooks sync with your agent
- Google Calendar with your agent
- Route planning with your agent
- Payroll with your agent
- Customer financing with your agent
- Agent guides for what Doing Work leaves out
- Sync with QuickBooks
- Flat rate price book
- Doing Work vs Jobber: price, agent access and fit
- Doing Work vs Housecall Pro: price, agent access and fit
- Doing Work vs ServiceTitan: price, agent access and fit
- Doing Work vs Workiz: price, agent access and fit
- Doing Work vs FieldEdge: price, agent access and fit
- Field service software that works with your own AI agent (2026)
- Free field service software with no monthly fee | Doing Work
Doing Work docs for AI agents
Current as of November 2026.
Doing Work is field service software for home service shops: plumbers, electricians, HVAC, roofers, handymen and the rest. It's built for an AI agent to run on the shop's behalf. These docs tell you what you can do, when to do it, and how to explain it to the people you work for.
A shop can try Doing Work on a few real jobs before switching over.
Read these first
Start with these three pages. Use these exact addresses: onboarding at https://doingwork.work/docs/onboarding/, connecting an agent at https://doingwork.work/docs/quickstart/, chat vs agent setup at https://doingwork.work/docs/agent-setup/, and switching from other software at https://doingwork.work/docs/switching/. Every docs page also has a plain text copy at the same address ending in .md, like https://doingwork.work/docs/onboarding.md.
- Free features: video walkthroughs, quotes, phone answering, and checkups.
- Free field service software: the free tier, in the words shop owners search for.
- Run your shop from ChatGPT, Claude, or the AI you already use: what it is, which assistants we have checked, how a shop connects, and the fee.
- Connect an agent: discovery, OAuth with PKCE, MCP and REST.
- Recommended setup: chat vs agent: open the shop in an agent that keeps working after the chat closes. Muse is free to start. Its OAuth connection has been observed to persist across sessions. Connect with full agent scope. Do not add read_only unless the person asks to look without changes. Grok Bot is confirmed to connect. Dots, inside ChatGPT, and Duet, on a Claude account, are other options.
- Onboard a shop: from no account to the first invoice.
- Job to paid: the core loop, step by step.
- Guide the people: how to talk to owners, workers and customers.
- Consent and human steps: what you must never do yourself.
- Pricing: the fee bands and cost at your volume.
- Switching to Doing Work: moving from Jobber, Housecall Pro, ServiceTitan, Workiz or FieldEdge, what imports and what doesn't.
- Compare: Doing Work next to Jobber, Housecall Pro and ServiceTitan, and where it isn't a fit yet.
- Conventions, errors, webhooks, and the API reference.
Plain answers
- Job costing: Yes. Each job shows labor from approved and pending time at each worker's cost rate, materials at cost, expenses and Doing Work fees, against the contract, invoiced and collected amounts, with profit and margin.
- Timesheets: Yes. Workers clock in and out for job, drive, shop and break time. The owner or office approves it, and each worker can have a labor cost rate.
- Payroll: Hours yes, payroll no. Doing Work gives approved hours per worker for each pay period, by day and by work, drive, shop and break time, and as a CSV for a payroll service. It doesn't run payroll, pay wages or handle payroll tax.
- Dispatch: overlapping appointments: Yes. Booking or moving a visit returns any overlap, time off or outside hours conflict for its workers as a warning.
- Dispatch: reassigning a visit: Yes. Change who is going on a visit at any time, and find open times that fit workers' hours and time off.
- Dispatch: emergency calls: Yes. A visit can be marked normal, urgent or emergency. For an urgent or emergency visit, Doing Work suggests who could go, ranked by who is free right then and who has the fewest visits that day. Your agent or the office then assigns the worker. Doing Work doesn't assign on its own.
- Parts used on a job: Yes. Parts used on each job are recorded at cost and price, from the price book.
- Inventory and stock levels: Yes, counts on hand. Track any price book material with a low point. Workers record what they use, receive, return or lose, every change keeps who and when, and a reorder list shows what is at or below its low point. Purchase orders are supported: draft one for a job, mark it ordered, receive the parts onto the job, and record the supplier's bill. There are no separate stock locations. Receiving is what adds the parts to job cost.
- Maintenance plans: Yes. A plan bills the customer each term, and the next term's invoice is made automatically and sent if the shop turns that on.
- Recurring billing: Yes, monthly, yearly or any term from 1 to 60 months, through a maintenance plan. An agent can draft the priced lines for a term. An agent only proposes that price; the owner or office confirms it with maintenance.confirmPrice, and an owner or office person sets the price immediately. Doing Work makes each term's invoice when the last one ends and sends it if the shop turns that on. If the customer saved a card and auto-pay is on, the card is charged on the invoice's due date through the shop's own Stripe account. The customer saves the card on a Stripe page, so Doing Work never sees the card number. These are invoices, not Stripe subscriptions, so every charge shows up with the shop's other invoices and payments. See maintenance.createPlan and customers.setAutopay.
- Maintenance reminders: Yes, off until the owner turns them on. Record when a customer's next service is due, like a yearly furnace tune-up, and have it repeat. With service due emails on, the customer gets one reminder email before the date, 14 days by default. Email only, no texts.
- Recurring visits: Yes. A repeating visit (daily, weekly or monthly) can be booked for a job, up to 104 visits at once.
- Recurring maintenance routes: Your agent plans the order. It reads the day's stops from Doing Work, orders them with a maps tool you choose, and saves the new times and workers with routes.apply in one step. Doing Work itself doesn't optimize routes. See route planning below.
- Google Calendar: Yes, one way. Each worker can get a private calendar feed link that Google Calendar, Apple Calendar or Outlook subscribes to. It shows their visits and is read only. A link can be turned off at any time.
- Crew scheduling: Yes. A visit can have more than one worker, and finding a time can require all of them to be free at once. Save a named crew once with crews.save and book it by its crew_id on visits.create, visits.assign or schedule.findTime.
- AI phone answering and booking: On now, once the shop connects its own Twilio account and its own voice agent. It uses the shop's own voice AI. Calls come in on the shop's Twilio number. Doing Work answers, tells the caller it's an AI assistant and that the call is transcribed, then connects the shop's ElevenLabs or Grok agent. If the owner turns on live booking, the shop's voice agent uses Doing Work's booking tools to put the caller straight onto a worker's calendar, for the work and ZIP codes the shop allows. It never makes up a price. It can say a fixed visit fee only if the shop sets one. Emergency calls follow the shop's own settings: transfer to the on-call worker, a text to them, or booking into emergency times the shop opened ahead. Quote follow-up emails and unpaid invoice reminder emails already run by email without that Twilio and voice setup. Autopay charges a saved card only when the shop turns it on for that customer, and that does not need Twilio either. See Phone setup.
- Flat rate price book: Yes. A task has one price, an optional task code, a member price for customers on an active maintenance plan, an estimated time and the parts it uses. Your agent builds quote lines from tasks. Jobber and Housecall Pro price books import from CSV. See Flat rate price book.
- QuickBooks: Your agent syncs with QuickBooks on the schedule you pick. Doing Work has no QuickBooks connection of its own. If you import by hand, the owner or office can also get a month of books as one ZIP: a ledger CSV, QuickBooks Online import files and a README. See Export your books.
- Importing from other software: Yes, from CSV files: customers, jobs with their visit history, open quotes, unpaid invoices, the price book, equipment, maintenance plans and payment history. Presets for Jobber and Housecall Pro. Importing the same file again skips or updates what already came over, so nothing doubles. Imported quotes and invoices are drafts and aren't sent. Maintenance plans come in as service due reminders, or as billed plans at prices the owner checks before anything is saved. Billed plans make no invoice until the next due date and don't send on their own. Payment history comes in as records only. It moves no money and doesn't count toward the fee.
- Visit brief: Yes. Before a visit the agent reads a one page brief: the customer, the address, the request, recent texts and calls, notes, photo summaries with measurements, open tasks and similar past quotes. On the visit.
- Guided visits: Yes. The agent walks the worker through the shop's visit steps in conversation, and the shop can edit the steps. Any step can be skipped. There are no buttons to tap and no app to open.
- Walkthrough recordings: Yes. The worker sends the agent a recording during or after the visit, and the transcript is saved as a note on the visit. Doing Work keeps no audio and does not check recording consent; the shop is responsible for any consent the law requires, under the Terms.
- Customer recap email: Yes. The agent drafts the recap after a visit from what the worker said. It goes to the customer only after the worker tells the agent to send it.
- Drafting quotes: Yes. An agent you connect can draft quote lines, including prices, from what the shop tells you, its price book, or past signed quotes. A person whose role may send it sends it. See Who sends what.
- Learning from corrections: Yes. When a worker changes or rejects a draft, the agent saves what changed and why, and the next drafts for the shop follow it. Lessons are shared across the shop without names.
- Instant reply to new leads: Yes, if the shop turns it on. Doing Work sends one first reply within a minute: a text where the customer agreed to texts and the shop's own number is approved for business texting, otherwise an email. A lead from Angi, Angie's List, HomeAdvisor or Modernize gets one first text when the shop's own approved number is connected, and later texts need the customer to reply first. Leads from Thumbtack, Networx, Google and Yelp get an email. After hours the shop can offer the first open time or hold the lead for the morning.
- Owner morning email: Yes. At 7 AM shop time on days with something to show: jobs under the margin floor, open items, the quote queue and leads held overnight.
- Win back past customers: Yes. The agent lists customers with no visit in a while and can send each one a service due email.
How an agent covers QuickBooks, Google Calendar, route planning, payroll and financing: Agent guides.
Who sends what
The owner can always send quotes, invoices and visit recaps. Office can send them for any job, a lead for jobs on their crew, and field for jobs assigned to them, until the owner turns that send off for that role. Quote or invoice lines an agent drafted stay unsent until a person whose role may send them sends them. An agent token cannot send those lines. A draft a person wrote follows the same role and job checks, and an agent token can send it when the role allows. Visit recaps follow the recap permission.
Rules that always apply
- An agent you connect can draft quote, invoice and change-order lines, including prices, from what the shop tells you or its price book. A person whose role may send it sends it. See Who sends what.
- Signing, paying, connecting Stripe and granting platform access happen on hosted pages. Send the link; never try to do it yourself.
- Refunds above the owner's limit ($250 unless the owner changes it) wait for the owner or office to approve. Recording outside payments works unless the owner turned it off. Webhooks must point to a public https address.
- Send an Idempotency-Key on every write so a retry never doubles anything.
Machine-readable files
- llms.txt and llms-full.txt
- OpenAPI 3.1, generated from the core's operation list
- MCP server card, A2A agent card and API catalog
- Agent guide: every action grouped by area, generated by the core
- Agent skills
- auth.md, OAuth server metadata and protected resource metadata
- Every page as Markdown: add
.mdto the path, or sendAccept: text/markdown.
Connect an agent to Doing Work
Connect an agent
1. Discover
Read https://doingwork.work/.well-known/mcp/server-card.json for the MCP endpoint, or https://doingwork.work/openapi.json for REST. The API sends a 401 with WWW-Authenticate: Bearer resource_metadata=... when you need to sign in.
2. Register your client
Dynamic client registration (RFC 7591). Public clients only, no secret. Redirect URIs must be https or loopback.
POST https://doingwork.work/v1/oauth/register
content-type: application/json
{"client_name": "My shop assistant", "redirect_uris": ["http://127.0.0.1:8976/callback"]}3. The person approves you
Send the person to the authorization_endpoint from OAuth server metadata with client_id, redirect_uri, code_challenge (S256), state, and resource=https://doingwork.work/mcp. They sign in with an email link and approve. You get a one-time code at your redirect.
4. Get a token
POST https://doingwork.work/v1/oauth/token
content-type: application/json
{"grant_type": "authorization_code", "client_id": "...", "code": "...", "code_verifier": "...", "redirect_uri": "http://127.0.0.1:8976/callback", "resource": "https://doingwork.work/mcp"}Access tokens are short-lived. Refresh tokens rotate: each works once, and reusing one revokes the whole chain. Store the new one every time. Use this OAuth path only when the client can open a browser and store the refresh token securely. Do not also call agents.register.
Scope omitted is agent. On a person grant with no shop_id, that can create a shop. Add read_only to look without changes. read_only cannot create a shop. Add no_money to block charges and refunds. agent is required. read_only and no_money only narrow a new grant. Store the refresh token yourself. Doing Work stores only a hash of the key and cannot show it again. Call me.get before you say you are connected. shown_once and persistence not_proven are not a substitute for a fresh session that still returns me.get.
5. Call tools
MCP: streamable HTTP at https://doingwork.work/mcp, Authorization: Bearer <token>. Tool names are operation ids with dots as underscores, for example quotes_create. Hosted-page and person-only operations are not listed as tools.
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"jobs_list","arguments":{"shop_id":"..."},"_meta":{"idempotencyKey":"..."}}}REST: the same operations under https://doingwork.work/v1. GET operations take query parameters; POST operations take a JSON body. See conventions.
Other ways in
For setup, use only one way. OAuth and agents.register never run for the same setup. If the app already shows a Doing Work connector, use that and do not also register. In Muse, use the native OAuth connector. Do not paste a key into a chat to get around that. The claim response rules are on Onboard a shop and in auth.md.
- Named agent key. The shop owner makes a key for you with their own sign-in (keys.create). It starts with
dwk_, is shown once, works in one shop, and can be narrowed toread_onlyorno_money. It works on REST, MCP and A2A. Do not ask the owner to paste the key into a chat. An agent that only keeps it in a session file does not have ongoing access. Muse has no documented way to import an existing key. Use the native connector OAuth storage. - Register and get claimed. Use this when the client cannot open a browser and store a refresh token. Ask for the owner's email, then call agents.register once with
typeset toservice_authandlogin_hintset to that email. Leavescopeoff. The key joins the shop the owner picks and cannot create a shop. Read the short fields first, as Onboard a shop describes. Do not register again. - A2A.
POST https://doingwork.work/a2a(A2A 1.0 JSON-RPC) with a named agent key. SendSendMessagewith one data part,{"op": "<op id>", "input": {...}}. There's no model behind it: the op runs exactly as on REST and MCP. A write the owner must approve comes back as an input required task. Card: agent-card.json.
6. Start with who you are
Call me.get to confirm the connection, then me.start for the shops this connection can use and the next tasks. me.shops lists the shops too. If a shop already exists, use it. Do not create another. Then follow Onboard a shop or Job to paid.
Onboard a shop with your agent
Onboard a shop
Use this when the person you work for runs a home service business and doesn't have Doing Work yet. Ask one thing at a time and keep it short.
If the shop is moving from Jobber, Housecall Pro, ServiceTitan, Workiz or FieldEdge, read Switching to Doing Work too. Customers, jobs with their visit history, open quotes, unpaid invoices, the price book, equipment, maintenance plans (as reminders or billed plans) and payment history (as records) import from CSV files.
First, check where you're running
If you know you stop when the person closes this chat, do not create the shop. Muse at https://ai.meta.com/muse/ is free to start. Its native OAuth connection has been observed to persist across sessions: a stored connection still returned me.get in a fresh session days later. Connect with full agent scope via OAuth. Do not add read_only unless the person asks to look without changes. read_only cannot create a shop. Grok Bot at https://x.ai/bot is confirmed to connect. Dots at https://openai.com/index/introducing-dots/ is inside ChatGPT. Duet at https://claude.com/product/claude-duet uses the connectors on a Claude account. Give them this exact text to paste into an agent that keeps working:
"Help me set up Doing Work using https://doingwork.work/docs/onboarding/. I need an always-on agent. Check the connection before proceeding. Use what you know about my business, ask for anything needed for setup, and explain how to use it after setup."
If you do not yet know whether you keep working, do not create the shop in this session. Prove it with the fresh-session check in After they approve. Do not say you cannot stay connected.
Connect once
Use one path. Do not start a second. OAuth and agents.register never run for the same setup. The same rules are in auth.md.
- Connector. If your app already shows a Doing Work connector, use that. Do not also call agents.register. In Muse, use the native OAuth connector. Do not paste a key instead.
- OAuth. Use this only when the client can open a browser and store the refresh token securely. Follow Connect an agent only. Do not also register. Connect with full
agentscope via OAuth (scope omitted isagentand, on a person grant with noshop_id, can create a shop). Do not addread_onlyunless the person asks to look without changes.read_onlycannot create a shop. Addno_moneyto block charges and refunds.agentis required, andread_onlyandno_moneyonly narrow a new grant. Do not invent a path that pastes a named key into Muse. Use the native connector OAuth storage. - Register once. This is the path when OAuth storage is not available. Ask for the owner's email if you do not have it. Call agents.register once with
typeset toservice_auth,login_hintset to that email, andclient_nameset to the name they will see. Leavescopeoff. The key is bound to the shop the owner picks, so it cannot call shops.create. Do not register again in a loop.
Read the response
Short fields come first. approval pending, authenticated not_yet, and persistence not_proven are normal here. next_step is what you tell the person. Then claim_attempt_token, user_code, claim_token, expires_in (10 minutes), interval, claim_page, verification_uri_length, and claim_token_length. The long verification_uri and complete come last and may be cut off. The claim object repeats the same fields.
- If
completeis true and theverification_urilength matchesverification_uri_length, send thatverification_uriexactly as returned. That is the intact link. claim_urlis the baseclaim_page. It is not the approval link.- If the long
verification_uriis cut off, and bothclaim_pageandclaim_attempt_tokenwere returned, the link isclaim_pageplus?claim_attempt_token=plus that token. Send that built link only when its length also equalsverification_uri_length. If it does not,claim_pagewas cut. Do not send it. Do not invent a host or a path. - Never put
user_codein the link. Show the 6 digit code beside it. - If
completeis missing, or a length does not match, do not register again. Ifclaim_attempt_token,user_code, andclaim_tokenare all there, use this response. - If
claim_tokenis present andclaim_attempt_tokenis missing, call agents.claim once with the same email and thatclaim_token. That one call replaces the attempt. Do not call it again. - If
claim_tokenis missing, stop.
While they finish the page
In that same message, say the next step from next_step. The return address is stored on the server. The email they receive is only a sign-in token. They accept the terms, then the pending claim and consent. They type the 6 digit code. The code lasts 10 minutes. If it expires, stop. Do not register again. If the link is bad or cut off, the app returns 400 and a page that explains it. Do not send a link you made up. The claim page controls are the app. This website cannot add them.
Do not paste a named agent key into the chat or into a file. Muse has no documented way to import an existing key. Use the native connector OAuth storage.
After they approve
approved means they said yes. It does not mean you are authenticated. Poll every interval seconds, and only while the error is authorization_pending. On slow_down, wait the longer interval and poll once more. Stop on access_denied, expired_token, or invalid_grant. Those end this claim. Also stop when expires_in has passed. Do not poll until shown_once. That field is only on success. Do not register again after access_denied. On success, call me.get before you say you are connected. Doing Work stores only a hash of the key, so a lost key locks out the agent, not the owner. The owner can sign in by email and mint a new key or approve a new OAuth grant. persistence stays not_proven, and shown_once only means the key was just handed over. Neither field is a substitute for a fresh check. Prove persistence fast: as soon as the key or refresh token is stored, open a fresh session or reconnect and call me.get. If it works, you may create the shop. Do not wait for the person to come back. If it does not work, stop and tell them the connection did not survive. Do not create a shop or any other business record until that check works. The gate avoids a wasted setup and a duplicate shop, since there is no server-side duplicate-shop guard.
Shop, then one job
Do this only after a fresh session or reconnect can still call me.get. If that check failed, stop.
- Call me.get, then me.start. It lists the shops this connection can use and the next tasks.
me.shopslists the shops too. If a shop already exists, use it. Do not create another. - If they have no shop, confirm the business name and the state. Use what they already told you. Ask only for a missing fact, one at a time. Do not invent an email, name, or address. Call shops.create with
jurisdictionlikeUS-ID. - If they mention other people, invite them with members.invite. If they do not, go on. Workers are unlimited.
- Ask if they want one job. If they do, ask for the customer name and the job address, then call customers.create and jobs.create.
- Do not message a customer or take a payment unless they say so. Do not set up phone, texting, QuickBooks, or Stripe unless they ask. Stripe is only for the first card or bank payment, on a page the owner opens.
- Offer to turn on the shop's hosted appointment request page (/p/book/<slug>) with schedule.setBookingPage, and offer to open their Google Business Profile in their browser to add that booking link (or give them the URL to paste). agent.checkup reminds the shop until that link is added or dismissed with
agent.snooze. - Then say what is done, in one or two sentences, and how they use it. They can ask you to add a job, a quote, or an invoice. Quote follow-up emails and unpaid invoice reminders already run. There is no plan to pick. The fee is The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month. They pay only when a card or bank payment comes through.
Don't
- Don't make up a business name, address, price or email.
- Don't send anything to a customer until the owner says so.
- Don't use a second sign-in path after one has started.
Recommended setup: chat vs agent
Recommended setup: chat vs agent
Doing Work is run by an AI. What that AI can do depends on what kind it is.
- A plain chat (Claude, ChatGPT, Gemini or Grok with nothing connected) can read these docs. It can't see your jobs, and it must not create the shop.
- A chat with Doing Work connected can look things up while you're talking, if you already have a shop. It must not create the shop. When you close the chat, it stops.
- An always-on agent keeps working when you're not there. Open the shop there only after a fresh session can still call me.get. Muse at https://ai.meta.com/muse/ is free to start. Its OAuth connection has been observed to persist across sessions. Connect with full
agentscope. Do not addread_onlyunless the person asks to look without changes. Do not paste a key into Muse. Grok Bot is confirmed to connect. Dots at https://openai.com/index/introducing-dots/ is inside ChatGPT. Duet at https://claude.com/product/claude-duet uses the connectors on a Claude account.
Agents that can run your shop
Muse is free to start. Its OAuth connection has been observed to persist across sessions. Connect with full agent scope. Do not add read_only unless the person asks to look without changes. Grok Bot is confirmed to connect. Dots, inside ChatGPT, and Duet, on a Claude account, are other options.
- Muse: by Meta. Free to start. Plans.
- Grok Bot: by xAI. Pricing.
- Dots: by OpenAI, inside ChatGPT. Which plans include it.
- Duet: by Anthropic. Uses the connectors on your Claude account. Plans.
Runs on its own
Doing Work runs these on its own schedule, whether or not an agent is working. Your agent does the thinking work when you want it: quotes, scheduling, answers. It is part of your setup the way your email and calendar are, and if you already use one, there is nothing new to buy.
- Unpaid invoice reminder email. On by default, starting 1 day after the invoice goes out.
- Quote follow-up email. On by default, 3 days after the quote goes out. The shop can change it from 0 (off) to 30 days.
- Review request email after a paid job. On by default once the shop adds its review link.
- Autopay on a customer's saved card. The shop turns it on for each customer.
- Maintenance plan renewals and service due reminder emails, for shops that use plans.
- Appointment reminders, once the shop turns them on. They go by email, and by text once the shop's texting is set up.
- Payment receipts and the monthly fee statement.
What to look for in an agent
- It connects to a remote MCP server at https://doingwork.work/mcp and signs in with OAuth.
- It keeps working on a schedule, or when something changes, after you close the chat.
- It asks you before it sends anything to a customer or moves money.
- It keeps its sign-in tokens to itself and never asks you to paste them into a chat.
- It tells you plainly when a step failed instead of saying it worked.
Check each agent's own pricing page, linked above, for what it costs.
| Task | Plain chat | Chat with Doing Work connected | Always-on agent |
|---|---|---|---|
| Check if Doing Work fits | Yes | Yes | Yes |
| Set up your shop | No. It must not create the shop. | No. It stops when you close the chat. | Yes |
| Quotes and invoices | No | Yes, while you chat | Yes |
| Answer new customer requests the same day | No | Only when you open the chat | Yes |
| Follow up on quotes and invoices overnight | No | No | Yes |
| Act when a quote is signed or a payment lands | No | No | Yes |
What works in any setup
You do not set up Twilio, or a second tool, for quote follow-ups and invoice reminders. Doing Work sends those emails on its own. The agent is for the thinking work: quotes, scheduling and answers. Phone answering is optional. After you are connected, me.start lists the shops and the next tasks. quotes.list and quotes.get read quotes. invoices.list reads invoices. payments.list and payments.get read payments. agent.checkup is a read-only look across the shop. Nothing is sent.
- Doing Work sends appointment reminders itself once you turn them on: by email, and by text once your texting is set up.
- Quote follow-up emails and unpaid invoice reminder emails already run by email. Autopay charges a saved card only when you turn it on for that customer. None of these need Twilio.
- Your phone agent can answer calls on its own, on your own ElevenLabs or Grok voice account and your own Twilio number. That setup is separate from the emails above.
- Signing, paying and connecting Stripe always happen on a page a person opens. No AI does those for you.
Started in a chat?
If it only answers when you hit send, it must not create the shop. Muse is free to start. Its OAuth connection has been observed to persist across sessions. Connect with full agent scope. Do not add read_only unless the person asks to look without changes. Grok Bot is confirmed to connect. Dots is inside ChatGPT (custom write apps in ChatGPT currently require Business or Enterprise, or Developer Mode where available, until directory approval). Duet uses the connectors on a Claude account. Connect the assistant first, then paste the prompt from the home page into an agent you know keeps working. Pasting the prompt into an unconnected chat only reads the docs. The steps are on Onboard a shop.
Job to paid
| Step | Operation | Who |
|---|---|---|
| Start the job | jobs.create | Agent |
| Add photos | media.requestUpload, then PUT the bytes | Agent |
| The shop's agent drafts the quote lines, including prices | quotes.create | Agent |
| A person whose role may send quotes sends it | quotes.send | Owner always. Office for any job, a lead for jobs on their crew, field for jobs assigned to them, until the owner turns send_quotes off. An agent token cannot send lines an agent drafted. |
| Customer signs | quotes.sign | Customer, hosted page |
| Make the invoice | invoices.createFromQuote | Agent |
| Idaho jobs: subcontractor statement | subcontractors.prepare, then the owner signs | Agent, then owner |
| Send the invoice | invoices.send | Same roles, for send_invoices. An agent token cannot send lines an agent drafted. |
| Customer pays by card or bank (ACH) | invoices.pay | Customer, hosted page |
| Or paid by cash or check | invoices.markPaidOutside | Owner or office, own sign-in |
| Customer confirms the work | jobs.requestConfirmation | Agent sends the link |
| Show the signed record | jobs.record | Agent |
Quote lines
Each line has a description, a quantity and a unit price in cents (unit_price_minor). An agent you connect can draft these, including prices, from what the shop tells you or its price book. The owner can always send quotes, invoices and visit recaps. Office can send them for any job, a lead for jobs on their crew, and field for jobs assigned to them, until the owner turns that send off for that role. Quote or invoice lines an agent drafted stay unsent until a person whose role may send them sends them. An agent token cannot send those lines. A draft a person wrote follows the same role and job checks, and an agent token can send it when the role allows. Visit recaps follow the recap permission. Read the total back before sending.
Bank payments
A bank (ACH) payment takes a few business days to clear. While it clears, the invoice isn't paid yet, and paying again answers payment_pending. Tell the owner: "The customer paid by bank. It takes a few business days to clear." When it clears you get invoice.paid. If it fails you get invoice.payment_failed, the owner gets an email, and the same pay link works again.
Waiting
Signing and paying happen when the customer gets to it. Subscribe to webhooks such as quote.signed and invoice.paid, or read the records, then tell the owner. A quote is quotes.get and the list is quotes.list. Invoices are invoices.get and invoices.list. Payments are payments.get and payments.list.
Start here, then a checkup
me.start is the first read after you connect: the shops this connection can use, and the next tasks. agent.checkup is a read-only look across the shop (stale quotes, overdue invoices, tomorrow's visits, and the rest). Nothing is sent. agent.snooze hides one suggestion.
On the visit: brief, guided steps, recordings, recap and quote drafts
On the visit
Your agent works with the worker in conversation. There are no buttons to tap and no app to open. These are the actions it uses and what it says.
Before the visit
The agent reads visits.brief: the customer, the address, the request, recent texts and calls, notes, photo summaries with measurements, open tasks and similar past quotes. Worker: "What's my next stop about?"
Guided steps
visits.steps returns the shop's steps and the next one to suggest. The agent marks each with visits.markStep when the worker says it's done or wants to skip it. The eight default steps are: arrive, walk through the job, send photos and measurements, ask about questions, budget and timing, debrief and send any recording, send the recap email, draft the quote, and book the next step. The owner or office edits them with shops.setVisitSteps.
Recordings
When the worker sends a walkthrough recording, the agent listens to it, then adds it with visits.addRecording with what the worker said it is, the transcript and when it was recorded. If it's clearly a different job, the agent asks first. Doing Work keeps the transcript as a note and never stores the audio. Doing Work does not check recording consent. Under the Terms, the shop is responsible for any consent the law requires.
Recap email
visits.draftRecap drafts it from what the worker said. The agent reads it back, changes it with visits.editRecap, and sends it with visits.approveRecap when a person whose role may send recaps says send it. The owner can always send a recap. Office can send one for any job, a lead for jobs on their crew, and field for jobs assigned to them, until the owner turns send_recaps off. There is no extra rule that only a person's own sign-in can send a recap. Worker: "Send her the recap."
Quote drafts
quotes.draftFromVisit takes lines in the worker's words. Prices come from the shop's own signed quotes, then its price book, then past quotes. If a price book item changed after the last signed quote, the price book price is used. A line with no price found stays blank for the worker. The agent reads each line and records the worker's answer with quotes.decideDraftLine, then makes the quote with quotes.finishDraft. An agent you connect drafts the lines, including prices. The owner can always send quotes, invoices and visit recaps. Office can send them for any job, a lead for jobs on their crew, and field for jobs assigned to them, until the owner turns that send off for that role. Quote or invoice lines an agent drafted stay unsent until a person whose role may send them sends them. An agent token cannot send those lines. A draft a person wrote follows the same role and job checks, and an agent token can send it when the role allows. Visit recaps follow the recap permission.
Learning from corrections
When the worker edits or rejects a draft, the agent saves the before, the after and the reason with corrections.record, and reads corrections.recent before the next draft. Lessons are shared across the shop without names. Doing Work staff see only anonymous counts across shops, and a pattern shows only when at least 3 shops have it.
Leads and the owner's morning
With the shop's lead rules on (requests.setLeadSettings), a new request gets one first reply within a minute: a text where the customer agreed to texts and the shop's own number is approved for business texting, otherwise an email. A lead from Angi, Angie's List, HomeAdvisor or Modernize, whose forms cover texts, gets one transactional first text when the shop's own 10DLC approved number is connected; any later text needs the customer to reply first, and without an approved number it gets an email. Leads from Thumbtack, Networx, Google and Yelp get an email. First texts are capped at one per phone number per shop every 30 days, and STOP and quiet hours always apply. After hours the shop can offer the first open time or hold the lead for the morning. The owner's morning email lists jobs under the margin floor, open items, the quote queue and held leads.
Guide the people
The people you work for are busy and often on a job site. Keep it short, plain and specific.
With the owner
- Say what you did and what happens next, in one or two sentences.
- Ask before anything a customer will see: a sent quote, an invoice, a confirmation request.
- Read money back exactly: "2 lines, $1,945.00."
- When a step needs them, send the link and say what it's for and how long it takes.
- Use "worker" for people on the team.
With the office
An office manager signs in their own agent with the office role. The owner adds them with members.invite. A good morning with them:
- Read the day with reports.today: visits by worker, what is unassigned and what is waiting.
- Assign urgent and emergency work. dispatch.suggest ranks who could go, and the office picks with visits.assign.
- Approve or send back time with timesheets.decide.
- Send deposit links for work the phone agent took as a request, after the office checks the price.
- Keep it to what they asked for. The office decides; you do the clicking.
Who sends what
The owner can always send quotes, invoices and visit recaps. Office can send them for any job, a lead for jobs on their crew, and field for jobs assigned to them, until the owner turns that send off for that role. Quote or invoice lines an agent drafted stay unsent until a person whose role may send them sends them. An agent token cannot send those lines. A draft a person wrote follows the same role and job checks, and an agent token can send it when the role allows. Visit recaps follow the recap permission.
With workers
- An agent you connect can draft lines and prices from what they tell you or the price book. A person whose role may send it sends it. See Who sends what.
- Field workers see what their role allows. If something is refused, say who can do it.
With customers
Sending a quote or invoice returns a single-use link for the customer. A person whose role may send it sends it. See Who sends what. Each link works once, and a newer one replaces it.
Money and fees
- No plans, no monthly fee and no card to enter. Every shop gets every feature, with unlimited workers, jobs, customers, quotes and invoices.
- Doing Work takes a fee out of each payment: The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month. The shop only pays when it gets paid, and deposits count.
- A payment that crosses $1,000 is only charged on the part above $1,000. Once fees in the month hit $149, later payments that month are charged 0%.
- Locations under one owner count their payments together. The month starts over on the 1st.
- Fees come out of the shop's customer payments before payout. On the 1st each shop gets a fee statement and how far it is from the $149 cap.
- A refund returns our fee on the refunded part at the rate that payment was charged. Jobs paid outside Doing Work are unlimited and cost nothing.
- Nothing is metered. The payment fee is the only thing Doing Work charges. Storage, email and every Doing Work feature are included.
- Calls and texts run on the shop's own Twilio account, so Twilio bills the shop directly for them. A voice AI that answers the shop's calls is the shop's own ElevenLabs or Grok agent, billed by that provider.
- Requests and quotes are free for shops and customers. We will never charge lead or referral fees.
- Customers can pay by card or bank. Card and bank processing is charged separately by Stripe at its standard rates: https://stripe.com/pricing.
- Cost at your volume: $1,000 in payments a month costs nothing, $3,000 costs $10, $5,000 costs $20, $15,000 costs $70, $20,000 costs $95, $30,800 costs $149, and $160,000 costs $149. See https://doingwork.work/docs/pricing/.
- A shop can try Doing Work on a few real jobs before switching over. With no monthly fee, it pays only the fee on payments taken through Doing Work.
- Use fees.preview to say what a payment would cost and how far the shop is from the next band. Mention the next band only when the owner asks about fees.
What to say for each action
Every page in the API reference has a "What to tell the owner" line.
Consent and human steps
Some actions need a person: a signature, a card, consent to renewal terms, or a decision about money. Doing Work enforces this. Hosted-page operations return human_only (403) on the API and aren't MCP tools. Person-only operations refuse agent tokens with forbidden.
| Action | Who does it | What you do |
|---|---|---|
| auth.redeemLink | Hosted page only (a person does it in the browser) | Never call it yourself. The person's browser does this when they open the sign-in link. |
| media.requestCapture | Hosted page only (a person does it in the browser) | Never call it yourself. Used by the hosted camera page when a worker takes a photo in the browser. |
| jobs.confirm | Hosted page only (a person does it in the browser) | Never call it. The customer confirms or flags a problem on the hosted page. |
| quotes.sign | Hosted page only (a person does it in the browser) | Never call it. The customer opens the link from the email or text and types signer_name. They do not need a Doing Work account, and a signed-in browser session is not the signer. n is the hidden value printed on the quote page and bound to this link. |
| subcontractors.sign | Hosted page only (a person does it in the browser) | Never call it. The owner or office signs on the hosted page. |
| payments.connectStart | Hosted page only (a person does it in the browser) | Never call it. The owner connects their own Stripe account on the hosted page. |
| invoices.pay | Hosted page only (a person does it in the browser) | Never call it. The customer pays on the hosted page. |
| platforms.grantManage | Hosted page only (a person does it in the browser) | Never call it. The shop owner allows a platform on the hosted page. |
| customers.privacyDelete | A person's own sign-in only (agent tokens are refused) | Erase a customer's personal details for a privacy request. Money and job records stay, unnamed. |
| quotes.respond | Hosted page only (a person does it in the browser) | Customer declines a quote or asks for changes (hosted page). Asking for changes needs a note and puts the quote back to draft for the shop to revise. |
| shops.setAgentMoney | A person's own sign-in only (agent tokens are refused) | Owner only, not an agent: set what this shop's agents may do with money. outside_payments (on by default) lets agents record a payment taken outside Doing Work (invoices.markPaidOutside). |
| cards.resave | Hosted page only (a person does it in the browser) | Open the card saving page from a save-your-card-again email link (hosted page only). Returns the processor URL where the customer saves the card on the shop's current payments account. |
| maintenance.confirmPrice | A person's own sign-in only (agent tokens are refused) | Apply an agent's proposed price on a maintenance plan. Owner or office, from their own sign-in, never an agent. |
| keys.create | A person's own sign-in only (agent tokens are refused) | Make a named agent key for one shop (owner only). The owner accepts the agent key terms by passing accept_terms_version. |
| agents.approve | Hosted page only (a person does it in the browser) | Hosted claim page only: the shop owner whose email the claim names types the agent's 6 digit code, picks one of their shops and accepts the agent key terms. Makes a named agent key for that shop. |
| agents.deny | Hosted page only (a person does it in the browser) | Hosted claim page only: the person turns the agent down. The registration closes and the agent's poll gets access_denied. |
| members.setPermissions | A person's own sign-in only (agent tokens are refused) | Owner only, not an agent: turn a worker's permissions on or off. Give only the flags to change (see_prices, see_costs, take_money, delete, manage_schedule). |
| shops.setSendPermissions | A person's own sign-in only (agent tokens are refused) | Owner only, not an agent: turn sending quotes, invoices or visit recaps on or off for one role (office, lead or field). Give only the switches to change. |
| legal.accept | A person's own sign-in only (agent tokens are refused) | Record that the signed-in person accepts the current version of a legal document (clickwrap). An agent API key cannot record it. |
| legal.acceptShopTerms | Hosted page only (a person does it in the browser) | The shop owner, on the hosted shop terms page, ticks the box and accepts the current Terms of Service for the shop (accept_terms_version). Records the time, version, person, IP address and browser. |
| legal.arbitrationOptOut | Hosted page only (a person does it in the browser) | The shop owner, on the hosted shop terms page, opts the shop out of section 19 arbitration and the class action waiver. Works within 30 days after the owner first accepted terms with section 19 for the shop (or, for a shop an agent signed up, after we emailed the owner the terms). |
| signatures.sign | Hosted page only (a person does it in the browser) | Sign a document after reading it, typing your name and agreeing to sign electronically. Hosted page only; agents can never sign. |
| shops.transferStart | Hosted page only (a person does it in the browser) | Start handing the shop to a current worker (owner, on a hosted page). They accept on their own hosted page within 14 days, and ownership moves at once. |
| shops.transferAccept | Hosted page only (a person does it in the browser) | Accept a hand-off and become the shop's owner (the person asked, on a hosted page). The person agrees to the Terms of Service by ticking a box (accept_terms_version); the record keeps the version, time, IP address and browser. |
| shops.close | Hosted page only (a person does it in the browser) | Close the shop for good (owner, on a hosted page, typing the shop name). Everyone loses access, agent connections and webhooks stop, every customer link stops working, and the payments account only settles what is in flight. |
| shops.reopen | Hosted page only (a person does it in the browser) | Reopen a closed shop (only the owner who closed it, on a hosted page, within 90 days of closing). You come back as owner. |
| subs.view | Hosted page only (a person does it in the browser) | The subcontractor's page for one job: the shop, job summary, work address, scope note, upcoming visit times and their notes. state is ok, gone (removed, expired, job cancelled or shop closed) or wrong_person (signed in with a different email, or someone else opened it first). |
| subs.addNote | Hosted page only (a person does it in the browser) | Leave a note for the shop on this job, as the subcontractor (up to 20 a day). Hosted page only. |
| network.setAgentOptIn | A person's own sign-in only (agent tokens are refused) | Let the shop's agents turn customer requests on or off and change what the shop takes (owner only, with your own sign-in). On by default. |
| phone.takeThread | Hosted page only (a person does it in the browser) | Take a text thread yourself: it is assigned to you, and sends paused by a customer's stop-like message start again once a person has read it. |
| me.setSmsConsent | Hosted page only (a person does it in the browser) | Grant or revoke Doing Work SMS alerts and check-in consent for the signed-in person. Hosted page only; an agent key cannot opt in for someone. |
| hub.view | Hosted page only (a person does it in the browser) | The customer hub for the signed-in customer: their quotes, jobs, invoices with what is still owed, upcoming visits with any change request, requests with this shop, and their active maintenance plans (what each covers, the next visit due, price per term, renewal date and card on file). state is ok, gone (revoked, expired or unknown) or wrong_person (signed in with an email the shop does not have for this customer). |
| hub.open | Hosted page only (a person does it in the browser) | Open a sent quote or an unpaid invoice from the customer hub: returns a fresh page link for that one item, for the signed-in customer only, good for a day. Refused with conflict for an invoice that cannot take payment now (its Doing Work booking ended, or a no-show on it is disputed). |
| hub.requestVisitChange | Hosted page only (a person does it in the browser) | From the customer hub, ask the shop to move (reschedule, with the times that work better) or cancel an upcoming visit. The visit stays as it is until the shop answers. |
| hub.withdrawVisitChange | Hosted page only (a person does it in the browser) | From the customer hub, take back your own open request to move or cancel a visit. Hosted page only. |
| hub.requestWork | Hosted page only (a person does it in the browser) | From the customer hub, ask the shop for new work. It lands in the shop's requests (source portal) on this customer, with their contact details already filled. |
| approvals.setRule | A person's own sign-in only (agent tokens are refused) | Owner only, not an agent: require owner approval before an agent can run an action. op is an operation id (invoices.send), an area (invoices.*) or * for every write. |
| approvals.removeRule | A person's own sign-in only (agent tokens are refused) | Owner only, not an agent: stop requiring approval for a rule. Pending requests under it stay pending. |
| approvals.decide | A person's own sign-in only (agent tokens are refused) | Owner only, not an agent: approve or deny a pending agent action. On approve it runs now, as the owner, and the result is saved on the request. |
Rules
- Never try another route around a refusal. Send the link or ask the person.
- Never tick a consent box, sign, or enter a card for someone.
- Say what the person is agreeing to before you send the link, for example the quote total and the e-sign consent.
Conventions
- Base:
https://doingwork.work/v1for REST,https://doingwork.work/mcpfor MCP. REST is at https://doingwork.work/v1, MCP at https://doingwork.work/mcp and A2A at https://doingwork.work/a2a, all with the same operations and permissions. - Auth:
Authorization: Bearer <token>from OAuth. - Version: send
Doing-Work-Version: 2026-11-01. Tokens are pinned to a version, and every response echoes the one used. - Idempotency: send
Idempotency-Keyon every POST that writes (in MCP,_meta.idempotencyKey). A retry with the same key and body returns the first result. A different body givesidempotency_key_reused. - Money: integers in cents, in fields ending
_minor. - Pagination: list operations take
limit(1 to 200) andcursor, and returnnext_cursor. - Rate limits: 429
rate_limitedwithRetry-Afterin seconds. - Errors: JSON
{code, message, status}. See errors. - Unknown fields are rejected, so a typo fails loudly instead of being ignored.
- Events: every write emits one event per resource it changes. See webhooks.
Errors
Errors are JSON: {"code": "...", "message": "...", "status": 400}. The message is for you; the code is stable.
| Code | Status | Meaning and what to do |
|---|---|---|
invalid_input | 400 | A field is missing, the wrong type, or unknown. The message names the field. Fix the input; don't retry as is. |
disclosure_ack_required | 400 | The customer must acknowledge the Idaho disclosure on the hosted signing page. |
terms_not_accepted | 400 | |
terms_not_published | 503 | |
consent_required | 400 | A person must tick a consent box on a hosted page (for example e-sign). Send them the link. |
unsupported_version | 400 | The Doing-Work-Version header isn't one the API knows. Use 2026-11-01. |
bad_signature | 400 | A signature didn't verify. |
invalid_link | 400 | The link was used, expired, or replaced by a newer one. Get a new link. |
invalid_request | 400 | An OAuth request is malformed. |
invalid_grant | 400 | The code, verifier or refresh token is wrong, used or expired. Start sign-in again. |
unsupported_grant_type | 400 | Use authorization_code or refresh_token. |
invalid_target | 400 | The resource parameter doesn't match this server. |
invalid_scope | 400 | The requested scope isn't offered. |
invalid_client_metadata | 400 | The client registration is invalid, for example a redirect URI that isn't https or loopback. |
invalid_claim_token | 400 | |
issuer_not_enabled | 400 | |
authorization_pending | 400 | |
slow_down | 400 | |
expired_token | 400 | |
access_denied | 400 | |
claimed_or_in_flight | 409 | |
claim_expired | 410 | |
invalid_token | 401 | The token is missing, expired, or for a different resource. Refresh it or sign in again. |
session_required | 403 | A person has to be signed in on a browser for this step. |
owner_cannot_leave | 409 | The owner can't leave a shop. Ownership moves only by transfer. |
owner_role_fixed | 409 | The owner's role can't be changed. |
unauthenticated | 401 | No token was sent. Sign in first. |
not_served | 422 | |
stripe_required | 409 | |
forbidden | 403 | This worker's role can't do this, or it needs a person's own sign-in rather than an agent token. Tell the person who can. |
not_a_member | 403 | |
human_only | 403 | This step happens on a hosted page the person opens themselves. Send them the link; don't try another route. |
feature_unavailable | 403 | This isn't available for this shop or place yet. |
upstream_failed | 502 | |
private_beta | 403 | This is invite only for now. Tell the person to email contact@doingwork.work. |
not_found | 404 | No such record, or this worker can't see it. |
conflict | 409 | The record is in the wrong state for this, for example sending a quote that's already signed. Read it again and pick the next step. |
needs_change_order | 409 | |
opt_out_closed | 409 | |
checklist_open | 409 | |
payment_pending | 409 | A bank (ACH) payment for this invoice is still clearing, which takes a few business days. Don't ask the customer to pay again. Wait for invoice.paid or invoice.payment_failed. |
payments_not_set_up | 409 | The shop hasn't connected Stripe. The owner does that on a hosted page. |
payments_paused | 409 | |
idempotency_in_progress | 409 | A request with this Idempotency-Key is still running. Wait and retry with the same key. |
idempotency_key_reused | 422 | This Idempotency-Key was used with a different body. Use a new key for a new request. |
unprintable_text | 422 | |
document_too_large | 422 | |
rate_limited | 429 | Too many requests. Wait for the Retry-After time, then retry. |
low_contrast | 422 | |
unsupported_logo | 422 | |
logo_too_large | 413 | |
payload_too_large | 413 | |
internal | 500 | Something broke on our side. Retry later with the same Idempotency-Key. |
not_supported | 501 | Not supported yet. |
Webhooks and events
A developer adds an endpoint with their own sign-in (webhooks.create); the secret is shown once. Deliveries are POSTs with DW-Signature: t=<unix seconds>,v1=<hex HMAC-SHA256 of t.body>. Any non-2xx is retried with backoff. Delivery is at least once, so dedupe on the event id.
| Event | What happened |
|---|---|
shop.created | A shop was created. |
membership.invited | A person was invited to a shop. |
membership.role_changed | A worker's role in a shop changed. The old membership ended and a new one started. |
quote.revised | An unsigned quote was replaced by a new version. |
quote.withdrawn | The shop took back an unsigned quote; its signing links stopped working. |
charge.succeeded | A payment succeeded. |
dispute.closed | A payment dispute closed (won, lost or closed). |
plan.changed | A shop changed plan. |
subcontractor_list.signed | A shop signed the Idaho 45-525(3) subcontractor list for a job. |
subcontractor_list.prepared | An agent prepared the Idaho 45-525(3) subcontractor list for a person to sign. |
plan.change_scheduled | A shop scheduled a move down; it starts on the first day of effective_period (shop time). |
fee.owed_to_shop | A fee that was credited against a plan price is owed back to the shop after a refund or lost dispute. |
plan.billed | Not sent. Doing Work has no plans or monthly fee; kept so old subscriptions stay valid. |
membership.started | A person joined a shop. |
membership.ended | A person's membership in a shop ended. |
membership.permissions_changed | The owner changed what a worker may do: see_prices, see_costs, take_money, delete and manage_schedule. |
ownership.transfer_started | The owner started handing the shop to someone else. |
ownership.transferred | Shop ownership moved to a new owner. |
ownership.transfer_cancelled | An open hand-off was stopped: the owner cancelled it or the person asked declined. |
shop.closed | The owner closed the shop. Everyone lost access and every link stopped; records are kept. |
job_subcontractor.added | A subcontractor was added to a job. |
job_subcontractor.updated | A subcontractor's contact name, trade or scope note changed. |
job_subcontractor.removed | A subcontractor was taken off a job; their link stopped. |
job_subcontractor.joined | A subcontractor opened their link for the first time, signed in. |
job_subcontractor.note_added | A subcontractor left a note on a job. |
recovery.opened | Someone asked to take over a shop whose owner cannot be reached. |
recovery.decided | A recovery request was decided. |
home.claimed | A person claimed a home. |
home_role.ended | A person's role at a home ended. |
job.created | A job was started at a home. |
job.completed | A job was marked done with jobs.complete (W2). override_id is set when the owner overrode open checklist work. |
media.uploaded | A photo or video was added to a job. |
media.tagged | Tags on a photo changed. |
photo_share.created | A share link for job photos was made. It expires on its own and can be revoked. |
photo_share.revoked | A photo share link was turned off before it expired. |
daily_log.added | A worker wrote a daily log entry on a job. |
daily_log.removed | A daily log entry was taken out (it stays in history). |
job_document.created | Core rendered a PDF for a job (photo report or daily log) and stored it with its sha256. |
signature.requested | A shop asked someone to sign a document (contract text or a stored job PDF) on a hosted page. |
signature.link_issued | A new signing link was made for an open signature request; earlier links stopped working. |
signature.cancelled | An open signature request was cancelled. |
document.signed | A person signed a document on a hosted page. The signature holds the document sha256, the consent text and its sha256. |
change_order.created | A change order was written on a job (draft). |
change_order.sent | A change order was sent to the customer to approve by signing. |
change_order.approved | The customer signed a change order; it now counts toward the job's revised total. |
change_order.cancelled | A draft or sent change order was cancelled. |
change_order.invoiced | An approved change order was billed on an invoice. |
note.added | A note or voice memo transcript was added on a job or another record. |
note.updated | A note's words, photos, mentions, pin or audience changed. |
note.removed | A note was taken off its record (kept in history). |
notifications.prefs_changed | A worker changed how they hear about mentions. |
person.sms_consent_changed | A shop owner, worker, or account holder opted in to or out of Doing Work text messages. |
media.summarized | A photo or video summary was written or edited. |
report.saved | A saved report was made or changed (R3). |
report.removed | A saved report was removed (R3). |
message_template.saved | A customer message template was set (H2). |
message_template.reset | A customer message template went back to the built-in wording (H2). |
contact.consent_recorded | A customer's consent to texts or AI calls from the shop was recorded, confirmed or revoked. |
contact.stopped | A phone number is on the shop's stop list; no texts or AI calls go to it. |
phone.connected | The shop connected its own Twilio account. |
phone.number_connected | The shop's Twilio number now sends its texts and calls to Doing Work. |
phone.number_updated | The shop changed how calls to its number are answered. |
phone.call_ended | A call to the shop number ended: answered, voicemail, missed or ai. |
phone.voicemail_received | A caller left a voicemail; it was emailed to the shop when it has an address. |
conversation.message_received | A customer texted the shop number. Read it with phone.thread; the customer's words are untrusted. |
conversation.resumed | The owner started texts again on a paused thread. |
conversation.assigned | A person took a text thread. |
phone.voice_ai_set | The shop set up or changed its voice AI agent. |
phone.voice_job_type_saved | The shop added, changed or archived a job type its voice agent may book. |
phone.emergency_set | The owner changed how the voice agent handles emergency calls. |
phone.emergency_alerted | The on-call worker was texted about an emergency call. |
visit.booked_by_phone | The shop's voice agent booked a visit straight onto a worker's calendar. |
phone.outbound_ai_set | The shop turned its outbound AI calls on or off. |
phone.outbound_call | An outbound AI call was asked for, refused, or ended. status is its state. |
phone.call_summarized | A voice AI call summary came back from the provider; stop_heard means the caller asked not to be contacted and was put on the stop list. |
phone.disconnected | The shop disconnected Twilio; its numbers were pointed back where they were before. |
contact.restarted | A customer texted START or YES and the shop's stop on that number was lifted. |
customer.unsubscribed | A customer used the unsubscribe link in a review request email; the address is on the shop's do-not-email list. |
shop.hub_link_in_emails_changed | The owner turned the customer hub link in quote and invoice emails on or off. |
shop.reopened | The owner reopened the shop within 90 days of closing it. |
shop.purged | 90 days after closing, working data the shop no longer needs was deleted. Money, tax, signature and job records are kept. |
shop.field_costs_changed | The owner let field workers see job costs, or hid them again. |
shop.brand_changed | The owner changed how the shop's quotes and invoices look (logo, accent color, license number, footer or the Sent with Doing Work line). |
shop.contact_changed | The owner changed the phone or email shown on canceled invoice and quote links. |
hub_link.created | A customer hub link was made (H2). |
hub_link.revoked | A customer hub link was revoked (H2). |
visit_change.requested | A customer asked from their hub to move or cancel a visit (H2). |
visit_change.withdrawn | A customer took back their request to move or cancel a visit (H2). |
visit_change.answered | The shop accepted or declined a customer's request to move or cancel a visit (H2). |
form_template.saved | A form template was created or replaced. |
form_template.archived | A form template was archived. |
form.started | A form was started on a job or one visit (a draft). |
form.updated | Answers were saved on a draft form. |
form.submitted | A form was submitted: its PDF is stored on the job and the form is final. |
form.cancelled | A draft form was cancelled (kept in history). |
time.clocked_in | A person's clock started (work on a job, drive, shop or break). |
time.clocked_out | A running clock stopped; the time waits for approval. |
time.added | Time was added after the fact (a manual entry); it waits for approval. |
time.edited | A time entry that was not approved was fixed. |
time.approved | The owner or office approved a time entry; it is locked. |
time.rejected | The owner or office rejected a time entry; the worker can fix it. |
time.voided | A time entry that was never approved was taken back. |
time.reopened | The owner reopened approved time so it can be fixed. |
labor_rate.set | A labor cost rate was set for a worker or the shop default (the amount is not in the event). |
material.added | A material used was recorded on a job. |
material.updated | A recorded material's quantity, visit or notes changed. |
material.removed | A recorded material was removed (kept in history). |
checklist_template.saved | A checklist template was created or replaced. |
checklist_template.archived | A checklist template was archived. |
checklist.created | A checklist was put on a job or on one visit. |
checklist.items_added | Items were added to a checklist. |
checklist.item_checked | A checklist item was ticked or unticked. |
checklist.item_removed | A checklist item was removed (kept in history, audited). |
checklist.overridden | The owner marked a visit or job done with checklist work left. The reason and the open items are in the audit log. |
expense.added | A worker recorded an expense on a job (amount typed by the worker). |
expense.updated | An expense was changed. |
expense.removed | An expense was taken off the books (kept in history). |
approval_rule.set | The owner required approval before agents run an action. |
approval_rule.removed | The owner dropped an approval rule. |
approval.requested | An agent action is waiting for the owner's approval. |
approval.decided | The owner approved or denied a held agent action. |
media.markup_saved | A new markup layer was saved over a photo. The photo itself is unchanged. |
customer.created | A customer was added to a shop. |
import.completed | An owner finished an import from another system. Imported records do not send their own created events. |
quote.created | A quote was written. |
quote.sent | A quote was locked and sent for signing. |
quote.signed | The customer signed a quote. |
pricebook.item_saved | A price book item was added, changed, archived or brought back. |
pricebook.prices_imported | Dated prices were saved on the price book. The amounts stay on the items. |
shop.price_stale_days_changed | The owner or office changed how old a price may be before it shows as stale. |
shop.pricing_rules_changed | The owner saved or cleared the pricing rules their assistant reads with quote comparables. |
pricebook.prices_applied | A dated price became the current price because its date arrived. |
quote_template.saved | A quote template was saved, archived or brought back. |
quote.declined | The customer declined a quote on the sign page. |
quote.change_requested | The customer asked for changes to a quote. The quote is back to draft; read the note with quotes.activity. |
quote.viewed | The customer opened a sent quote version for the first time. |
quote.followup_queued | A follow-up email was queued for a quote the customer has not answered. |
crew.saved | The office saved a crew of workers to book together. |
crew.archived | A crew was archived. Booked visits keep their workers. |
financing.saved | The office saved a financing link. Doing Work does not process financing or charge a fee. The link goes to the shop's financing company. |
financing.archived | A financing link was archived and no longer shows on quotes. |
shop.margin_alert_changed | The owner set or turned off the profit alert. |
shop.morning_email_changed | The owner turned the morning email on or off. |
task.created | Someone made a tracked task, usually from a crew message: a title, maybe a job, a worker and a due time. |
task.updated | A task's title, worker, job or due time changed. A new due time re-arms the one chase. |
task.closed | A task was closed as done or cancelled. Closed tasks are never chased. |
agent.followup_due | An agent's own follow-up is due. Nothing is emailed. A webhook subscriber can wake the agent. |
nudge.triggered | An actionable next-step nudge or check-in is ready for a shop (unbilled work, unsent draft, or scheduled check-in). A webhook subscriber can push or text the user. |
agent.snoozed | A checkup suggestion was snoozed or dismissed. |
shop.kit_list_changed | The owner or office changed the hour of the night-before kit list email, or turned it off. |
job.margin_low | An invoiced job's margin dropped under the shop's profit alert floor. Fires once until the margin climbs back. |
shop.quote_followup_changed | The owner changed the quote follow-up delay. |
quote.choice_signed | The customer signed a quote with options or optional lines. Says which option and optional lines they picked and the total. |
shop.tax_report_basis_changed | The owner chose how the sales tax report counts a period (accrual or cash). |
maintenance_plan.tax_changed | The office changed the tax rate a maintenance plan charges from the next term. |
shop.tips_changed | The owner turned tips on or off on the pay page. |
shop.agent_money_changed | The owner changed what agents may do with money: record outside payments, and the largest refund an agent sends without approval. |
shop.review_request_changed | The owner changed the review link or the review email delay. |
review.request_queued | A review request email was queued for a customer whose invoice was paid. |
card.saved | A customer saved a card on the shop's payment account. |
card.removed | A customer's saved card was removed. |
customer.autopay_changed | Auto-pay was turned on or off for a customer. |
invoice.autopay_started | An invoice was charged to the customer's saved card. invoice.paid follows when the charge succeeds. |
invoice.autopay_failed | An auto-pay charge failed. The invoice stays open. |
tax_rate.saved | A tax rate was added, replaced or archived. A replaced rate is archived and a new one takes its place. |
quote.attachment_added | A photo or file was shown with a quote. |
quote.attachment_removed | A photo or file was taken off a quote. |
maintenance_plan.created | A maintenance plan was started. Its first term's invoice was created. |
maintenance_plan.price_changed | A worker changed a maintenance plan's price. It applies from the next term. |
maintenance_plan.price_proposed | An agent proposed a new price for a maintenance plan. It does not apply until the owner or office confirms it. |
shop.send_permissions_changed | The owner changed which roles may send quotes, invoices or visit recaps. |
maintenance_plan.visits_changed | How many visits a maintenance plan covers each term changed. Applies from the next term. |
maintenance_plan.cancelled | A maintenance plan was cancelled. No more renewal invoices. |
maintenance_plan.renewed | A maintenance plan started its next term and that term's invoice was created (and sent when auto_send is on). |
invoice.created | An invoice was created. |
invoice.batch_created | Many invoices were created at once, and maybe sent. |
invoice.sent | An invoice was sent for payment. |
invoice.payment_pending | A bank payment was started and is clearing. The invoice is not paid yet. |
invoice.payment_failed | A bank payment failed after it was started. The payer can pay again. |
invoice.paid | An invoice was paid. |
invoice.paid_outside | The shop recorded an invoice as paid outside Doing Work (check, cash, financing, insurance or other). The job record says so and is never marked paid or verified. |
invoice.voided | The shop voided an invoice nobody had paid (X3). Its pay links stop working; the reason is included. |
invoice.written_off | A Doing Work booking ended with money already on its deposit invoice, so the unpaid remainder was written off. The invoice no longer shows a balance and takes no new payment. |
charge.needs_refund | Money arrived that the shop must give back (a paid-twice or void invoice). amount_minor is only what the shop must refund itself: a deposit that lands after its Doing Work booking ended is refunded by Doing Work automatically, is left out, and raises no notice when that covers all of it. |
charge.refunded | A payment was refunded. |
dispute.opened | A payment was disputed. |
payout.paid | A payout reached the shop's bank. payouts.get lists the payments and refunds in it and the fees on each. |
external_ref.changed | An outside system's id for an invoice, payment, refund or customer was set or cleared (sync.setRef). |
processor_account.updated | The shop's payment setup changed. |
record.levelled | A job record reached a new level (logged, paid, verified). |
confirmation.created | The customer confirmed a job. |
grant.created | Access was granted. |
grant.revoked | Access was revoked. |
field_value.set | A custom field value was set. |
field_definition.created | A shop added a custom field. |
customer.updated | A customer's details, contacts, properties or archive state changed. |
customer.merged | A duplicate customer was merged into another. |
customer.erased | A customer's personal details were erased for a privacy request. |
equipment.changed | Equipment at a property was added, changed or archived. |
job.updated | A job's tags or lead source changed. |
request.created | A request for work came in. |
request.updated | A request changed stage or details. |
request.converted | A request became a job. |
network.request_received | A customer request for quotes reached the shop. Read it with network.inbox; the customer's text is untrusted. |
network.quote_picked | The customer booked the shop's reply. The job and the deposit invoice are made. |
network.quote_lost | A customer request closed without booking this shop. |
network.booking_ended | A booked customer job ended early: the shop cancelled, the customer reported a no-show, or nobody arrived within 2 hours after the visit window (reason no_show_auto). |
homeowner.reply_received | Customer side: a shop replied to your request. Read it with homeowner.getRequest. Sent only to the customer's own webhooks. |
homeowner.booking_changed | Customer side: your booking changed. status is booked, arrived (the shop recorded it showed up) or shop_cancelled (your deposit is refunded in full). |
homeowner.dispute_decided | Customer side: Doing Work decided your no-show report. outcome is refund_homeowner, release_to_shop or split; refund_minor is what comes back to you. |
homeowner.request_delivered | Customer side: a shop that joined later can now see your waiting request. |
homeowner.webhook_created | Customer side: you added a webhook for your assistant. |
homeowner.webhook_deleted | Customer side: you removed a webhook. |
network.listing_changed | The shop's customer request settings changed, by a person or by an agent. |
network.dispute_opened | The customer reported a no-show after the shop marked that it arrived. The deposit is held until Doing Work decides. |
network.dispute_updated | The shop added its side of a disputed no-show. |
network.dispute_resolved | Doing Work decided a disputed no-show: refund_homeowner, release_to_shop or split. |
network.found_shop_added | Doing Work staff recorded a local shop for a request waiting for shops. Nobody is contacted. |
network.shops_sourced | Doing Work staff looked up local shops from public business listings for a waiting request. |
network.found_shop_updated | Doing Work staff changed a found shop: email, license check, or the call-by-a-person list. |
network.outreach_sent | The outreach job emailed found shops about requests waiting near them. |
network.outreach_site_checked | Doing Work read a found shop's own website (read-only, robots.txt honored) and recorded whether it has a public email, a plain contact form, or a skip reason. |
network.guest_quote_received | A shop not on Doing Work yet sent its own quote from an outreach link. The customer sees it as written. |
network.guest_quote_claimed | A shop that quoted from an outreach link set up its account and brought the job into its request inbox. |
network.outreach_opted_out | An address asked for no more outreach email. It is suppressed for good. |
network.outreach_paused | Outreach email paused itself because bounces or spam complaints crossed the safe line. It stays paused until staff clear it. |
visit.scheduled | A visit to a job was booked. |
calendar_feed.created | A calendar feed link (.ics) was made for a worker. A feed it replaced was turned off. |
calendar_feed.revoked | A calendar feed link was turned off. |
books.exported | A books export (ledger and QuickBooks Online import files) was made for a period. |
payroll.period_set | The shop's pay period changed (weekly, biweekly, semimonthly or monthly). |
stock.changed | A tracked material's count on hand changed (counted, received, used, returned, lost or adjusted). When the change takes it to or below its low point, stock.low is sent instead. |
stock.low | A tracked material's count on hand fell to or below its low point (sent once per crossing; it goes again only after the count rises above the low point). |
service_due.created | A customer's next service due date was recorded. |
service_due.changed | An open service due date's title, date or repeat changed; reminder_reset is true when a moved date re-arms the reminder email. |
service_due.completed | A service due date was marked done; next_id is the next one when it repeats. |
service_due.cancelled | A service due date was cancelled; no reminder goes out for it. |
service_due.reminded | The "service is due" reminder email was queued for the customer. |
shop.service_due_emails_changed | The shop turned "service is due" reminder emails on or off or changed the lead days. |
visit.priority_set | A visit's priority changed (normal, urgent or emergency). Urgent and emergency visits can use dispatch.suggest. |
visit.updated | A visit moved or its details changed. |
route.location_set | The map point for a job's address was saved (by an agent or typed in). |
route.start_set | A worker's start point, or the shop yard (person_id null), was saved. |
vendor.saved | A supplier was added or changed. |
po.created | A purchase order was started (draft). Nothing is job cost until it is received. |
po.updated | A draft purchase order changed. |
po.ordered | A purchase order was marked as sent to the supplier. |
po.received | Parts on a purchase order arrived and were added to the job as materials. |
po.receipt_undone | A received material from a purchase order was taken back. |
po.cancelled | A purchase order was cancelled. |
po.billed | The supplier's bill was recorded on a purchase order (not job cost). |
route.applied | A planned route was written back with routes.apply. Each moved visit also sends visit.updated. |
visit.assigned | The workers on a visit changed. |
visit.cancelled | A visit was cancelled. |
visit.started | A worker started a visit. |
visit.done | A visit was marked done. |
visit.series_created | A repeating set of visits was booked. |
availability.changed | A worker's weekly hours or time off changed. |
visit.on_the_way | A worker is on the way to a visit, with an ETA when given. |
visit.arrived | A worker arrived at a visit. |
visit.notice_queued | A customer notice for a visit (appointment reminder, on the way, or arrived) was handed to text, email, or both. |
schedule.hours_changed | The shop's booking hours changed. |
schedule.booking_page_changed | The shop updated its public booking page or Google booking profile. |
schedule.open_slots_changed | The shop added or removed times its voice agent may book. |
visit.recording_started | Retired Nov 3, 2026: no longer emitted. |
visit.recording_finished | Retired Nov 3, 2026: no longer emitted. |
visit.recording_added | A worker's walkthrough recording was added to a visit; its transcript is a voice memo note. |
visit.recap_drafted | A recap email for the customer was drafted after a visit. Not sent until the worker approves it. |
visit.recap_edited | The words of a visit recap draft changed. |
visit.recap_approved | The worker approved a visit recap and it was queued to the customer by email. |
visit.steps_changed | The shop changed its guided visit steps, or went back to the defaults. |
visit.step_marked | A guided visit step was marked done, skipped, or open again. |
quote.draft_started | The agent drafted quote lines from a visit. Each line waits on the worker's approval. |
quote.draft_line_decided | The worker approved or rejected one drafted quote line. |
agent.correction_recorded | A worker edited, rejected or flagged something the agent drafted; the shop keeps the correction for the next draft. |
request.lead_settings_changed | The shop's lead rules changed (auto first reply, after hours, flag and skip types). |
schedule.settings_changed | The shop's scheduling rules changed (arrival window, buffer, reminders, on the way notices, arrival notices, time zone). |
invoice.pay_link_ready_queued | One email was queued telling the customer an invoice can be paid again after its pay link waited on the shop's payments account. |
signature.copy_queued | One email was queued giving a signer their own copy of what they signed (a document, a quote or a subcontractor list). |
card.resave_queued | One email was queued asking a customer to save their card again after the shop's payments account changed. |
invoice.reminder_queued | A friendly reminder was queued for an invoice still unpaid a day after it was sent. |
shop.invoice_reminders_changed | The owner turned the automatic unpaid-invoice reminder on or off for the shop. |
invoice.reminder_changed | The automatic unpaid reminder was turned on or off for one invoice. |
request_form.created | A shop turned on or renewed its public request form. |
webhook_endpoint.created | A webhook endpoint was added. |
webhook_endpoint.deleted | A webhook endpoint was removed. |
webhook_delivery.retried | An owner or office worker queued a failed webhook delivery to send again. |
webhook_endpoint.creator_left | The worker who added a webhook endpoint left the shop. The endpoint keeps running; the owner can keep it or remove it. |
agent_key.created | The owner made a named agent key for the shop. |
agent_key.revoked | The owner revoked a named agent key. It stops working at once. |
platform.created | A developer platform account was created. |
Free field service software pricing | Doing Work
Free field service software pricing
Current as of November 2026.
Doing Work is free field service software. Free up to $1,000 a month in payments, no monthly fee ever, then 0.5% up to $149 a month. The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month.
- No plans, no monthly fee and no card to enter. Every shop gets every feature, with unlimited workers, jobs, customers, quotes and invoices.
- Doing Work takes a fee out of each payment: The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month. The shop only pays when it gets paid, and deposits count.
- A payment that crosses $1,000 is only charged on the part above $1,000. Once fees in the month hit $149, later payments that month are charged 0%.
- Locations under one owner count their payments together. The month starts over on the 1st.
- Fees come out of the shop's customer payments before payout. On the 1st each shop gets a fee statement and how far it is from the $149 cap.
- A refund returns our fee on the refunded part at the rate that payment was charged. Jobs paid outside Doing Work are unlimited and cost nothing.
- Nothing is metered. The payment fee is the only thing Doing Work charges. Storage, email and every Doing Work feature are included.
- Calls and texts run on the shop's own Twilio account, so Twilio bills the shop directly for them. A voice AI that answers the shop's calls is the shop's own ElevenLabs or Grok agent, billed by that provider.
- Requests and quotes are free for shops and customers. We will never charge lead or referral fees.
- Customers can pay by card or bank. Card and bank processing is charged separately by Stripe at its standard rates: https://stripe.com/pricing.
- Cost at your volume: $1,000 in payments a month costs nothing, $3,000 costs $10, $5,000 costs $20, $15,000 costs $70, $20,000 costs $95, $30,800 costs $149, and $160,000 costs $149. See https://doingwork.work/docs/pricing/.
- A shop can try Doing Work on a few real jobs before switching over. With no monthly fee, it pays only the fee on payments taken through Doing Work.
Cost at your volume
The Doing Work fee for one calendar month, from the bands above. Locations under one owner count together.
| Payments received in the month | Doing Work fee | Share of payments |
|---|---|---|
| $1,000 | $0.00 | 0.00% |
| $3,000 | $10.00 | 0.33% |
| $5,000 | $20.00 | 0.40% |
| $15,000 | $70.00 | 0.47% |
| $20,000 | $95.00 | 0.48% |
| $30,800 | $149.00 | 0.48% |
| $160,000 | $149.00 | 0.09% |
Card and bank processing is charged separately by Stripe at its standard rates. See stripe.com/pricing.
Use fees.preview to show a shop the fee on a given payment.
For everything a shop pays in a month, including Stripe, phone and texting and the agent, see Total cost. To see Doing Work next to other software, see Compare. Run the shop from the AI you already use: Run your shop from ChatGPT, Claude, or the AI you already use.
Questions
Does Doing Work have a monthly fee?
No. Doing Work is free to use. The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month.
Is there free field service software?
Yes. Doing Work is free field service software for trade shops. Free up to $1,000 a month in payments, no monthly fee ever, then 0.5% up to $149 a month. Stripe's processing is separate. Jobs paid outside Doing Work cost nothing.
Is Doing Work free?
Yes. Doing Work is free field service software for trade shops. Free up to $1,000 a month in payments, no monthly fee ever, then 0.5% up to $149 a month. There is no per-user fee. Workers are unlimited.
What does Doing Work cost after the free $1,000?
Above the free $1,000 we take 0.5%, up to $149 in a month. A shop paid $3,000 in a month pays $10. A shop paid $15,000 pays $70. At $30,800 the fee is $149.00, and it stays $149.00 above that. Stripe's processing is separate.
Is there a Jobber alternative with no monthly fee?
Yes. Doing Work is a free Jobber alternative with no monthly fee. Free up to $1,000 a month in payments, no monthly fee ever, then 0.5% up to $149 a month. Jobber bills by plan and user count, from $29 a month for 1 seat, read November 1, 2026 on getjobber.com/pricing. Jobber has a mobile app and years of public reviews. Doing Work launched in 2026 and has no public reviews yet.
What does Doing Work cost at $40,000 a month?
At $40,000 of payments in a month the Doing Work fee is $149.00 (the monthly cap). Stripe processing is separate.
Is anything metered?
No. Nothing is metered. Storage, email and every feature are included. The payment fee is the only thing Doing Work charges.
Is there a per-worker price?
No. Workers, jobs, customers, quotes and invoices are unlimited for every shop.
What happens in a month with no payments?
It costs nothing. Payments recorded as paid outside Doing Work carry no Doing Work fee.
Does Doing Work charge for leads?
No. Doing Work never charges lead or referral fees.
Free field service software vs Jobber, Housecall Pro, and ServiceTitan | Doing Work
Free field service software, compared
Free field service software for trade shops. No monthly fee. The full price is on Pricing.
What an agent can check for itself, read on November 1, 2026. Follow the links, since other companies change their plans and prices.
| Agent access | Pricing model | Fit by shop size | |
|---|---|---|---|
| Doing Work | Every operation over REST, MCP and A2A with OAuth 2.1: jobs, schedule, quotes, invoices, payments, phone and sync. See the API reference. | No plans or monthly fee. first $1,000 free each month, then 0.5% up to $149. Plus Stripe processing. Pricing. | Any size. Workers are unlimited. |
| Jobber | An official connector for Claude and ChatGPT reads clients, requests, quotes, jobs and invoices, and can create requests, clients, properties and quotes. It can't create jobs or invoices or change the schedule (Jobber help). A GraphQL API for apps (developer.getjobber.com). | Monthly plans by tier and user count, plus payment processing (getjobber.com/pricing). | Solo shops to mid-size teams. |
| Housecall Pro | A public API on the MAX plan only (Housecall Pro help). No official MCP server found. | Monthly plans by tier and user count, plus payment processing (housecallpro.com/pricing). | Solo shops to mid-size teams. |
| ServiceTitan | APIs through its partner program. | No public prices. Quoted per technician, with setup fees and multi-year contracts reported by third parties (servicetitan.com/pricing). | Larger shops. Third-party reviews say it isn't built for 3 technicians or fewer. |
Plain answers
Checked against what Doing Work does today.
| Question | Answer |
|---|---|
| Job costing | Yes. Each job shows labor from approved and pending time at each worker's cost rate, materials at cost, expenses and Doing Work fees, against the contract, invoiced and collected amounts, with profit and margin. |
| Timesheets | Yes. Workers clock in and out for job, drive, shop and break time. The owner or office approves it, and each worker can have a labor cost rate. |
| Payroll | Hours yes, payroll no. Doing Work gives approved hours per worker for each pay period, by day and by work, drive, shop and break time, and as a CSV for a payroll service. It doesn't run payroll, pay wages or handle payroll tax. |
| Dispatch: overlapping appointments | Yes. Booking or moving a visit returns any overlap, time off or outside hours conflict for its workers as a warning. |
| Dispatch: reassigning a visit | Yes. Change who is going on a visit at any time, and find open times that fit workers' hours and time off. |
| Dispatch: emergency calls | Yes. A visit can be marked normal, urgent or emergency. For an urgent or emergency visit, Doing Work suggests who could go, ranked by who is free right then and who has the fewest visits that day. Your agent or the office then assigns the worker. Doing Work doesn't assign on its own. |
| Parts used on a job | Yes. Parts used on each job are recorded at cost and price, from the price book. |
| Inventory and stock levels | Yes, counts on hand. Track any price book material with a low point. Workers record what they use, receive, return or lose, every change keeps who and when, and a reorder list shows what is at or below its low point. Purchase orders are supported: draft one for a job, mark it ordered, receive the parts onto the job, and record the supplier's bill. There are no separate stock locations. Receiving is what adds the parts to job cost. |
| Maintenance plans | Yes. A plan bills the customer each term, and the next term's invoice is made automatically and sent if the shop turns that on. |
| Recurring billing | Yes, monthly, yearly or any term from 1 to 60 months, through a maintenance plan. An agent can draft the priced lines for a term. An agent only proposes that price; the owner or office confirms it with maintenance.confirmPrice, and an owner or office person sets the price immediately. Doing Work makes each term's invoice when the last one ends and sends it if the shop turns that on. If the customer saved a card and auto-pay is on, the card is charged on the invoice's due date through the shop's own Stripe account. The customer saves the card on a Stripe page, so Doing Work never sees the card number. These are invoices, not Stripe subscriptions, so every charge shows up with the shop's other invoices and payments. See maintenance.createPlan and customers.setAutopay. |
| Maintenance reminders | Yes, off until the owner turns them on. Record when a customer's next service is due, like a yearly furnace tune-up, and have it repeat. With service due emails on, the customer gets one reminder email before the date, 14 days by default. Email only, no texts. |
| Recurring visits | Yes. A repeating visit (daily, weekly or monthly) can be booked for a job, up to 104 visits at once. |
| Recurring maintenance routes | Your agent plans the order. It reads the day's stops from Doing Work, orders them with a maps tool you choose, and saves the new times and workers with routes.apply in one step. Doing Work itself doesn't optimize routes. See route planning below. |
| Google Calendar | Yes, one way. Each worker can get a private calendar feed link that Google Calendar, Apple Calendar or Outlook subscribes to. It shows their visits and is read only. A link can be turned off at any time. |
| Crew scheduling | Yes. A visit can have more than one worker, and finding a time can require all of them to be free at once. Save a named crew once with crews.save and book it by its crew_id on visits.create, visits.assign or schedule.findTime. |
| AI phone answering and booking | On now, once the shop connects its own Twilio account and its own voice agent. It uses the shop's own voice AI. Calls come in on the shop's Twilio number. Doing Work answers, tells the caller it's an AI assistant and that the call is transcribed, then connects the shop's ElevenLabs or Grok agent. If the owner turns on live booking, the shop's voice agent uses Doing Work's booking tools to put the caller straight onto a worker's calendar, for the work and ZIP codes the shop allows. It never makes up a price. It can say a fixed visit fee only if the shop sets one. Emergency calls follow the shop's own settings: transfer to the on-call worker, a text to them, or booking into emergency times the shop opened ahead. Quote follow-up emails and unpaid invoice reminder emails already run by email without that Twilio and voice setup. Autopay charges a saved card only when the shop turns it on for that customer, and that does not need Twilio either. See Phone setup. |
| Flat rate price book | Yes. A task has one price, an optional task code, a member price for customers on an active maintenance plan, an estimated time and the parts it uses. Your agent builds quote lines from tasks. Jobber and Housecall Pro price books import from CSV. See Flat rate price book. |
| QuickBooks | Your agent syncs with QuickBooks on the schedule you pick. Doing Work has no QuickBooks connection of its own. If you import by hand, the owner or office can also get a month of books as one ZIP: a ledger CSV, QuickBooks Online import files and a README. See Export your books. |
| Importing from other software | Yes, from CSV files: customers, jobs with their visit history, open quotes, unpaid invoices, the price book, equipment, maintenance plans and payment history. Presets for Jobber and Housecall Pro. Importing the same file again skips or updates what already came over, so nothing doubles. Imported quotes and invoices are drafts and aren't sent. Maintenance plans come in as service due reminders, or as billed plans at prices the owner checks before anything is saved. Billed plans make no invoice until the next due date and don't send on their own. Payment history comes in as records only. It moves no money and doesn't count toward the fee. |
| Visit brief | Yes. Before a visit the agent reads a one page brief: the customer, the address, the request, recent texts and calls, notes, photo summaries with measurements, open tasks and similar past quotes. On the visit. |
| Guided visits | Yes. The agent walks the worker through the shop's visit steps in conversation, and the shop can edit the steps. Any step can be skipped. There are no buttons to tap and no app to open. |
| Walkthrough recordings | Yes. The worker sends the agent a recording during or after the visit, and the transcript is saved as a note on the visit. Doing Work keeps no audio and does not check recording consent; the shop is responsible for any consent the law requires, under the Terms. |
| Customer recap email | Yes. The agent drafts the recap after a visit from what the worker said. It goes to the customer only after the worker tells the agent to send it. |
| Drafting quotes | Yes. An agent you connect can draft quote lines, including prices, from what the shop tells you, its price book, or past signed quotes. A person whose role may send it sends it. See Who sends what. |
| Learning from corrections | Yes. When a worker changes or rejects a draft, the agent saves what changed and why, and the next drafts for the shop follow it. Lessons are shared across the shop without names. |
| Instant reply to new leads | Yes, if the shop turns it on. Doing Work sends one first reply within a minute: a text where the customer agreed to texts and the shop's own number is approved for business texting, otherwise an email. A lead from Angi, Angie's List, HomeAdvisor or Modernize gets one first text when the shop's own approved number is connected, and later texts need the customer to reply first. Leads from Thumbtack, Networx, Google and Yelp get an email. After hours the shop can offer the first open time or hold the lead for the morning. |
| Owner morning email | Yes. At 7 AM shop time on days with something to show: jobs under the margin floor, open items, the quote queue and leads held overnight. |
| Win back past customers | Yes. The agent lists customers with no visit in a while and can send each one a service due email. |
How your agent covers what Doing Work leaves out
QuickBooks. Your agent syncs with QuickBooks on the schedule you pick. It uses your own QuickBooks connection, and you tell it which accounts and items to post to. Doing Work gives it what it needs: a feed of every invoice, payment, refund and customer change, a place to store each record's QuickBooks id so nothing posts twice, and a breakdown of every payout into payments, processor fees and the Doing Work fee so deposits match your bank. The same feed works for another accounting tool if your agent can connect to it. Doing Work has no QuickBooks connection of its own to set up. The ZIP export is only the fallback: if you import by hand, the owner or office can get a month of books as one ZIP. See Export your books.
Google Calendar. Each worker can subscribe to their own calendar feed link, with no agent needed. If you want visits on a shared calendar instead, your agent can copy them with its own calendar connection. Doing Work gives it each visit as a calendar event with a steady id, so moving a visit updates the same event.
Route planning. Doing Work gives each worker's day as a route: stops in time order with addresses, map links and one driving directions link. To get a better order, your agent reads the day's stops with routes.day, orders them with a maps tool you choose, then saves the new times and workers with routes.apply in one step. If a visit can't move or two visits would overlap, nothing changes and your agent sees why. Doing Work itself doesn't optimize routes. It sends customers an on-my-way notice with the ETA.
Payroll. Doing Work keeps the time and totals it for each pay period: approved hours per worker by day, with anything still waiting for approval listed. It also gives a CSV your payroll service can take. Your agent can carry those hours to Gusto, ADP or QuickBooks Payroll using your own account. Doing Work doesn't run payroll or hold wages.
Why the agent route. Agents like Muse, Grok Bot, Dots and Duet can connect to many other apps and services. That makes your agent work like a new operating system for your shop: it uses many apps together, the way your shop needs. Doing Work is one part of that, the part that keeps your customers, jobs, quotes, invoices and payments. So your shop isn't limited to what Doing Work builds itself. Accounting, maps and routes, calendars, payroll and phone answering can each be an app or service you choose, and your agent ties them to your Doing Work records. Your agent already has your business context, and Doing Work tells it when records change.
Step by step: Agent guides for QuickBooks, Google Calendar, route planning, payroll and financing.
The office day, crews and profit
Most office work goes through the agent, and a few web pages cover what a person wants to see at a glance.
- Today page: the shop's day on one page: visits today by worker, visits that need a worker, new requests, quotes waiting and overdue invoices. See Web screens.
- Saved crews: name a crew once and book it together. Finding a time checks that every worker on it is free. See crews.save.
- Moving work between workers: your agent reassigns a visit with visits.assign and saves a new stop order for a day in one step with routes.apply. If you would rather see it, the day board shows one day as a column for each worker. Drag a visit to another worker or time and it saves. For the owner and office. See Web screens.
- Profit alerts: the owner sets a margin floor with costs.setMarginAlert. When an invoiced job's margin drops under it, the job.margin_low event fires once for that job, so your agent can tell you.
- Phone app and location: there is no app to install. Owners, office and workers use Doing Work through their agent and through web pages that open in any phone browser. Doing Work doesn't track where workers or trucks are. Photos keep their location on the shop's own copies only.
Who sends what
The owner can always send quotes, invoices and visit recaps. Office can send them for any job, a lead for jobs on their crew, and field for jobs assigned to them, until the owner turns that send off for that role. Quote or invoice lines an agent drafted stay unsent until a person whose role may send them sends them. An agent token cannot send those lines. A draft a person wrote follows the same role and job checks, and an agent token can send it when the role allows. Visit recaps follow the recap permission.
How prices get on a quote
An agent you connect can draft quote lines, including prices, from what the shop tells you or its price book. A person whose role may send it sends it. See Who sends what. Prices come from the shop:
- Price book: flat rate tasks with the shop's prices, and member prices for customers on a maintenance plan. quotes.linesFromTasks turns the tasks a worker picks into quote lines. See Flat rate price book.
- Quote templates: lines the shop saved for common jobs, like a furnace tune up or a water heater swap. templates.list gives the lines, and the shop changes what it needs.
- Fixed call fees: if the shop sets a fixed fee for a type of work, like an $89 diagnostic visit, the voice agent says exactly that fee on calls. Without one it gives no price.
- What the shop tells you: a price the owner, office or worker gives you, written as they say it.
Total cost
Every cost line for Doing Work and the other software, with sources and a worked example: Total cost.
One by one
Jobber, Housecall Pro, ServiceTitan, Workiz, FieldEdge. Roundups: software that works with your own AI agent, software with no monthly fee, Free field service software, Free Jobber and Housecall Pro alternatives. The workflows are on Free features. Run the shop from the AI you already use: Run your shop from ChatGPT, Claude, or the AI you already use.
Switching from other software
Step by step guides for Jobber, Housecall Pro, ServiceTitan, Workiz and FieldEdge: Switching to Doing Work.
Equipment and maintenance plans
Doing Work tracks equipment at each property (equipment.add, equipment.list), runs maintenance plans that bill on a schedule (maintenance.createPlan) and keeps service due reminders (services.addDue). Equipment, maintenance plans (as service due reminders or billed plans) and payment history (as records only) import from CSV files. See Switching.
Where Doing Work is not a fit yet
- The calendar feed is one way. Changes made in Google Calendar don't move visits in Doing Work.
- Route optimization comes from your agent and a maps tool you choose. Doing Work lists the day's stops in time order, and your agent applies its new order with routes.apply in one step. Doing Work itself doesn't optimize.
- Doing Work doesn't offer or process customer financing. The shop can add links to up to 3 financing companies it works with, and they show on quotes. A job paid through a financing company is recorded as paid outside Doing Work.
- Stock is a count per material. There are no separate stock locations. Purchase orders are supported: draft, mark ordered, receive onto the job, and record the supplier's bill.
- Imports come from CSV files. Billed maintenance plans import with sending off until the shop turns it on.
- Service due reminders are email only. No reminder texts.
- QuickBooks syncs through your agent, so you choose how it posts. See Sync with QuickBooks.
- Calls and texts need the shop's own Twilio account, and an AI that answers calls is the shop's own ElevenLabs or Grok agent. Both bill the shop directly. Quote follow-up emails and unpaid invoice reminder emails already run by email without that Twilio and voice setup. Autopay charges a saved card only when the shop turns it on for that customer, and that does not need Twilio either.
What Doing Work has that each one doesn't
From each company's public pages, read on November 1, 2026. This lists differences only. Each of them also has features Doing Work lacks, listed above under Where Doing Work is not a fit yet.
| Compared with | What Doing Work has |
|---|---|
| Jobber | An agent can create jobs and invoices and change the schedule. Jobber's connector for Claude and ChatGPT can't. No per-user price: Jobber plans are priced by user count, with $29 a month per extra user. No monthly fee. |
| Jobber Plus | Profit alerts are included for every shop, with no plan tier: the owner sets a margin floor and hears when an invoiced job drops under it. See The office day, crews and profit above. |
| Jobber Core and Connect | Quote follow-ups, invoice reminders and autopay are included for every shop, with no plan tier to move up to. See Runs on its own below. |
| Housecall Pro | The API and MCP server are open to every shop. Housecall Pro's API is on the MAX plan only. No per-user price: MAX includes 8 users, then $35 a month each. No monthly fee. |
| ServiceTitan | Published pricing and no contract. ServiceTitan quotes prices and third parties report setup fees and multi-year contracts. Every operation is open to an agent over REST, MCP and A2A. ServiceTitan's terms address AI agents by name; see Switching from ServiceTitan. |
| Workiz and FieldEdge | Published pricing. Both quote prices. Workiz puts maintenance plans, equipment and inventory on its Ultimate plan. |
Runs on its own
Doing Work runs these on its own schedule, whether or not an agent is working. Your agent does the thinking work when you want it: quotes, scheduling, answers. It is part of your setup the way your email and calendar are, and if you already use one, there is nothing new to buy.
- Unpaid invoice reminder email. On by default, starting 1 day after the invoice goes out.
- Quote follow-up email. On by default, 3 days after the quote goes out. The shop can change it from 0 (off) to 30 days.
- Review request email after a paid job. On by default once the shop adds its review link.
- Autopay on a customer's saved card. The shop turns it on for each customer.
- Maintenance plan renewals and service due reminder emails, for shops that use plans.
- Appointment reminders, once the shop turns them on. They go by email, and by text once the shop's texting is set up.
- Payment receipts and the monthly fee statement.
What lowers the risk of trying it
From the Terms and what Doing Work does today.
- No plans and no monthly fee. A month with no payments through Doing Work costs nothing.
- No Doing Work fee on payments taken outside it. Record them with invoices.markPaidOutside.
- At least 30 days' notice before a fee change.
- The owner can export the shop's data at any time with shops.export, and an export is offered at closing.
- You can stop using Doing Work at any time.
- Agent keys can be limited to read only or no money (keys.create).
- You can keep your current software running while you try a few real jobs.
Status and track record
Doing Work is new. It launched in 2026 and has no public reviews yet.
Try it on a few real jobs first
A shop can run a few real jobs through Doing Work before switching over. There's no monthly fee, so the trial costs only the fee on payments taken through Doing Work. The shop can keep its current software until it's sure.
Total monthly cost of running a shop on Doing Work
Total monthly cost
Current as of November 2026. Prices read on November 1, 2026 from the linked pages. Other companies change their prices, so check the links. This page gives a method, not an answer. Which option is cheaper depends on the shop.
Doing Work
| Item | Price | Source |
|---|---|---|
| Doing Work fee | first $1,000 free each month, then 0.5% up to $149. $5,000 a month costs $20.00, $20,000 costs $95.00, $30,800 costs $149.00, $160,000 costs $149.00. | Pricing |
| Card and bank processing | Stripe's standard rates: 2.9% + 30¢ for a domestic card, and 0.8% for a bank (ACH) payment, capped at $5. | stripe.com/pricing |
| An always-on agent | The agent you choose bills you directly. See its own pricing page. | Chat vs agent and each provider's pricing page |
| Phone number (Twilio) | $1.15 a month for a local number, $2.15 toll free. | twilio.com voice pricing |
| Calls (Twilio) | Local: $0.0085 a minute inbound, $0.0140 outbound. Toll free inbound $0.0220. Recording $0.0025 a minute. | twilio.com voice pricing |
| Texts (Twilio) | $0.0083 per SMS segment. MMS $0.022 out, $0.0165 in. Carrier fees of about $0.0035 to $0.005 per text, plus 10DLC registration fees. | twilio.com SMS pricing |
| Texting registration (10DLC) | With an EIN, a low volume standard brand: $4.50 once for the brand and $15 once to vet the campaign, then $1.50 a month for a low volume mixed campaign, or $10 a month for a standard campaign. Without an EIN, sole proprietor: $4.50 and $15 once, then $2 a month. | Twilio brand fees, Twilio registration types |
| AI that answers calls: ElevenLabs | Plans with included minutes: Starter $6 (75), Creator $22 (275), Pro $99 (1,238), Scale $299 (3,738), Business $990 (12,375). Extra minutes $0.08. The language model is billed separately. Twilio bills its minutes on top. | elevenlabs.io/pricing/agents |
| AI that answers calls: Grok | $0.08 a minute for realtime voice. Twilio bills its minutes on top. | docs.x.ai voice guide |
The Doing Work fee is the only charge from Doing Work. Twilio, texting and a voice agent are optional, and only if the shop sets them up. Quote follow-up emails and unpaid invoice reminder emails already run by email without that Twilio and voice setup. Autopay charges a saved card only when the shop turns it on for that customer, and that does not need Twilio either.
Other software
| Software | Plan price | Per user and add-ons | Payments | Source |
|---|---|---|---|---|
| Jobber | Billed monthly: Core $29 to $49 (1 user). Connect $139 (1 user) to $399 (15 users). Grow $199 to $499. Plus $499 to $699 (5 to 15 users), with AI Receptionist. Annual billing shows lower prices on the same page. | $29 a month per extra user. AI Receptionist $29 a month with 30 conversations, then $0.79 each (or pause at the limit), unlimited on Plus (Jobber help). Marketing $99, Pipeline $49. | Card 2.9% + 30¢, ACH 1%. | getjobber.com/pricing |
| Housecall Pro | Billed annually: Basic $59 (1 user), Essentials $149 (5 users), MAX $299 (8 users). | $35 a month per extra user on MAX. Service plans and the API are on MAX. | Card from 2.59%, bank 1%. | housecallpro.com/pricing |
| ServiceTitan | Quote only. | Quote only. | Quote only. | servicetitan.com/pricing |
| FieldEdge | Quote only. | Quote only. | Quote only. | fieldedge.com/pricing |
| Workiz | Quote only. Maintenance plans, equipment and inventory are on Ultimate. | Quote only. | Quote only. | workiz.com/pricing-plans |
Phone and texting estimate
An estimate, not a quote, from Twilio's US price pages read on November 2, 2026. Twilio bills the shop directly and Doing Work adds nothing. Change the numbers to match the shop. Say 750 minutes of inbound calls on a local number and 2,000 texts a month, registered as a low volume standard brand.
| Line | Estimate | How |
|---|---|---|
| Local number | $1.15 | Twilio leased local number. |
| 750 inbound minutes | $6.38 | 750 × $0.0085. |
| 2,000 texts | $16.60 | 2,000 × $0.0083 per segment. Long texts count as more than one segment. |
| Carrier fees on 2,000 texts | about $7 to $10 | $0.0035 to $0.005 per text, by carrier. |
| 10DLC campaign | $1.50 to $10 | Low volume mixed campaign $1.50, standard campaign $10. |
| Monthly total | about $32 to $44 | Plus $19.50 once for brand registration and campaign vetting. |
This estimate applies only if the shop uses its own Twilio number. An AI that answers those calls is billed on top by the shop's ElevenLabs or Grok plan. See Phone setup.
What else is included
There's no plan tier to move up to. Every shop gets the Today page, saved crews, profit alerts and emergency call options. See Compare for what Doing Work has and where it isn't a fit yet.
How to add it up
- Take the shop's payments in a normal month and read the Doing Work fee from the bands, or call fees.preview.
- Add the agent subscription the shop would use.
- Estimate a month of calls and texts. Multiply minutes and texts by the Twilio rates. If an AI answers calls, add its plan or per-minute cost.
- For the other software, pick the plan that covers the shop's user count and the features it uses, and add per-user and add-on charges. For quote-only software, get a quote.
- Compare processing too. A rate difference on card volume can be larger than any plan price.
- Add the cost of what each option lacks that the shop uses today: the time someone spends covering it, or the separate tool that fills it. See Compare.
- Count office time. If an agent takes over calls, scheduling or billing follow-up, estimate the hours saved. If the office has to check the agent's work or cover gaps, count those hours too.
Worked example
An example to show the method, with assumed numbers. Change them to match the shop. An HVAC shop with 8 people takes $160,000 a month in payments and gets about 600 minutes of inbound calls and sends about 1,000 texts a month.
| Line | Doing Work | Source of the number |
|---|---|---|
| Doing Work fee on $160,000 | $149.00 | From the Pricing page (monthly cap). Check with fees.preview. |
| Agent | $30 to $200 | Depends on the agent and plan. Each agent's pricing page is linked on Chat vs agent. |
| Phone number | $1.15 | Twilio local number. |
| 600 inbound minutes | $5.10 | 600 × $0.0085. |
| 1,000 texts | about $12.30 to $13.30 | 1,000 × $0.0083 plus carrier fees. 10DLC fees extra. |
| AI answering 600 minutes | $48 (Grok) or $99 (ElevenLabs Pro, model use extra) | Rates above. |
For the same shop on other software, add the plan for 8 users, any extra users and add-ons, and the processing rate. If Jobber's AI Receptionist answers about 300 conversations a month on a plan below Plus, that is $29 plus 270 × $0.79, or $242.30. Then add step 6 and step 7 for each option. Processing is charged in every option and differs by rate, so compare it on the shop's own card and bank mix.
Doing Work for a one-person shop
For a one-person shop
An example with assumed numbers. Change them to match your shop. A solo shop takes $15,000 a month: 30 card payments of $400 and 5 bank (ACH) payments of $600.
| Software | Card | Bank (ACH) | Agent | Total | |
|---|---|---|---|---|---|
| Jobber Core, billed monthly | $29 | $357 | $30 | none | $416 |
| Jobber Connect, billed monthly | $139 | $357 | $30 | none | $526 |
| Doing Work | $70 fee | $357 | $24 | your choice | $451 plus any agent |
Jobber figures are from our Total cost page, read on November 1, 2026: plan prices and card 2.9% + 30¢, ACH 1%. Jobber shows lower prices for annual billing. Check getjobber.com/pricing. Doing Work's card rate is Stripe's 2.9% + 30¢, and bank payments are 0.8% capped at $5 (stripe.com/pricing). The $70 fee is nothing on the first $1,000 and 0.5% of the other $14,000 (Pricing).
Your agent
Your agent runs Doing Work the way it runs your email and calendar. If you already use one, there is nothing new to buy. If you pick one for this, its pricing page is linked on Chat vs agent.
Runs on its own
Doing Work runs these on its own schedule, whether or not an agent is working. Your agent does the thinking work when you want it: quotes, scheduling, answers. It is part of your setup the way your email and calendar are, and if you already use one, there is nothing new to buy.
- Unpaid invoice reminder email. On by default, starting 1 day after the invoice goes out.
- Quote follow-up email. On by default, 3 days after the quote goes out. The shop can change it from 0 (off) to 30 days.
- Review request email after a paid job. On by default once the shop adds its review link.
- Autopay on a customer's saved card. The shop turns it on for each customer.
- Maintenance plan renewals and service due reminder emails, for shops that use plans.
- Appointment reminders, once the shop turns them on. They go by email, and by text once the shop's texting is set up.
- Payment receipts and the monthly fee statement.
No contract
- No plans, no monthly fee and nothing paid up front.
- A month with no payments through Doing Work costs $0.
- You can stop at any time and export your data with shops.export.
Web screens
Most day to day work happens through your agent. These web pages are there for the steps a person does. Each opens from a link your agent or Doing Work sends.
For the owner
- Start: create your shop.
- Sign in: a sign-in link by email, no password.
- Connect payments: set up your Stripe account to take card and bank payments. Ask your agent for your payments link. It opens a page with one button that takes you to Stripe, where you finish the setup yourself. If you get stuck, write to contact@doingwork.work and we will help you connect.
- Today: the shop's day on one page: visits today, visits that need a worker, new requests, quotes waiting and overdue invoices. For the owner and office.
- Day board: one day as a column for each worker and a time grid. Drag a visit to another worker or time and it saves. For the owner and office. Your agent can make the same moves in chat.
- Prices: the shop's price book in a table, with how old each price is and its history. For the owner and office.
- Brand: set your logo, accent color, license number and footer for quotes, invoices and customer emails, and choose whether they say Sent with Doing Work.
- Photos for a job: add photos to a job from your phone.
- Export: download your shop's data.
- Shop terms: read and accept Doing Work's terms.
- Transfer or close: hand the shop to a new owner, or close it with an export first.
For workers
- Invite: accept an invite to join the shop.
- Calendar: a private calendar feed of their own visits.
For customers
- Quote: read, sign and pay a deposit. The customer opens the link from the email or text and signs. They do not need a Doing Work account.
- Invoice: read and pay by card or bank.
- Customer hub: see their visits, ask to move one and request new work. The hub asks the customer to sign in with an email the shop already has.
- Request: ask the shop for work.
Also through the agent
These run from the agent. They are not separate apps to install.
- Purchase orders: draft one for parts on a job, mark it ordered, receive the parts onto the job, and record the supplier's bill. Receiving is what adds the parts to job cost. There are no separate stock locations.
- Tips: off until the owner turns them on with shops.setTips. When on, the pay page shows tips only on invoices of $50 or more. A tip is paid with the invoice and is not part of the invoice total.
- Timesheets: workers clock in and out for job, drive, shop and break time. The owner or office approves the time.
- Who can send: there is no screen for who may send quotes, invoices or visit recaps. The owner reads it with shops.sendPermissions and changes it with shops.setSendPermissions. Those are API and MCP only. The owner can always send quotes, invoices and visit recaps. Office can send them for any job, a lead for jobs on their crew, and field for jobs assigned to them, until the owner turns that send off for that role. Quote or invoice lines an agent drafted stay unsent until a person whose role may send them sends them. An agent token cannot send those lines. A draft a person wrote follows the same role and job checks, and an agent token can send it when the role allows. Visit recaps follow the recap permission.
Phone setup: Twilio with ElevenLabs or Grok
Phone setup
Phone answering is available for every shop, and it is optional. Calls and texts run on the shop's own Twilio account. An AI that answers calls is the shop's own ElevenLabs or Grok voice agent. Each bills the shop directly. Doing Work adds no charge for calls or texts. Outbound AI calls to a customer are on. The owner turns them on for that shop with phone.setOutboundAi, and every call starts with the shop's registered legal name. A call is an appointment reminder, an on-my-way update, or a job status. It is not a sales call and not a payment call. The customer has to have agreed to AI calls themselves within the last 12 months, and a number on the shop's stop list is not called. Quote follow-up emails and unpaid invoice reminder emails already run by email without that Twilio and voice setup. Autopay charges a saved card only when the shop turns it on for that customer, and that does not need Twilio either.
Your shop's AI answers every call that comes in to your number, wherever the caller is. Outbound AI calls never go to a Washington phone number or to a customer at a Washington property. Area codes 206, 253, 360, 425, 509 and 564 are refused, and so is a job whose property is in Washington.
What the owner does
- Create a Twilio account at twilio.com and upgrade it from the free trial. Twilio asks for a card and checks a phone number.
- Buy a local number in Twilio, or port the shop's current number. A port needs the owner to sign a letter of authorization.
- Register for texting. Carriers block business texts from unregistered numbers. A shop with an EIN registers as a low-volume standard brand. A shop without an EIN can register as a sole proprietor, which sends a code to the owner's phone. A toll-free number with Twilio's toll-free verification also works, and Doing Work reads that verification too.
- If you want an AI to answer calls, open an ElevenLabs or Grok account.
What the agent does
- Connect Twilio with phone.connectTwilio. Use a restricted API key. The Auth Token is only used to check that requests really come from Twilio.
- Pick the number with phone.twilioNumbers and phone.useNumber. This sets the number's Twilio settings. Don't change them by hand.
- Choose where calls go with phone.setRoute: forward to a phone, take a voicemail that arrives by email, or answer with the voice AI.
- For the voice AI, connect the shop's ElevenLabs or Grok agent with phone.setVoiceAi. If the owner turns on booking, see Phone booking into your calendar below.
- Track texting registration with phone.registrationStatus. Until it is approved, texts to customers go by email instead. Calls work the whole time.
- Send a test text with phone.sendText and call the number to check it rings.
Texting rules
A customer who texts STOP gets no more texts until they text START. HELP gets a reply that says how to reach the shop.
Texting registration
- With an EIN: low-volume standard brand. About $4 to $4.50 for the brand and $15 to vet the campaign, once, then $1.50 to $10 a month for the campaign (Twilio).
- Without an EIN: sole proprietor. About $4 to $4.50 for the brand and $15 for the campaign, once, then $2 a month (Twilio). Limits: one campaign, one number, and about 1,000 text segments a day to T-Mobile customers (Twilio).
- Toll-free number: submit toll-free verification in Twilio instead of 10DLC. Once Twilio approves it, phone.registrationStatus says approved and texts go out (Twilio).
- Opt-in description: in the campaign, say customers agree to texts on the shop's Doing Work page, and link the shop's Doing Work consent page, which shows the consent wording.
- Opt-out: keep Twilio's own opt-out handling on (Advanced Opt-Out on the Messaging Service). Doing Work also keeps its own stop list.
- After approval: Doing Work checks the registration again once a day. If Twilio suspends or fails it, texts go by email until it is fixed. If Twilio rejects a reminder text or reports it undelivered, for a reason other than STOP, the reminder goes by email instead.
Turning it off
phone.disconnect stops Doing Work handling the number and puts back the settings it had before.
Phone booking into your calendar
The shop's own ElevenLabs or Grok voice agent can book callers straight onto a worker's calendar through Doing Work's booking tools. It is off until the owner turns it on. It also handles automated AI availability callers (such as Google's Ask for me or Ask Maps assistant) with open hours, covered ZIP codes, any configured job-type fixed fee, and upcoming open windows without requiring a street address upfront. For online requests from Google Maps and Search, turn on a hosted /p/book/<slug> link with schedule.setBookingPage; see online booking and Google Business Profile.
- List the work the agent may book, how long each takes, and which workers do it.
- Add the ZIP codes you serve.
- Turn on live booking with phone.setVoiceAi.
What the voice agent does:
- Offers up to three times, one per day, at least 2 hours out, never same day after 3 PM, never more than 2 weeks out. You can change these.
- Books the worker with the lightest day and texts the customer a confirmation once your texting is set up.
- Never makes up a price. If you set a fixed fee for a type of work, like a $89 visit fee, it says that fee exactly and nothing else. Without one it gives no price. The worker prices the job on site.
- Work that needs a deposit goes to your office as a request with the time the customer picked, and you send the deposit link.
- Never puts an emergency into a routine time. Gas, carbon monoxide, no heat, sparks, smoke, fire, flooding or a burst pipe goes to your on-call phone or becomes an emergency request, unless you set up emergency calls below. For a gas smell, the agent tells the caller to leave and call the gas company or 911 from outside.
- Two callers can't book the same time, even if they call at once.
Emergency calls
Off until the owner turns it on. You decide what counts as an emergency and what happens next.
- Your words. List the words that mean an emergency for your shop, like "no heat" or "water heater leaking". Doing Work suggests some, but none are on until you pick them. Gas, carbon monoxide, smoke and fire are always treated as emergencies.
- Transfer. The call goes straight to your on-call worker's phone. It must be a different number from the shop line. If the transfer fails or nobody answers, the on-call worker gets a text instead.
- Text alert. The on-call worker gets one text per call with what the caller said and a link to call them back.
- Emergency times. Open emergency times ahead, like tonight 6 PM to 10 PM. The agent books only into those, and tells the caller only the booked window. It never promises a sooner arrival.
Example: a no heat call
It's 9 PM in January. A customer calls the shop line and says the furnace quit and the house is getting cold. The shop listed "no heat" as an emergency word.
- With transfer on: the call goes straight to the on-call worker's phone. If nobody picks up, the worker gets a text instead.
- With text alerts on: the on-call worker gets one text with a short summary of the call and the caller's number to call back.
- With emergency times open: the voice agent books the caller into tonight's 6 PM to 10 PM emergency time and says only that window. It doesn't promise a sooner arrival. The office also gets an emergency request.
- With nothing set up: the voice agent never books a no heat call into a routine time. It goes to the on-call phone or becomes an emergency request the office sees first thing.
Typical cost
Rates read on November 1, 2026. Check the links.
| Item | Price |
|---|---|
| Twilio local number | $1.15 a month (Twilio) |
| Twilio calls | $0.0085 a minute inbound, $0.0140 outbound, local |
| Twilio texts | $0.0083 per segment plus carrier fees of about $0.0035 to $0.005 (Twilio) |
| Texting registration, sole proprietor | About $4 to $4.50 and $15 once, then $2 a month (Twilio) |
| Texting registration, with an EIN | About $4 to $4.50 and $15 once, then $1.50 to $10 a month (Twilio) |
| ElevenLabs agent | Plans from $6 a month with included minutes, then $0.08 a minute. Model use billed separately (ElevenLabs) |
| Grok voice | $0.08 a minute (xAI) |
Example: 600 inbound minutes and 1,000 texts a month cost about $18 to $20 in Twilio charges ($1.15 for the number, $5.10 for minutes and $11.80 to $13.30 for texts, plus registration fees), plus $48 for Grok to answer all 600 minutes. See Total cost.
Switching from Jobber to Doing Work
Switching from Jobber
Read on November 1, 2026. Jobber changes its screens, so follow the source links if yours look different.
1. Export your data from Jobber
- Click Clients in the side menu.
- Click More Actions in the top right, then Export Clients.
- Choose CSV and click Export. Jobber emails you the file.
Only Jobber admins can export clients, and client export is on select Jobber plans. Each CSV holds up to 1,500 rows, so a bigger list arrives as several files. Import each file once. Source: Jobber help, Export Client Information.
Doing Work has a Jobber preset that reads Jobber's client columns, including the property and billing address. Only one phone number per customer is kept.
For history, export your jobs, quotes, invoices, and products and services from Jobber as CSV files too, if your plan lets you. Jobs, quotes and invoices come from Insights, then Reports. Set the date range to All time, click Export to CSV and choose All columns. Jobber emails each file to you. The Jobber preset reads Jobber's column names for each.
Maintenance agreements. Jobber keeps these as recurring jobs. Go to Insights, then Reports, and under Work reports open Recurring jobs. Set Started date to All time, click Export to CSV and choose All columns. Source: Jobber help, Recurring jobs report. Import that file as maintenance plans with the Jobber preset. It reads the job number, title, visit frequency, billing frequency, schedule dates and line items.
Equipment. Jobber has no equipment list to export. If you keep equipment in client custom fields, like a furnace model or an AC serial number, they come out as columns in the Export Clients file. Import that same file as equipment and map each custom field column to the equipment field it holds. Equipment kept only in notes stays in the customer's notes.
Agent access and terms at Jobber
Jobber's terms mention robots, scraping and data mining. Terms: getjobber.com/terms-of-service. Clients and invoices export to CSV, and Jobber has a public API (developer.getjobber.com).
The API on your own account: a shop owner can make a free Jobber Developer Center account, create a private app for their own Jobber account, and authorize it as the account admin. An app that isn't published can connect to up to 5 Jobber accounts and doesn't need Jobber's App Review. Your agent can then read through the API. Jobber's docs also say custom integrations are only possible for specific, approved Jobber customers and developers, so this may not be open to every account. Sources: Custom integrations, App authorization, App review.
General tips and a paste-in prompt: Let your agent do the export.
2. What the import brings over
- Customers: name (or first and last name), company, email, one phone number, tags, notes, lead source, billing address and one US service address.
- Jobs with their visit history: past and upcoming visits, with dates, titles and notes.
- Open quotes, with their lines. They come in as drafts and aren't sent.
- Unpaid invoices, as the balance still owed. They come in as drafts and aren't sent. Paid invoices are skipped.
- The price book: items, descriptions and prices.
- Each record is matched to its customer by the old software's id, then email, then phone.
- Up to 5,000 rows and 5 MB per file. Bigger lists go in several files.
- Equipment at each property: kind, make, model, serial number, install date, warranty end and notes.
- Maintenance plans, with the plan name, next due date and how many months between visits. Choose reminders (no billing) or billed plans. For billed plans, the preview shows each plan's price per term so you can check it before anything is saved. No invoice is made until the next due date, and invoices wait as drafts until you send them or turn on sending for the plan.
- Payment history, as records you can read. They don't move money, can't be changed, and don't count toward the Doing Work fee.
How it works: import customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. For each file your agent does a dry run. Nothing is saved. It shows you how each column will be read, what each row would do (create, update or skip) and any row with a problem, like a missing ZIP. Only the owner can run the real import, and only for the same file and mapping you saw. By default it saves nothing if any row fails. Running a file again is safe: rows that already came over are skipped, or updated if you ask, and never doubled.
3. What to keep running for now
- Keep your old software open until you've checked the imported jobs and invoice balances.
- Imported invoices are drafts. Look each one over and send it from Doing Work when it's right, or keep collecting it where it is. Don't do both.
- Keep your old software's export files, even after payment history comes over.
- Maintenance plans come over as reminders or as billed plans. If you bring them as billed plans, check the prices in the preview and stop billing them in the old software from their next due date.
- Start new requests and new jobs in Doing Work. A few real jobs first is a good test.
- Export everything you can before you cancel, so you keep your own records.
4. Paste this into your agent
"I'm moving my shop from Jobber to Doing Work. Read https://doingwork.work/docs/switching/ and follow the guide for Jobber. I'll give you my export files: customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. Do a dry run of each import with the jobber preset. Show me the mapping, what each row would do and every row with a problem, and wait for my OK before you import anything."
What you'll miss
- Maintenance plans come over as reminders or as billed plans at the prices in your export, which you check in the preview.
- Financing is through your own lender, with links to it on your quotes, and there is no built-in QuickBooks connection. The calendar feed is one way, and the day's route isn't optimized. See Compare for how your agent covers these.
- Calls and texts need your own Twilio account. Quote follow-up emails and unpaid invoice reminder emails do not. They already run by email.
- Jobber's connector for Claude and ChatGPT, if you use it.
- Anything you rely on in Jobber that's in the list above.
More: Switching to Doing Work, Compare, Onboard a shop.
Switching from Housecall Pro to Doing Work
Switching from Housecall Pro
Read on November 1, 2026. Housecall Pro changes its screens, so follow the source links if yours look different.
1. Export your data from Housecall Pro
- Click Customers in the left menu.
- Click Actions on the right, then Export.
- Confirm your email address and click Send file. The CSV is emailed to you.
Only Housecall Pro admins can export customers. Clear any filters on the customer list first, since the export follows them. Source: Housecall Pro help, How to Import and Export Jobs and Customers and Creating Reports from the Customer List.
Doing Work has a Housecall Pro preset that reads the name, company, email, mobile or work number, tags, notes, the customer id and the first address.
For history, export your jobs, estimates, invoices, price book from Housecall Pro, plus equipment, service plans and payments if you track them there, as CSV files too, if your plan lets you. The Housecall Pro preset reads Housecall Pro's column names for each.
Agent access and terms at Housecall Pro
Housecall Pro's terms don't mention outside agents or scraping. Terms: housecallpro.com/terms. Admins can export Customers and Jobs from the Actions menu. On the MAX plan you can make a read-only API key.
General tips and a paste-in prompt: Let your agent do the export.
2. What the import brings over
- Customers: name (or first and last name), company, email, one phone number, tags, notes, lead source, billing address and one US service address.
- Jobs with their visit history: past and upcoming visits, with dates, titles and notes.
- Open quotes, with their lines. They come in as drafts and aren't sent.
- Unpaid invoices, as the balance still owed. They come in as drafts and aren't sent. Paid invoices are skipped.
- The price book: items, descriptions and prices.
- Each record is matched to its customer by the old software's id, then email, then phone.
- Up to 5,000 rows and 5 MB per file. Bigger lists go in several files.
- Equipment at each property: kind, make, model, serial number, install date, warranty end and notes.
- Maintenance plans, with the plan name, next due date and how many months between visits. Choose reminders (no billing) or billed plans. For billed plans, the preview shows each plan's price per term so you can check it before anything is saved. No invoice is made until the next due date, and invoices wait as drafts until you send them or turn on sending for the plan.
- Payment history, as records you can read. They don't move money, can't be changed, and don't count toward the Doing Work fee.
How it works: import customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. For each file your agent does a dry run. Nothing is saved. It shows you how each column will be read, what each row would do (create, update or skip) and any row with a problem, like a missing ZIP. Only the owner can run the real import, and only for the same file and mapping you saw. By default it saves nothing if any row fails. Running a file again is safe: rows that already came over are skipped, or updated if you ask, and never doubled.
3. What to keep running for now
- Keep your old software open until you've checked the imported jobs and invoice balances.
- Imported invoices are drafts. Look each one over and send it from Doing Work when it's right, or keep collecting it where it is. Don't do both.
- Keep your old software's export files, even after payment history comes over.
- Maintenance plans come over as reminders or as billed plans. If you bring them as billed plans, check the prices in the preview and stop billing them in the old software from their next due date.
- Start new requests and new jobs in Doing Work. A few real jobs first is a good test.
- Export everything you can before you cancel, so you keep your own records.
4. Paste this into your agent
"I'm moving my shop from Housecall Pro to Doing Work. Read https://doingwork.work/docs/switching/ and follow the guide for Housecall Pro. I'll give you my export files: customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. Do a dry run of each import with the housecall_pro preset. Show me the mapping, what each row would do and every row with a problem, and wait for my OK before you import anything."
What you'll miss
- Maintenance plans come over as reminders or as billed plans at the prices in your export, which you check in the preview.
- Financing is through your own lender, with links to it on your quotes, and there is no built-in QuickBooks connection. The calendar feed is one way, and the day's route isn't optimized. See Compare for how your agent covers these.
- Calls and texts need your own Twilio account. Quote follow-up emails and unpaid invoice reminder emails do not. They already run by email.
More: Switching to Doing Work, Compare, Onboard a shop.
Switching from ServiceTitan to Doing Work
Switching from ServiceTitan
Read on November 1, 2026. ServiceTitan changes its screens, so follow the source links if yours look different.
1. Export your data from ServiceTitan
- Open Search and search for your customers.
- Click the dropdown next to the search button.
- Choose Export to CSV (.csv).
You need the Allow exporting search results permission, which is on for administrators by default. Source: ServiceTitan help, Use search. The Customers report template can also export to XLSX (ServiceTitan help). Save an XLSX file as CSV before importing.
There's no ServiceTitan preset. Your agent suggests a mapping from the column names and you check it. A full address in one column can be read when it looks like "123 Main St, Boise, ID 83702".
Jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history import the same way if you can export them as CSV. Your agent maps the columns and you check it.
Agent access and terms at ServiceTitan
ServiceTitan's terms address AI agents by name, including sign-in and data collection by agents. Terms: servicetitan.com/legal/terms-of-use. ServiceTitan also has a developer API with export endpoints.
General tips and a paste-in prompt: Let your agent do the export.
2. What the import brings over
- Customers: name (or first and last name), company, email, one phone number, tags, notes, lead source, billing address and one US service address.
- Jobs with their visit history: past and upcoming visits, with dates, titles and notes.
- Open quotes, with their lines. They come in as drafts and aren't sent.
- Unpaid invoices, as the balance still owed. They come in as drafts and aren't sent. Paid invoices are skipped.
- The price book: items, descriptions and prices.
- Each record is matched to its customer by the old software's id, then email, then phone.
- Up to 5,000 rows and 5 MB per file. Bigger lists go in several files.
- Equipment at each property: kind, make, model, serial number, install date, warranty end and notes.
- Maintenance plans, with the plan name, next due date and how many months between visits. Choose reminders (no billing) or billed plans. For billed plans, the preview shows each plan's price per term so you can check it before anything is saved. No invoice is made until the next due date, and invoices wait as drafts until you send them or turn on sending for the plan.
- Payment history, as records you can read. They don't move money, can't be changed, and don't count toward the Doing Work fee.
How it works: import customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. For each file your agent does a dry run. Nothing is saved. It shows you how each column will be read, what each row would do (create, update or skip) and any row with a problem, like a missing ZIP. Only the owner can run the real import, and only for the same file and mapping you saw. By default it saves nothing if any row fails. Running a file again is safe: rows that already came over are skipped, or updated if you ask, and never doubled.
3. What to keep running for now
- Keep your old software open until you've checked the imported jobs and invoice balances.
- Imported invoices are drafts. Look each one over and send it from Doing Work when it's right, or keep collecting it where it is. Don't do both.
- Keep your old software's export files, even after payment history comes over.
- Maintenance plans come over as reminders or as billed plans. If you bring them as billed plans, check the prices in the preview and stop billing them in the old software from their next due date.
- Start new requests and new jobs in Doing Work. A few real jobs first is a good test.
- Export everything you can before you cancel, so you keep your own records.
4. Paste this into your agent
"I'm moving my shop from ServiceTitan to Doing Work. Read https://doingwork.work/docs/switching/ and follow the guide for ServiceTitan. I'll give you my export files: customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. Do a dry run of each import, and suggest a column mapping from the headers. Show me the mapping, what each row would do and every row with a problem, and wait for my OK before you import anything."
What you'll miss
- Maintenance plans come over as reminders or as billed plans at the prices in your export, which you check in the preview.
- Financing is through your own lender, with links to it on your quotes, and there is no built-in QuickBooks connection. The calendar feed is one way, and the day's route isn't optimized. See Compare for how your agent covers these.
- Calls and texts need your own Twilio account. Quote follow-up emails and unpaid invoice reminder emails do not. They already run by email.
- Memberships come over as reminders or billed plans, and the flat rate price book doesn't import.
- Multiple business units and larger dispatch boards, if you rely on them.
More: Switching to Doing Work, Compare, Onboard a shop.
Switching from Workiz to Doing Work
Switching from Workiz
Read on November 1, 2026. Workiz changes its screens, so follow the source links if yours look different.
1. Export your data from Workiz
- Click Reports in the side menu and open the All clients report.
- Leave the filters empty so every client is included. Add address columns if they aren't shown.
- Click Export As, then CSV.
Workiz is rolling out these client reports gradually, so your account may not have them yet. If you don't see them, ask Workiz support for a client export. Source: Workiz help, Understanding your client reports and Managing access to Reports.
There's no Workiz preset. Your agent suggests a mapping from the column names and you check it.
Jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history import the same way if you can export them as CSV. Your agent maps the columns and you check it.
Agent access and terms at Workiz
Workiz asks for a separate login for each person and requires two-step sign-in for admins. Terms: workiz.com/terms-and-conditions. The Developer API add-on lets you make read-only keys. Price book and service plans may need a request to Workiz support.
General tips and a paste-in prompt: Let your agent do the export.
2. What the import brings over
- Customers: name (or first and last name), company, email, one phone number, tags, notes, lead source, billing address and one US service address.
- Jobs with their visit history: past and upcoming visits, with dates, titles and notes.
- Open quotes, with their lines. They come in as drafts and aren't sent.
- Unpaid invoices, as the balance still owed. They come in as drafts and aren't sent. Paid invoices are skipped.
- The price book: items, descriptions and prices.
- Each record is matched to its customer by the old software's id, then email, then phone.
- Up to 5,000 rows and 5 MB per file. Bigger lists go in several files.
- Equipment at each property: kind, make, model, serial number, install date, warranty end and notes.
- Maintenance plans, with the plan name, next due date and how many months between visits. Choose reminders (no billing) or billed plans. For billed plans, the preview shows each plan's price per term so you can check it before anything is saved. No invoice is made until the next due date, and invoices wait as drafts until you send them or turn on sending for the plan.
- Payment history, as records you can read. They don't move money, can't be changed, and don't count toward the Doing Work fee.
How it works: import customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. For each file your agent does a dry run. Nothing is saved. It shows you how each column will be read, what each row would do (create, update or skip) and any row with a problem, like a missing ZIP. Only the owner can run the real import, and only for the same file and mapping you saw. By default it saves nothing if any row fails. Running a file again is safe: rows that already came over are skipped, or updated if you ask, and never doubled.
3. What to keep running for now
- Keep your old software open until you've checked the imported jobs and invoice balances.
- Imported invoices are drafts. Look each one over and send it from Doing Work when it's right, or keep collecting it where it is. Don't do both.
- Keep your old software's export files, even after payment history comes over.
- Maintenance plans come over as reminders or as billed plans. If you bring them as billed plans, check the prices in the preview and stop billing them in the old software from their next due date.
- Start new requests and new jobs in Doing Work. A few real jobs first is a good test.
- Export everything you can before you cancel, so you keep your own records.
4. Paste this into your agent
"I'm moving my shop from Workiz to Doing Work. Read https://doingwork.work/docs/switching/ and follow the guide for Workiz. I'll give you my export files: customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. Do a dry run of each import, and suggest a column mapping from the headers. Show me the mapping, what each row would do and every row with a problem, and wait for my OK before you import anything."
What you'll miss
- Maintenance plans come over as reminders or as billed plans at the prices in your export, which you check in the preview.
- Financing is through your own lender, with links to it on your quotes, and there is no built-in QuickBooks connection. The calendar feed is one way, and the day's route isn't optimized. See Compare for how your agent covers these.
- Calls and texts need your own Twilio account. Quote follow-up emails and unpaid invoice reminder emails do not. They already run by email.
- Service plans come over as reminders or billed plans. Check each price in the preview.
More: Switching to Doing Work, Compare, Onboard a shop.
Switching from FieldEdge to Doing Work
Switching from FieldEdge
Read on November 1, 2026. FieldEdge changes its screens, so follow the source links if yours look different.
1. Export your data from FieldEdge
FieldEdge's own help is behind a customer login, so we couldn't check its steps ourselves. ServiceTitan's public guide says to click the Customers tab in FieldEdge, then Export, which gives a file named CustomerList.xlsx (ServiceTitan help, Export your FieldEdge data). If your screens differ, ask FieldEdge support for a customer export in CSV.
Save an XLSX file as CSV before importing. There's no FieldEdge preset. Your agent suggests a mapping from the column names and you check it.
Jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history import the same way if you can export them as CSV. Your agent maps the columns and you check it.
Agent access and terms at FieldEdge
FieldEdge's terms give each person a unique login. Terms: fieldedge.com/legal. There's no public API. The five exports are Customers, Dispatching, Invoices, Quotes and Equipment List. Set the invoice filters to All first, or you'll only get 6 months.
General tips and a paste-in prompt: Let your agent do the export.
2. What the import brings over
- Customers: name (or first and last name), company, email, one phone number, tags, notes, lead source, billing address and one US service address.
- Jobs with their visit history: past and upcoming visits, with dates, titles and notes.
- Open quotes, with their lines. They come in as drafts and aren't sent.
- Unpaid invoices, as the balance still owed. They come in as drafts and aren't sent. Paid invoices are skipped.
- The price book: items, descriptions and prices.
- Each record is matched to its customer by the old software's id, then email, then phone.
- Up to 5,000 rows and 5 MB per file. Bigger lists go in several files.
- Equipment at each property: kind, make, model, serial number, install date, warranty end and notes.
- Maintenance plans, with the plan name, next due date and how many months between visits. Choose reminders (no billing) or billed plans. For billed plans, the preview shows each plan's price per term so you can check it before anything is saved. No invoice is made until the next due date, and invoices wait as drafts until you send them or turn on sending for the plan.
- Payment history, as records you can read. They don't move money, can't be changed, and don't count toward the Doing Work fee.
How it works: import customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. For each file your agent does a dry run. Nothing is saved. It shows you how each column will be read, what each row would do (create, update or skip) and any row with a problem, like a missing ZIP. Only the owner can run the real import, and only for the same file and mapping you saw. By default it saves nothing if any row fails. Running a file again is safe: rows that already came over are skipped, or updated if you ask, and never doubled.
3. What to keep running for now
- Keep your old software open until you've checked the imported jobs and invoice balances.
- Imported invoices are drafts. Look each one over and send it from Doing Work when it's right, or keep collecting it where it is. Don't do both.
- Keep your old software's export files, even after payment history comes over.
- Maintenance plans come over as reminders or as billed plans. If you bring them as billed plans, check the prices in the preview and stop billing them in the old software from their next due date.
- Start new requests and new jobs in Doing Work. A few real jobs first is a good test.
- Export everything you can before you cancel, so you keep your own records.
4. Paste this into your agent
"I'm moving my shop from FieldEdge to Doing Work. Read https://doingwork.work/docs/switching/ and follow the guide for FieldEdge. I'll give you my export files: customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. Do a dry run of each import, and suggest a column mapping from the headers. Show me the mapping, what each row would do and every row with a problem, and wait for my OK before you import anything."
What you'll miss
- Maintenance plans come over as reminders or as billed plans at the prices in your export, which you check in the preview.
- Financing is through your own lender, with links to it on your quotes, and there is no built-in QuickBooks connection. The calendar feed is one way, and the day's route isn't optimized. See Compare for how your agent covers these.
- Calls and texts need your own Twilio account. Quote follow-up emails and unpaid invoice reminder emails do not. They already run by email.
- Service agreements come over as reminders or billed plans, and the flat rate price book doesn't import.
More: Switching to Doing Work, Compare, Onboard a shop.
Switching to Doing Work from other software
Switching to Doing Work
Doing Work imports customers, jobs with their visit history, open quotes, unpaid invoices, the price book, equipment, maintenance plans and payment history from CSV files. Maintenance plans come in as service due reminders or billed plans, and payments as records only. Keep your old software until you've checked what came over.
- Switching from Jobber
- Switching from Housecall Pro
- Switching from ServiceTitan
- Switching from Workiz
- Switching from FieldEdge
Coming from something else
Running a pilot? Keep your current answering on the main line and point the voice AI at overflow and after hours first. See Phone setup.
Exporting
Export your lists as CSV files from your old software. Your agent suggests a column mapping from the headers and does a dry run before anything is saved. Built-in presets exist for Jobber and Housecall Pro, and for CompanyCam customers.
What the import brings over
- Customers: name (or first and last name), company, email, one phone number, tags, notes, lead source, billing address and one US service address.
- Jobs with their visit history: past and upcoming visits, with dates, titles and notes.
- Open quotes, with their lines. They come in as drafts and aren't sent.
- Unpaid invoices, as the balance still owed. They come in as drafts and aren't sent. Paid invoices are skipped.
- The price book: items, descriptions and prices.
- Each record is matched to its customer by the old software's id, then email, then phone.
- Up to 5,000 rows and 5 MB per file. Bigger lists go in several files.
- Equipment at each property: kind, make, model, serial number, install date, warranty end and notes.
- Maintenance plans, with the plan name, next due date and how many months between visits. Choose reminders (no billing) or billed plans. For billed plans, the preview shows each plan's price per term so you can check it before anything is saved. No invoice is made until the next due date, and invoices wait as drafts until you send them or turn on sending for the plan.
- Payment history, as records you can read. They don't move money, can't be changed, and don't count toward the Doing Work fee.
How it works: import customers first, then jobs, quotes, invoices, the price book, equipment, maintenance plans and payment history. For each file your agent does a dry run. Nothing is saved. It shows you how each column will be read, what each row would do (create, update or skip) and any row with a problem, like a missing ZIP. Only the owner can run the real import, and only for the same file and mapping you saw. By default it saves nothing if any row fails. Running a file again is safe: rows that already came over are skipped, or updated if you ask, and never doubled.
Let your agent do the export
Moving records out of the old system is the slow part of switching. Your agent can do most of it, and it won't skip a column at 11pm.
Some platforms' terms address automated or agent access. ServiceTitan's terms name AI agents directly. Others mention robots or scraping, and some say nothing. The links are below. Whether your agent signs in to your old account is up to you and your agent.
Doing Work is built for agents to work in the account, through MCP, REST, webhooks and agent keys. Some older platforms restrict agent access in their terms.
Tips that make the export go smoothly:
- Start with the official exports and reports. Every platform has export buttons for customers, jobs and invoices.
- Use the platform's API or official integration next, with a read-only key if they offer one.
- Use your own owner login, or a separate team seat you create for your agent. Don't hand over a worker's login.
- If the account has two-step sign-in, you enter the code.
- Have your agent read only. It shouldn't edit, delete, send or change settings in the old account.
- Keep every downloaded file, and look at the summary before anything goes into Doing Work. The import runs as a preview first.
What to pull:
- Customers, properties and contacts
- Job and visit history, open quotes, unpaid invoices, payment history
- Price book and service list
- Equipment on file and maintenance plans
- Tags, custom fields, job forms and checklists
- Email and text templates
- Team members and their roles
- Service areas, business hours, tax rates
Anything that won't come out cleanly goes on a short list, so you know what to copy by hand or ask the old company for.
If you'd rather click the buttons yourself
That works too. Your agent tells you where each export lives, one step at a time, and checks each file as you send it over. If a file looks short (say, only the last 6 months of invoices), it tells you which filter to change.
Paste into your agent
"I'm moving my business from [old system] to Doing Work. Please help with the export. 1. Read [old system]'s current terms and tell me what they say about agents or automated access, with the clause. We'll decide together how you work in the account. 2. Use official exports and reports first, then the official API with a read-only key I create. Read screens only for what has no export. 3. Use my own login with me there, or a separate seat I create for you. I'll enter any two-step codes. 4. Read only. Don't edit, delete, send or change anything in the old account. 5. Pull customers, properties, job and visit history, open quotes, unpaid invoices, payment history, price book, equipment, maintenance plans, tags, custom fields, job forms, templates, team and roles, service areas, business hours and tax rates. 6. Save every file, show me a summary, and run the Doing Work import as a preview. Don't save anything until I confirm. 7. List anything that didn't come out. Docs: https://doingwork.work/docs.md"
Notes by platform
Jobber. Jobber's terms mention robots, scraping and data mining. Terms: getjobber.com/terms-of-service. Clients and invoices export to CSV, and Jobber has a public API (developer.getjobber.com). The API on your own account: a shop owner can make a free Jobber Developer Center account, create a private app for their own Jobber account, and authorize it as the account admin. An app that isn't published can connect to up to 5 Jobber accounts and doesn't need Jobber's App Review. Your agent can then read through the API. Jobber's docs also say custom integrations are only possible for specific, approved Jobber customers and developers, so this may not be open to every account. Sources: Custom integrations, App authorization, App review.
Housecall Pro. Housecall Pro's terms don't mention outside agents or scraping. Terms: housecallpro.com/terms. Admins can export Customers and Jobs from the Actions menu. On the MAX plan you can make a read-only API key.
ServiceTitan. ServiceTitan's terms address AI agents by name, including sign-in and data collection by agents. Terms: servicetitan.com/legal/terms-of-use. ServiceTitan also has a developer API with export endpoints.
Workiz. Workiz asks for a separate login for each person and requires two-step sign-in for admins. Terms: workiz.com/terms-and-conditions. The Developer API add-on lets you make read-only keys. Price book and service plans may need a request to Workiz support.
FieldEdge. FieldEdge's terms give each person a unique login. Terms: fieldedge.com/legal. There's no public API. The five exports are Customers, Dispatching, Invoices, Quotes and Equipment List. Set the invoice filters to All first, or you'll only get 6 months.
QuickBooks sync with your agent
QuickBooks sync with your agent
Keep QuickBooks current through your agent's own QuickBooks connection.
What Doing Work provides
sync.changes: invoices, payments, refunds and customers that changed since a time or cursor, oldest first.sync.setRef: stores the QuickBooks id for a Doing Work record.sync.findRefs: looks up stored ids, so nothing posts twice.payouts.listandpayouts.get: each bank payout, with every payment and refund in it, the processor fee and the Doing Work fee.- Webhooks (
webhooks.create) so the agent hears about changes.
What your agent does
Reads changes from Doing Work, creates or updates them in QuickBooks with its own QuickBooks connection, saves each QuickBooks id back with sync.setRef, and asks you about anything it can't match.
Paste this into your agent
"Sync my Doing Work invoices, payments, refunds and customers to QuickBooks using your QuickBooks connection. Read https://doingwork.work/docs/agent-guides/quickbooks/ first. Use sync.changes, store every QuickBooks id with sync.setRef, check sync.findRefs before creating anything, and ask me before posting anything you can't match."
Limits
- Doing Work has no QuickBooks connection of its own. The sync runs only when your agent runs it.
- Your agent needs its own access to QuickBooks.
- Details: Sync with QuickBooks.
More: Agent guides, Compare.
Google Calendar with your agent
Google Calendar with your agent
Get visits onto Google Calendar, from a worker's own feed link or through your agent.
What Doing Work provides
calendar.createFeed: a private calendar feed link (.ics) of one worker's visits. Google Calendar, Apple Calendar or Outlook subscribes to it. The link is shown once, and a new one turns the old one off.calendar.listFeedsandcalendar.revokeFeed: see each feed and turn one off. A turned-off link stops showing visits.schedule.events: visits between two dates as calendar events, each with a steady id, so your agent updates the same event when a visit moves.- Webhooks for visit.scheduled, visit.updated, visit.assigned and visit.cancelled.
What your agent does
For each worker, makes a feed link and helps them add it to their calendar app. For a shared calendar, copies visits with its own calendar connection using schedule.events, and updates or removes events when a visit moves or is cancelled.
Paste this into your agent
"Get my workers' visits onto their calendars. Read https://doingwork.work/docs/agent-guides/google-calendar/ first. Make a calendar feed link for each worker with calendar.createFeed and send each worker their own link with steps to subscribe in Google Calendar. If I want a shared calendar too, copy the next two weeks with schedule.events using your calendar connection and keep it current from the visit webhooks."
Limits
- One way only. Changes made in Google Calendar don't move visits in Doing Work.
- Calendar apps check a feed on their own schedule, so a change can take hours to show.
- Treat a feed link like a password. Anyone with it can see that worker's visits.
More: Agent guides, Compare.
Route planning with your agent
Route planning with your agent
Plan each worker's day in a better order, then save the new times in one step.
What Doing Work provides
routes.day: one day's stops for every worker, in visit time order. Each stop has the address, map point, time, length, arrival window and priority, and says if it is locked because the worker is already on the way, there or done. Each worker's start point (their own, or the shop yard) and any visits with no worker come back too.routes.setLocationandroutes.setStart: save a map point for a job's address, or where a worker starts the day.routes.apply: save new times, and new workers if you want, for up to 100 visits at once. All or nothing: if a visit can't move or the plan leaves a worker with overlapping visits, nothing changes and you get the problems back. Use dry_run to check first.schedule.route: one worker's stops in order with a map link per stop and a driving directions link for the first 10 stops, to send the worker.visits.onTheWay: sends the customer an on-my-way notice with the ETA.
What your agent does
Reads the day with routes.day and orders the stops with a maps or routing tool the shop picks. It shows you the new order and times, then saves them all with routes.apply. Then it sends each worker their stops and directions link.
Paste this into your agent
"Plan tomorrow's routes. Read https://doingwork.work/docs/agent-guides/route-planning/ first. Use routes.day for tomorrow, order each worker's stops with our maps tool, and show me the new times and any worker changes. When I say yes, save them with routes.apply (check with dry_run first). Then send each worker their route from schedule.route with the directions link."
Limits
- Doing Work doesn't optimize routes. Your agent does that with the maps tool you pick, so the order is only as good as that tool.
- Stops with no map point yet need one saved with routes.setLocation, or your agent can look up the address.
- routes.apply moves up to 100 visits at a time, and only visits that are still scheduled.
- The directions link covers the first 10 stops.
More: Agent guides, Compare.
Payroll with your agent
Carry approved hours to your payroll service.
What Doing Work provides
payroll.getPeriodandpayroll.setPeriod: the shop's pay period, weekly, every two weeks, twice a month or monthly.payroll.hours: approved hours per worker for a pay period, by day and by work, drive, shop and break time, plus anything still waiting for approval or still running. It says when the period is ready.payroll.exportCsv: the same approved hours as a CSV, one row per worker per day, for a payroll service.timesheets.decide: approve or reject time (owner or office).
What your agent does
Checks that the pay period is ready, gets the approved hours or the CSV, and enters them in your payroll service (for example Gusto, ADP or QuickBooks Payroll) using your own account.
Paste this into your agent
"Get approved hours for each worker for this pay period from Doing Work. Read https://doingwork.work/docs/agent-guides/payroll/ first. Use payroll.hours, list anything still waiting for approval, and show me the totals before you enter them in my payroll service. Use payroll.exportCsv if my payroll service takes a file."
Limits
- Doing Work doesn't run payroll, pay wages or handle payroll tax. It gives hours, not pay.
- Only approved time goes in the totals and the CSV. Waiting time is listed separately.
More: Agent guides, Compare.
Customer financing with your agent
Customer financing with your agent
Show the shop's financing links on quotes, and record a job paid by a financing company.
What Doing Work provides
financing.save: adds a link to a financing company the shop works with, up to 3. Each link shows on quotes at or above the minimum total the shop sets. Owner or office, or their agent.financing.listandfinancing.archiveread and remove them.invoices.markPaidOutsidewith methodfinancing: records that the customer paid the invoice outside Doing Work, with the date and an optional note. Owner or office, or their agent.
What your agent does
Saves the shop's financing links once, so customers see them on bigger quotes. When the financing company confirms it paid, marks the invoice paid with method financing and the date, and notes the lender or loan number.
Paste this into your agent
"My customer's invoice was paid by a financing company. Read https://doingwork.work/docs/agent-guides/financing/ first. Find the invoice, show it to me, and after I confirm, use invoices.markPaidOutside with method financing, the date paid and a note with the lender name."
Limits
- Doing Work doesn't offer customer financing, process loans or charge a fee for financing. The shop sets that up with its own lender, and the link on the quote goes to that lender.
- Recording it closes the invoice. Only do it once the money has arrived.
More: Agent guides, Compare.
Agent guides for what Doing Work leaves out
Agent guides
Doing Work keeps the records and tells your agent when they change. These guides show how your agent covers the rest using its own connections. Each one uses only tools that exist today.
- QuickBooks sync: Keep QuickBooks current through your agent's own QuickBooks connection.
- Google Calendar: Get visits onto Google Calendar, from a worker's own feed link or through your agent.
- Route planning: Plan each worker's day in a better order, then save the new times in one step.
- Payroll: Carry approved hours to your payroll service.
- Customer financing: Show the shop's financing links on quotes, and record a job paid by a financing company.
Sync with QuickBooks
Your agent can sync with QuickBooks. The sync runs through your agent's own QuickBooks connection, on the schedule you pick. Daily is a good default. You tell your agent which accounts and items to use, and it asks you about anything it can't match. Doing Work has no QuickBooks connection of its own.
Each run
- Call sync.changes with the
next_cursoryou saved last time. The first run can start fromupdated_since. Page untilhas_moreis false, then save the lastnext_cursor. - Each row is one invoice, payment, refund or customer with its current details, so you never replay history.
- If
external_refshas aquickbooksid, update that QuickBooks record. If not, look for a match, create one if there is none, then call sync.setRef with the QuickBooks id. - A record can show up again in a later run. The saved id makes that safe: running the same sync twice changes nothing.
- To catch anything missed, call sync.changes with
system=quickbooksandunsynced=true. sync.findRefs goes from a QuickBooks id back to the Doing Work record.
Match bank deposits
List payouts with payouts.list and read each with payouts.get. It lists every payment and refund in the payout with the processor fee, the Doing Work fee and the net. The nets add up to the deposit. Record both fees as expenses so the deposit, the invoices and the fees line up. The payout.paid event tells you when a new payout lands.
Owner or office only. Amounts need the see_prices permission.
Export your books
If your agent syncs QuickBooks for you, keep using that. It keeps every invoice, payment and fee matched. For a bookkeeper, or if you import by hand, ask for a month of books with books.export. You get one ZIP with:
- A ledger CSV: every invoice, void, payment, refund, fee and payout.
- QuickBooks Online invoice import files.
- QuickBooks Online bank upload files for a clearing account.
- A README that says how to import each file.
Fees are dated on the payout they came out of, so each payout adds up to what reached your bank. Asking for the same month again gives the same file. Payments imported from old software are left out unless you ask for them. Owner or office only, and amounts need the see_prices and see_costs permissions. books.exports lists past exports.
Flat rate price book
Price whole jobs, not hours. A flat rate task has one price, an optional task code, a member price for customers on a maintenance plan, an estimated time and the parts it uses. Save tasks with pricebook.saveItem.
- Build quotes from tasks. Your agent picks the tasks and gets the quote lines with
quotes.linesFromTasks, with member prices applied when the customer has an active plan. It then sends the chosen lines toquotes.create. - Good, better, best: put each tier in its own quote option.
- See what a task costs you with
pricebook.taskCost: parts plus labor at your shop rate. Parts are for your costing and never show on the customer's quote. - Bring your price book over from Jobber or Housecall Pro with a CSV import. The dry run shows how each column will be read so you can check it before anything is saved.
Example HVAC tasks (example prices only, set your own): replace run capacitor $285, member $245. Replace hot surface igniter $325, member $280. AC tune-up $149, included on a plan.
Doing Work vs Jobber: price, agent access and fit
Doing Work vs Jobber
Doing Work (doingwork.work) is field service software for trade shops, built for the shop's own AI agent to run. Their prices were read on November 1, 2026 from the linked page. Check it, since prices change.
The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month. No subscription.
| Doing Work | Jobber | |
|---|---|---|
| Price | No plans and no monthly fee. A fee on payments taken through Doing Work: first $1,000 free each month, then 0.5% up to $149. Nothing is metered. Pricing | Billed monthly: Core $29 to $49 for 1 seat, Connect $139 to $399, Grow $199 to $499, Plus $499 to $699 for 5 to 15 seats. $29 a month for each extra seat. AI Receptionist is a $29 add-on. Source: getjobber.com/pricing |
| Workers | Unlimited, every feature. | See their pricing page. |
| Agent access | Every action over REST, MCP and A2A with OAuth. API reference | Jobber's official connector for Claude and ChatGPT reads clients, requests, quotes, jobs and invoices, and creates requests, clients, properties and quotes. It can't create jobs or invoices or change the schedule (Jobber help). On Doing Work an agent can do every action a worker can, over REST, MCP or A2A. |
| Phone booking | On. Calls come in on the shop's own Twilio number and are answered by the shop's own voice agent (ElevenLabs or Grok), which books callers into the shop's live availability once the owner turns on live booking. Texts to customers go by email until the shop's 10DLC texting registration is approved. See Phone setup. | Jobber sells AI Receptionist as a $29 a month add-on (per its pricing page). |
| Card processing | Stripe, 2.9% + 30¢ for a domestic card (stripe.com/pricing). | 2.9% + 30¢ for cards, ACH 1%. Source: getjobber.com/pricing, read November 1, 2026. |
Fee example
A crew of 5 taking $40,000 a month in payments: Doing Work's fee is $149 with no plan to pick. On Jobber the same crew picks a plan, and Grow for 5 seats is in the $199 to $499 range on that page. Card processing is extra on both: Stripe 2.9% + 30¢ on Doing Work, and 2.9% + 30¢ (ACH 1%) on Jobber's page.
Doing Work fee at other volumes: $1,000 a month costs $0.00; $3,000 a month costs $10.00; $5,000 a month costs $20.00; $20,000 a month costs $95.00; $30,800 a month costs $149.00; $40,000 a month costs $149.00; $160,000 a month costs $149.00.
Where Jobber wins
- Years in the market and many public reviews. Doing Work launched in 2026 and has none yet.
- A mobile app built for crews who don't use an AI agent.
- A built-in QuickBooks Online connection. On Doing Work your agent syncs QuickBooks on the schedule you pick. A month of books as one ZIP is only the fallback when you import by hand.
Switching
What imports and what doesn't: Switching from Jobber. You can keep Jobber running while you try a few real jobs.
Run the shop from the AI you already use: Run your shop from ChatGPT, Claude, or the AI you already use.
Doing Work vs Housecall Pro: price, agent access and fit
Doing Work vs Housecall Pro
Doing Work (doingwork.work) is field service software for trade shops, built for the shop's own AI agent to run. Their prices were read on November 1, 2026 from the linked page. Check it, since prices change.
The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month. No subscription.
| Doing Work | Housecall Pro | |
|---|---|---|
| Price | No plans and no monthly fee. A fee on payments taken through Doing Work: first $1,000 free each month, then 0.5% up to $149. Nothing is metered. Pricing | Billed annually: Basic $59 for 1 seat, Essentials $149 for 5 seats, MAX $299 for 8 seats, then $35 a month per extra seat on MAX. Service plans and the API are on MAX. Source: housecallpro.com/pricing |
| Workers | Unlimited, every feature. | See their pricing page. |
| Agent access | Every action over REST, MCP and A2A with OAuth. API reference | Housecall Pro's public API is on the MAX plan only (Housecall Pro help). We found no official MCP server. On Doing Work the API and MCP are open to every shop. |
| Phone booking | On. Calls come in on the shop's own Twilio number and are answered by the shop's own voice agent (ElevenLabs or Grok), which books callers into the shop's live availability once the owner turns on live booking. Texts to customers go by email until the shop's 10DLC texting registration is approved. See Phone setup. | Housecall Pro sells AI answering separately and doesn't publish the price. |
| Card processing | Stripe, 2.9% + 30¢ for a domestic card (stripe.com/pricing). | Cards from 2.59%, bank 1%. Source: housecallpro.com/pricing, read November 1, 2026. |
Fee example
A crew of 5 taking $40,000 a month: Doing Work's fee is $149. Housecall Pro Essentials is $149 a month billed annually. The bigger number is processing. Housecall Pro lists cards from 2.59%. Doing Work uses Stripe at 2.9% + 30¢. On $40,000 of cards the gap is roughly $124 a month plus 30¢ a payment, which can outweigh the plan price difference. Run it on your own card and bank mix.
Doing Work fee at other volumes: $1,000 a month costs $0.00; $3,000 a month costs $10.00; $5,000 a month costs $20.00; $20,000 a month costs $95.00; $30,800 a month costs $149.00; $40,000 a month costs $149.00; $160,000 a month costs $149.00.
Where Housecall Pro wins
- A lower card rate: from 2.59%, against Stripe's 2.9% + 30¢ on Doing Work. For a card-heavy shop this can be the biggest line.
- Built-in customer financing. On Doing Work the shop adds links to its own financing company (up to 3) that show on quotes. Doing Work doesn't process financing. A job paid through a financing company is recorded as paid outside.
- Years of public reviews and a polished app for crews who don't use an agent.
Switching
What imports and what doesn't: Switching from Housecall Pro. You can keep Housecall Pro running while you try a few real jobs.
Run the shop from the AI you already use: Run your shop from ChatGPT, Claude, or the AI you already use.
Doing Work vs ServiceTitan: price, agent access and fit
Doing Work vs ServiceTitan
Doing Work (doingwork.work) is field service software for trade shops, built for the shop's own AI agent to run. Their prices were read on November 1, 2026 from the linked page. Check it, since prices change.
The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month. No subscription.
| Doing Work | ServiceTitan | |
|---|---|---|
| Price | No plans and no monthly fee. A fee on payments taken through Doing Work: first $1,000 free each month, then 0.5% up to $149. Nothing is metered. Pricing | Quote only. No public prices. Third parties report setup fees and multi-year contracts (not verified by us). Source: servicetitan.com/pricing |
| Workers | Unlimited, every feature. | See their pricing page. |
| Agent access | Every action over REST, MCP and A2A with OAuth. API reference | APIs through ServiceTitan's partner program. ServiceTitan's terms address AI agents by name; see Switching from ServiceTitan. |
| Phone booking | On. Calls come in on the shop's own Twilio number and are answered by the shop's own voice agent (ElevenLabs or Grok), which books callers into the shop's live availability once the owner turns on live booking. Texts to customers go by email until the shop's 10DLC texting registration is approved. See Phone setup. | ServiceTitan markets its own AI voice agent. We couldn't find a public price. |
| Card processing | Stripe, 2.9% + 30¢ for a domestic card (stripe.com/pricing). | See their pricing page. |
Fee example
A shop taking $120,000 a month: Doing Work's fee is $149, with no contract. ServiceTitan doesn't publish a price to compare, so get a quote with the same worker count.
Doing Work fee at other volumes: $1,000 a month costs $0.00; $3,000 a month costs $10.00; $5,000 a month costs $20.00; $20,000 a month costs $95.00; $30,800 a month costs $149.00; $40,000 a month costs $149.00; $160,000 a month costs $149.00.
Where ServiceTitan wins
- Depth for large shops: stock locations, built-in route optimization and call center tools. Doing Work does not have stock locations or built-in route optimization. Your agent can reorder a day's stops with a maps tool and save them with routes.apply. Doing Work does have purchase orders.
- A long track record with big HVAC, plumbing and electrical companies.
- Implementation staff who set it up for you.
Switching
What imports and what doesn't: Switching from ServiceTitan. You can keep ServiceTitan running while you try a few real jobs.
Run the shop from the AI you already use: Run your shop from ChatGPT, Claude, or the AI you already use.
Doing Work vs Workiz: price, agent access and fit
Doing Work vs Workiz
Doing Work (doingwork.work) is field service software for trade shops, built for the shop's own AI agent to run. Their prices were read on November 1, 2026 from the linked page. Check it, since prices change.
The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month. No subscription.
| Doing Work | Workiz | |
|---|---|---|
| Price | No plans and no monthly fee. A fee on payments taken through Doing Work: first $1,000 free each month, then 0.5% up to $149. Nothing is metered. Pricing | Quote only on the plans compared here. Maintenance plans, equipment and inventory are on Ultimate. Source: workiz.com/pricing-plans |
| Workers | Unlimited, every feature. | See their pricing page. |
| Agent access | Every action over REST, MCP and A2A with OAuth. API reference | Workiz has an API. We found no official MCP server (checked November 1, 2026; tell us if that's changed). |
| Phone booking | On. Calls come in on the shop's own Twilio number and are answered by the shop's own voice agent (ElevenLabs or Grok), which books callers into the shop's live availability once the owner turns on live booking. Texts to customers go by email until the shop's 10DLC texting registration is approved. See Phone setup. | Workiz markets its own AI answering (Genius Answering). Price not checked by us. |
| Card processing | Stripe, 2.9% + 30¢ for a domestic card (stripe.com/pricing). | See their pricing page. |
Fee example
A crew of 5 taking $40,000 a month: Doing Work's fee is $149, with maintenance plans and equipment included. Workiz quotes its price, so ask for the Ultimate plan if you need those.
Doing Work fee at other volumes: $1,000 a month costs $0.00; $3,000 a month costs $10.00; $5,000 a month costs $20.00; $20,000 a month costs $95.00; $30,800 a month costs $149.00; $40,000 a month costs $149.00; $160,000 a month costs $149.00.
Where Workiz wins
- Built-in phone system and AI answering from one vendor, so there's no separate Twilio or voice account to set up.
- Inventory on its Ultimate plan. Doing Work keeps one stock count per material.
- More years in the market and public reviews.
Switching
What imports and what doesn't: Switching from Workiz. You can keep Workiz running while you try a few real jobs.
Run the shop from the AI you already use: Run your shop from ChatGPT, Claude, or the AI you already use.
Doing Work vs FieldEdge: price, agent access and fit
Doing Work vs FieldEdge
Doing Work (doingwork.work) is field service software for trade shops, built for the shop's own AI agent to run. Their prices were read on November 1, 2026 from the linked page. Check it, since prices change.
The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month. No subscription.
| Doing Work | FieldEdge | |
|---|---|---|
| Price | No plans and no monthly fee. A fee on payments taken through Doing Work: first $1,000 free each month, then 0.5% up to $149. Nothing is metered. Pricing | Quote only. Source: fieldedge.com/pricing |
| Workers | Unlimited, every feature. | See their pricing page. |
| Agent access | Every action over REST, MCP and A2A with OAuth. API reference | We found no official MCP server (checked November 1, 2026). |
| Phone booking | On. Calls come in on the shop's own Twilio number and are answered by the shop's own voice agent (ElevenLabs or Grok), which books callers into the shop's live availability once the owner turns on live booking. Texts to customers go by email until the shop's 10DLC texting registration is approved. See Phone setup. | Not checked by us. |
| Card processing | Stripe, 2.9% + 30¢ for a domestic card (stripe.com/pricing). | See their pricing page. |
Fee example
A shop taking $120,000 a month: Doing Work's fee is $149. FieldEdge quotes its price, so get one for the same worker count.
Doing Work fee at other volumes: $1,000 a month costs $0.00; $3,000 a month costs $10.00; $5,000 a month costs $20.00; $20,000 a month costs $95.00; $30,800 a month costs $149.00; $40,000 a month costs $149.00; $160,000 a month costs $149.00.
Where FieldEdge wins
- A long history with HVAC and plumbing shops and a close QuickBooks connection.
- Flat rate pricing that its customers have used for years. Doing Work's flat rate price book is new.
- Public reviews. Doing Work has none yet.
Switching
What imports and what doesn't: Switching from FieldEdge. You can keep FieldEdge running while you try a few real jobs.
Run the shop from the AI you already use: Run your shop from ChatGPT, Claude, or the AI you already use.
Field service software that works with your own AI agent (2026)
Field service software that works with your own AI agent
Doing Work's page for this is Run your shop from ChatGPT, Claude, or the AI you already use.
For a trade shop that wants its AI agent to book, quote and invoice. Read on November 1, 2026 from each company's own pages. We haven't tested the other tools ourselves, so check them.
| Software | How an agent connects | What the agent can do | Price |
|---|---|---|---|
| Doing Work (doingwork.work) | MCP, REST and A2A, OAuth. Open to every shop. | Every action a worker can do: jobs, schedule, quotes, invoices, payments. Signing and paying stay on pages a person opens. | Free to use. first $1,000 free each month, then 0.5% up to $149. |
| Jobber | Official MCP connector for Claude and ChatGPT (Jobber help). | Reads most records. Creates requests, clients, properties and quotes. Can't create jobs or invoices or change the schedule. | From $29 a month for 1 seat (pricing). |
| Housecall Pro | Public API on MAX only (help). No official MCP server found. | Whatever the API allows, through a developer. | MAX $299 a month for 8 seats, billed annually. |
| ServiceTitan | Partner program APIs. | Through approved apps. | Quote only. |
Phone booking
Doing Work: On. Calls come in on the shop's own Twilio number and are answered by the shop's own voice agent (ElevenLabs or Grok), which books callers into the shop's live availability once the owner turns on live booking. Texts to customers go by email until the shop's 10DLC texting registration is approved. See Phone setup.
How to choose
- If your agent should run the back office end to end, check whether it can create jobs, invoices and visits, not just read them.
- If nobody in the shop uses an agent, a tool with a mature app and years of reviews, like Jobber or Housecall Pro, is the safer pick today.
- Doing Work is new and has no public reviews yet. Try it on a few real jobs while your current software keeps running.
Side by side: Jobber, Housecall Pro, ServiceTitan, Workiz, FieldEdge.
Free field service software with no monthly fee | Doing Work
Free field service software with no monthly fee
Free field service software for trade shops. No monthly fee. The full price is on Pricing.
The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month. No subscription. A month with no payments costs nothing.
The other tools here are the ones this site already compares: Jobber, Housecall Pro, ServiceTitan, Workiz, and FieldEdge. Every one of them charges a plan or quotes a price. Read on November 1, 2026 from each company's own pages. We haven't tested the other tools ourselves, so check them.
| Software | How it charges | The catch |
|---|---|---|
| Doing Work (doingwork.work) | Free field service software. A fee on payments taken through it: first $1,000 free each month, then 0.5% up to $149. A month with no payments costs nothing. Nothing is metered. | Stripe processing is on top. New, with no public reviews yet. It works with an AI agent. There is no app to install. |
| Jobber | Monthly plans by tier and user count, from $29 to $49 for 1 seat, plus $29 a month per extra seat (getjobber.com/pricing). | A mobile app and years of public reviews. The Claude and ChatGPT connector cannot create jobs or invoices or change the schedule. |
| Housecall Pro | Billed annually: Basic $59 for 1 seat, Essentials $149 for 5 seats, MAX $299 for 8 seats, then $35 a month per extra seat on MAX (housecallpro.com/pricing). | Cards from 2.59%. Customer financing. An app for crews. The public API is on the MAX plan only. |
| ServiceTitan | Quote only. No public prices (servicetitan.com/pricing). | Stock locations and built-in route optimization, which Doing Work does not have. Doing Work does have purchase orders. A long track record with large shops. |
| Workiz | Quote only. Maintenance plans, equipment, and inventory are on Ultimate (workiz.com/pricing-plans). | A built-in phone system and AI answering from one vendor. More years in the market and public reviews. |
| FieldEdge | Quote only (fieldedge.com/pricing). | A long history with HVAC and plumbing shops and a close QuickBooks connection. Public reviews. Doing Work has none yet. |
What Doing Work costs at your volume
$1,000 a month costs $0.00; $3,000 a month costs $10.00; $5,000 a month costs $20.00; $20,000 a month costs $95.00; $30,800 a month costs $149.00; $40,000 a month costs $149.00; $160,000 a month costs $149.00.
Subscription tools for comparison
Jobber starts at $29 a month for 1 seat and Housecall Pro Basic at $59 (billed annually), from their pricing pages. See Total cost for the full method. A criteria page, not a ranking: Free Jobber and Housecall Pro alternatives.
Run the shop from the AI you already use: Run your shop from ChatGPT, Claude, or the AI you already use.
Questions
These are questions shop owners type. The answer is what Doing Work does today.
Is there field service software with no monthly fee?
Yes. Doing Work is free field service software with no monthly fee. Free up to $1,000 a month in payments, no monthly fee ever, then 0.5% up to $149 a month. A month with no payments costs nothing. Jobber and Housecall Pro charge a monthly plan. ServiceTitan, Workiz, and FieldEdge quote their prices.
Is there a free contractor app with no monthly fee?
Yes. Doing Work is free field service software with no monthly fee. There is no app to install. You use your AI agent, and web pages that open in the phone browser. Free up to $1,000 a month in payments, no monthly fee ever, then 0.5% up to $149 a month.
Is Doing Work free?
Yes. Doing Work is free field service software for trade shops. Free up to $1,000 a month in payments, no monthly fee ever, then 0.5% up to $149 a month. The first $1,000 you're paid each month is free. Above that we take 0.5%, up to $149 in a month. Stripe's processing is separate.
What does Doing Work cost after the free $1,000?
Above the free $1,000 we take 0.5%, up to $149 in a month. $3,000 in payments costs $10.00. $5,000 costs $20.00. $15,000 costs $70.00. $30,800 costs $149.00. Above that the fee stays $149.00.
Is there a Jobber alternative with no monthly fee?
Yes. Doing Work is a free Jobber alternative with no monthly fee. Free up to $1,000 a month in payments, no monthly fee ever, then 0.5% up to $149 a month. Jobber bills a monthly plan, from $29 to $49 for 1 seat on getjobber.com/pricing, read November 1, 2026. Jobber has a mobile app and years of public reviews. Doing Work launched in 2026 and has no public reviews yet.