What Counts as a Touch: Defining Contact Attempts per Lead

Your CRM says a Marketplace lead received eight touches in three days. The customer says they heard from you once. Both can be true. The eight "touches" were two unanswered calls logged as attempts, a voicemail that never recorded, three auto-logged emails the customer filtered, a CRM note that says "working," and a text that bounced. The one real contact was a Marketplace reply that actually reached the buyer.

Until the store defines what counts as a touch, every activity report is a negotiation. Managers think the floor is working leads. Reps think they are being measured on busywork. Customers experience silence. Contact attempts per lead become a vanity number, the same way raw posting volume is a vanity number if listings never get seen.

This article gives used-car managers a definition they can train, audit, and pay against. It is an operating standard, not a published industry rule. Tune it to your CRM, your channels, and your state's contact rules, and confirm text and calling practices with counsel. Nothing here is legal advice.

Why Stores Need a Written Definition of a Touch

Activity metrics collapse when the unit of measure is fuzzy. "I touched it" can mean anything from a completed conversation to opening the record and closing it.

Inflated counts hide dropped leads

Consider a lot with 60 internet leads in a week. If every voicemail, every CRM open, and every duplicate auto-email counts, the store looks busy. Sort the same list by "customer-confirmed contact" and you may find a thin set of real conversations. The gap is where appointments should have been set.

Pay plans and spiffs will get gamed

If you pay or rank people on touch count without defining the touch, you will buy the behavior you specified: more logs, not more conversations. A definition is a fairness tool. Reps who actually talk to buyers should not lose a leaderboard to reps who click save eight times.

Follow-up cadences only work on real attempts

A cadence that says "attempt 1, 2, and 3 across two days" is meaningless if attempt 1 was an auto-reply and attempt 2 was a blank note. Pair your definition with a follow-up cadence for Marketplace leads so the sequence and the unit of measure match.

What Counts as a Touch on a Used-Car Floor

Write one sentence at the top of the policy: a touch is a contact attempt the customer could reasonably have received, logged with evidence, on a live lead, by a named person. Then break it into rules the desk can apply in seconds.

The core test

A logged event counts as a touch only if all of the following are true:

• Outbound intent: the store tried to reach the customer, or completed a live conversation.
• Reachability: the attempt used a channel the customer used or consented to (call, text, email, Marketplace/Messenger, in-person).
• Evidence: a note, recording, screenshot, or system log that shows what happened, not just that someone opened the record.
• Live lead: the unit is still available or the conversation has moved to an alternative unit. Pitching a sold car is not a productive touch.

Opening the CRM, starring a record, or assigning the lead to yourself is not a touch.

Completed conversations vs. attempts

Track two buckets. Do not mix them in one column.

• Attempt: you reached out; you do not know if the customer received it (ring-no-answer, voicemail left, text sent, Marketplace reply sent).
• Connect: two-way contact happened (live call, two-way text, two-way Marketplace thread, in-person).

Managers should manage connects. Attempts are the leading activity that should produce connects. If attempts are high and connects are low, the issue is timing, number quality, or message quality, not effort theater.

What never counts

Publish a short exclusion list:

• Auto-responders and chatbot first lines, unless a human took over in the same thread within the store's stated window.
• Duplicate sends of the same email or text in the same hour.
• Internal notes ("will call later," "hot," "working").
• Viewing a Marketplace thread without replying.
• Calling a bad number after the first confirmed disconnect, unless a new number was found.

Contact Attempts by Channel: Calls, Texts, Messages, and Voicemail

Channel rules stop arguments. Put them on a one-page card at the BDC desk.

Phone calls

Two dials in two minutes to the same number are one attempt, not two. The customer did not get two chances; they got a redial.

Text messages

A text counts when it is sent to a number the customer provided or used, contains a real message (not a blank or a failed template), and is logged with the copy or a summary. A bounce or "undelivered" is not a touch; it is a data problem. Stop-and-honor opt-outs immediately. Confirm your texting practices with counsel; this is not legal advice.

Marketplace and social messages

A human reply in the thread counts. A saved reply fired without reading the customer's question can count as an attempt in your CRM, but it should not count as a quality connect. If two reps reply in the same thread, that is still one customer-facing touch, plus an internal process failure. Log the first meaningful reply.

Email

Email counts when it is sent to a working address, is not a duplicate of a message sent the same day, and is not a newsletter blast. Marketing drips are not sales touches. If your CRM auto-logs every template, turn that off for the sales activity report or tag marketing separately.

In-person and appointment-related contact

A show, a no-show call, and a "we're ready for you" confirmation can all count if they are real outbound or live contact. Walking past the customer in the service lane does not count unless you actually spoke about the deal.

How Many Contact Attempts per Lead, and How to Audit Them

Definition without a cap still produces spam. Definition without an audit still produces fiction.

Set a sequence, not a lifetime total

Do not tell reps "make eight touches." Tell them the sequence:

1. First human reply on the inbound channel, as fast as the store's in-hours standard allows.
2. A same-day second channel if the first was unanswered (for example, Marketplace reply then a call if a number exists).
3. A next-day follow-up with a new piece of information (availability, similar unit, appointment options).
4. A stop or recycle after a written number of unanswered attempts.

The exact count is a store decision. Write it down. Raise it only if connects, not just logs, improve.

Evidence standards for the CRM

Require enough detail that a manager can reconstruct the attempt from the note. CRM note standards for lead conversations should match this definition so logging and scoring are the same conversation. Minimum fields:

• Channel
• Attempt vs connect
• Timestamp
• What was said or asked
• Next step and time

"LM" and "N/A" fail the evidence test.

Weekly audit that takes fifteen minutes

1. Pull ten leads marked as fully worked.
2. Count CRM events vs. events that pass the core test.
3. Call out the delta in the internet meeting, without humiliating people in public if the definition is new.
4. Recode the report if the CRM is auto-logging junk.

After two weeks of auditing, the definition will either stick or you will discover the CRM is padding the report. Fix the report. Do not train people to feed a bad counter.

Tie the definition to the store playbook

The touch definition belongs inside your lead handling playbook, not as a side argument in a sales meeting. When a new hire asks "does a voicemail count?" the answer should be a page number, not a debate.

How PostToMarket Automates This

False touch counts often start upstream of the CRM. A sold unit is still listed, so reps "touch" buyers about a truck that is gone. Two people posted the same VIN, so two threads look like two leads. Managers cannot see which inquiries were actually answered. PostToMarket does not replace your CRM's task engine. It makes the inventory and inquiry layer honest enough that contact attempts refer to real, available vehicles and visible conversations.

Stop working ghosts

• Inventory statuses and mark as sold / archive so follow-up energy is not spent on units that already left the lot.
• Bulk import with a row-level error log so bad phone fields and missing prices are caught before a listing creates a junk conversation.

One owner per conversation

• Per-rep queues and manager assignment so the person who should attempt contact is named, which is the first requirement of a real touch log.
• Roles that keep associates from silently working (and double-logging) a senior's leads.

A leads inbox managers can audit

• The leads inbox gives managers a place to see inquiries instead of taking a rep's word that eight touches happened.
• Team analytics by rep and source show posting and source patterns that should match CRM activity, not contradict it.
• The mobile dashboard lets a rep log a real next step between customers instead of batch-logging "touches" at 8 p.m. from memory.

PostToMarket is not affiliated with Meta. It cannot guarantee reach or that a logged attempt becomes a connect. It can reduce the operational mistakes that turn contact reports into fiction.

Count Conversations, Not Clicks

If you cannot say what counts as a touch, you cannot say whether the floor is working. Define contact attempts per lead, exclude the junk, audit ten records a week, and put the definition in the playbook. The stores that do this stop arguing about activity and start arguing about appointments, which is the argument worth having.

PostToMarket keeps the vehicles, queues, and Marketplace-originated inquiries in one workflow so those attempts are attached to live inventory. Unlimited vehicles, AI titles and descriptions you edit before posting, human-paced AutoPost through the Chrome extension, and a leads inbox for managers are included. Starter runs $59 a month with one login for a solo seller or independent lot. Dealership runs $299 a month with up to 13 logins for a full team.

Start your 10-day free trial through secure Stripe checkout. Connect inventory, assign owners, and cancel anytime.