CLEANING MOVE-OUT SCOPE ENQUIRY STARTER
Prepared October 18, 2026. Free resource; production voice usage can cost money.

Purpose: prepare a staff-readable cleaning-scope enquiry with a corrected service,
approved inclusions and separate access/deadline fields. This is a planning kit,
not an installed booking, quoting or contractor-dispatch integration.

1. APPROVE THE BUSINESS FACTS
Company and staff approver:
Actual supported services and geographic area:
Which service questions change the scope:
Current inclusions by service:
Requested extras that require staff review:
Unsupported requests and approved next step:
What property context reception should ask for:
Actual staff review location/process and responsible person:
Response wording when staff cannot meet the requested timing:
Facts owner and review date:

Do not invent a room-based price, legal guarantee or inclusion. Staff approve
actual commercial terms and any jurisdiction wording. Do not provide chemical,
stain-treatment or product-safety instructions as part of this administrative kit.

2. PREPARE IN BURKI WHEN AUTHORIZED
Assistants -> New assistant -> Set up manually -> Receptionist.
Assistant name: [descriptive name]
Business setup -> Assistant job: Receptionist.
Business name: [real name]
Business facts: [approved services, inclusions/extras, scope questions, area,
unknown route and real staff review process]
Desired outcome: a concise enquiry using the latest service choice, property
state, requested work, separate earliest access and requested finish deadline.
Apply business details to instructions, then review Instructions/First greeting.
Applying details replaces those fields. Create assistant persists the setup.

Greeting example:
I can take a few details for the cleaning team to review. Is this a regular clean,
a move-out clean or another service?
GPT Live may paraphrase greeting guidance; this is not proof of exact playback.

Review current saved/published state in Publish before a real change. Versioned
publication separates saved and published telephone versions; legacy live
settings can affect connected calls differently. Follow the actual release process.
Review Voice funding/provider prerequisites and required route/handoff readiness.
No Apply/Create/Save/Publish/Test or paid conversation is performed by this kit.

3. ADAPTABLE INSTRUCTIONS
You prepare cleaning-scope enquiries for staff review.
Ask which supported service the caller wants. If they correct it, use the latest
service and the questions appropriate to that service.
Ask one relevant question at a time. Preserve unknown answers.
Clarify property type/size, current state and requested inclusions/extras using
only the approved service list.
Keep earliest access and requested finish deadline separate. Clarify date and
the property's local time when needed. Do not infer availability or job duration.
Read back scope and constraints so the caller can correct them.
Explain the actual approved staff review process.
Do not quote an unsupported price, accept a crew/time, promise a deposit return,
or claim a message, ticket, quote or booking was created. No such action is
configured in this starter. Do not collect alarm codes, key-safe combinations,
passwords or payment data. Use the company's approved access process later.

4. SCOPE BRIEF TO COMPLETE FROM THE CALLER'S STATEMENTS
Requested service, latest value:
Earlier service superseded by correction, if relevant:
Property type and caller-supplied approximate size:
Occupancy/furniture/boxes or other current state described:
Requested included work:
Requested extras and what remains unreviewed:
Service area detail appropriate at this enquiry stage:
Earliest access: explicit date/time/property timezone:
Requested finish: explicit date/time/property timezone:
Reason for deadline, only if volunteered:
Other unanswered scope questions:
Approved staff review process explained:

Keep location detail proportionate to the actual task. Do not collect access
secrets or assume the property is empty because someone says move-out.
Access permission/time is not a crew arrival or accepted completion slot.

5. WORKED EXAMPLE, FICTIONAL AND NOT A PERFORMED TEST
Alder Cleaning Desk is invented.
Caller first asks for a regular two-bedroom clean on Friday.
Caller corrects it: moving out; oven and carpet work requested; boxes may remain.
Caller supplies the explicit job date, access after 10 AM and keys due 4 PM in the
property's local time.

Expected planning brief:
Service: move-out clean, replacing earlier regular-clean enquiry.
Property: caller describes two bedrooms; other size details unknown.
State: boxes may remain during the move.
Work: oven and carpet requests; actual inclusions/feasibility pending staff review.
Access: caller-stated explicit date after 10 AM, property local time.
Requested finish: same explicit date before 4 PM key handover.
Staff task: review scope, access constraints, feasibility and quote process.
Not confirmed: price, crew, arrival, completion promise, quote or booking.

Do not calculate that six hours is sufficient. Do not call this a saved system
record or actual handoff. In a real setup use the company's approved review route.

6. PLANNING CASES AND LATER AUTHORIZED REVIEW
Case A: recurring -> move-out correction; latest service must replace the old one.
Case B: requested extra absent from approved list; preserve request for review.
Case C: access after 10 AM / keys due 4 PM; keep separate, no accepted-slot claim.
Case D: property still occupied/boxes present; preserve the stated condition.
Case E: caller asks for a deposit guarantee or unapproved immediate price.

For each case:
Approved facts/version:
Expected questions and brief:
Actual response/evidence, ONLY if later evaluated:
Missing or superseded scope details:
Unapproved price/inclusion/timing/action claimed:
Required improvement and reviewer:

7. STAFF OUTCOMES, COMPLETE ONLY IF ACTUALLY EVIDENCED
Enquiry reviewed by/date:
Additional information needed:
Actual quote record/terms and responsible staff:
Crew/arrival/completion acceptance, if genuinely confirmed:
Actual booking record, if any:
Follow-up actually sent/received, if any:
Unverified states:

Explaining a process or writing a brief does not create any of those outcomes.
No customer data, live integration, paid call or business action was used here.