The buying committee
When a company decides whether to buy from you, a few people decide, push, weigh in or stand in the way. Every contact has a Buying role that says which part they play at their organization. The organization page shows who holds which role and what's missing, and the assistant can propose a role for everyone at an organization on a card you check and apply.
What you can do here
- Set a contact's Buying role in the Work section of their profile.
- Rename the roles, or add your own, in Settings → Fields.
- See an organization's committee on its Contacts card: each person's role, the people with a role first, and a line that names what's missing.
- Click Map with the assistant, or ask in a session — "Map Acme Corporation's buying committee" — and apply the roles you agree with.
- Find accounts by their committee: an organization whose Buying committee has no Decision maker is a condition for organization segments, the Organizations tab's Filter and journeys.
The Buying role field
Buying role is a built-in contact field in the Work section, after Job title and before Department. A contact has one role at a time: the part they play at the organization they're linked to. It comes with five roles:
- Decision maker — signs off on buying.
- Champion — pushes for you inside the company.
- Influencer — has a say in the decision.
- User — will work with what you sell.
- Blocker — stands in the way.
Click the value on a contact's page to set it. Like the other built-in contact fields, Buying role can be a column in the Contacts list and sorted by, and set by a journey's Update contact step. A contacts import doesn't offer it as a column yet.
Your own role list. In Settings → Fields, choose Contact, open Buying role's ⋯ menu and click Edit field to rename a role, add one — "Budget holder" or "Legal", say — or remove one. A removed role stays on the people who have it and is no longer offered. Decision maker and Champion are the two roles the organization page looks for, and they stay that way when you rename them: rename Decision maker to "Economic buyer" and the page says "No economic buyer known".
Moving someone clears their role. A role is about one company, so when a contact moves to another organization, or is unlinked, their Buying role is cleared. That includes a move your CRM sync makes when it puts the contact under another organization. That counts as a change to their Buying role, so a journey that starts when it changes starts for them. Linking someone who has no organization yet keeps a role they already have (one set through the API, say), and merging two organizations keeps everyone's role.
It's never printed. Buying role isn't a merge field, so no email or text can print it — "Blocker" never reaches the person it describes. It isn't synced with your CRM yet.
The committee on the organization page
The Contacts card on an organization page shows the committee:
- Role pills. Each person's role shows as a pill next to them; a Blocker's pill is marked as a risk. Someone with no role has no pill.
- People with a role first, in the order of your role list (Decision maker, then Champion, and so on), then everyone else as before. The card shows the first five; View all N in Contacts lists everyone.
- The committee line at the top of the card is counted over all of the
organization's active contacts, not only the five shown. It says:
- "No decision maker known" and "No champion known" when nobody holds those roles — the two a committee needs;
- "1 blocker" (or "2 blockers", and so on) when someone is a Blocker;
- Map with the assistant, when something is missing or someone has no role yet.
Archived contacts aren't counted, and an organization with no active contacts shows no line. Archived contacts are listed after the active ones on the card and show no role. If you remove Decision maker or Champion from your role list, the line stops looking for it. The card is read-only: to change someone's role, open their page.
Mapping the committee with the assistant
Click Map with the assistant on the Contacts card, pick a campaign, and a new session opens with "Map the buying committee at @Acme Corporation." typed for you — nothing is sent, and no AI credits are used, until you press Send. You can also ask in any session, or start from an example: + → Examples → Organizations.
The assistant reads the organization and its people — their job titles, departments and current roles, people with no role first — and decides a role for each person:
- From a job title it proposes only Decision maker, Influencer or User — or a role you added whose name the title plainly fits. What you sell counts: a CFO decides on finance software, but only influences a marketing tool.
- Champion and Blocker need a team note. A job title says what someone does, not whether they're for or against you. The assistant proposes Champion or Blocker only when one of the organization's team notes says so, and the note is shown as the source. To give it one, add a note on the organization's page; it can't read the notes on a contact's own page.
- A person with no job title is never guessed.
You don't have to use the button. Ask for the whole committee — "Map Acme Corporation's buying committee", or to review or update it — and the assistant proposes roles on the card. A plain question, such as "Who's the champion at Acme?", is answered straight from what's recorded, with no card. And if you name the contact and the role — "Set Dana's buying role to Champion" — the assistant sets it, as your edit, with no card.
The card
The card is titled with the organization's name and "buying committee", says "Proposed from job titles just now", and lists one row per person in two groups:
- No role today — will be set — people with no role. They start ticked.
- Has a role — suggested change — people whose role is different. They start unticked and show the current role beside the proposed one; tick one to change it.
A person whose role already matches isn't shown. Each row shows the person's name and job title, the proposed role and its source — "from title", or, for Champion and Blocker, a note such as "from a note by Dana, 3 Nov": the first name of the teammate who wrote it and its date. These two roles never come from a job title alone. Hover to read the reason, or the note's words. Not used lists who was left out and why — for example the people with no job title (up to five names, then "and N others"), someone no longer at the organization, or a role that's no longer offered. A card holds up to 50 people; for a larger organization the assistant tells you how many are left and can propose them on another card.
Under the rows the card says "Applying sets each contact's Buying role as your edit. Journeys watching Buying role will run." Click Apply — it shows how many roles it will set, and is off while nothing is ticked — or Skip. If you reload the page while the card is waiting, it comes back.
Applying
Apply sets each ticked person's Buying role as your own edit — the same as setting it on their page — and journeys watching Buying role start, as they do for any edit. Each row is checked again first:
- A person whose role was changed after the card was made is skipped, "changed since proposal". A person who already has the role is reported "already set", so clicking twice, or applying two cards, does no harm.
- A person who has left the organization, or was archived or merged away, is skipped, and so is a role that's been removed from your list — "role no longer offered".
- If you can't edit contacts, Apply is refused: the card says "You can't edit contacts." and turns Apply off — you can still skip.
- If saving fails, the card shows the error and stays open, so you can try again or skip.
The assistant then tells you what it set, what was skipped and why. Skip changes nothing.
Conditions
On a contact: Buying role
Wherever you build a condition on a contact — a segment, the Contacts list's Filter, a journey's If / Else, Switch, goal and exit conditions, or a trigger's conditions — you can pick Buying role and compare it with one role or none. In a segment or the Contacts list's Filter you can also match several roles at once. A journey can start when someone's role changes: pick Contact updated and watch Buying role (see Triggers).
On an organization: Buying committee
Buying committee is a read-only organization field: the roles that the organization's active contacts hold. Its conditions:
- has — at least one active contact holds the role you pick;
- has no — nobody does: "has no Decision maker" is the "No decision maker known" the Contacts card shows;
- has any of or has none of several roles;
- has any role — somebody there has a role — or has no roles — nobody does.
A trigger's conditions offer the first four.
It works wherever organization conditions do: in an organization segment, in the Organizations tab's Filter and Save as segment, and in a journey's conditions on a contact's organization, where it reads "Organization · Buying committee". It isn't a column on the Organizations list. A change to someone's role isn't a change to the organization, so Organization updated never watches it: to react when a committee changes, start the journey on Contact updated watching Buying role, and check Organization · Buying committee in an If / Else.
Example: accounts with no decision maker
- Go to Organizations and click Filter.
- Add Buying committee · has no · Decision maker — and, if you like, Type is Customer.
- Click Save as ▾ → Save as segment and name it "No decision maker known".
The segment keeps itself up to date: an organization leaves it as soon as someone there becomes a Decision maker. Use it as a journey's audience to reach the people you do know at those accounts, or open each one and click Map with the assistant.
Roles stay with your team
Roles and gaps are your team's judgment about people, so they're kept out of anything that may write to them. Routines, automations and journey AI steps are never given anyone's Buying role or an organization's committee, and they can't map one — when they look up an organization or a contact, the roles are left out. The same goes for any other run nobody is typing into, such as a scheduled insight a routine runs. A journey can still branch on Buying role or Buying committee: a condition decides which way a contact goes and prints nothing.
In a session you're typing into, the assistant sees the roles and the committee. An organization's AI summary can mention the gaps and blockers, and a change to anyone's role counts as new activity, so the summary is written again the next time someone opens the page (at most once every 6 hours). In an account plan, People we know shows each person's role and Risks and open questions names the gaps, and names blockers only while the committee counts one (see The account summary and account plans).
Privacy
A contact's Buying role is part of their data: it's included when you export it and erased with them (see Privacy). An organization's committee is worked out from its people each time, so it holds nothing of its own.
FAQ
Q: Can the assistant set roles on its own? A: No. It proposes them on a card; a role is set only when you click Apply, as your edit.
Q: Can a contact have more than one role? A: No. A contact has one Buying role, at the organization they're linked to.
Q: Can I change roles on the organization page? A: Not yet. Open the person's page and set Buying role in the Work section.
Q: Can I map many organizations at once? A: Not yet. A card maps one organization, and a routine, an automation or a journey can't map one.
Q: Why did someone's role disappear? A: They were moved to another organization or unlinked, which clears it — see The Buying role field.