Skip to content
User Manual · Chapter 17 — CRM

Parties — who you are talking to

Add a party for every organisation or person you are in conversation with: name, kind (organisation or person), contact details, and notes. On the party's record, Contacts holds the named people you actually talk to there. If the party is already a Customer or a Donor, link them in the Linked records section — one less duplicate to wonder about later.

The party's record is its 360 — the whole conversation in one place, the way a customer's record gathers theirs. The top of the page names the party and its linked master records: where the party is a Customer or a Donor, the master is named there and the name takes you to the record itself (CRM points at masters; it never copies them). Below, tabs gather Contacts, Leads (each with its status and the opportunity it qualified into), Opportunities (pipeline, stage, and the value in the opportunity's own currency), Conversions — the sales orders and donations the party's opportunities became, each linking onward to the record itself — Channel history (the signals, with where each came from) and Activity. A tab with nothing in it says so plainly.

Campaign traceability sits on the same page. For every campaign recorded against this party's work, a thread walks the chain end to end: the campaign → the leads recorded under it → the opportunities they qualified into → the quote or donation each opportunity converted into, with its state — every step a link to the record itself. Read the thread the way the campaign figures must be read: a campaign named here was written on the records, not proven to have produced them — associated, never caused. And the chain is built only from campaigns actually recorded on a lead or an opportunity: a campaign name arriving on a channel signal is that channel's own label — it shows in Channel history as provenance, and it never becomes a link in the chain.

Snapshot: portal-v0-2026-11-10