Website & portal

The client portal

What clients can do themselves — and how phoned-in requests use the same rails.

The portal exists to absorb the phone calls: clients help themselves to the small stuff so it reaches you as tidy requests instead of interruptions. Invite a client and they sign in with their email — the main sollos3.com login recognizes a client account and routes it straight to the portal, so nobody needs to know a special address (/client also works, with an emailed sign-in link as the primary route and a "Forgot password?" reset — no account babysitting). If the client's email already has a Sollos login, the invite page sends them to sign in with it first; opening the invite link while signed in connects that login to their client account.

What a client can do

See their visits — upcoming and past, with date, time, and service.
Leave a note for a visit — "skip the bathroom this week". It goes straight to the assigned cleaner's job screen as a highlighted card, notifies the crew, and shows on the booking for the office. Notes arrive already-resolved: they're information, not a decision waiting on you.
Skip a visit — far enough out, it just happens and you're told; close in, it becomes a request you approve or decline on the Requests page.
Leave a review, anytime — every finished visit in their cleans list carries a review link, no waiting to be asked. Automated review asks follow your cadence (Settings → Automations): after every clean, 4×, 2×, or once a year — and someone who just left a review is never re-asked within that window.
Request a new booking — service, preferred date and time window, address, notes. It lands on Requests, and Create booking there opens the form with everything they said pre-filled.

The phone is a portal too

A client who calls instead of tapping loses nothing: on any booking's page, the office can type a client note for this visit into the same channel — the cleaner sees the identical highlighted card, and nobody has to know whether it was typed or phoned in.

Client notes are deliberately separate from the booking's own notes. A booking note edited "for this and future visits" becomes a standing instruction for the whole series — a client's "just this week" must never do that, and in this channel it can't.

The client portal

What clients can do themselves — and how phoned-in requests use the same rails.

What a client can do

See their visits — upcoming and past, with date, time, and service.
Leave a note for a visit — "skip the bathroom this week". It goes straight to the assigned cleaner's job screen as a highlighted card, notifies the crew, and shows on the booking for the office. Notes arrive already-resolved: they're information, not a decision waiting on you.
Skip a visit — far enough out, it just happens and you're told; close in, it becomes a request you approve or decline on the Requests page.
Leave a review, anytime — every finished visit in their cleans list carries a review link, no waiting to be asked. Automated review asks follow your cadence (Settings → Automations): after every clean, 4×, 2×, or once a year — and someone who just left a review is never re-asked within that window.
Request a new booking — service, preferred date and time window, address, notes. It lands on Requests, and Create booking there opens the form with everything they said pre-filled.

The client portal

What a client can do

The phone is a portal too

See it with your own jobs

The client portal

What a client can do

The phone is a portal too

See it with your own jobs