Use case

A services company → the contract number is there before the lead is saved

October 27, 2026
Widget Conditional Required
Abstract list of leads, each with a filled-field mark

A services company sells to businesses and to individuals. Business clients pay by invoice and need a contract; individuals pay by card and need none. The sales team keeps saving invoice leads without a contract number, and the accountant chases them a week later.

The scenario

Kommo’s “required for a stage” would force the contract number on every lead at the stage, including card payments. The company needs a rule that depends on another field.

The rule

  • Required field: Contract number.
  • When: Payment method is Invoice and the sales value is at least 10000.
  • Stage: Contract discussion.
  • What happens: warn first for the first week, then block the save.

What changes

A manager who moves an invoice lead into Contract discussion and presses Save sees a message: the contract number is required because the payment method is Invoice and the sales value is at least 10000. Card leads are not touched. After a week of warnings the rule is switched to blocking, and the accountant gets the number with the lead.

Where it stops

The widget checks the Save of the lead card. A lead dragged between stages on the pipeline board, a bulk change or an import is not checked.

Data: demo account, made-up data. Results depend on your pipeline.

5
conditions per rule, joined by AND or OR
2
modes: warn first and block the save
$100
per year for the whole account