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.

• Connect an agent: discovery, OAuth with PKCE, MCP and REST.
• Recommended setup: chat vs agent: what a plain AI chat can do, and why running a shop needs an agent that keeps working. Grok Bot and Dots need a paid subscription. Muse is free to start.
• 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. No stock locations or purchase orders.
• 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.
• 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: A day's route, not an optimized one. Doing Work lists a worker's stops in time order with a map link for each and one driving directions link. It doesn't reorder stops. 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. There are no saved crews, so pick the workers for each visit.
• AI phone answering and booking: Coming soon, not yet on for shops. 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 quotes a price and never books an emergency. 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.
• Bookkeeping export: Yes. Your agent can sync with QuickBooks, and that stays the best way. Without a sync, the owner or office can 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, not billing. Payment history comes in as records only. It moves no money and doesn't count toward the fee.

How an agent covers QuickBooks, Google Calendar, route planning, payroll and financing: Agent guides.

Rules that always apply

• Workers write their own quote lines and prices. Write exactly what they tell you. Never invent, estimate or fill in a price.
• 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 .md to the path, or send Accept: text/markdown.

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.

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

• 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 to read_only or no_money. It works on REST, MCP and A2A.
• Register and get claimed. With no key yet, agents.register gives you a claim token. agents.claim with the owner's email returns a 6 digit code the owner types on a hosted page. Poll the token endpoint until they approve. Details in auth.md.
• A2A. POST https://doingwork.work/a2a (A2A 1.0 JSON-RPC) with a named agent key. Send SendMessage with 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 see the person and their shops. Then follow Onboard a shop or Job to paid.

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) and payment history (as records) import from CSV files.

First, check where you're running

Before step 1, check two things about yourself. Can you call tools at https://doingwork.work/mcp right now? Can you keep working when the person isn't chatting with you, on a schedule or by checking for new requests? If both are yes, go to step 1. If either is no, or you're not sure, stop and tell them:

"I can answer questions about Doing Work, but I can't run your shop from this chat. I stop when you close it. Your first step is to set up an AI agent that keeps working when you're away, like Grok Bot, Muse or Dots. Once it's set up, paste this into it:"

"Set up Doing Work for my shop. Read https://doingwork.work/docs.md and follow https://doingwork.work/docs/onboarding/ step by step. Connect to https://doingwork.work/mcp and ask me one thing at a time."

Then only answer questions until they've moved. Don't create the shop or invite workers from a chat. The rest of onboarding happens inside the agent. See Recommended setup: chat vs agent.

Steps

1. Account. Ask their email. Call auth.requestLink. Tell them: "I sent a sign-in link to your email. Open it on this device." Then complete Connect an agent so they approve you.
2. Shop. Ask the business name and the state or province it works in. Call shops.create with jurisdiction like US-ID. They're the owner.
3. Team. Ask if anyone else works with them. For each, ask the email and whether they're office or field. Call members.invite. Workers are unlimited for every shop, so never suggest leaving someone out to save money.
4. Pricing. There are no plans to pick. Doing Work takes 1% of the first $5,000 in card and bank payments each month, then 0.25% up to $40,000 and 0.04% above, with no monthly fee and no cap. The shop only pays when it gets paid. If they ask, read the rates from fees.schedule.
5. First job. Ask for the customer name and the job address. Call customers.create then jobs.create.
6. Stripe. Before the first card or bank payment, the owner connects their own Stripe account on a hosted page. Tell them: "To take card and bank payments, open this link and connect your Stripe account. Customers then pay you directly."
7. Wrap up. Tell them what's set up and what's next, in one or two sentences.

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.

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 and tell you if Doing Work fits your shop. It can't see your jobs or do anything in your account.
• A chat with Doing Work connected can do real work while you're talking to it. Add https://doingwork.work/mcp as a custom connector and sign in. Then it can set up your shop, write quotes and invoices with your prices, and check what's owed. When you close the chat, it stops.
• An always-on agent, like Grok Bot, Muse or Dots, keeps working when you're not there. It can check for new customer requests and answer them the same day, follow up on unsigned quotes overnight and act when a payment comes in. This is the setup we recommend for running your shop. Grok Bot and Dots need a paid subscription. Muse is free to start.

What works in any setup

• Doing Work sends appointment reminder emails itself once you turn them on.
• Coming soon: your phone agent answers calls on its own, on your own ElevenLabs or Grok voice account.
• Signing, paying and connecting Stripe always happen on a page a person opens. No AI does those for you.

Started in a chat?

That's fine for checking fit. Your first setup step is an always-on agent. Your chat will give you the text to paste into it, and the rest of setup happens there. Not sure which you have? If it only answers when you hit send, it's a chat.

Job to paid

Quote lines

Each line has a description, a quantity and a unit price in cents (unit_price_minor). Take these from the worker word for word. If a price is missing, ask. 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 check with the read operations, then tell the owner.

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 workers

• Ask for their lines and prices. Never suggest a price.
• 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. Give it to the owner to send, or send it the way the owner tells you. 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 card or bank (ACH) payment, set by the shop's total for the calendar month: 1% of the first $5,000, 0.25% from $5,000 to $40,000, and 0.04% above $40,000, with no cap. The shop only pays when it gets paid, and deposits count.
• Each rate applies only to the dollars in its band. A payment that crosses a band is split across the two rates. Cards and bank payments cost the same, with no cap per payment.
• 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 next band.
• A refund returns our fee on the refunded part at the rate it was charged. Jobs paid outside Doing Work are unlimited and cost nothing.
• Nothing is metered. The payment fee bands are the only thing Doing Work charges. Storage, email and every Doing Work feature are included.
• Phone is coming soon. When it is on, 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.
• Card and bank processing is charged separately by Stripe at its standard rates: https://stripe.com/pricing.
• Cost at your volume: $5,000 in payments a month costs $50, $20,000 costs $87.50, $60,000 costs $145.50 and $100,000 costs $161.50. 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.

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/v1 for REST, https://doingwork.work/mcp for 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-Key on every POST that writes (in MCP, _meta.idempotencyKey). A retry with the same key and body returns the first result. A different body gives idempotency_key_reused.
• Money: integers in cents, in fields ending _minor.
• Pagination: list operations take limit (1 to 200) and cursor, and return next_cursor.
• Rate limits: 429 rate_limited with Retry-After in 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.

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.

Pricing

Current as of November 2026.

• 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 card or bank (ACH) payment, set by the shop's total for the calendar month: 1% of the first $5,000, 0.25% from $5,000 to $40,000, and 0.04% above $40,000, with no cap. The shop only pays when it gets paid, and deposits count.
• Each rate applies only to the dollars in its band. A payment that crosses a band is split across the two rates. Cards and bank payments cost the same, with no cap per payment.
• 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 next band.
• A refund returns our fee on the refunded part at the rate it was charged. Jobs paid outside Doing Work are unlimited and cost nothing.
• Nothing is metered. The payment fee bands are the only thing Doing Work charges. Storage, email and every Doing Work feature are included.
• Phone is coming soon. When it is on, 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.
• Card and bank processing is charged separately by Stripe at its standard rates: https://stripe.com/pricing.
• Cost at your volume: $5,000 in payments a month costs $50, $20,000 costs $87.50, $60,000 costs $145.50 and $100,000 costs $161.50. 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.

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.

Compare

What an agent can check for itself, read on November 1, 2026. Follow the links, since other companies change their plans and prices.

Plain answers

Checked against what Doing Work does today.

How your agent covers what Doing Work leaves out

QuickBooks. Doing Work doesn't connect to QuickBooks directly. Your agent can sync with QuickBooks. It uses your own QuickBooks connection, on the schedule you pick. 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 with the Doing Work fee shown. Your agent already knows your jobs and customers, so it can match them and ask you about anything unclear, rather than a fixed sync guessing. There's no extra Doing Work connection to set up or break. For a bookkeeper, or if you import by hand, you can also get a month of books as files. 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 change the order, your agent can use a maps tool you choose, then move visits in Doing Work. Doing Work flags overlaps and time off, and 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. Your agent already has your business context and your own accounts. Doing Work keeps the records and tells your agent when they change. Each tool you add is a connection you control, not another integration Doing Work has to maintain.

Step by step: Agent guides for QuickBooks, Google Calendar, route planning, payroll and financing.

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) 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.
• No route optimization. The day's route lists stops in time order.
• No customer financing offers. A job paid through a financing company can be recorded as paid outside Doing Work.
• Stock is a count per material. No stock locations or purchase orders.
• Imports come from CSV files. Maintenance plans import as reminders, not billing.
• Service due reminders are email only. No reminder texts.
• No built-in QuickBooks connection. Your agent can sync it. See Sync with QuickBooks.
• Phone is coming soon. When it is on, 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.

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.

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

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

Other software

How to add it up

1. Take the shop's payments in a normal month and read the Doing Work fee from the bands, or call fees.preview.
2. Add the agent subscription the shop would use.
3. Estimate a month of calls and texts. Phone is coming soon, so this is for planning. Multiply minutes and texts by the Twilio rates. If an AI answers calls, add its plan or per-minute cost.
4. 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.
5. Compare processing too. A rate difference on card volume can be larger than any plan price.
6. 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.
7. 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.

For the same shop on other software, add the plan for 8 users, any extra users and add-ons, and the processing rate. 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.

Phone setup

Coming soon. Phone is not yet on for shops. This page shows how it will work so you can plan. 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.

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 small shop can register as a sole proprietor, which sends a code to the owner's phone. A toll-free number with verification also works.
• If you want an AI to answer calls, open an ElevenLabs or Grok account.

What the agent does

1. Connect Twilio with phone.connectTwilio. Use a restricted API key. The Auth Token is only used to check that requests really come from Twilio.
2. Pick the number with phone.twilioNumbers and phone.useNumber. This sets the number's Twilio settings. Don't change them by hand.
3. Choose where calls go with phone.setRoute: forward to a phone, take a voicemail that arrives by email, or answer with the voice AI.
4. 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.
5. Track texting registration with phone.registrationStatus. Until it is approved, texts to customers go by email instead. Calls work the whole time.
6. 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.

Turning it off

phone.disconnect stops Doing Work handling the number and puts back the settings it had before.

Phone booking into your calendar

Coming soon, with phone. 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.

1. List the work the agent may book, how long each takes, and which workers do it.
2. Add the ZIP codes you serve.
3. 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 quotes a price. 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 books an emergency. Gas, carbon monoxide, no heat, sparks, smoke, fire, flooding or a burst pipe goes to your on-call phone or becomes an emergency request. 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.

Typical cost

Rates read on November 1, 2026. Check the links.

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

Read on November 1, 2026. Jobber changes its screens, so follow the source links if yours look different.

1. Export your data from Jobber

1. Click Clients in the side menu.
2. Click More Actions in the top right, then Export Clients.
3. 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, products and services from Jobber, plus equipment, plans and payments if you track them there, as CSV files too, if your plan lets you. The Jobber preset reads Jobber's column names for each.

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, as service due reminders with the plan name, next due date and how many months between visits. No plan billing or invoices are created. Set up billing for a plan in Doing Work if you want it.
• 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, not billing. Keep billing them where they are until you set up billing for each one in Doing Work.
• 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 only. Plan billing has to be set up again in Doing Work.
• No customer financing offers and 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.
• 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

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

1. Click Customers in the left menu.
2. Click Actions on the right, then Export.
3. 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, as service due reminders with the plan name, next due date and how many months between visits. No plan billing or invoices are created. Set up billing for a plan in Doing Work if you want it.
• 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, not billing. Keep billing them where they are until you set up billing for each one in Doing Work.
• 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 only. Plan billing has to be set up again in Doing Work.
• No customer financing offers and 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.

More: Switching to Doing Work, Compare, Onboard a shop.

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

1. Open Search and search for your customers.
2. Click the dropdown next to the search button.
3. 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, as service due reminders with the plan name, next due date and how many months between visits. No plan billing or invoices are created. Set up billing for a plan in Doing Work if you want it.
• 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, not billing. Keep billing them where they are until you set up billing for each one in Doing Work.
• 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 only. Plan billing has to be set up again in Doing Work.
• No customer financing offers and 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.
• Memberships come over as reminders only, 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

Read on November 1, 2026. Workiz changes its screens, so follow the source links if yours look different.

1. Export your data from Workiz

1. Click Reports in the side menu and open the All clients report.
2. Leave the filters empty so every client is included. Add address columns if they aren't shown.
3. 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, as service due reminders with the plan name, next due date and how many months between visits. No plan billing or invoices are created. Set up billing for a plan in Doing Work if you want it.
• 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, not billing. Keep billing them where they are until you set up billing for each one in Doing Work.
• 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 only. Plan billing has to be set up again in Doing Work.
• No customer financing offers and 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.
• Service plans come over as reminders only.

More: Switching to Doing Work, Compare, Onboard a shop.

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, as service due reminders with the plan name, next due date and how many months between visits. No plan billing or invoices are created. Set up billing for a plan in Doing Work if you want it.
• 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, not billing. Keep billing them where they are until you set up billing for each one in Doing Work.
• 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 only. Plan billing has to be set up again in Doing Work.
• No customer financing offers and 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.
• Service agreements come over as reminders only, and the flat rate price book doesn't import.

More: Switching to Doing Work, Compare, Onboard a shop.

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 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

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, as service due reminders with the plan name, next due date and how many months between visits. No plan billing or invoices are created. Set up billing for a plan in Doing Work if you want it.
• 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:

1. Start with the official exports and reports. Every platform has export buttons for customers, jobs and invoices.
2. Use the platform's API or official integration next, with a read-only key if they offer one.
3. Use your own owner login, or a separate team seat you create for your agent. Don't hand over a worker's login.
4. If the account has two-step sign-in, you enter the code.
5. Have your agent read only. It shouldn't edit, delete, send or change settings in the old account.
6. 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

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.list and payouts.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

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.listFeeds and calendar.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

Give each worker the day's stops in order, with directions.

What Doing Work provides

• schedule.route: one worker's visits for a day in time order, with the customer's name, phone and address, a map link per stop and one driving directions link for the first 10 stops.
• visits.update: move a visit. It returns any overlap, time off or outside hours conflict.
• visits.assign: change who is going.
• visits.onTheWay: sends the customer an on-my-way notice with the ETA.

What your agent does

Sends each worker their route and directions link for the day. If you want a better order, it uses a maps tool you choose, shows you the new times, then moves visits in Doing Work.

Paste this into your agent

"Send each worker tomorrow's route. Read https://doingwork.work/docs/agent-guides/route-planning/ first. Use schedule.route for each worker for tomorrow and send them the stops and the directions link. If the order looks wrong, suggest a better one and show me the new times before you change any visit with visits.update."

Limits

• schedule.route keeps the booked order. It doesn't optimize the route.
• The directions link covers the first 10 stops.
• A better order depends on the maps tool your agent uses.

More: Agent guides, Compare.

Payroll with your agent

Carry approved hours to your payroll service.

What Doing Work provides

• payroll.getPeriod and payroll.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

Record a job paid by a financing company.

What Doing Work provides

• invoices.markPaidOutside with method financing: 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

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 or partner with a lender today. The shop sets that up with its own lender.
• Recording it closes the invoice. Only do it once the money has arrived.

More: Agent guides, Compare.

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: Give each worker the day's stops in order, with directions.
• Payroll: Carry approved hours to your payroll service.
• Customer financing: Record a job paid by a financing company.

Sync with QuickBooks

Doing Work doesn't connect to QuickBooks itself. The shop's agent does the sync, on the schedule the shop picks. Daily is a good default.

Each run

• Call sync.changes with the next_cursor you saved last time. The first run can start from updated_since. Page until has_more is false, then save the last next_cursor.
• Each row is one invoice, payment, refund or customer with its current details, so you never replay history.
• If external_refs has a quickbooks id, 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=quickbooks and unsynced=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 is the best way to keep 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 to quotes.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.