Pipelines and leads: create, move a stage, close
This chapter shows you how to organize your sales work: create a pipeline, add leads for a contact, move a lead between stages, and close it as won or lost.
Before you start — who this is for
Any business member who can open the CRM tools. Note that some actions in SMS CRM ask for your multi-factor (MFA) code — this is documented for contact imports (Contacts) and follow-ups (Follow-ups); the verification for the pipeline and lead forms themselves is listed under Evidence below.
Step 1 — create a pipeline
Open the CRM tools from the overview's navigation and use the pipeline form. Give the pipeline its stages; once saved, the pipeline appears immediately in the overview's pipeline selector with its stages in order.
In the independent first-use verification, a customer on their very first sign-in created a real pipeline through this form, then reloaded the page — the saved pipeline was still there, and no re-activation was asked for. What you save stays saved.
Step 2 — add a lead for a contact
Use the enquiry/deal form to create a lead tied to a contact.
- You can have more than one lead for the same contact — the board and the overview count them honestly.
- There is currently no owner/assignee field on a lead — you cannot assign a lead to a person, because the feature does not exist yet. Where other tools might show an owner, this product shows the real lead counts instead of inventing something. Assignment remains an open item (see Not yet covered).
Step 3 — move a lead between stages
Use the stage action on the lead. The board immediately rebuilds from your real records — the ordered stages and every per-stage count update after the move.
Step 4 — close a lead (won or lost)
Use the close action and choose won or lost. The overview's won/lost totals come from these actual closed records — they are counts, not estimates.
Step 5 — confirm it saved
Everything above is saved on the server. In the retained verification, persistence was checked beyond the screen: the records were read back directly from the database and through a page reload, and every created/changed item matched. Refreshing the overview shows the same records again.
If something goes wrong
| What you see | What it means | What to do |
|---|---|---|
| You want to assign a lead to a person | That feature does not exist yet | Track it another way for now; see Not yet covered |
| A saved pipeline or lead seems missing after a reload | It should not be — persistence after reload is verified (see Step 5) | Refresh again; if it is genuinely gone, report it — that would be a defect, not expected behaviour |
What is deliberately not here
- No campaign composer, no bulk consent editing, no contact editor — this area exposes the working pipeline/deal forms only.
- No lead-source, reply, click or revenue attribution is inferred for any lead — a lead is exactly what you recorded.
- The existing lead-scoring utility is unchanged; what its scores mean and any link to SMS campaigns are outside what has been verified.
Evidence and receipts
- Evidence base:
tools/sms-crm-approved-overview-20261013/(run06 main suite, 19/19) for the persisted create/stage/close actions through the actual API, anddocs/reviews/2026-10-18-sms-crm-entry-rca.md(the independent first-use run) for a customer creating a real pipeline through the form and finding it still saved after reload. - Evidence kind: locally qualified PASS against the real mounted API and ordinary-role disposable PostgreSQL with synthetic identity (overview lane); the first-use pipeline persistence case is an independently executed Chief check (also synthetic identity, loopback providers). No live provider, no SMS sent.
| Fact in this chapter | Receipt |
|---|---|
POST /v1/crm/pipelines, POST /v1/crm/deals, POST /v1/crm/deals/:id/stage, POST /v1/crm/deals/:id/close exercised through real forms; SQL + reload substantiate persistence |
tools/sms-crm-approved-overview-20261013/HANDOFF.md "Persisted actions" paragraph, evidence/run06/result.json (19/19) |
| Multi-pipeline selection; multiple leads per contact | same HANDOFF surface table (pipelines/deals rows) |
| Pipeline created through the form survives reload on first use (independent Chief run) | docs/reviews/2026-10-18-sms-crm-entry-rca.md first-use journey, run apps/workspace/tests/sms-crm-first-use.run.cjs (2026-10-17T21:33Z) |
| No assignee/owner contract; lead counts used instead | same 2026-10-13 HANDOFF, limitations section |