A Contact Preference Log for Calls Texts and Emails
A contact preference log tells every rep how this buyer wants to be reached. Without it, the store calls the texter, emails the caller, and burns the lead.
The internet lead said "text me, I can't take calls at work." At 2:40 p.m. a floor rep who did not read the notes leaves a voicemail. At 5:10 a BDC associate sends a long email with the same photos. At 7:00 the original rep texts "just checking in." Three channels, one irritated buyer, zero appointment. The store will call this a flaky lead. It was a preference failure.
A contact preference log for calls, texts, and emails is the smallest CRM habit that prevents that pile-on. It is not a marketing-automation suite. It is a visible, dated record of how this person asked to be reached, which channels are closed, and who last changed the record. When it is missing, every rep improvises, and improvisation looks like harassment from the buyer's side of the phone.
This guide is for used-car managers and internet directors who already have a CRM and still cannot tell whether a given customer should be called. It covers the fields, the update rules, and the coaching that make the log real.
Why a Contact Preference Log for Calls, Texts, and Emails Beats a Notes Dump
Notes are where preferences go to die. "Prefers text" on line 14 of a 40-line history will not be seen by the next up. A structured log is seen because it sits next to name and mobile, in the same place on every record.
What the log is for
- Stop calling people who asked not to be called.
- Stop texting people who opted out of SMS.
- Stop emailing a dead address while ignoring the Messenger thread they actually use.
- Stop two departments from running two cadences on the same person.
- Give a manager a way to inspect whether follow-up matched the ask.
It is also how you keep Marketplace, website, phone-up, and sold-customer records from treating every number as an all-channel license. That is the same discipline as text messaging consent basics for dealership teams, made visible for every channel, not only SMS.
What the log is not
It is not a substitute for your legal obligations, vendor suppression lists, or do-not-call files. It is the floor-facing layer. If counsel or a vendor requires a specific suppression tool, that tool still wins. The preference log is how a Saturday associate knows not to "just try them." This is operational guidance, not legal advice. Confirm required contact and privacy practices with counsel.
Fields Every Preference Log Needs
Keep it short or nobody will fill it. Six fields do most of the work.
The core record
| Field | Values that work on a sales floor |
|---|---|
| Preferred channel | Call, SMS, email, Marketplace/Messenger, in person |
| Allowed channels | Checkboxes, not a paragraph |
| Do-not-use channels | Explicit stops |
| Best time window | Lunch, after 5, weekends, unknown |
| Language | English, Spanish, other, unknown |
| Last confirmed | Date, and who confirmed it |
Add a free-text line for one constraint: "no calls at work," "husband handles email," "text only about this VIN." If the free-text line becomes a novel, the structured fields are not being used.
Status of each channel, not a single "OK to contact"
A buyer can want appointment texts and refuse marketing email. A single yes/no "OK to contact" field is how you either go silent on a hot lead or blast a closed channel. Split them. When SMS is closed, handling text opt-out requests from leads should update this log the same hour, not "when someone has time."
Identity of the number and the inbox
Log which number is the mobile, which is the work line, and which email actually gets read. Wrong-number notes belong here: "mobile in CRM is spouse; buyer uses the other." Without that, the next rep calls the spouse and starts the deal over.
Rules for Updating the Log
A stale preference is as dangerous as no preference. Write when it must be updated, and who is allowed to change it.
Capture at first meaningful contact
The first human reply is the cheapest time to ask. "Is text or a call better for you this week?" is enough. Then record the answer immediately. If the lead originated on Marketplace and they want to stay there, preferred channel is that inbox. Do not "upgrade" them to SMS as a store default.
Update on every explicit change
Triggers that should rewrite the log the same day:
- STOP or any SMS opt-out.
- "Don't call this number."
- A bounced email or a "this is not my email."
- A request to move from text to a phone appointment.
- A language request.
- A complaint about too many contacts.
The person who heard the change owns the update. If they are an associate who cannot edit the field, they notify a manager before the next cadence fire. "I didn't have access" is not an excuse for another voicemail.
Do not let reps overwrite a stop to save a deal
A manager should be the only role that can clear a do-not-use channel, and only with a new, dated yes. Floor reps will otherwise "fix" the record because the buyer seemed friendlier on the lot. Friendliness is not a logged consent. Put that in the playbook next to lead data privacy habits for dealership sales reps: the record is the store's, and it is not a personal notepad to edit for convenience.
Cadence must read the log before it sends
If your drip tool cannot read preferred and do-not-use fields, the drip is too dumb for a multi-channel store. Either fix the tool or keep those people on a manual list a human checks. Automated email to a "text only" buyer is how you train them to ignore you.
How to Run a Contact Preference Log on a Real Floor
Process beats software. A small independent lot can run this on a disciplined CRM. A larger store needs the same fields plus a weekly audit.
Morning habit for BDC and internet staff
Before the first outbound wave, filter today's follow-ups by channel. Call the callers. Text the texters. Email the emailers. Skip the stops. This sounds obvious. It is not what happens when a round-robin dump puts 40 leads on one associate with a single "call all" instruction.
Desk habit for floor reps
When a walk-in or appointment arrives, glance at preferred channel before you ask for a new number. People who already told you to text should not be enrolled in a call-only manager's contest. After the visit, update best time window. A buyer who came at 6:30 p.m. has told you something.
Weekly manager audit
Sample ten records with activity:
- Does the last outbound match the preferred channel?
- Is there a stop that was ignored?
- Did two departments contact them on the same day on different channels?
- Is last-confirmed older than it should be for an active deal?
Coach the misses in the internet meeting. Do not only coach tone. Coach whether the log was read.
Multi-lot and multi-department collisions
Sales, service, and a second rooftop can all hold the same mobile. The preference log should be customer-level, not rooftop-level, whenever your system allows it. If it does not, publish a rule: sales checks service notes before a blast. A customer who opted out of sales texts and still wants service reminders is a split preference, not a conflict to ignore.
Common Failures and How to Prevent Them
- Hidden in comments. Move preferences to fields. Comments are for color, not for STOP.
- One rep's memory. If they are off Tuesday, the log has to stand in for them.
- Channel stacking. A missed call should not automatically add SMS and email in the same hour unless the buyer asked for that.
- Ghost emails. Marketing lists that never touch the sales preference log will email people your BDC has already soothed.
- Marketplace amnesia. The buyer is live in Messenger while three people call the extracted number. Assign one owner and one channel until they ask to switch.
A preference log will not raise close rate by itself. It will stop your own team from becoming the reason the lead went cold.
How PostToMarket Automates This
PostToMarket is not a CRM and it does not replace your preference fields. It does keep the original Marketplace inquiry and the vehicle in a store-visible workflow, which is where a lot of "just call them, I have their number" behavior starts. When the thread and the unit are visible to a manager, you can insist that follow-up match the channel the buyer is already using.
One place to see the inquiry
- Leads inbox so managers can see Marketplace conversations instead of reconstructing them from personal phones.
- Team analytics by rep and source to spot shotgun follow-up patterns.
The vehicle state that should drive contact
Do not contact someone three ways about a unit that is sold. Inventory statuses and mark as sold and archive from inventory or the queue keep the catalog honest so preference-respecting follow-up is about a car you still have.
Ownership without shared logins
- Per-rep queues, manager assignment for associates, and a team queue view to release claims.
- Mobile dashboard so a rep can reorder posting work between customers without dumping leftover tasks into a random text.
Keep the preference log in the CRM. Use PostToMarket so the lead's first channel and the inventory status are not a mystery.
Put Preference Next to the Phone Number
A contact preference log for calls, texts, and emails is a visible, dated set of fields plus a rule that cadence must read them. If your team still treats every lead as "call, then text, then email," you are running a volume contest, not a customer process. Build the log, audit ten records a week, and make stops impossible to miss.
PostToMarket holds unlimited inventory, a leads inbox, and role-based queues so the store can see the work. The Starter plan is $59 per month for one login on a solo lot. The Dealership plan is $299 per month for up to 13 logins so BDC and managers are not guessing from one person's phone.
Start your 10-day free trial with secure Stripe checkout. Get inquiries into a shared inbox, then attach the preference habit in your CRM. Cancel anytime.