Deals
Configure stuck-deal thresholds, speed-to-lead alerts and loss reasons
Three settings on one screen shape a sales team's discipline in Naffes CRM: when a deal counts as stuck, when the owner hears that nobody has contacted a new lead, and how loss reasons are recorded. Admins set them; the whole team feels the effect.
Where the settings live
Open the deals settings
Go to Settings → Records & Fields → Modules → Deals.
Set the stuck thresholds
Under Stuck Deal Thresholds, set the Watch (early warning), Stuck and Frozen multiples. They must rise in order: above zero, then watch below stuck, and stuck below frozen.
Set speed to lead
Under Speed to lead, set the minutes for Tell the owner after and Tell the managers after. Leave a field empty for the default, or enter 0 to switch that rule off. The managers' delay must be longer than the owner's.
Manage loss reasons
Under Lost Reasons, click Create Lost Reason or edit and remove existing ones. Then decide on Lost reason is required and Allow sales agents to enter custom lost reason, and save.
How stuck thresholds work
Stuck is measured against each stage's usual time, set on the pipeline page. The default multiples are 1, 2 and 3. Example: a Negotiation stage with a 10-day usual time flags a deal Watch after 10 days, Stuck after 20 and Frozen after 30. If your cycle varies a lot, raise Watch to 1.5 to cut early noise.
Flagged deals show under the Stuck quick filter on the deals list, and their count appears on the metrics rail. A stage without a usual time stays out of the calculation, however long a deal sits in it.
How speed-to-lead alerts work
| Rule | Who is alerted | When |
|---|---|---|
| Tell the owner after | The deal owner | After the minutes you enter, or the default printed under the field if you leave it empty |
| Tell the managers after | Workspace managers | After a longer delay than the owner alert (60 minutes by default), or at once if the deal has no owner |
Outreach counts as a message, a logged call, or an email sent from the app. The check runs every minute and only looks at deals created in the last 48 hours, so old deals never trigger a flood of alerts. A line under the card sums up the two delays in force. To track the whole team's response speed, install the ready-made Speed-to-lead board from the Dashboards page.
Choosing a loss-reason policy
- Five reasons to start: Price, Timing, Went with competitor, No budget and Lack of expertise.
- Reason required (default): reps must pick one when marking a deal lost, from the button or the Kanban board.
- No custom reasons: with the custom-reason switch off, reps are limited to the list and the server refuses any other text, so loss reporting stays groupable.
For closing the deal itself, see mark a deal as won or lost.
Questions
Questions 2
What counts as reaching out to a new lead?
A message from a person, a logged call, or an email sent from the app. Email sent outside Naffes is not seen.
Can each pipeline have different usual times?
Yes. Usual time is set per stage on each pipeline's page, while the multiples apply to the whole workspace.