CRM Contacts
Assigning a contact to a rep
Giving a contact an owner, moving them to someone else, and why unassigned work is work nobody does.
Last updated September 2, 2026
Every contact being worked should have someone's name on it. Assigned to is that name, and it drives the personal lists and dashboards the whole team works from.
Assigning one
Change Assigned to at the top of the contact's profile. It saves immediately. The list of people you can pick from is the tribe's team members who are included in the CRM — see Team Members if someone is missing from it.
Assigning a lot at once
Filter the contacts list to the set you want, tick them, and use Bulk Edit. This is how a new starter gets a patch, and how someone's accounts get shared out when they leave.
What assignment actually changes
| Assignment does | Assignment does not |
|---|---|
| Put the contact in that person's My Contacts. | Hide the contact from anyone else — the whole tribe still sees it. |
| Feed their dashboard and activity report. | Move tasks. A task keeps the owner it was given. |
| Give a name to chase when nothing is happening. | Notify the new owner on its own — book them a task as well. |
CHECK THE UNASSIGNED FILTER EVERY WEEK
An unassigned contact is invisible on every personal dashboard, so nothing about it ever feels urgent. Filter Assigned To → Unassigned once a week and the leak closes.
When someone leaves
- Filter contacts by Assigned To — them.
- Bulk reassign to whoever is taking the patch.
- Check their open tasks and opportunities too. Reassigning contacts does not move either.
- Only then remove them from the tribe.