# The ops console: Our lead pipeline, support desk and sales playbook in one login

> A product we built and run ourselves, so every detail here is real.

The internal system that runs our own funnel: every enquiry and support ticket arrives here, is worked through stages, and becomes a client and a project when it is won.

## Challenge
Enquiries from a site, a voice agent and a support page all need one home, one set of stages and one place where the sales playbook lives so human and AI agents follow the same script.

## Approach
- **One inbox for everything.** Sales enquiries and support tickets are kept apart but live side by side, filterable by service and status.
- **Won leads become clients.** A single action converts a won enquiry into a client and a project with the original conversation attached.
- **The playbook inside the tool.** Openers, qualifying questions and objection answers per service, so a caller reads the script on the call.
- **Secure by default.** Individual logins, hashed passwords, session cookies and a forced password change on first sign-in.

## Built
- Lead and ticket console
- Client and project records with phases
- Convert-to-client action
- Per-service sales playbook
- Username and password sign-in
- Notes that append and never overwrite

Stack: FastAPI, SQLite, Vanilla JavaScript, scrypt, Caddy.

## Facts
- Sections: Leads, Tickets, Clients, Playbook
- Auth: Username and password, forced change on first login
- Rule: Support tickets can never convert to a project

Page: https://devraxo.com/work/ops-console/