WHAT HAPPENS AFTER SEND? CLEANING ENQUIRY HANDOFF CHECKLIST Copy or print this worksheet. Complete it with the person who answers quote requests. Use one sheet for the setup and one handoff card for each request. The examples are planning aids, not customer results or claims about a particular product. Business: __________________________ Date: __________________________ Website/form: ______________________ Reviewed by: ___________________ 1. MAKE THE FIRST DECISION CLEAR This form is for: ___________________________________________________ The next decision is: _______________________________________________ Our services and coverage are: ______________________________________ Submitting the form does this: ______________________________________ A quote is confirmed by: ____________________________________________ An appointment is confirmed by: _____________________________________ [ ] The button describes the actual action: request, assessment or booking. [ ] The page explains service and coverage before asking for a request. [ ] Each required answer changes a decision we need to make now. [ ] We ask for one usable reply route and respect the chosen channel. [ ] Optional fields are visibly optional. [ ] We ask for the location detail needed now; further address details wait until needed. [ ] The open text box tells people to leave out keys, entry codes, payment details and private documents. [ ] The explanation of information handling matches our actual process and links to current privacy information. Field we may remove or ask later: ___________________________________ Reason: ____________________________________________________________ 2. GIVE THE ENQUIRY SOMEWHERE TO GO Requests are saved in: ______________________________________________ The person checking new requests is: ________________________________ They check during these working hours: ______________________________ Absence cover: ______________________________________________________ Response expectation this person has accepted: ______________________ We tell visitors about closed days as follows: ______________________ If notifications fail, requests can be found here: ___________________ How an unassigned request becomes visible: __________________________ Who can access the information: _____________________________________ Who removes test/unneeded records under our process: ________________ [ ] A saved request can be found without relying on an email alert. [ ] The reply owner and absence cover can access the record they need. [ ] Receipt acknowledgement and first human reply are recorded separately. [ ] The visitor sees a saved confirmation only after saving is confirmed. [ ] A failed or uncertain submission gives a working alternative contact route. [ ] No quote or appointment is implied before our actual agreement steps are complete. 3. COPY THIS HANDOFF CARD FOR A REQUEST Keep this card in your approved record system, not a public document. Use a request reference where possible and avoid copying unnecessary personal information. ENQUIRY HANDOFF Request reference: ______________________________________ Received date/time and zone: ____________________________ Service and area: _______________________________________ Customer's requested channel/time: ______________________ Latest event: ___________________________________________ What we know: ___________________________________________ One detail still needed, if any: ________________________ Current stage: [ ] Saved, awaiting review [ ] Awaiting clarification [ ] Assessment being arranged [ ] Quote sent [ ] Arrangement confirmed through our actual process [ ] Closed: declined / not a fit / no response / other Next action: ____________________________________________ Owner: __________________________________________________ Due at the agreed point: ________________________________ Cover if owner is unavailable: __________________________ Last human reply and channel: ___________________________ Any queued reminder: ____________________________________ Keep / change / cancel reminder because: _________________ Test or duplicate? If yes, mark and exclude from totals: _ Outcome and reason when known: __________________________ 4. CHECK BEFORE THE NEXT MESSAGE [ ] I have read the latest conversation, including calls or messages handled by someone else. [ ] This message matches what has actually happened. [ ] I am asking a necessary question that has not already been answered. [ ] The channel and timing match what the customer requested. [ ] The customer has not replied, booked, declined or asked us to stop since the message was prepared. [ ] Any quote, price, scope or availability mentioned is current and checked. [ ] Every placeholder is replaced; a real person owns the response. [ ] There is no duplicate message waiting or already sent. [ ] A delivery failure goes to an owner for review, rather than an endless retry. If one of these is unresolved, next action and owner: ________________ ____________________________________________________________________ 5. REHEARSE BEFORE INVITING ENQUIRIES Use a local or staging form, synthetic details and an agreed test destination. Ask the form owner to arrange technical failure simulations safely. Do not experiment with genuine customer requests. Environment / form version: _________________________________________ Test reviewer and date: _____________________________________________ Device / browser: ___________________________________________________ Synthetic request reference: ________________________________________ [ ] Form is readable and usable on a phone and with a keyboard. Observed result / evidence: ______________________________ Fix owner / next step: ___________________________________ [ ] Missing required information produces a clear field error and keeps other answers. Observed result / evidence: ______________________________ Fix owner / next step: ___________________________________ [ ] An out-of-area request is explained or clearly sent for coverage review. Observed result / evidence: ______________________________ Fix owner / next step: ___________________________________ [ ] The saved confirmation matches an actual stored record. Observed result / evidence: ______________________________ Fix owner / next step: ___________________________________ [ ] The assigned person can find the saved record. Observed result / evidence: ______________________________ Fix owner / next step: ___________________________________ [ ] The absence cover can identify the latest conversation and next action. Observed result / evidence: ______________________________ Fix owner / next step: ___________________________________ [ ] A safely simulated repeated submit/retry does not cause duplicate follow-up for the same request. Observed result / evidence: ______________________________ Fix owner / next step: ___________________________________ [ ] A safely simulated failed notification still leaves the saved request accessible. Observed result / evidence: ______________________________ Fix owner / next step: ___________________________________ [ ] A customer reply through another channel causes the obsolete reminder to be cancelled. Observed result / evidence: ______________________________ Fix owner / next step: ___________________________________ [ ] Test records are marked and excluded from genuine-enquiry counts. Observed result / evidence: ______________________________ Fix owner / next step: ___________________________________ 6. MAKE THE READINESS DECISION Use what you observed. A tick is not a guarantee of future results. [ ] The advertised action can be completed. [ ] Its outcome is explained accurately to the visitor. [ ] A saved request can be found and assigned. [ ] The owner and cover know what to do next. [ ] Service, coverage and any price statements are accurate. [ ] Any problem that can lose or misrepresent a request has been fixed and rehearsed again. Decision: [ ] Ready for the reviewed journey [ ] Fix and rehearse again Evidence reviewed: __________________________________________________ Decision owner and date: ____________________________________________ Unresolved issue: ___________________________________________________ Fix owner and due date: _____________________________________________ Next review date: ___________________________________________________ 7. LEARN FROM GENUINE REQUESTS Review period: ____________________ Review owner: ___________________ Repeated missing information: _______________________________________ Common reason a request did not fit: ________________________________ Where the next action became unclear: _______________________________ One change to the page, form or handoff: _____________________________ How we will check the change: _______________________________________ Keep tests, duplicates, unsuitable requests, quotes and confirmed appointments distinguishable. An acknowledgement, message count or email open does not establish a booking. USE WITH THE GUIDES Cleaning quote request form: https://realboss.ai/blog/cleaning-quote-request-form Cleaning enquiry follow-up templates: https://realboss.ai/blog/cleaning-enquiry-follow-up-templates Cleaning business website checklist: https://realboss.ai/blog/cleaning-business-website-checklist RealBoss for home services: https://realboss.ai/solutions/home-services Original planning worksheet. Updated: 9 October 2026.