How can I connect website enquiries to ServiceM8 or Tradify?
Check your job software’s own enquiry tools first. You may be able to link or embed a native form on your website. If that cannot capture or route the information you need, a custom connection can be considered after checking supported access and permissions.
The result should be one useful enquiry in the right queue. A new website message should not silently become a confirmed job or appointment.
Start with the native option
Tradify documents adding its Website Enquiry Form to a website, with the form link available under its enquiry settings. Review the current instructions and your plan before commissioning a separate integration. Tradify’s website enquiry form guide.
ServiceM8 publishes an API operation for creating a job. That establishes a possible technical building block, not a promise that every website form has a ready-made connection or that a created job will have the right business status. A developer must verify authentication, field requirements and the complete process. ServiceM8’s create-job reference.
Define what a new enquiry should contain
Use this field map as a starting point. Confirm the actual destination fields in your account before building:
- Name: the contact person, kept separate from company name where relevant.
- Reply details: a valid phone number or email and preferred contact method.
- Location: enough information to check your service area.
- Requested work: preserve the customer’s original description.
- Attachments: only if needed, with supported types and access controls.
- Source: which form or page produced the enquiry.
- Tracking reference: a unique submission identifier for detecting retries.
- Next owner: the person or team that reviews new enquiries.
Do not make every field mandatory. Ask only what the next step requires. If someone cannot describe the problem technically, the form should still let them request a callback.
Keep enquiry, quote and booking separate
An illustrative intake sequence is: customer submits the form, the system stores the original request, the office checks fit and availability, then the business quotes or books as appropriate.
The website confirmation should match that sequence: “Your enquiry has been received. We will review it and contact you using the details provided.” Add a response window only if the team can meet it. Do not show “job booked” simply because an API returned success.
Plan for retries and failed connections
Ask the implementer how the original enquiry is preserved if the destination is unavailable. The customer should not have to guess whether to submit again, and staff need a visible queue of items awaiting delivery.
Store the submission reference with the destination result. If an attempt times out after the job system has accepted it, the retry should check for the existing record before creating another one.
Use a documented matching process for existing contacts. Avoid merging records just because names look similar, or creating a new customer every time the same person asks a question.
Run a practical acceptance test
- Submit an ordinary enquiry and find the resulting record.
- Submit using only the permitted minimum contact details.
- Try a suburb outside the service area.
- Submit the same request twice and inspect duplicate handling.
- Simulate the destination being unavailable in a test environment.
- Restore the connection and confirm the preserved enquiry arrives once.
- Check that staff can open any attachments they are authorised to see.
Verify the record, notification and customer-facing confirmation. A form submission is successful only when those parts agree about what happened.
What to prepare before requesting a quote
Bring your website platform, job software and plan, current form, destination queue and a few anonymised examples of enquiries. Include a problematic example, such as an existing customer requesting a change, so the scope accounts for real work.
RightLink can help scope a website-to-job-system workflow. Compatibility and permitted actions should be verified before any implementation commitment.