How it works — propose, then approve
The council never changes a lead by itself. It hands you a proposal — a suggested stage change, a note explaining its reasoning, and any planned actions — and you decide.
1 Run it on a lead
Open a lead and choose Run council (or run the whole queue from the batch panel). It reads the enquiry and works through: qualify (is this a real, in-scope lead?), enrich (background/context, optionally a web look-up), and draft (a suggested reply or proposal).
2 Read the proposal
You'll see what it suggests and why. For example:
Proposed: move to Qualified
Note: "Reachable (valid email), a real in-scope need (wants a booking automation), clear intent — asked for an audit. Not a competitor."
On approve → post the note + set the stage. (Any sends are dry-run unless live actions are on.)
3 Approve or reject
- Approve — the change is written to the lead (stage + note), and any planned actions run (respecting your dry-run / live setting).
- Reject — nothing happens; the proposal is set aside.
Demo vs Live: a chip shows whether the council is running in Demo (free, canned reasoning — great for trying it) or Live (real AI, which uses metered credit). Approvals write to the CRM either way.
Where it fits
The council is the "brain"; AI Automations decide when it runs, and the Pipeline is where its approved decisions land. Together: a lead arrives → the council proposes → you approve → it moves through the pipeline.