Deal automation settings
Deal automation controls how Helpin turns customer evidence into deal recommendations, and when those recommendations can act without waiting for review. Use this page to set confidence thresholds and decide which signals reach your team. Only CRM admins can open and change these settings.
Open the settings
Go to Settings → CRM → Deal automation. You can also select the Autonomy icon at the bottom of the CRM menu.
Deal recommendations
Setting | What it does |
|---|---|
Enable deal recommendations | Lets CRM activity produce deal suggestions. Turn it off to stop new deal recommendations. |
Create-deal recommendations | Suggests a deal when corroborated activity shows buying intent. |
Stage-change recommendations | Suggests the next stage when recent evidence shows real progress. |
Direct execution threshold | The recommendation confidence required before Helpin may act without review. Choose 50% to 100%. The default is 90%. |
Review threshold | The recommendation confidence required for a suggestion to enter the review queue. Choose 30% to 100%. The default is 70%. |
Select Save Settings to apply your changes.
How the thresholds work
At or above the direct execution threshold, Helpin can create or advance the deal directly, but only when every supporting signal is verified and its rule version is live.
Between the review threshold and the direct execution threshold, the suggestion waits for review.
Evidence that is unverified, lower trust, or from a rule that isn't live always requires review, whatever its confidence.
Signal rules start in shadow mode, so a new workspace gets suggestions for review before anything runs directly. See CRM suggestions.
Signal activation and routing
These settings decide which signals become work for your team.
Setting | What it does |
|---|---|
Minimum lane priority | An account enters a signal lane only when its evidence reaches this score. Select Save inbox settings. |
Default signal owner | Who receives signals when there is no CS owner or company owner. Choose a member or Unassigned but visible. The workspace owner is the final fallback. |
Minimum business priority | The lowest priority a signal needs to be routed. |
Required identity trust | Verified only, Probabilistic or verified, or All identity levels. |
After you set priority and trust, select Save and activate policy. Until a routing policy is active, signals stay as context only.
Promote a signal rule
The Rule versions list shows each signal rule with its status: Live, Shadow, Context only, or Disabled. Where your team has reviewed signals, it also shows precision based on that feedback.
To let a rule create work for your team:
Review the rule's evidence and precision.
Select Promote for that version.
Confirm. Only evidence that also passes identity, priority, and routing checks becomes actionable.
Related articles
Was this article helpful?