Sales CRM
Configure outcome branches in a cadence
Choose whether each activity outcome continues, ends the process or skips forward to a later step.
Where to start
Sales → Sales CRM setup → Configure cadence → Outcome branches
Fields and options
- Access needed
- Administrator
- Permission and scope
- Administrator
Before you begin
Open the correct company workspace and confirm Administrator. Review the original record before following these steps. Open the relevant entry under the native Sales menu; the workspace tabs use shorter labels such as Deals, Reports, Relationships and Sales setup.
Follow these steps
- Create all the steps you expect to use before configuring jumps.
- Expand Outcome branches on the relevant step.
- For Completed, Connected, No answer, Positive, Negative and Rescheduled, choose Next step, End cadence or an existing later step.
- For example, a discovery call can continue after No answer and end after Negative. Configure Positive according to your sales process.
- Save the template, then check the selected outcome when completing an enrolled activity.
Check the result
Expand each branch and confirm every outcome has the intended destination. Check the deal history after completion: it should record the next scheduled step or the completed cadence.
If something does not look right
If the process continued unexpectedly, check which outcome was selected before Complete. A missing target is usually a removed or earlier step. Choose a valid later position. When a cadence is paused, completing an activity records the outcome but waits for Resume before applying the branch.
Fields, rules and limits
- A branch runs only when a staff member completes the current activity and records its outcome. It does not infer a result from a mailbox reply or phone call.
- Next step advances one position. On the last step it completes the cadence. End cadence also records the run as completed, with the outcome in its ending reason.
- Jumps can only target an existing later step. Backward jumps and loops are rejected. Skipped steps do not create activities.
- Unspecified outcomes default to Next step. Rescheduled is an outcome label; its configured branch still applies. It does not automatically edit the due date of the current activity.
- The target step delay is measured from the completed activity’s completion time, even when intermediate steps are skipped.
- Branches cannot be revised after the template has been used.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.