Pipeline Rules for Contacts and Companies

What it is

You can now set pipeline rules for contact and company lifecycle stages, the same kind of rules already available for deals, tickets, leads, and custom objects. You can define which stages a record can be created in, whether stages can be skipped, and whether a record can move backward. Alongside it, a general enhancement lands for every object type with pipelines: admins can now set the default stage a record is created in. That default-stage control is the new piece this round, and it applies well beyond contacts and companies. Available for Professional and Enterprise tiers, in public beta.

Why it matters

These are guardrails for data quality, and the honest framing is that they are really lifecycle-stage rules, since the lifecycle stages are the pipeline of a contact or company. Preventing records from skipping critical stages or being created in the wrong phase is what keeps conversion rates and stage reporting trustworthy. Not every company wants records to start in the same place, and the new default-stage setting is what makes that controllable instead of assumed. For a portal-level look at how these guardrails behave in practice, our show conversation on pipeline rules for contacts and companies walks through it: how lifecycle-stage guardrails play out in a real portal.