One request in. Provisioned, live, secured.
A customer's request becomes a working, secured site, with a person on anything that touches money or risk.
What goes in, what comes out.
A support email: a new site, a fault or a plan change.
An account provisioned, DNS configured, a certificate issued and a health check passing, with billing updated to match.
- 01
Read the request
And decide what kind it is.
- 02
Open the ticket
Prioritised and routed.
- 03
Provision
The account and its resources.
- 04
Configure and secure
DNS and the certificate.
- 05
Check it is up
A health check on the site before the ticket closes.
Where a person decides.
Faults are diagnosed and a fix is proposed. A person approves it, with a window to undo, or escalates to the engineer on call. A request the system is unsure of goes to a person too.
- Support inbox
- Ticketing
- Provisioning
- DNS
- Certificate issuer
- Billing
- On-call alerts
Mocked in the demonstration. In a delivery, they are yours.
The numbers on this screen are invented. What we have measured in production is on Proof.
If your process needs people to run, it's broken.
Pick one process. We design it in a week and prove it in 14 days.