Scheduling & Booking · Workiz + Claude
Workiz MCP with Claude: Faster Job Scheduling and Dispatch for Service Teams
The short answer
Claude connects to Workiz through the Model Context Protocol, a secure standard that lets Claude read and act within your Workiz account. Once connected, your team can ask Claude to book jobs, update leads, assign technicians and record payments in plain language, with permissions you control and approvals for important actions.
What is Workiz?
Workiz is a field service management platform used by service businesses such as plumbing, HVAC, cleaning, pest control and home repair companies. It helps owners and office staff schedule jobs, track incoming leads, coordinate mobile teams, send invoices and record payments. Dispatchers and business owners use it to keep daily work organised across office and field.
How Claude connects to Workiz through MCP
The Model Context Protocol, or MCP, is an open standard that lets Claude use other software securely. Think of it as a universal adapter between Claude and your tool. Workiz offers an MCP server and a direct API, and this connection is set up using an API key that your organisation controls.
Once connected, Claude can read information such as upcoming jobs, lead details and technician availability. It can also take actions you allow, for example creating a booking, assigning a technician or recording a payment. Access is limited to what you grant, so Claude only works within the permissions you set.
People stay in charge. Consequential actions such as refunds, large invoices or changes to existing bookings can require a team member's approval before they are carried out. Activity is logged, so you can review what Claude did and when.
What you can automate
Booking jobs from plain-language requests
A dispatcher can type or speak a request such as 'book a boiler service for Tuesday morning in the north district'. Claude checks the schedule, proposes a suitable slot and creates the job in Workiz after the dispatcher confirms. This saves time spent switching between screens and reduces double bookings.
Qualifying and managing new leads
When enquiries arrive from web forms, calls or messages, Claude can review the lead details, add notes, tag the service type and update the lead status in Workiz. Sales staff then see a clean, prioritised list. Leads are less likely to be missed during busy periods.
Assigning technicians to the right jobs
Claude can look at which technicians are free, their location and the skills needed for a job. It can suggest an assignment and, once approved, record it in Workiz. Office managers spend less time on manual matching and more time on customer service.
Recording payments and follow-ups
After a job is completed, Claude can help record the payment received and note any outstanding balance. Staff can ask for a summary of unpaid jobs for the week. This supports tidier books and fewer forgotten invoices.
Daily dispatch summaries
Each morning, Claude can produce a summary of the day's jobs, technician assignments and open leads drawn from Workiz. Owners and dispatchers get a clear picture before the first van leaves the depot, which helps prevent last-minute confusion.
An end-to-end workflow: Web enquiry to booked and paid job
TriggerA new enquiry arrives from the company website or a missed call is logged.
Claude reads the enquiry and creates or updates the lead in Workiz with the service type and address.
Claude checks technician availability and suggests the nearest free team member.
A dispatcher approves the suggested booking, and Claude schedules the job in Workiz.
Claude sends the confirmed appointment details to the customer through your existing messaging tool.
After the job is closed, Claude records the payment in Workiz and flags any balance for the accounts team in Microsoft 365.
OutcomeTypically, enquiries are booked faster, fewer leads are lost, and payments are recorded on the same day, giving the office a more accurate view of revenue.
How we set it up
Free automation audit
We review how your team takes enquiries, schedules jobs, dispatches technicians and records payments. We identify the workflows where Claude will save the most time.
Connection design
We set up the connection to Workiz using the API key sign-in method, with least-privilege access so Claude can only do what your workflows need.
Workflow build
We design the end-to-end process across Workiz and your other systems such as Microsoft 365, CRM or accounting software, and agree which actions need human approval.
Testing with real cases
We test the workflows against past jobs and enquiries from your own business to check accuracy before anything goes live.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your dispatchers, office staff and managers on how to use Claude with Workiz day to day.
Who benefits
- Business owner
- Gets a clear daily picture of jobs, leads and revenue without digging through reports.
- Dispatcher or office manager
- Spends less time on repetitive booking and matching, and more time on customer calls.
- Technician coordinator
- Can assign work faster based on availability, location and skills.
- Accounts or finance lead
- Sees payments recorded promptly and outstanding balances flagged early.
Security and control
- Least-privilege API key access, limited to the actions your workflows require.
- Human approval for consequential actions such as refunds, large invoices and changes to existing bookings.
- Audit logs that record what Claude did, when, and on whose instruction.
- Regular review of permissions as your team and processes change.
- Testing against real cases before launch, with monitoring afterwards.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in a region that matches their data expectations. Businesses in India must consider the Digital Personal Data Protection Act, 2023, when handling customer data. Organisations in the UAE and Saudi Arabia must follow their local data protection laws, and we select the hosting region to help meet these requirements. Hosting location is chosen during the audit.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Workiz MCP server do?
The Workiz MCP server acts as a secure bridge between Claude and your Workiz account. It lets Claude read information such as jobs and leads, and take actions you permit, such as scheduling a job or recording a payment. It works through the Model Context Protocol, an open standard, so the connection is structured and controlled.
Is connecting Claude to Workiz secure?
Security depends on how the connection is configured. We use an API key with least-privilege access, so Claude only has the permissions your workflows need. Approvals for important actions and audit logs add further control. We review the setup with your IT team before launch.
What can Claude actually do in Workiz?
Typically, Claude can help schedule and update jobs, manage leads, suggest and record technician assignments, and log payments. It can also produce summaries of the day's work. The exact actions available depend on the Workiz API and the permissions you grant during setup.
How long does setup take?
A typical setup takes a few weeks, from the free audit through testing to launch and training. Simpler workflows can go live sooner, while larger operations with several systems take longer. We agree a timeline after the audit.
What Workiz plan or permissions are needed?
You need an active Workiz account with API access enabled and an API key generated for the connection. The specific plan requirements depend on your Workiz subscription, so we confirm this with you during the free audit.