
ServiceM8
Homeowners call asking about their plumber's arrival time. Business clients want invoice details. Your AI agent connects to ServiceM8, pulling live job status, client records, and payment information so every inquiry gets an immediate, accurate answer without dispatchers picking up the phone.




Your AI agent accesses ServiceM8's job management, client records, and payment data to answer field service inquiries and automate scheduling conversations.
ServiceM8
See how trade businesses use AI agents connected to ServiceM8 to handle customer inquiries, schedule jobs, and keep field teams informed without office staff involvement.
A homeowner messages at 10 PM about a burst pipe. Your AI Agent asks for the address and problem details, confirms the emergency, and creates a new urgent job in ServiceM8 with all the details. The on-call plumber sees the job on their mobile app immediately. The homeowner gets confirmation without waiting until morning to reach the office.
A client texts 'Is the electrician still coming today?' Your AI Agent pulls the job from ServiceM8, checks the current status and time slot, and responds with the technician's expected arrival window. If the job is running late, the agent explains the delay. The customer feels informed, and your dispatcher handles one fewer phone call.
A customer asks 'Did my payment for the air conditioning repair go through?' Your AI Agent retrieves the job payment record from ServiceM8, verifies the amount and payment method, and confirms the transaction. The customer gets peace of mind, and your bookkeeper does not field unnecessary payment confirmation calls.

ServiceM8
FAQs
The agent uses ServiceM8's job listing API with filter parameters. It can search by job status, date, client UUID, or description text. When a customer asks about their service call, the agent matches by their contact details or job reference to find the right record.
Yes. The agent can create a new job in ServiceM8 even for first-time customers. It captures the address, description, and contact information during the conversation and creates the job record with the appropriate status. Client records can be created or linked afterward.
Tars requests read and write OAuth scopes from ServiceM8. Read access is needed for job lookups, client details, and payment records. Write access enables job creation, note adding, and payment recording. You authorize these through the standard ServiceM8 OAuth flow.
The agent creates jobs with specific statuses that control their placement on the ServiceM8 dispatch board. Setting a job to 'Work Order' puts it in the queue, while 'Quote' keeps it in the quoting stage. Your existing dispatch workflow continues to work with AI-created jobs.
No. Tars queries ServiceM8 in real time during conversations. Client names, addresses, job details, and payment information are fetched live and used only for the current response. No ServiceM8 data is stored in a separate Tars database.
ServiceM8's online booking is a form-based process. Tars AI Agent has a conversation, asking follow-up questions to understand the issue, collecting the right details, and even providing preliminary pricing or availability before creating the job. It works on WhatsApp, SMS, and web, not just your booking page.
The agent can create and update job notes in ServiceM8 through the API. When a customer provides additional details or special instructions during a conversation, the agent attaches them to the correct job. Photo uploads require the file attachment API which is available for supported formats.
You train the agent on your specific services during setup. If a customer requests something outside your scope, the agent politely explains your service offerings and can suggest alternatives. It only creates ServiceM8 jobs for services you actually provide.
Don't limit your AI Agent to basic conversations. Watch how to configure and add powerful tools making your agent smarter and more functional.

Privacy & Security
At Tars, we take privacy and security very seriously. We are compliant with GDPR, ISO, SOC 2, and HIPAA.