Cleaning Service Intake Checklist: What an AI Receptionist Should Ask


A cleaning service intake checklist should collect enough information to choose the next step: assess a residential request, arrange a commercial site assessment, clarify missing details, or explain a service restriction. It should not make every caller complete the same long questionnaire.
Start with the requested service and location. Add property details only when they help the company assess the work. Before ending, establish who should follow up and what remains unresolved.
Intake is not a quote or a confirmed booking. A customer’s preferred date remains a request until the company has checked availability and confirmed an appointment.
Use the following checklist for a phone conversation, web chat, or cleaning enquiry form. Adapt the requirements to the next action your company actually takes.
Here, core means needed to assess a new service request. Conditional means needed only when a rule or next step depends on it. Optional means useful but not a reason to hold up the enquiry.
|
What to establish |
Example question |
Why it matters |
When to ask |
If there is no answer |
|
Residential or commercial request — core |
“Is this for a home or business premises?” |
Selects the relevant questions and staff recipient |
At the start, unless already clear |
Clarify before asking property-specific questions |
|
Requested service — core |
“What kind of cleaning do you need?” |
Checks whether the company handles the work |
Early |
Ask for a short description rather than forcing the customer to choose unfamiliar terminology |
|
Area or postcode — core for coverage screening |
“What postcode is the property in?” |
Checks the service area before detailed scoping |
Before collecting a full property brief |
Leave coverage unconfirmed; do not guess from a nearby landmark |
|
Basic property scope — conditional on the assessment method |
“Approximately how large is the property?” |
Helps determine the information an estimator needs |
After the location and service appear relevant |
Offer an approved alternative, such as room counts, or refer for assessment |
|
One-time or recurring work — conditional |
“Is this a one-time clean or ongoing service?” |
Identifies the requested service pattern |
When frequency affects scope or routing |
Record that the customer has not decided |
|
Preferred timing — conditional |
“When would you like the service to start?” |
Identifies deadlines and any notice-period issue |
When timing affects the next decision |
Record “Not specified”; do not invent urgency |
|
Name and suitable callback method — conditional on follow-up |
“What name and contact method should our team use?” |
Makes a callback or written response possible |
Before a follow-up is needed |
Explain the limitation; do not require both phone and email without a reason |
|
Relevant restrictions or special conditions — conditional |
“Is there anything about the property or requested work our team should review?” |
Identifies exceptions and operational constraints |
When the service or earlier answers make it relevant |
Keep the condition unconfirmed and refer if it blocks assessment |
A customer asking whether you cover an area does not necessarily need to provide their name, phone number, and exact street address. Those details become relevant when the conversation moves toward an assessment or follow-up.
Record unknown, not applicable, and declined separately. They mean different things: the customer may not know the floor area, may have no parking restrictions, or may choose not to provide a contact number.
For residential enquiries, establish the type of home, the requested cleaning, and the scope information your company uses. Do not collect floor area, every room count, and a detailed inventory unless the next decision requires all three.
Use these follow-up questions selectively:
If the first message says, “I need a weekly clean for a two-bedroom apartment with one bathroom,” the intake already contains the property type, frequency, and room counts. The next question should fill a genuine gap, such as the postcode or requested scope.
For the platform implementation, see the residential lead qualification guide in CogniAgent. It covers the residential conversation and estimator handoff; the checklist here defines which questions belong in that conversation.
Commercial cleaning intake needs to establish what premises are involved and whether someone can assess the work from the initial information or needs a site visit.
Ask the following questions when they support that decision:
Budget, the current contractor’s details, and the full procurement process do not have to be mandatory at first contact. Collect them when the company has a defined reason, such as preparing a proposal for a formal purchasing process.
Do not ask the receptionist to decide whether unfamiliar specialist work is safe or within the team’s competence. Preserve the customer’s description and refer it to an appropriate person.
The commercial lead qualification guide in CogniAgent addresses implementing the commercial intake and preparing a brief for assessment.
The checklist should branch according to the information received. A field being available is not a reason to ask every customer about it.
Ask about an additional task when the customer requests it or when it changes the scope already under discussion.
If someone asks for a routine clean, do not automatically read out every possible add-on. If they mention an oven, clarify whether they want that included in the assessment and check the company’s supported-service information.
Check service fit before collecting detailed access arrangements.
A building that requires advance visitor registration may need an operational note. That does not justify collecting alarm codes, passwords, or door-entry credentials during initial intake.
Do not copy the first site’s details across the rest of a commercial enquiry.
Two locations may have different floor areas, working hours, access restrictions, and requested tasks. Record which information applies to which property. If the customer cannot provide it all, identify the missing sites and arrange the appropriate follow-up.
Use an alternative only if the company accepts it for the next step.
A residential company might accept bedroom and bathroom counts for an initial review. A commercial estimator might need a floor plan or a site assessment. Neither approach is a universal cleaning-industry requirement.
Do not calculate a floor area from an unsupported assumption.
When the customer corrects a detail, use the corrected value and reassess any decision that depends on it.
Changing the requested service from routine cleaning to move-out cleaning can affect the relevant questions. Changing the postcode can affect coverage. The brief should reflect the latest answer rather than preserving the earlier value as if both were current.
Stop detailed intake when the next step is already clear. A confirmed mismatch does not justify continuing through the remaining questions.
The following are suggested operating rules to adapt to company policy.
|
Situation |
Action |
What to tell the customer |
What to pass to staff |
|
Confirmed location outside the service area |
Stop unrelated property questions |
Explain that the location is outside the listed coverage; mention an exception review only if the company offers one |
Location and the coverage rule applied, if the enquiry is retained |
|
Unsupported service |
Explain the relevant limitation |
State which requested work the company does not provide |
Requested task and any unresolved distinction |
|
Required information is missing |
Ask for an accepted alternative, then stop if unavailable |
Explain what the team still needs and how it can be supplied |
Known facts, missing fields, and whether they are unknown or declined |
|
A site assessment is required |
Collect enough information to arrange human follow-up |
Explain that assessment is needed before the company can determine scope or prepare a proposal |
Property details, reason for assessment, and contact preference |
|
Ambiguous or specialist requirement |
Refer without improvising an answer |
Say that the appropriate team member needs to review the requirement |
The customer’s description and the specific unanswered question |
|
Customer asks for a person |
Stop insisting on completing the checklist |
Explain the available handoff or callback process |
Reason for contact and information already supplied |
|
Complaint or existing service request |
Switch away from new-lead intake |
Explain that the request belongs with the service or support team |
Enough information to locate the existing matter under the company’s verification process |
A request for a person does not mean a live transfer is always available. If the process supports only a callback, say so.
If a conversation ends unexpectedly, retain the information available through the company’s approved process and mark it incomplete. Do not assume a handoff occurred just because the conversation has ended.
Separate company knowledge, current operational data, and permission to act.
The receptionist needs an approved source for:
Assign someone to maintain this information. If two sources conflict, the receptionist should seek clarification rather than choose whichever answer sounds more convenient.
For organizing business documents in the platform, refer to the CogniAgent Knowledge Base guide.
Appointment availability and the status of an existing enquiry require current information from the relevant operational source or a responsible person.
A document describing services does not establish that a crew is free on Tuesday. An old confirmation email does not prove an appointment remains unchanged.
If the receptionist cannot check the relevant source, it should record the request and explain that confirmation is pending.
Define what the receptionist may actually do: prepare a brief, send it to an approved recipient, request a callback, or perform another specifically configured action.
“Please book the customer” is an instruction, not evidence that a booking succeeded. Only describe an external action as completed when the connected process returns an appropriate result.
Keep the customer’s contact details separate from the internal recipient. A callback email belongs in the enquiry; it should not silently replace the estimator’s address.
These are fictional training examples, not customer transcripts. The company rules described within each example are assumptions for that scenario.
Customer: “I need a weekly clean for a two-bedroom apartment with one bathroom.”
Receptionist: “What postcode is the apartment in?”
Customer: “10003.”
Receptionist: “That postcode is within our listed service area. Are you looking for routine cleaning, or is there additional work you want the estimator to review?”
Customer: “Routine cleaning. Please contact me by email.”
Receptionist: “What email address should the estimator use?”
For this example, assume the company’s approved list includes that postcode. The receptionist uses the property type, room counts, and frequency already provided instead of asking for them again. The next step is an estimator review, not a confirmed weekly appointment.
Customer: “We need cleaning for two offices after staff leave. One is about 4,000 square feet; I don’t know the size of the other.”
Receptionist: “Are both offices at the same location, or are they separate sites?”
Customer: “Separate sites.”
Receptionist: “Our process requires a site assessment for multi-site proposals. What are the two locations, and who should our estimator contact to discuss access?”
The site-assessment rule is an illustrative company policy. The receptionist preserves the known size for the first office and leaves the second unknown. It does not apply the first site’s measurement to both or promise an inspection time.
Customer: “I need a deep clean, but I don’t know the floor area.”
Receptionist: “For an initial review, our team can use bedroom and bathroom counts instead. Do you know those?”
Customer: “Not yet. I’m arranging this for a relative and need to check.”
Receptionist: “I’ll leave those details unconfirmed. Would you prefer to return with the information, or ask our team about another way to assess the work?”
Here, room counts are an accepted alternative under the example company’s policy. If the customer cannot provide them, the enquiry stays incomplete. No size or cleaning scope is invented to finish the form.
A complete brief accounts for the information received and the information still missing. It does not require every field to contain a known value.
Include the request type, customer-provided facts, unresolved questions, initial assessment, next action, and responsible recipient. Identify which statements came from the customer and which are conclusions based on company policy.
This fictional example assumes the company serves the location and requires an estimator to review commercial scope.
CLEANING INTAKE BRIEF
Request type
New commercial cleaning enquiry.
Customer-provided information
Business: Example Studio
Contact: Morgan
Preferred callback: [email protected]
Premises: One office, approximately 3,000 square feet.
Location: Confirmed against the company’s service-area list.
Requested work: Recurring office cleaning twice a week.
Preferred working window: After 6 p.m.
Preferred start: Tuesday, subject to confirmation.
Unknown information
Floor count and detailed task list.
Site-assessment access arrangements.
Initial assessment
Commercial scope review required.
Reason: Company policy requires an estimator to assess the work before a proposal is prepared.
Next step
Estimator contacts Morgan to clarify scope and discuss whether a site assessment is needed.
Responsible recipient
Commercial estimating team.
Confirmation boundary
No price, crew availability, start date, or appointment confirmed.
Handoff status
Brief prepared; receipt by the estimating team not yet confirmed.
“Would like service to start Tuesday” must not become “Service starts Tuesday.” Likewise, a prepared brief must not be marked received until the handoff has been verified.
If the customer corrects a detail after the brief is sent, identify the correction in an update rather than leaving staff to reconcile two apparently current versions.
Start by deciding which next actions your company supports. Then define the minimum information for each action, the questions that depend on earlier answers, and the conditions that stop intake.
For a web form, show residential or commercial follow-up fields only when relevant. For a phone or chat conversation, have the receptionist check what the customer already supplied before asking another question.
In CogniAgent, the AI receptionist for cleaning companies is the product context for implementing this process. Use the residential and commercial guides linked above for their respective workflows, and keep company knowledge separate from live operational checks and authorized actions.
Before routing customer enquiries through the checklist, test a supported residential request, a commercial request requiring assessment, an out-of-area property, missing information, a correction, and a request to speak to a person.
For each test, inspect the questions asked, the resulting brief, the chosen recipient, and evidence of the handoff. Assign an owner to incomplete enquiries and failed notifications so that a finished conversation does not leave an unhandled request.