What Is the Difference Between Claiming and Engaging an Account in Unify?
Claiming an account assigns it to a rep and adds it to that rep's book of business. Engaging an account means taking outreach actions, such as creating tasks, enrolling people in sequences, or making outbound calls. Unify controls the permissions separately. A rep can be allowed to engage without claiming; a policy can also assign an eligible account automatically when the rep engages.
Ownership is therefore one input to the outreach decision. It does not override exclusions or guarantee permission to contact every person at the account.
What changes when you claim or engage?
The account eligibility guide explains the distinction and where reps can inspect the rules that apply to them.
| Action | What it means | What it does not establish |
|---|---|---|
| Claim | Assign the company to your book through the policy's ownership rules | Unrestricted permission to contact the account |
| Engage | Take an outreach action such as a task, sequence enrollment, or call | An ownership change in every policy |
Your book of business organizes assigned accounts for daily work. A book ranking helps prioritize them. A high-priority account can still be restricted: priority, ownership, and outreach eligibility answer different questions.
Can you engage without claiming?
Yes, when the applicable policy allows engage-only access. In engagement policies, an administrator can configure eligible existing CRM companies for claiming and engagement, or engagement only. If claiming is allowed, the administrator can choose whether engagement assigns the account automatically or reps must claim it themselves.
Rules can differ for companies in another policy member's book. A policy can allow engagement with a warning or restrict engagement to the assignee. Claiming another member's account can depend on the configured inactivity rule. Do not treat another team's choices as universal Unify defaults.
New companies have their own policy settings. Claiming or engaging an eligible company that does not yet exist in the CRM creates its CRM record. If automatic claiming on engagement is allowed, Unify also assigns the company to the rep. Creation and assignment remain distinct effects to inspect.
Where can a rep check what is allowed?
Open Book of business → What accounts can I work? to review your team's rules. For a particular company, inspect the restriction shown beside its name. The eligibility guide describes how to respond to a claim-first requirement, a warning, or a blocked action.
Read the reason before acting. A claim-first restriction can require an ownership step; a warning asks you to review context; a block prevents the action. Repeating the same action from a different screen is not a way to establish that the account is eligible.
The underlying workflow also matters. Creating a task, enrolling someone in a sequence, and making a call are distinct actions. Check the account restriction relevant to the work you intend to perform, rather than inferring permission from the ability to view the record.
Which exclusions and ownership settings still apply?
Engagement policies require permission to manage them and a workspace CRM connection with bidirectional syncs enabled. The policy uses a CRM ownership field, such as the standard company owner or a separate user field. The documented setup supports Salesforce and HubSpot. The ownership mapping must be ready before relying on the policy's assignments.
Each exclusion can independently Allow, Warn, or Block claiming and engagement. Other rules still apply; when several rules match, the most restrictive result determines the outcome. An account already in your book can therefore remain blocked for outreach.
For users assigned to an engagement policy, its exclusions replace sequence ruleset exclusions. Administrators should add the intended workspace exclusions to the policy, including protections previously applied through sequence exclusions. Users without an engagement policy follow other applicable workspace restrictions. Do not assume the same configuration governs both groups.
Members and roles also affect which controls a user can access. Being a rep who can work an account does not mean that rep can publish or edit the team's policy.
What should your team verify before outreach?
Use this blank checklist with the account you actually intend to work. It is a review aid, not a record of a completed test.
| Question | Evidence to inspect | Your finding |
|---|---|---|
| Who owns the account? | Policy ownership field and CRM mapping | |
| Which action is permitted? | Claim, engage, or engage-only eligibility | |
| Why is there a restriction? | Account warning or block and matching rule | |
| Will engagement assign ownership? | Automatic-claiming setting | |
| Is this a new CRM company? | New-company policy and resulting CRM record | |
| Which exclusions apply? | Assigned policy and its selected exclusions |
Resolve an unexpected restriction with the administrator responsible for the policy. Preserve the account identity and the displayed reason so the administrator can inspect the relevant rule. A generic permission change is a poor substitute for understanding why that specific account is protected.
For broader workflow design, see outbound routing with CRM ownership data. For the immediate rep decision, start with What accounts can I work? and the restriction on the account you intend to contact.
Frequently asked questions
Does engaging an account always claim it?
No. Engage-only access is possible. Automatic assignment depends on the policy and whether claiming on engagement is enabled for that eligible account.
Can I contact every account in my book?
No. Exclusions and other policy rules still apply to owned accounts. Check the restriction before taking outreach actions.
Do engagement policy exclusions add to sequence ruleset exclusions?
For users assigned to a policy, policy exclusions replace sequence ruleset exclusions. Administrators should configure the protections intended for that team in the policy.
Can every rep change the policy?
No. Managing engagement policies requires the relevant permission. Reps can inspect their eligibility and ask the responsible administrator to review unexpected restrictions.
