Lead lifecycle
New, contacted, viewing booked, quoted, won, lost — and how statuses move.
Every lead has a status that tells you (and your team) where the deal sits. Six values, flowing roughly left-to-right.
The six statuses
| Status | Meaning | Set by |
|---|---|---|
new | Just submitted. Nobody on your team has touched it. | System (on widget submit). |
contacted | Someone replied or called. The clock is ticking. | Operator. Sets contacted_at timestamp. |
viewing_booked | A site visit is on the calendar. | Operator. |
quoted | A formal quote has been issued (often the auto-generated one is enough). | Operator. |
won | Deposit paid, contract signed. Done. | Operator. |
lost | Closed without a booking — write a note about why. | Operator. |
Updating a lead
- Open Leads from the dashboard.
- Click into the row.
- Use the status dropdown at the top right of the lead detail page.
- Add a note in the free-text field — these are private to your team and useful for handoffs.
What's stored on a lead
- UUID, name, email, phone
- Event type, event date, guest count
- GDPR consent (always true for widget submissions — we won't accept a submission without it)
- Source URL — the page the guest was on when they hit Submit
- UTM source, medium and campaign — captured silently from the URL
- Notes — private operator-facing
- Status, contacted_at, created_at, updated_at
Filtering & searching
The leads index supports filtering by status. We currently paginate at 50 leads per page — if you've got more, jump to the dashboard's search field and filter by name or email.
What about contacted_at?
The contacted_at timestamp is set automatically the first time you flip a lead
from new to contacted. It's there so you can measure your response time —
the gap between created_at and contacted_at. Industry research says replying
within 5 minutes is roughly 9× more likely to convert than replying within an hour.
Statuses don't push to your CRM
Lead status changes happen entirely inside Innkept. We don't push them to your CRM — your CRM has its own pipeline stages and they're rarely a clean match. The initial push (on Submit) is the only sync.
Something missing or wrong? Tell us.
Updated regularly. UK English. No AI slop.