Onboard a Client in 10 Minutes
A repeatable checklist for adding a new client to SiroPing as an agency or maintenance team. Total time: about 10 minutes per client.
tip
Keep this as your standard: every client follows the same 10 steps, so
nothing is missed and reports/status pages look identical across clients.
The 10-minute checklist
| # | Step | Where | Time |
|---|---|---|---|
| 1 | Create the client workspace — name it after the client | Workspaces | 1 min |
| 2 | Create a project inside the workspace (e.g. "Main site") | Project | 1 min |
| 3 | Add the website (HTTP monitor) | Monitors → New HTTP Monitor | 1 min |
| 4 | Add API endpoints (method/headers/body) if the client has APIs | New HTTP Monitor → POST/Bearer | 1 min |
| 5 | Add a login-form check for anything behind a login (ERP, admin) | New HTTP Monitor → "Log in before checking" | 2 min |
| 6 | Add heartbeat for cron/backup jobs | New Heartbeat Monitor → ping URL into their cron | 1 min |
| 7 | Set alerts — Telegram/Email/Webhook + send a test alert | Settings → Notifications | 1 min |
| 8 | Enable the public status page (slug = client) | Project → Status Page | 1 min |
| 9 | Set white-label branding (logo + company name) | Workspace → Edit | 1 min |
| 10 | Generate the first monthly report to confirm it looks right | Project → Monthly Report | 1 min |
That is the full client lifecycle — monitor, alert, status page, branded report.
Naming template (keep it consistent)
Workspace: <Client Name>
Project: Main website
HTTP: https://client.com
HTTP: https://api.client.com (POST, Bearer)
HTTP: Admin — behind login
Heartbeat: Nightly backup
Status page slug: <client>
NOTE
Use **one workspace per client** (Business = 10). Data between workspaces is
fully isolated, and each client gets their own report + status page branding.
Best practices
- Read-only monitoring account for behind-login checks — see HTTP Monitoring → Privacy & best practices.
- Set the Expected Content on each HTTP monitor so a "200 but it's a login/error page" is caught as a warning, not a false "up".
- Send a test alert right after configuring notifications — never find out a channel is broken during a real incident.
- Check the first monthly report yourself before sending it to the client — it's the deliverable they'll see.