What's New

Give a sales stage rules of its own

A stage on the CRM board can now run rules when a lead arrives or has sat there too long: assign an owner, add a tag, notify the team, start a cadence, move the lead on, and more. It can also refuse to let a lead leave until a note, an owner or a booking is in place.

A sales stage used to be a place a card sat. It can now do things when a lead arrives, chase a lead that has been sitting there too long, and refuse to let a lead move on until the work that stage stands for is done.

All of it lives under Company Info, then CRM, on the stage itself.

Rules

Each stage carries its own list of rules. A rule is one sentence: when this happens, do this. The When is either the moment a lead arrives in the stage (whoever moved it: a person, the AI, a flow or another rule) or once a lead has sat in the stage for a number of days you set, checked once a day.

The Do this options are:

  • Assign an owner, alongside anyone already there.
  • Add a tag.
  • Notify the team, as a dashboard notification and an email to the teammates you pick.
  • Add a note to the lead.
  • Create a follow-up by email or SMS, a set number of days out.
  • Start a follow-up cadence.
  • Send an NPS survey.
  • Move the lead to another stage.
  • Archive the lead.

A rule can be switched off without deleting it, and every batch of rules writes one line to the lead's activity saying what ran and what was skipped.

What a rule will not do

Rules are built so they cannot loop. A rule that moves a lead does not run the destination's rules, so one arrival causes at most one further move. A rule never blocks the move that triggered it: if it points at a cadence you deleted, the move still happens and the rule is skipped with the reason recorded. A dwell rule fires once per visit, and the clock only starts for leads that move from now on, so nothing fires against leads that have been sitting still since before this shipped.

Exit requirements

Separately, a stage can insist a lead has something before it may leave: a note, an assigned owner, or a completed booking. Set it under Before A Lead Can Leave, then choose what happens when something is missing: ask the person for a reason and record it on the lead, or refuse the move until it is done.

One more change: a card dragged on the CRM board now fires everything a move made any other way fires, including cadence triggers, NPS triggers, flow events and the stage's own rules.

Coming next

What's next

Keep up with QuickCasa

Want this on
your portfolio?

Book a demo to see what's live today, or browse every update we've shipped.