Enquiry management for tradies is the controlled process of capturing a potential customer’s request, recording the information needed to assess it, assigning responsibility, progressing it through quoting and follow-up, and recording whether it became a booked job.
That definition matters because receiving an enquiry is not the same as managing one. A phone call written on a scrap of paper, a Facebook message left unread and a quote stored in an email thread are three separate conversations. They do not form a sales system until each has an owner, a status, a next action and a measurable outcome.
More visibility can create more calls and forms, but marketing cannot recover an enquiry that was never recorded, qualified or followed up. An apparent lead-generation problem may therefore be an operational loss after contact.
This guide develops an enquiry-management system for Australian service-area trades. It covers the path from first contact to booked work, including operational, measurement, software, privacy and follow-up decisions.
How We Researched This Guide
We reviewed the enquiry journey from three perspectives rather than relying on one software vendor or a single marketing statistic.
First, we examined Australian government guidance covering customer relationship management, digital tools, personal information and commercial electronic messages. These sources include the Australian Government’s business.gov.au guidance on managing customer relationships, the Office of the Australian Information Commissioner’s small-business privacy guidance, and the Australian Communications and Media Authority’s Spam Act guidance.
Second, we reviewed the public workflows and feature descriptions of trade-focused job-management platforms, including Tradify, ServiceM8, Fergus and NextMinute. The aim was not to name a universal “best” product. We looked for the recurring operational entities these platforms connect: enquiries, customer records, estimates, quotes, schedules, jobs, invoices, payments, notes and reporting.
Third, we mapped those entities against the measurement path used in our SEO for tradies work:
search visibility → qualified visit → customer action → sales opportunity → booked job
The resulting model is our interpretation, not a survey of every Australian trade business. Vendor performance claims remain attributed to their vendors.
Why Enquiry Management Is a Business System, Not an Inbox Task
Enquiry management sits inside the broader trade-business operating system. Its upstream inputs are marketing, referrals, repeat customers and existing contracts. Its downstream outputs are site visits, quotes, scheduled work, invoices and revenue.
The system has five functions:
- Capture: create one record for every legitimate request.
- Qualification: decide whether the work fits the services, area, timing, value and capacity of the business.
- Progression: move the opportunity through contact, inspection, estimating, quoting and decision.
- Communication: keep the customer informed and make the next step clear.
- Measurement: record the source, quality, outcome and reason for loss.
Most breakdowns can be traced to one of these functions. A missed call without a callback process is a capture failure. Driving across town for a job outside the service area is a qualification failure. Sending a quote without a follow-up date is a progression failure. Leaving a customer unsure whether a technician is coming is a communication failure. Counting every form submission as a successful lead is a measurement failure.
Australia also has a large and changing business population. The Australian Bureau of Statistics recorded 2,814,778 actively trading businesses at 30 June 2026, with 460,461 entries and 375,331 exits during 2025–26. Those economy-wide figures do not measure enquiry handling, but they show why local operators cannot assume that being available is enough. Customers often have alternatives, and new competitors continue to enter the market. ABS, Counts of Australian Businesses, 2025–26
Every enquiry should reach a controlled process. It may live in a spreadsheet for a sole trader or a job-management platform for a multi-crew operation. The tool changes; the required states do not.
The Enquiry Lifecycle: From First Contact to Final Outcome
An enquiry lifecycle is the ordered set of states through which a potential job moves. Each state should describe what happened rather than use a vague label such as “warm lead.”
A useful base lifecycle is:
| Stage | Meaning | Required next action |
|---|---|---|
| New | Request received but not assessed | Review and acknowledge |
| Contact attempted | Customer has not yet been reached | Set callback time |
| Contacted | Two-way communication established | Collect missing details |
| Qualified | Job fits defined acceptance rules | Arrange next commercial step |
| Site visit required | Inspection is needed before pricing | Schedule and confirm visit |
| Quote in preparation | Scope is known and estimate is being built | Assign quote due date |
| Quote sent | Customer has received the offer | Schedule follow-up |
| Decision pending | Customer is considering the quote | Follow agreed cadence |
| Won | Customer accepted | Convert to scheduled job |
| Lost | Customer declined or chose another provider | Record reason |
| Disqualified | Enquiry does not fit | Record reason and close |
| No response | Contact attempts completed | Close or place in permitted nurture |
These stages reveal whether the backlog consists of untouched enquiries, overdue quotes or customers awaiting follow-up. Add a status only when it changes ownership, required information, communication or the next action.
Emergency, routine and project enquiries need different paths
One lifecycle cannot impose the same timing on every job type. A burst pipe, power failure, roof leak or lockout may require immediate triage. A switchboard upgrade or air-conditioning installation may need photographs and a site visit. A renovation or commercial maintenance contract may involve plans, multiple stakeholders and a longer estimating process.
The parent entity is still enquiry management, but the child workflows differ:
- Emergency service: availability check → safety questions → address → dispatch or decline.
- Routine service: problem details → service-area check → estimate or booking → confirmation.
- Quoted installation: requirements → photos/site visit → estimate → quote → follow-up.
- Large project: fit check → documents → consultation → scope → staged proposal → decision.
- Commercial account: site and asset details → authority and terms → inspection → formal quote or work order.
This is why local SEO for tradies should map different search intentions to suitable pages and actions. An emergency visitor needs a fast call path and clear operating area. A project buyer needs evidence, scope details and a quote pathway. Both may become enquiries, but they should not enter identical intake forms.
Where Tradie Enquiries Enter—and Where Context Gets Lost
Enquiries arrive through channels, but channels are not the system of record. A system of record is the single place the team trusts for the current status, owner and next action.
Common entry points include:
- direct phone calls and missed calls;
- website quote and contact forms;
- Google Business Profile calls and website actions;
- email;
- SMS;
- Facebook, Instagram and WhatsApp messages;
- online booking forms;
- lead platforms;
- builder, strata or property-manager work orders;
- supplier and professional referrals;
- repeat customers; and
- walk-ins or conversations on site.
The danger is not simply having many channels. The danger is leaving each enquiry inside the channel where it arrived. When that happens, an office administrator may see an email while the owner holds the phone conversation and a technician receives the customer’s photo by SMS. No person sees the complete record.
The capture rule should therefore be:
Every legitimate enquiry receives one record, one current owner, one current stage and one next-action date, regardless of its source.
This does not require a complicated integration on day one. A sole trader can enter missed calls and form submissions into a simple register each morning and afternoon. A larger team may automate form, call and advertising data into its CRM. The standard is consistency, not software complexity.
Acknowledgement is not the same as resolution
An automated reply can confirm that a message arrived and set an expectation. It cannot determine whether the requested work is safe, feasible, profitable or within the service area unless the necessary rules and information are present.
A useful acknowledgement states:
- that the request was received;
- when a human response should be expected;
- what urgent customers should do;
- which missing information can speed up assessment; and
- the business identity and contact details.
Avoid promising “we will be there today” before availability and location are checked. The purpose of acknowledgement is to reduce uncertainty while the enquiry enters the qualification process.
What Information Should a Tradie Capture?
Capture only information that helps the business decide, act, communicate or measure. Long forms can create friction, while short forms can force repeated calls and make qualification impossible.
A minimum enquiry record normally needs:
| Field group | Example fields | Operational purpose |
|---|---|---|
| Identity | Name, business name, preferred contact | Know who is requesting work |
| Contact | Phone, email | Respond and confirm details |
| Location | Suburb, postcode, site address when needed | Check coverage and travel |
| Service | Requested service, problem or project | Route to the right person |
| Timing | Emergency, desired date, deadline | Assess urgency and capacity |
| Property/job context | Residential, commercial, strata, construction site | Apply the right workflow |
| Evidence | Photos, plans, model numbers, access notes | Improve remote assessment |
| Source | Organic search, Maps, ads, referral, repeat client | Measure acquisition channels |
| Consent/preferences | Contact permission and preferred channel | Communicate appropriately |
| Workflow | Owner, stage, next action, due date | Prevent inactivity |
| Outcome | Won, lost, disqualified and reason | Learn what happened |
Some trades need additional fields. An electrician may ask about the fault, switchboard and immediate safety risk. A roofer may need roof type, storeys, access and leak location. An HVAC business may need system type, brand and fault code. A builder may need project type, plans, budget readiness, approvals and expected start date.
The form should not attempt to replace professional diagnosis. Its role is to collect enough context to select the correct next step.
Separate customer statements from your assessment
“Hot-water system is leaking” is the customer’s statement. “Qualified emergency replacement” is the business’s assessment. Store them separately.
Mixing the two creates reporting errors. A customer may describe an issue incorrectly, and the job type may change after inspection. Retaining the original request alongside the assessed service helps staff understand the conversation and helps marketers see whether the landing page attracted relevant demand.
Qualification: Decide Which Enquiries Deserve Which Action
Qualification is not a method for dismissing small jobs indiscriminately. It is a consistent decision about fit and next action.
A practical qualification framework uses six dimensions:
1. Service fit
Does the business perform the requested work? “Plumber” does not mean every plumber clears sewers, installs gas appliances, handles roofing drainage and accepts commercial maintenance. The service list used by the website, Google Business Profile, advertising and intake team should describe the same real capability.
2. Geographic fit
Is the site inside the genuine operating area? Check distance, travel time, call-out economics, crew location and any border or licence limitations. A lead can match the service yet remain commercially unsuitable because of travel.
3. Timing and capacity
Can the team meet the required time? An honest decline or alternative timeframe is better than accepting an urgent enquiry that cannot be serviced. Capacity rules may differ by crew, job type and season.
4. Job value and commercial fit
Does the opportunity meet the minimum call-out, project size or contract type the business accepts? Value should not be guessed from postcode or customer tone. Use observable attributes such as scope, property type, likely labour, materials and procurement process.
5. Authority and readiness
Is the person authorised to approve the work or gathering information for somebody else? Has a planned-project customer supplied the information needed for a meaningful estimate? A low-readiness prospect may still be valuable, but the next step may be education or document collection rather than an immediate site visit.
6. Risk and feasibility
Are there safety, access, insurance, payment, compliance or scope risks? The intake process should escalate questions that require a licensed practitioner or manager rather than letting an administrator make a technical promise.
The output should be a route, not merely a score. A qualified emergency call goes to dispatch. A qualified project goes to estimating. An out-of-area customer receives a clear decline or referral where appropriate. An incomplete request receives a list of required details.
Ownership and Response Standards Prevent Silent Failure
An enquiry without an owner belongs to nobody. “The office will handle it” is not ownership unless one named role is accountable for checking the queue, making contact and changing the status.
Define ownership at each stage:
| Stage | Typical owner | Completion condition |
|---|---|---|
| New enquiry | Intake/admin | Acknowledged and assessed |
| Technical qualification | Supervisor or licensed person | Correct route confirmed |
| Site visit | Assigned estimator/technician | Findings recorded |
| Quote preparation | Estimator | Quote approved and sent |
| Quote follow-up | Sales/admin/owner | Decision or next date recorded |
| Won work | Scheduler | Job date and resources confirmed |
Response standards should also reflect intent. Instead of copying an unsupported universal rule such as “all leads must be answered within five minutes,” set standards the business can deliver and test. An example internal standard might require emergency calls to be triaged during advertised hours, all other new enquiries to be acknowledged the same business day, and every quote to leave the system with a scheduled follow-up.
Measure actual performance before tightening the target. If the target says 15 minutes but the median response is three hours, the gap is operational. If the team meets the target but few contacts become qualified opportunities, traffic relevance, targeting or intake questions may be the larger problem.
Quoting Is a Stage, Not the End of the Process
A quote represents a proposed exchange: defined work under defined conditions for a defined price. It does not represent a completed sales outcome.
Before sending, the quote should align with the enquiry record. Confirm the customer, site, scope, exclusions, assumptions, price basis, validity, payment terms, scheduling conditions and acceptance method. For larger work, explain variations and dependencies in language the customer can understand.
After sending, record:
- date and delivery channel;
- quote value or value band;
- responsible owner;
- expected decision timeframe;
- next follow-up date;
- customer questions or objections;
- acceptance, loss or delay; and
- loss reason where known.
Trade platforms increasingly connect these stages. Tradify publicly describes a path from enquiries to quotes, jobs and invoices, including automated email and SMS quote follow-ups. ServiceM8 describes managing work from the first call through scheduling, quoting, completion, invoicing and payment. Fergus presents an enquiry-to-invoice workflow with job cards holding quotes, notes, tasks and customer details. These observations show a shared product model; they do not prove that buying software automatically improves conversion. Tradify · ServiceM8 · Fergus
The operational lesson is that quoting belongs inside the same customer and job record. When estimating occurs in one tool and follow-up lives in somebody’s memory, the workflow breaks at its most commercially important point.
Follow-Up Should Create a Decision, Not Harass the Customer
Follow-up is a planned request for the next decision. It may confirm receipt, answer a question, revise scope, schedule a later conversation or close the opportunity.
The cadence should reflect the job:
- An emergency customer may choose within minutes and no longer be available later.
- A routine repair quote may need a short confirmation and one or two follow-ups.
- A renovation or commercial proposal may require stakeholder review over weeks.
- A seasonal replacement may be delayed until budget or weather conditions change.
Avoid sending the same automated sequence to all four. Automation should carry context, not erase it.
A practical follow-up record includes the last meaningful contact, the customer’s stated timing, the next agreed action and a stopping condition. “Follow up next week after strata meeting” is more useful than “send reminder three.”
Closed-lost reasons should be specific enough to guide a decision:
- chose another provider;
- price outside budget;
- timing unavailable;
- work postponed;
- no decision/no response;
- service mismatch;
- outside service area;
- duplicate or spam;
- customer completed work themselves; or
- unknown.
Do not treat “lost on price” as fact unless the customer said so. Guessing turns reporting into folklore.
Follow-up messages have legal boundaries
Operational messages about an active enquiry are not automatically the same as adding the person to a promotional list. Australian businesses should distinguish requested communication from marketing.
ACMA states that commercial electronic messages generally require consent, sender identification and a working unsubscribe method. It also warns that automatically adding someone to a marketing list merely because they submitted an enquiry may breach consent requirements. This guide is not legal advice, but the workflow implication is clear: store contact purpose and marketing permission separately. ACMA spam guidance and ACMA guidance on common e-marketing mistakes
Spreadsheet, CRM or Job-Management Software?
The correct tool is the simplest system that preserves the required information and remains reliable at the business’s actual volume and complexity.
A spreadsheet can work when the workflow is small
A controlled spreadsheet may suit a sole trader or small office receiving a manageable number of enquiries. It can store source, service, suburb, stage, owner, next action, value and outcome.
Its weakness appears when several people edit records, conversations occur across devices, reminders are missed, documents detach from records or the same customer creates multiple jobs. A spreadsheet is not automatically amateur; an uncontrolled spreadsheet is.
A CRM focuses on relationships and opportunities
A customer relationship management system records contacts and interactions with customers. Australian Government guidance notes that CRMs can record customer contacts and help businesses manage relationships, with cloud products commonly offering tiered or pay-as-you-go structures. business.gov.au digital tools guidance
A CRM may suit a trade business with longer sales cycles, commercial accounts, multiple decision-makers or dedicated sales activity. Check whether it also handles job scheduling and field operations or must integrate with another platform.
Job-management software connects the opportunity to delivery
Job-management platforms usually extend beyond lead handling into quoting, scheduling, field notes, time, materials, forms, invoicing and payment. This can reduce duplicate entry because the accepted enquiry becomes the job record.
However, feature quantity is not the selection criterion. Evaluate:
| Decision factor | Question to test |
|---|---|
| Workflow fit | Can it represent your real enquiry types and stages? |
| Field use | Can technicians update the record easily on site? |
| Channel capture | Which calls, forms, emails and messages enter automatically? |
| Quoting | Does it support your scope, approvals and follow-up process? |
| Scheduling | Can it handle crews, skills, locations and urgent work? |
| Integrations | Does it connect to accounting, calendars, forms and marketing data? |
| Reporting | Can you report source through qualified, quoted, won and lost? |
| Data access | Can you export customers, jobs and history if you leave? |
| Security | Are access controls, backups and staff permissions suitable? |
| Adoption | Can the team use it correctly during a normal workday? |
| Cost | What is the total cost including setup, migration, training and add-ons? |
Software cannot repair an undefined process. If nobody agrees what “qualified” means, a CRM will produce inconsistent qualified records faster. Define the states, rules and owners first; configure the product second.
Privacy and Customer Information Require Deliberate Handling
An enquiry record may contain names, phone numbers, email addresses, site addresses, access information, photographs and notes. That information should not be copied across uncontrolled personal devices and inboxes without thought.
The OAIC explains that most small businesses with annual turnover of $3 million or less are not covered by the Privacy Act, but some are covered because of the activities they conduct, and larger organisations generally have obligations. Coverage should be checked rather than assumed. Where the Australian Privacy Principles apply, entities must take reasonable steps to protect personal information from misuse, interference, loss and unauthorised access, modification or disclosure. OAIC small-business guidance · OAIC guide to securing personal information
Practical controls include collecting only necessary data, explaining why it is required, restricting access by role, using individual logins and multi-factor authentication, securing photos and access codes, removing departing staff, and checking how connected vendors store data. Privacy therefore affects intake forms, permissions, integrations and follow-up lists.
The Metrics That Reveal Where Enquiries Are Being Lost
A useful report follows the funnel instead of combining every stage into “leads.”
Enquiries received
Count legitimate new requests, then separate spam, job applications, supplier messages and duplicates. Keep channel and campaign source where technically available.
Contact rate
Contact rate = enquiries with two-way contact ÷ legitimate enquiries × 100
If 80 legitimate enquiries arrive and the team speaks or exchanges meaningful messages with 60, the contact rate is 75%. This is a calculated example, not an industry benchmark.
Qualification rate
Qualification rate = qualified opportunities ÷ contacted enquiries × 100
If 45 of the 60 contacted enquiries match the business’s services, area and commercial rules, the qualification rate is 75%. A low rate can signal irrelevant marketing, unclear website information, overly broad service areas or restrictive acceptance rules.
Quote or booking rate
For bookable work:
direct booking rate = booked jobs ÷ qualified opportunities × 100
For quoted work:
quote rate = quotes sent ÷ qualified opportunities requiring quotes × 100
Do not penalise a workflow because emergency jobs book directly while projects require proposals. Segment by enquiry type.
Quote acceptance rate
quote acceptance rate = accepted quotes ÷ decided quotes × 100
Using decided quotes avoids temporarily treating every open proposal as a loss. Also report the value of accepted quotes because ten minor repairs and one commercial contract are not economically equivalent.
Time-to-first-response and time-in-stage
Time-to-first-response measures the interval from receipt to the first meaningful human response. Time-in-stage measures how long a record remains in states such as “quote in preparation” or “decision pending.”
Medians are often more informative than averages because one forgotten enquiry can distort the mean. Report the percentage that met the internal standard as well.
Cost per qualified enquiry and booked job
cost per qualified enquiry = channel cost ÷ qualified enquiries attributed to that channel
cost per booked job = channel cost ÷ booked jobs attributed to that channel
Attribution has limits. A customer may discover the business through Google, return through a branded search and call from the profile. Use call tracking, form data, analytics and customer confirmation together where practical; do not pretend the tracking is more exact than it is.
This is also why Google Ads for tradies should not be assessed only by form volume. Paid campaigns need feedback about location, requested service, qualification, quote status and booked outcome. Otherwise the platform may optimise toward easy form completions rather than commercially useful work.
Use the Funnel to Diagnose Marketing and Operational Problems Separately
The same symptom—too few booked jobs—can have different causes.
| Funnel pattern | Likely investigation |
|---|---|
| Low visibility and few enquiries | Search presence, demand, targeting and competition |
| Traffic but few calls/forms | Page intent, offer, trust, usability and contact path |
| Many enquiries but low qualification | Keyword targeting, service messaging, area and form design |
| Qualified enquiries but few quotes | Capacity, inspection and estimating process |
| Quotes sent but few decisions | Follow-up, scope clarity, price, proof and timing |
| Jobs won but low profit | Estimating, job costing, variation control and delivery |
An SEO audit for tradies can inspect visibility, landing pages and tracking, but the business must supply or record downstream outcomes to distinguish a search problem from a sales-process problem.
This boundary matters. SEO can improve the relevance of search traffic, clarify services, strengthen local visibility and make calls or forms easier. It cannot force the office to answer, make an estimator issue a quote or create crew capacity. Conversely, perfect enquiry handling cannot compensate for a website that attracts people outside the service area or for work the business does not perform.
A Practical 30-Day Implementation Plan
During days 1–5, list every phone number, form, email address, social account, booking tool and lead platform. Submit test forms, trace notifications and check missed-call and after-hours behaviour. Create one temporary register if no reliable system exists.
During days 6–10, document accepted services, service areas, operating hours, minimum job rules, emergency definitions and escalation points. Adopt a short lifecycle and define what must be true before a record advances.
During days 11–15, assign named roles to intake, technical questions, site visits, quotes and follow-up. Create visible overdue queues and realistic response standards based on urgency and staffed hours.
During days 16–20, prepare acknowledgement, information-request, booking-confirmation, quote-follow-up and polite-decline templates. Check consent, sender-identification and unsubscribe requirements before adding promotional nurture.
During days 21–25, add source fields and preserve campaign information. Test the complete path from search result or advertisement to the enquiry record. Review your tradie website design and remove form fields nobody uses while adding details needed for qualification.
During days 26–30, report legitimate enquiries, contacted, qualified, quoted, won, lost and open. Segment by service, area and source. The first report should expose missing data and bottlenecks; it is too early to claim channel ROI from a small sample.
Common Enquiry-Management Mistakes
Do not report every form as a qualified lead. A form is an action; qualification requires service, area and commercial fit. Do not allow the phone, inbox, technician’s notes and spreadsheet to become competing records. Customers then repeat themselves while staff reconstruct the conversation.
Do not optimise response time in isolation. A fast reply to unsuitable work creates no revenue. Measure contact, qualification, quote and booking outcomes alongside speed. Define exceptions before automating because emergency, high-risk, commercial and out-of-area enquiries need different handling.
Software also fails when staff keep using personal messages, omit next-action dates or close lost jobs without reasons. Finally, do not hide operational loss inside marketing reports. If 50 relevant enquiries arrive but only 20 receive quotes, investigate the missing 30 before buying more traffic.
What Good Enquiry Management Looks Like
Good enquiry management is observable. Every legitimate request has a record. Staff can see who owns it, what the customer needs, whether the work fits, what happens next and when that action is due. Quotes do not disappear after sending. Lost work produces a reason rather than a guess. Marketing reports extend beyond clicks and forms when downstream data is available.
The system does not need to be elaborate. It needs to be complete enough for the business’s enquiry volume, job types and team structure.
For marketing, the most important change is feedback. When SEO, Google Maps, advertising and website pages can be evaluated against qualified enquiries and booked work, the business can distinguish visibility from commercial performance. That is the point at which “more leads” becomes a measurable question rather than a standing assumption.
If your website attracts the wrong jobs, leaves important actions untracked or makes it difficult for customers to enquire, request a tradie SEO audit. The audit should identify the visibility, intent, page and tracking gaps upstream of your internal enquiry process.
Frequently Asked Questions
What is enquiry management for tradies?
Enquiry management for tradies is the process of capturing customer requests, checking whether the work fits, assigning responsibility, progressing the opportunity through booking or quoting, following up and recording the final outcome. It connects marketing activity to the operational steps that create booked jobs.
Does a sole trader need a CRM?
Not always. A controlled spreadsheet or job-management app may be enough when enquiry volume is low and one person owns the process. A CRM becomes more useful when opportunities involve longer sales cycles, several contacts, multiple staff or complex follow-up.
Which enquiry stages should a trade business use?
A practical starting set is new, contact attempted, contacted, qualified, site visit required, quote in preparation, quote sent, decision pending, won, lost, disqualified and no response. Remove stages that do not change the next action and add specialist stages only where the workflow requires them.
How quickly should tradies respond to enquiries?
There is no single response time suitable for every trade and job. Emergency calls require faster triage than planned projects. Set standards by enquiry type, advertised hours and capacity, then measure actual time-to-first-response and the percentage meeting the standard.
What should be tracked for each enquiry?
Track customer contact details, suburb or site, requested service, urgency, property or project type, source, owner, stage, next action, quote or booking status, outcome and reason for loss. Add trade-specific information only when it supports assessment or delivery.
Can SEO improve enquiry quality?
SEO can improve enquiry quality by aligning pages with specific services, locations and customer intentions. It cannot determine final quality alone. Availability, pricing, qualification rules, customer expectations and enquiry handling also affect whether a search-generated contact becomes suitable work.
How do you measure whether enquiry management is working?
Measure legitimate enquiries, contact rate, qualification rate, quote or direct-booking rate, quote acceptance, response time, time in stage, lost reasons, cost per qualified enquiry and cost per booked job. Segment results by service, area and source to avoid misleading averages.
