CRM overview
A kanban pipeline for the people you’re actively trying to close — not everyone in your Contacts list, just real, ongoing sales conversations. Deals connect to the same contacts, orders, and bookings already living in your workspace, so value and history don’t have to be typed in by hand.
Pipelines and stages
You can run more than one pipeline — Sales, Calls & Bookings, Courses, or however your business actually segments conversations. Each pipeline has its own set of stages you fully control (add, rename, reorder, delete).
Pick a starting template (Sales, Calls & Bookings, Courses, or a blank Pipeline) — each seeds a sensible starting set of stages you can change afterward.
Attach it to a contact (existing or new), give it a title, and optionally a value. It lands in whichever stage you add it to.
Nothing here happens automatically from a drag except the stage change itself — moving a deal to a "Won" stage doesn’t on its own do anything more than that, unless you’ve built an automation on top of it (see below).
Custom fields
Add fields specific to how you actually track a deal — beyond the built-in title, value, and notes.
| Type | Use it for |
|---|---|
| Text | A short note field — referral source, project name, anything free-form. |
| Number | A quantity, a headcount, anything numeric beyond the deal's own value. |
| Date | A target close date, a contract start date. |
| Select | A fixed set of options you define — lead source, deal size tier, whatever your team picks from a dropdown. |
Fields are defined per pipeline, not globally — a field that makes sense on your Sales pipeline doesn’t have to clutter your Courses pipeline. Manage them inline from the deal panel without leaving it.
Deal value fills itself in
A deal doesn’t have to start as a manually-typed dollar amount. When an automation creates a deal off a real order or booking, its value is pulled from the actual charge.
| New deal, created by automation | Value is set from the real order amount automatically — nothing to type. |
| Existing deal, being moved by automation | Value is never touched — an automation moving a deal you've already priced by hand won't silently overwrite what you set. |
| Manual deal creation | Same as always — type a value, or leave it blank. |
Lifetime value on contacts
Every real purchase from a contact — a product order or a paid-page membership — rolls up into a running lifetime-value total on their contact record, visible right on the deal panel next to their name.
Tracking a booking as a deal
A confirmed booking can become a deal on your pipeline in one click, from the Booking admin page — no need to re-type a contact you already have.
Team permissions
On a reseller (White Label) account, CRM access for team members is its own separate permission — granting someone CRM access doesn’t also give them Booking, Automations, or any other feature, and vice versa. See team members & client access for the full permission model.
Troubleshooting
| Symptom | What it means |
|---|---|
| A deal's value looks wrong after an automation moved it | Automations only set value on a brand-new deal — if it looks wrong, check whether the value was set manually earlier rather than assuming the automation just overwrote it. |
| Lifetime value seems lower than what a customer has actually paid | Expected for a subscription paid-page member past their first payment — renewals aren't counted yet (see above). |
| A team member can't see the CRM at all | Check whether they've been individually granted CRM access — it's off by default for every new team member on a reseller account. |