Who Sees What: Lead Visibility Rules in Your CRM

A new associate opens the CRM on a Tuesday and scrolls a list of 400 internet leads. Half are named to other reps. A few are marked hot. One has a note from last night: "coming Saturday, wants the F-150." The associate texts that customer from a personal phone, "just checking if you still want the truck." The assigned rep, who already set the appointment, walks into a confused conversation and a customer who now thinks two people at the same store do not talk to each other.

Open visibility feels fair. In practice it turns the pipeline into a buffet. Lead visibility rules in your CRM decide who can see, edit, reassign and close a record. Get them wrong and you get poaching, duplicate outreach, and managers who cannot see the real book because reps hide leads in personal inboxes. Get them right and a covering associate can work a shift without shopping the whole floor.

This guide is for general managers, internet directors and used-car managers. It is operational, not a vendor setup manual. Write the rules in plain language, then map them onto whatever permissions your CRM actually offers. If the software cannot match the rule, change the process or change the tool — do not pretend a permission you do not have is "the policy."

Who Sees What Goes Wrong Without Lead Visibility Rules

Everyone-sees-everything invites cherry-picking

Reps will work the newest, highest-priced, most-talkative leads, regardless of whose name is on the file. Older leads, lower-priced units and quiet shoppers starve. The CRM still shows "assigned," so the original owner looks lazy while someone else skimmed the cream.

Locked-to-owner with no coverage creates dead air

The opposite failure is a file only the assigned rep can open. That rep takes a day off, calls in sick, or leaves at 6 p.m. while Marketplace messages continue. The lead goes cold inside a permission setting. Coverage needs a controlled window, not a free-for-all.

Managers flying blind

If managers cannot see every open internet lead, they cannot run aging, cannot settle ownership disputes, and cannot tell whether the BDC is actually working the book. Manager visibility is not optional. It is how the store stays honest.

Personal inboxes become the real CRM

When the CRM is either too open or too closed, conversations migrate to personal Messenger, personal texts and paper. Visibility rules only work if the record of the conversation lives in a system the store controls. Pair this with lead data privacy habits for dealership sales reps so "I have it on my phone" is not an accepted filing system.

A Practical Visibility Model for a Used-Car Floor

You do not need a dozen roles. You need four viewing layers and a coverage exception. Map them to admin, manager, sales rep and associate the way your store actually works.

Layer 1: Assigned owner

The named owner sees the full record: contact details, notes, status, appointments, and the unit of interest. They can edit notes and status. They cannot delete the lead. They cannot reassign it to themselves from someone else — only a manager can reassign.

Layer 2: Coverage group

A small group can see a limited view of leads they are covering: name, vehicle, next step, contact preference, and the last note. They can add a coverage note. They cannot change owner. They cannot see the full history of every other rep's book. This is how Saturday and after-hours work without opening the buffet.

Layer 3: Managers and internet director

Managers see every internet lead, every owner, every aging bucket, and every disposition. They can reassign, merge duplicates, and close junk. They are the only people who can move a lead from one owner to another without a documented coverage window.

Layer 4: House and unassigned

Unassigned leads are visible to the people allowed to claim them under your distribution rule. If you use round-robin, the system assigns and the owner then has Layer 1 rights. If you allow self-claim from a house queue, show the house queue to eligible roles and hide everyone else's book. Fairness lives in fair lead distribution on the sales floor, not in a shared search of the entire database.

What associates should not see

Junior associates who post and take first replies do not need the whole store's sold-lost history, other reps' commission notes, or home addresses on deals they do not own. Give them the coverage view plus their assigned queue. Curiosity is not a business need.

Write Lead Visibility Rules as If a Dispute Will Happen Tomorrow

Visibility fights show up as "that's my customer." Put the answers in writing before the fight.

Default visibility

• Sales reps see their own open leads and their own sold-pending files.
• Associates see only leads a manager assigned to them, plus any coverage list for their shift.
• Managers see all internet leads for the rooftop.
• No one except managers sees another rooftop's leads in a multi-lot group unless you have a documented shared-internet model.

Coverage windows

Define when Layer 2 opens:

• Named days off, already on the schedule.
• After closing until opening, for the person on after-hours duty.
• Mid-shift when the owner is on a test drive or at lunch, if you want live coverage — many stores skip this and accept a short delay rather than constant overlapping texts.

When the window closes, coverage notes stay on the file. Ownership returns to the named rep unless a manager reassigns.

Reassignment

Only managers reassign. Reasons belong in a note: day off with no coverage, unworked past the SLA, customer request, or departure. For the departure case, use your protecting leads when a salesperson leaves process so visibility and ownership change together, not a week apart.

Customer-initiated contact with a different rep

If a customer messages a second person at the store, that person logs the contact on the existing file if they can see it, or flags a manager if they cannot. They do not open a second lead. They do not "win" the customer by being the second inbox. Duplicate records are how visibility rules get bypassed.

Implementation Checklist in Any CRM

CRMs differ. The checklist does not.

1. List the roles you actually have. Do not invent a CRM role you will not staff.
2. Turn off global search of other reps' open leads for non-managers, if the product allows it.
3. Create a coverage permission or a coverage queue, even if it is a saved filter a manager enables for a shift.
4. Keep sold and lost files visible to managers and limited for reps — enough to recognize a be-back, not enough to mine the archive for names.
5. Log permission changes. If a manager opens a book for coverage, there should be a record of when and why.
6. Train the floor on what they will not see. Surprise is what drives people back to personal phones.

Multi-lot special case

Two lots on one CRM is the most common visibility leak. A rep at Lot A should not be working Lot B's Marketplace leads unless they are scheduled to cover that rooftop. Pin visibility to location the same way you pin inventory to location. A shared "internet" team can be a third location in the permission model, with its own book and its own manager view.

BHPH and special-finance files

If those deals carry extra personal financial detail, tighten visibility further. The internet associate who answered "is this available?" does not need the full credit file. Limit sensitive screens to the people who desk and finance. This is operational hygiene; confirm with counsel if your state or your group has specific record-access rules. This article is not legal advice.

How Managers Use Visibility Without Becoming the Bottleneck

Daily look, not daily takeover

Managers should open the all-leads view to find aging, dual ownership and unassigned records — not to work every lead themselves. If the only person who can see the book is the internet director, you have a single point of failure, not a control.

Settle disputes from the record

When two reps claim a customer, the visibility log, the first CRM create time, and the first note beat a hallway argument. If those are missing, fix the intake process. Do not reward the person who shouted.

Mystery-shop your own permissions

Once a quarter, log in as an associate (or sit with one) and try to open another rep's hot lead. If you can, the rule is theater. If you cannot cover a scheduled day off, the rule is too tight. Adjust the permission, then rewrite the one-pager so the floor's understanding matches the software.

How PostToMarket Automates This

CRM visibility fights often start outside the CRM: one shared Facebook login, one shared posting queue, and inquiries landing on whichever phone still has the session open. PostToMarket does not control your CRM permissions. It stops the shared-login pattern that makes "who saw the lead first" impossible to answer.

Separate people, separate work

• Roles: admin, manager, sales rep and sales associate, each with a login. Associates work manager-assigned queues; sales reps self-queue from shared inventory.
• Per-rep posting queues so the person posting a unit is visible, which makes it easier to name the right CRM owner when the first message arrives.
• Team queue view where managers can see and release any claim, the same idea as a manager-only reassignment in the CRM.

Manager sight without a buffet on the floor

• Leads inbox for managers so internet directors can review inquiries without putting every thread on every associate's phone.
• Team analytics by rep and source so you can see who is posting and from where, without handing every rep everyone else's book.
• Mobile dashboard so a covering rep can reorder their own queue between customers instead of browsing the entire store's list.

Inventory state that coverage can trust

• Statuses (draft, posting, posted, sold, failed) and mark as sold from inventory or the queue, so a covering associate does not message a customer about a unit that is already gone.

Visibility is a people rule. PostToMarket makes the posting side of that rule enforceable so the CRM is not compensating for a shared inbox.

Close the Buffet, Keep Coverage

Who sees what is not a philosophy about teamwork. It is a permission model: owners work their book, coverage sees a slice on a clock, managers see everything, and nobody shops the store. Write the four layers, test them by logging in as an associate, and pair them with a reassignment note that a grown-up can read.

If leads currently live in personal profiles and shared passwords, CRM rules will not save you. Give each person a login, a queue and a manager view that actually matches how the floor runs.

PostToMarket includes unlimited inventory, per-rep queues, a team queue view, a leads inbox, and AutoPost with human-like delays. The Starter plan at $59 per month is one login for a solo seller. The Dealership plan at $299 per month is up to 13 logins for a real floor.

Start your 10-day free trial with secure Stripe checkout. Assign queues the way you want CRM visibility to work, then keep sold units off the coverage list. Cancel anytime.