Run every pool you staff from one organization.
Your company is one organization. Each client pool is a community inside it, with its own hours, devices, manager and gate staff, and you watch them all in one live feed.
One organization, a community per client.
You create and manage every community. Your clients and your crews each see only their own.
A community for each client pool
Each client pool has its own hours, amenities, devices and staff, and its own optional resident list.
A manager for each client
Create one manager account per community. That manager sees the community’s check-ins, residents, reports and log export, and nothing of your other clients.
Gate staff for each community
Create gate staff accounts and bind each one to a community. Each account belongs to one community, so a guard who works three pools has three accounts.
A live feed across your clients
See check-ins from all your communities in one feed, with each community’s reports, check-in log and CSV export a click away.
At the gate.
Staff check people in on a phone or tablet registered to the community with its PIN.
Hours are enforced
Check-ins outside the community’s hours are blocked, and a barred or suspended household is refused.
Names, households and walk-ins
Look up a household, or check people in by name where a community keeps no resident list. A household behind on dues shows the client’s note. Vendor check-in and check-out is built in.
Works offline
The roster stays on the tablet, so check-ins keep working with a bad signal. Entries queue and send when the connection returns.
Every check-in has a name on it
Each check-in records which staff member made it, where and on which device, and each person’s sign-in history is kept.
Reports filed from the gate.
Photos come from the device camera. The client’s manager and your owner account both read what staff file.
Rounds
A round every half hour, logged by the person who walked it.
Start and end checklists
Start-of-day and end-of-day checklists for each pool.
Amenity inspections
Inspect an amenity and attach photos of what you found.
Incident reports
Write up an incident at the pool with photos, while it is fresh.
Connect it to your own systems.
Webhooks and the read API are set up per organization, under integrations in the admin.
Signed webhooks
Receive a signed webhook for a check-in, a vendor visit or a submitted report.
A read API
Read your records with per-organization tokens.
Put your clients’ pools in one organization.
Pool Check-in costs a service company what it costs a community, and the tiers, limits and trials are on its own pricing page. A company with many client pools should look at Premium, which is per organization.