A clear next step for each cleaning enquiry.

The proposed service is the ongoing handling of enquiries, owner decisions and agreed follow-ups. This fictional prototype illustrates that process. It does not demonstrate a live integration.

Proposed first month

$250One enquiry channel

Integrations, limits and start date agreed before payment or activation. No guaranteed bookings.

0–20 seconds · capture and responsibility

Make the owner’s next step visible.

“Maya’s fictional request enters the tracker. The acknowledgement uses an approved demo template and stays a preview. The owner still decides availability and price.”

Demo: simulate an incoming request, then simulate its acknowledgement.

Fictional Xylo enquiry tracker showing Maya's request, owner attention, a never-sent acknowledgement preview, and the proposed first-month scope. — Fictional example: three seeded requests become four when Maya’s request is added. No message has been sent.

20–40 seconds · agreed follow-up

Use explicit eligibility rules.

“With recorded customer permission and owner agreement, this example allows one follow-up after 24 hours. Nothing is sent. A second check creates no additional preview.”

Demo: record owner review and agreement, advance the demo clock, then run the follow-up check.

Demo rules showing one fictional follow-up is eligible only after approval, permission, an available simulated connection and 24 elapsed hours. — The one-follow-up / 24-hour rule is illustrative. Live timing and limits remain to be agreed.

40–60 seconds · stop and escalate

Handle exceptions without assuming delivery.

“Duplicates do not add tracker rows. A reply, booking or opt-out stops reminders. A lost connection flags the owner instead of claiming delivery.”

Demo: replay the same request; try a stop condition. For connection loss, reset, add a request, disconnect the simulation and attempt an acknowledgement.

Fictional opt-out blocking the follow-up check, with an activity trail stating no message was sent. — Opt-out stops contact. Original permission is shown as withdrawn.

Unavailable simulated connection requiring owner attention while the acknowledgement remains unrecorded. — No delivery is claimed. Restoring the simulation does not retry automatically.

60–85 seconds · a small first month

Agree the scope before paying or activating.

“The proposed first month is $250 for one enquiry channel. We agree integrations, limits and the start date before payment or activation. There are no guaranteed bookings.”

Choose one enquiry channel and check integration feasibility.
Agree volume limits, operating hours, owner responsibilities, approved wording, permission and stop rules, and customer-data handling.
Confirm the start date and written scope before payment or any live setup.

These are proposed discussion points, not established service levels. The demonstration stores only fictional state in browser memory. It has no real inbox, account, customer data, payment flow or connected integration. No actual clients or delivered messages are represented.

Presenter script and click cues

XYLO FOLLOW-THROUGH — 60–90 SECOND SALES WALKTHROUGH
Public fictional demonstration for review and discussion.
Simulation: no messages sent or accounts connected.
All names, enquiries, permissions and approvals are fictional.

0–20 seconds | Capture and responsibility
[Click “Simulate incoming request”, then “Simulate acknowledgement”.]
“This is a simulation for a fictional cleaning company. Maya's enquiry enters a tracker with a clear next step. The approved acknowledgement is only a preview. The owner still decides availability and price.”

20–40 seconds | An agreed next step
[Click “Record owner review & follow-up agreement”, “Advance 24 hours”, then “Simulate follow-up check”.]
“With recorded customer permission and owner agreement, this example allows one follow-up after 24 hours. Nothing is sent. A second check creates no additional preview.”

40–60 seconds | Stop and escalate
[Click “Replay same request”. Select Lila, Noah and Avery, or use the stop-condition buttons.]
“Duplicates do not add tracker rows. A reply, booking or opt-out stops reminders. A lost connection flags the owner instead of claiming delivery. The proposed service is the ongoing handling of these next steps and exceptions.”

60–85 seconds | Define a small first month
[Point to the proposal strip.]
“The proposed first month is $250 for one enquiry channel. We agree integrations, limits and the start date before payment or activation. There are no guaranteed bookings. The next step is to agree the channel, owner responsibilities and follow-up rules before any live setup.”

OPTIONAL CONNECTION-LOSS EXAMPLE
Reset the demo. Add Maya's request. Click “Simulate connection loss”, then “Simulate acknowledgement”. The acknowledgement stays unrecorded and owner attention is required. Restoring the simulated connection never retries automatically.

BEFORE ANY PAID OR LIVE PILOT
Agree one enquiry channel, integration feasibility and access method, volume limits, operating hours, response expectations, owner escalation responsibilities, approved wording, permission and stop rules, handling of customer data, and the start date. These are discussion items, not capabilities or service levels established by this demo.

The one-follow-up / 24-hour rule is illustrative. Live limits and timing remain to be agreed. No inbox, account, customer data, payment flow or live integration is connected. This walkthrough does not authorise live setup or customer outreach.