> ## Documentation Index > Fetch the complete documentation index at: https://docs.salesfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # Rules of engagement > Scenarios that decide who may be enrolled and when a step may run, reactions that decide what an outcome does, the team default policy, and approvals. Rules of engagement are the team's policy for outreach. They are evaluated automatically: when someone is enrolled, before a step runs, and when an outcome happens. Reps do not have to remember them. Manage them under **Sequencer › Rules of engagement**. A team has one **default policy** that every sequence uses. A sequence can be given a different policy of its own, for example a lighter one for a re-engagement cadence. A policy has two halves: **scenarios** and **reactions**. ## Scenarios: who may be enrolled, and when a step may run A scenario is a condition group plus an action plus a scope. Conditions in a group can be combined with AND and OR. ### Conditions | Condition | What it checks | | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- | | CRM owner is another rep | The contact's owner in the CRM is not the rep enrolling them. | | Open deal in the CRM | The contact, or their company, has an open deal. | | CRM field | A CRM field on the contact or company matches a value, for example Lead Status or Deal Stage. Options are read live from your CRM. | | Opted out in the CRM | The CRM marks the contact as opted out of email. | | Active in another sequence | The person already has a live enrollment in a different sequence on the team. | | Touched within the last N days | Anyone on the team called, emailed or sequenced this person within N days. | | N unopened emails in a row | The current enrollment has sent N emails without an open. | | N unanswered calls in a row | The current enrollment has logged N calls without a connect. | | Contact field | A Salesfinity contact field matches a value. | ### Actions | Action | Effect | | ------------------------- | ------------------------------------------------------------------------------------------------------- | | **Do not enroll** | The prospect is skipped and the reason is reported in the preview. | | **Enroll with a warning** | The prospect is enrolled; the warning is shown and logged. | | **Hold for approval** | The prospect is enrolled in a pending state until a manager approves or rejects it. | | **Skip this step** | The step is passed over and the cadence continues. | | **Pause the enrollment** | Pauses; resumes automatically after the given number of days, or stays paused until someone resumes it. | | **Finish the enrollment** | The prospect leaves the sequence. | ### Scope Where the scenario is checked: **when enrolling**, **before every step**, **before an email step**, or **before a call step**. "Do not enroll", "enroll with a warning" and "hold for approval" only make sense when enrolling; "skip this step" only makes sense before a step. ## Reactions: what an outcome does An outcome is something that happened on the enrollment. Each reaction pairs one outcome with one or more actions. ### Outcomes | Outcome | When it fires | | ----------------------------------- | ----------------------------------------------------------- | | Meeting booked | A call was dispositioned as meeting set. | | Positive reply | A reply was classified as interested or a meeting request. | | Not interested | A reply or a call disposition said no. | | Asked to call back later | A call was dispositioned as callback later. | | Asked to reach out in a few months | A call was dispositioned as reach out in six months. | | Deal opened in the CRM | A deal appeared on the contact or company after enrollment. | | Finished without a reply | The cadence ran out of steps and nobody answered. | | A reply matched one of your labels | A custom reply label from **Sequencer › Settings** matched. | | A call got a particular disposition | Any disposition you pick. | ### Actions | Action | Effect | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | Finish this contact's sequence | The prospect leaves the sequence. | | Pause this contact | Pauses, optionally resuming after N days. | | Enroll in another sequence | Hands the prospect to a follow-up sequence after N days, owned by the original rep or by the follow-up sequence's owner. | | Create a task for the rep | A call, email or to-do lands in the rep's inbox with a note and priority. | | Finish everyone else at the company | Ends the other enrollments at the same account, in this sequence only or in every sequence on the team. | | Pause everyone else at the company | Same reach as finishing, but the enrollments resume later. | ## The default policy New teams start with a default policy that most teams keep: * **Warn** when the CRM owner is another rep. * **Do not enroll** contacts with an open deal. * **Do not enroll** contacts the CRM marks as opted out. * **Warn** when another rep is already working the contact. * **Skip the email step** after 3 unopened emails in a row. * **Skip the call step** after 4 unanswered calls in a row. * **A meeting** stops outreach to everyone else at the company, across every sequence on the team. * **A positive reply** stops outreach to everyone else at the company, across every sequence on the team. ## Approvals When a scenario holds an enrollment for approval, it shows in the sequence's people list as **Awaiting approval** with the rule that held it. A manager approves or rejects it there, singly or in bulk. Approved enrollments start at their first step; rejected ones are finished with the note the manager left. Both decisions are recorded on the enrollment's timeline. ## Preview a policy **Preview** on the rules page runs a policy against a person or a list without enrolling anyone, and shows which scenarios would fire. Use it before changing the default policy on a busy team. ## Permissions Creating and editing policies, and setting the team default, is limited to team admins. Reps can see which rule applied to an enrollment and why.