Cleaning Business Enquiry Pipeline: Stages and Next Actions

Start with one list your team can actually use

Choose where the enquiry record lives. Notifications can alert you, but the record should still be findable if an email is missed. If requests arrive through several channels, agree who adds them to that list and how they check for an existing request.

Use a reference for each job enquiry. One person may ask about two different properties; two messages may concern the same job. Review the context before combining records. Keep contact details in your approved system, and use references rather than personal information in shared marketing reports.

• Plan the information your quote request form needs

Use stages that tell you what needs to happen

Start with the stages below and remove any your process does not need. The stage describes the current situation; the next action describes the work. A card labelled “Waiting for customer” still needs an owner and a review date.

Use “Work agreed” only when your actual acceptance process is complete. An enquiry receipt, email open or quote sent is not proof of an accepted job. Scheduling, service delivery and payment can remain in their own records.

Keep the record short enough to maintain

Every field should support a decision or handoff. Start with the enquiry reference, arrival date and source, service and suburb, stage, owner, next action and due date. Link to the current quote or correspondence instead of copying every message into a second place.

A source such as “website” is useful even when you cannot identify the campaign. Keep an unknown source unknown. A person who clicked a guide has not necessarily requested help, and a saved request has not necessarily been reviewed as suitable.

Enquiry reference:
Received at / source:
Service / suburb:
Current stage:
Owner / absence cover:
Latest relevant customer response:
Next action / due date:
Quote or agreement reference, if applicable:
Reason closed, if applicable:
Any request to stop or defer contact:

Follow one fictional enquiry through the board

Imagine a team that offers regular home cleaning in Brunswick. A new request asks for cleaning in Brunswick but does not say whether it is a one-off or recurring job. Those service details are invented for this example; use your actual coverage and scope.

The owner checks the request and moves it to “Clarification needed”, with the action “Ask whether the customer needs a one-off or recurring clean”. When the customer replies, the owner updates the record before deciding what comes next. If the service fits, the team prepares its quote or assessment. If it does not, the owner explains that and closes the enquiry with a reason.

Once a quote is issued, record which version the customer received. If they later accept it, complete your acceptance checks and hand over the agreed work. If they ask you to wait, record that instruction and change the next action. The board should follow the conversation, not keep sending a sequence that no longer fits.

• Choose a reply for the current enquiry state

Make absence and missed notifications manageable

Choose a backup who can see the information needed to take over. Before an absence, review open actions together and confirm who will reply. A shared inbox with no assignment can still leave everyone expecting someone else to act.

During staffed hours, compare new saved requests with the unassigned queue. If a notification fails, work from the saved record and repair the alert. Before retrying a message or recreating a request, check whether it already succeeded. Keep recovery steps small enough that the next person can follow them.

Review the queue before increasing traffic

Choose a regular review with the person handling replies. Look first for open requests with no owner, no next action or an overdue action. Then review why enquiries closed. A repeated service-area mismatch suggests a different fix from quotes waiting on a missing detail.

Count real enquiries separately from spam, duplicates and QA. Define “suitable” using your service, coverage and capacity criteria. Keep enquiries received this week separate from older jobs agreed this week: dividing those two totals can produce a misleading conversion rate.

If you compare outcomes, follow requests received in the same period and show how many remain open at the review date. There is no universal win-rate target in this guide. Use the review to choose one problem to address, then look again after the change.

Period reviewed / review date:
Valid new enquiries (exclude QA, spam and duplicates):
Source unknown:
Open requests with no owner:
Open requests with no next action or overdue action:
Requests from this period reviewed as suitable:
Requests from this period with work agreed:
Requests from this period still open:
Most common evidenced closure reason:
One change to make / owner / review date:

Use the workflow to decide whether you need software

If your current process reliably shows the next action and supports absence cover, keep that working foundation. Consider a different tool when a recurring problem is clear: requests cannot be found, handoffs are missed or staff repeatedly copy the same information.

Give a supplier this board and ask them to demonstrate one sample request, one duplicate and one reassignment using the plan you would buy. Record manual steps and unanswered requirements. A proposed customer workflow can help you explain the job; it does not prove a feature or a measured business result.

• Use the CRM demo checklist and decision scorecard
• Explore the proposed Cleaningly enquiry-to-contract workflow