Test mode

Every operator account starts in test mode, and the panel says so across the top:

Test mode. Everything here works as it will live, except that no cleaner is sent and nothing is charged. Our team will review your account and switch it on.

That is the whole of it, and it is deliberately a small difference. You are building an integration against the real screens, the real prices and the real states — not against a mock that will behave differently on the day it matters.

What you need

• Nothing. A new account is already in it.

What is the same as live

• Every screen, every field, every validation.
• Bookings arrive, land on the calendar, and become anticipated turnovers.
• A checkout raises a cleaning, with its price worked out exactly as it would be.
• The cleaning appears in your lists, in the reports, and on the board.
• Webhooks are signed, checked, throttled and idempotent exactly as they will be.
• The API answers the same envelope, the same error codes, the same paging.

What is different

Two things, and only two:

1. No cleaner is dispatched. The cleaning exists and is priced and visible to you — it simply never reaches a cleaning company. A sandbox must never put a real person in front of a real door.
2. No money moves. Nothing is charged to a wallet, no invoice is collected.

Step 1 — Build the whole flow in it

Connect a channel or point your system at the webhook, send a booking, send its checkout, and watch the event row, the calendar and the board. Everything you can see there is what you will see live.

Step 2 — Check your signature before you go live

The commonest reason a live integration is silent on day one is a signature computed over re-serialised bytes. Send one signed event in test mode and read the response: a 401 here costs you a minute; the same 401 after go-live costs you a day of missing cleanings.

Step 3 — Ask to be switched on

A person at Suitiee reviews the account and switches it to live. It is not a toggle you hold, on purpose: going live means real cleaners travelling to real addresses.

Test traffic stays test traffic

A booking taken in the sandbox stays a sandbox booking for its whole life, including its checkout and any mid-stay clean, even if the account goes live in between. Going live never turns yesterday's test traffic into today's real work.

You can also filter on it: Test traffic is a condition in the automation rule builder, so a rule can be written to ignore it — or to run only against it while you are trying the rule out.

When it goes wrong