Hold the Send roadmap

Concept. Under consideration. Not available.

1. Channel-scoped contact preference at draft time

Consent and contact · . Research rank P1 · . Research grouping Near-term

Problem it addresses

A buyer asks for email, or asks for no texts, and the next person still calls or texts. A rep is also unsure whether one stop applies to every channel.

What it would do

The idea would store, for each buyer, whether email, text, and phone are allowed or blocked, plus where that choice came from and the day it was saved. A draft on a blocked channel would show a warning and the channel that is still allowed. Overriding it would require a typed reason. A person would still decide and press Send.

What it could help with

• The rep sees the buyer's channel choice before writing, instead of relying on memory.
• A typed reason would leave a record when someone contacts a blocked channel anyway.

Compared with the desk today

On the signed-in floor, a rep can block text, email, Facebook, or phone for one buyer, and a draft on that channel stays held until they type a reason. A signed-in production exercise of this screen is not available.

Concept. Under consideration. Not available.

2. Store-wide suppression ledger with reason codes

Suppression and opt-out · . Research rank P1 · . Research grouping Near-term

Problem it addresses

A stop, or a note that the buyer already purchased, stays with one rep. Other people at the store keep reaching out.

What it would do

The idea would be one ledger for the store: stop text, stop all, do not call, purchased elsewhere, or wrong person. Each row would record who logged it, when, and the message it came from. Every draft and work list for that buyer would check the ledger and explain the block. Taking a row off would need a new request from the buyer, and that request would be recorded. Nothing would send on its own.

What it could help with

• A second rep would see the block without asking the first rep.
• The reason, the author, and the day would sit on the row the draft is checking.

Compared with the desk today

STOP on a chosen buyer blocks marketing copy and stores a reason code on that buyer and the timeline. A separate downloaded report for every rep is not available.

Concept. Under consideration. Not available.

3. Ambiguous-reply triage before the next touch

Suppression and opt-out · . Research rank P1 · . Research grouping Near-term

Problem it addresses

Replies such as "I'll reach out when ready" or "not interested" get treated as noise, and the next nudge goes out anyway.

What it would do

When an inbound reply looked like a pause, a decline, or a stop, the next draft would be held. The rep would classify it: pause until a date, stop one channel, stop all, or continue. That choice would write to the preference or the ledger. No follow-up draft would be offered until the rep picked. A person would still send anything that continued.

What it could help with

• An unclear reply would not slide straight into another nudge.
• The classification would be a choice a person makes, not a guess the desk acts on.

Compared with the desk today

The desk can move to the next open play. It does not hold the next draft until someone classifies an unclear reply. This idea is not available.

Concept. Under consideration. Not available.

4. Recipient-local quiet-hours guard on manual send

Time zones · . Research rank P1 · . Research grouping Near-term

Problem it addresses

A message goes out late at night for the buyer, or in the wrong time zone, and the owner hears about it afterward.

What it would do

The idea would estimate the buyer's time zone from an address first, then from an area code, and label that estimate as a guess. Outside hours the store had set, Send would show the buyer's local time and offer the rep a reminder. Sending anyway would need a typed reason. The store would choose the hours with its own counsel. A person would still press Send. This does not settle any legal duty.

What it could help with

• The rep would see the buyer's local time on the send step, not only the store's clock.
• An after-hours send would keep the reason with the message.

Compared with the desk today

Copy stays off from 9 PM to 8 AM on a buyer-local guess when the thread has a ZIP, a single-zone state, or an area code. That guess is labeled. Without one, this device's clock is used. The reason stays on this device. Store-chosen hours beyond the fixed 9 PM to 8 AM window are not available.

Concept. Under consideration. Not available.

5. Lead source and consent provenance card

Consent and contact · . Research rank P2 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today · Dealership framing

Problem it addresses

A rep works a lead from a website or a vendor and cannot see what the person agreed to, or whether a named store was disclosed. The buyer may say they never asked to be contacted.

What it would do

Each lead would show the source, the form or vendor label the store entered, the consent text that was captured, the time, and whether a named store was disclosed. Missing evidence would be flagged. A rep could still call by hand, and drafts would carry a note that consent evidence is missing. A person would still review and send. The store would decide, with its own counsel, what counts as enough evidence.

What it could help with

• The rep would see a missing consent note before writing, instead of discovering it in a complaint.
• The draft header would carry the same gap the card shows.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Written for a dealership desk: reps, BDC, managers, and owners. Not presented as confirmed dealership evidence.

Concept. Under consideration. Not available.

6. Inquiry-age and relationship-window indicator

Consent and contact · . Research rank P3 · . Research grouping Parked · Exploratory, no confirmed match on the desk today

Problem it addresses

People repeat informal rules about how long a lead stays fair game, without checking the date of the last inquiry, purchase, or service visit.

What it would do

The idea would show days since the last inquiry, purchase, or service visit. Windows the store set with its own counsel would color the label. The label would inform the rep and would not block a draft on its own. A person would still decide whether to reach out. It is not legal advice, and it would not make a store's process lawful by itself.

What it could help with

• The rep would see the age of the inquiry next to the draft.
• The label would name the window the store set, and who set it, instead of a folk rule.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

7. Wrong-person and changed-number handling

Suppression and opt-out · . Research rank P2 · . Research grouping Exploring · Exploratory, no confirmed match on the desk today · Dealership framing

Problem it addresses

A call or text reaches someone who never asked about a vehicle, or the number now belongs to someone else.

What it would do

A rep could mark "not me / wrong number" in one step. That would suppress the number on that buyer record and add a mark on the lead-source card. Drafts would no longer offer that number. A person would still handle any later contact by hand.

What it could help with

• The wrong number would leave the draft instead of staying in the rep's notes.
• The lead source would pick up one wrong-person mark the owner can review.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Written for a dealership desk: reps, BDC, managers, and owners. Not presented as confirmed dealership evidence.

Concept. Under consideration. Not available.

8. Who-is-talking collision guard and single owner

Handoffs and ownership · . Research rank P1 · . Research grouping Near-term

Problem it addresses

Several people at the store contact the same buyer within minutes. The buyer does not know whom to work with.

What it would do

Before a draft, the desk would show other staff contact in the last stretch of hours the store chose, and the assigned owner. Someone who is not the owner would get an internal note to the owner as the default, instead of a message to the buyer. A manager could reassign. A person would still send any buyer-facing message.

What it could help with

• A second rep would see that someone already reached out, and who owns the buyer.
• The default action would be a note to that owner, not another message to the buyer.

Compared with the desk today

A manager can reassign a buyer, and a merge can keep the earlier owner. A warning that another rep already reached out, with an internal note as the default, is not available.

Concept. Under consideration. Not available.

9. Neutral credit timeline for split disputes

Handoffs and ownership · . Research rank P2 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

Split deals and "someone took my buyer" disputes get settled from memory and seniority.

What it would do

The idea would build a timeline of first contact, appointment set, showroom greet, test drive, and deal work, each with the person and the time. A manager would use it to decide credit. The desk would not decide commission or pay.

What it could help with

• The manager would see the sequence of staff actions in one place.
• The timeline would not assign pay. A person would still decide.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

10. Structured BDC-to-salesperson handoff packet

Handoffs and ownership · . Research rank P1 · . Research grouping Near-term

Problem it addresses

Once an appointment is set, the context is lost: what the buyer asked, what was quoted, and what was left open.

What it would do

A handoff form would fill from the thread: the buyer's questions, open requests, what was quoted and what was not, the vehicle, and preferences. The receiving rep would have to acknowledge it. Unacknowledged handoffs would show on a manager list after a wait the store set. A person would still send any message to the buyer.

What it could help with

• The floor rep would see the open requests without retyping the thread.
• A handoff nobody accepted would be visible to a manager.

Compared with the desk today

The named person can accept a saved handoff on the published floor. An isolated preview proved that accept. A signed-in production exercise is not recorded. A packet filled from the thread is not available.

Concept. Under consideration. Not available.

11. Customer-request and promise tracker with due times

Follow-up ownership · . Research rank P1 · . Research grouping Near-term

Problem it addresses

A buyer asks for photos, an out-the-door price, or a trade number, and the request sits.

What it would do

Explicit requests in an inbound message would become tasks with an owner and a due time, after a person confirmed the request. The draft could include the answer. Overdue items would show to a manager as work owed to the buyer, not as a dial count. Closing a task would need a linked outbound message that a person sent.

What it could help with

• A photo or price request would have an owner and a due time instead of living in a thread.
• The manager view would be about the unfinished request, not about activity volume.

Compared with the desk today

A rep can record a promise with a due time and mark it done on the signed-in floor. Closing it only when a person sent a message is not available.

Concept. Under consideration. Not available.

12. Departure and absence reassignment with context

Handoffs and ownership · . Research rank P2 · . Research grouping Near-term

Problem it addresses

A rep leaves or goes away, and open buyers, unmet promises, and quotes are hard to find.

What it would do

An away or leaving action would list that rep's open threads, unmet promises, and quotes, write a short summary per buyer for the new owner, and prepare an optional introduction draft for a person to review. A manager could confirm only after every open thread had a summary and a new owner. Nothing would be sent until a person sent it.

What it could help with

• Open buyers would not depend on notes that walk out with one rep.
• The introduction to the new owner would be a draft a person reviews.

Compared with the desk today

A manager can reassign a buyer. A leaving-rep list that writes a summary for every open thread is not available.

Concept. Under consideration. Not available.

13. Orphan-customer re-engagement brief

Stale context · . Research rank P3 · . Research grouping Near-term

Problem it addresses

A new rep calls an old customer with no record of the last purchase, the prior rep, or whether contact is allowed.

What it would do

For each old customer the store still holds, the brief would show last purchase or service, the prior rep, the last contact, the suppression state, and a factual opener the rep edits. Each fact would carry a source label. Suppressed buyers would be left out. A person would edit and send. This depends on records the store already keeps. It is not a feed from a system the store has not connected.

What it could help with

• The opener would start from stored facts, which the rep can edit.
• A buyer who is already suppressed would not appear as someone to call.

Compared with the desk today

Drafts can use facts the rep already pasted or saved. A brief of an old customer, limited to stored records and skipping suppressed buyers, is not available.

Concept. Under consideration. Not available.

14. Lead-routing rule transparency

Governance and oversight · . Research rank P3 · . Research grouping Parked · Exploratory, no confirmed match on the desk today

Problem it addresses

Routing rules change without a record, and reps read the change as arbitrary.

What it would do

Rules a manager set would be shown read-only to staff, with the day they took effect and a change history. Changing a rule would record the author and the day, and the new rule would show to the reps it affects. The desk would not route around a person. A person would still work the lead.

What it could help with

• A rep could read the current rule and when it changed.
• The history would name who changed it.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

15. Answer-the-question-first draft check

Messaging quality · . Research rank P1 · . Research grouping Near-term

Problem it addresses

Replies skip the buyer's question and only push for an appointment.

What it would do

Before Send, the draft panel would list the questions in the buyer's last message and mark each one answered or not. An unanswered question would need a rep choice: answer it, or say why not yet. Send would stay unavailable until the rep resolved each one. A person would still press Send.

What it could help with

• The unanswered question would be visible on the draft, not buried in the inbound message.
• The rep would choose to answer or to say why not, instead of sending past it.

Compared with the desk today

The desk can score a draft for the unit, a time, and the store's voice. It does not list each question and hold Send until the rep resolves the ones still open. This idea is not available.

Concept. Under consideration. Not available.

16. Vehicle-of-interest consistency guard

Messaging quality · . Research rank P1 · . Research grouping Near-term

Problem it addresses

A template names the wrong vehicle, the wrong stock number, or even the wrong store.

What it would do

Names in the draft (vehicle, stock number, store) would be checked against the lead and the inventory the store has connected. A mismatch would block Send until the rep fixed it or confirmed it on purpose. A person would still send the corrected draft.

What it could help with

• A draft about a different model than the lead would be flagged before copy.
• The rep would fix it or confirm the mismatch. It would not pass through quietly.

Compared with the desk today

A draft that names a different vehicle than the one the buyer asked about is held on the signed-in floor. A signed-in production exercise of that hold is not available.

Concept. Under consideration. Not available.

17. Inventory freshness check before confirming availability

Quote accuracy · . Research rank P1 · . Research grouping Near-term

Problem it addresses

A buyer is told a vehicle is available, then arrives and it is sold or not ready.

What it would do

A draft that confirmed availability or set an appointment would pull status (in stock, pending, sold, in recon) with a time stamp, from inventory the store connected. A stale status would ask for a re-check. Appointment wording for a sold vehicle would be blocked. A person would still send. This is not a live inventory feed until a store connects one.

What it could help with

• Availability wording would show the status and the time it was read.
• A sold unit would not get appointment wording until a person dealt with the status.

Compared with the desk today

Saying a unit is available is held on the signed-in floor when the lot check is older than 24 hours, and a sold or pending unit is held. A checked-at time on every availability sentence is not available.

Concept. Under consideration. Not available.

18. Sender identification in every first contact

Messaging quality · . Research rank P2 · . Research grouping Near-term

Problem it addresses

A first text with no name and no store looks like spam, and the buyer blocks it.

What it would do

A store-set identity block (rep name, store name, and how to opt out) would be added to first messages and when the channel changed. The rep could edit the wording and could not remove the block. A person would still review and send.

What it could help with

• The first text would name the rep and the store.
• The opt-out line would stay even if the rep rewrote the greeting.

Compared with the desk today

Starter replies are on the desk. A first-text block that must keep the rep's name and the store name is not available.

Concept. Under consideration. Not available.

19. Honest AI-assistance setting

Messaging quality · . Research rank P2 · . Research grouping Near-term

Problem it addresses

A named assistant persona tells a buyer it is a person. The buyer loses trust when that turns out to be false.

What it would do

A store setting would keep drafts from claiming to be a human. If a buyer asked whether they were writing to a bot, the draft would say plainly that a person reviews and sends, and the thread would be flagged for a human reply. The draft would not claim to be a named person unless that person was the one sending. A person would still press Send.

What it could help with

• A "are you a bot?" question would get a plain answer in the draft, for a person to send.
• The thread would be flagged so a person replies, instead of another persona line.

Compared with the desk today

A rep can add a note that a draft had help, and a manager can save up to five real store phrases. A rule that the draft never claims to be a person, and a flag when a buyer asks, is not available.

Concept. Under consideration. Not available.

20. Cadence fatigue view and close-the-loop option

Follow-up ownership · . Research rank P1 · . Research grouping Near-term

Problem it addresses

A buyer hears from several people and channels, and no one rep can see the total.

What it would do

The idea would show touches in the last 7 days and the last 30 days across staff and channels. After a count the store set, with no answer, the next play would offer a polite close-the-loop draft or a pause before another nudge. A person would choose and would still press Send. The count is a store setting for discussion, not a result we are claiming.

What it could help with

• The rep would see how many times the store already reached out.
• The next suggestion could be a close-the-loop note or a pause, before another nudge.

Compared with the desk today

The desk can select the next open play. A view of touches across staff, with a close-the-loop suggestion first, is not available.

Concept. Under consideration. Not available.

21. Fresh photos or video when the buyer asks

Messaging quality · . Research rank P3 · . Research grouping Near-term

Problem it addresses

A buyer asks about condition or for photos, and the reply is a generic template with no picture of that vehicle.

What it would do

When a message asked about condition or features, the draft would leave a place for a fresh walkaround or photos and would open a task if none were on file. The rep would add the media. A person would still review and press Send. The file would not leave the store's process on its own.

What it could help with

• A photo request would show up as a task, not only as another template.
• The draft would have a visible gap where the photo belongs, until the rep fills it.

Compared with the desk today

A walkaround can be recorded on that phone, and the file stays on that phone. A draft that leaves a place for new photos, plus a task when none exist, is not available.

Concept. Under consideration. Not available.

22. Numbers only from approved desk figures

Quote accuracy · . Research rank P1 · . Research grouping Near-term

Problem it addresses

A price or payment a rep types does not match what the desk will honor.

What it would do

Price, payment, and trade figures would enter a draft only from figures a manager had approved, with what is included and an expiry. A number typed freehand would be flagged and routed for manager approval. A person would send only after that, by hand.

What it could help with

• A typed dollar amount that is not on the approved figure would be flagged.
• The draft could show what the figure includes, and when it expires.

Compared with the desk today

The signed-in floor holds a payment quote and a price that does not match the unit. Filling those numbers from a manager-approved figure is not available.

Concept. Under consideration. Not available.

23. Quote snapshot and version history

Evidence and versioning · . Research rank P1 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

Later, nobody can show what price, trade number, or payment was shared, when, or on what basis.

What it would do

Every figure shared with a buyer would be saved as a snapshot that cannot be edited: the value, the basis, the source listing or appraisal, the expiry, and the sender. A new version would link to the older one. A draft could cite the version. A person would still send. This is a record idea, not a promise that a quote is binding.

What it could help with

• A changed trade number would keep version 1 next to version 2, with times and senders.
• A later export could include both versions instead of the latest number only.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

24. Trade estimate conditions template

Quote accuracy · . Research rank P2 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

A trade number given by phone or text turns into a dispute after an inspection or a delay.

What it would do

A trade draft would carry a range or a figure plus conditions from the appraiser's entry: inspection, mileage, payoff, and valid-until. A trade draft with no expiry could not be sent until the appraiser filled it in. A person would still review and send. The number would stay an estimate with conditions, not a promise.

What it could help with

• The conditions would travel with the number, in the draft the rep sends.
• A missing expiry would hold the draft until the appraiser filled it.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

25. Listing-price change alert for active conversations

Quote accuracy · . Research rank P2 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

The advertised price changes during a conversation, and the rep hears it from the buyer.

What it would do

When a vehicle's advertised price changed in a feed the store connected, reps with an open thread on that stock number would get an alert and a draft that acknowledges the change, for a person to review. Nothing would be sent until that person sent it. Without a price feed, this idea has nothing to watch.

What it could help with

• The rep with the open thread would see the change before the buyer has to explain it.
• The acknowledgment would be a draft, not a message that leaves on its own.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

26. Itemized fee and add-on disclosure block

Quote accuracy · . Research rank P2 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

A package, a fee, or a market adjustment shows up late, after the buyer thought the price was complete.

What it would do

A quote draft would include an itemization from the desk record: vehicle price, each fee, and each add-on marked optional or pre-installed. Required lines and wording would be set by the store with its own counsel. A quote missing a desk line could not be sent. A person would still send the completed quote. This is not legal advice.

What it could help with

• The draft would list the lines the desk record already has, before the buyer is in the store.
• A missing line would hold the quote until it was filled in.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

27. Payment-estimate assumptions block

Quote accuracy · . Research rank P2 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

A monthly figure goes out with no rate, term, down payment, or amount financed, and the buyer cannot tell what it assumes.

What it would do

Any payment figure in a draft would have to carry the APR assumption, the term, the down payment, and the amount financed, labeled as an estimate. A monthly figure with no term would fail the check. A person would still review and send. The figure would stay an estimate, not an approval.

What it could help with

• The assumptions would sit next to the monthly figure in the draft.
• A payment line with a blank term would not pass the check.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

28. Verbal promise capture into a written due-bill list

Evidence and versioning · . Research rank P2 · . Research grouping Near-term

Problem it addresses

A verbal promise, such as a second key or a repair, never gets written down.

What it would do

Commitments spotted in the thread, or typed by the rep, would go on a "we owe" list for a manager to confirm, plus a confirmation draft for the buyer. A person would still send that confirmation. The list would not create the promise by itself.

What it could help with

• A promise said in the thread would land on a list a manager can confirm.
• The buyer-facing confirmation would be a draft a person sends.

Compared with the desk today

A note can be stored on the buyer. A we-owe list that waits for a manager before a confirmation draft is not available.

Concept. Under consideration. Not available.

29. Pre-close variance explainer

Quote accuracy · . Research rank P3 · . Research grouping Exploring · Exploratory, no confirmed match on the desk today · Dealership framing

Problem it addresses

The out-the-door price, payment, or fees on the desk worksheet differ from what the buyer was shown earlier, and the change looks like a surprise.

What it would do

The idea would compare the earlier quote with the later desk figures, list each changed line with a reason the store entered, and draft an explanation for a person to review. Quotes would carry a note that they are preliminary until the desk review. A person would still send. This does not make a changed number acceptable. It only makes the difference visible.

What it could help with

• Each changed line would have a reason next to it, in a draft a person can edit.
• The earlier quote would stay marked preliminary until the desk review.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Written for a dealership desk: reps, BDC, managers, and owners. Not presented as confirmed dealership evidence.

Concept. Under consideration. Not available.

30. Manager approval queue for sensitive drafts

Manager approvals · . Research rank P1 · . Research grouping Near-term

Problem it addresses

Price, payment, and promise questions turn into repeated trips to a manager, and a number said earlier gets overridden later with no record.

What it would do

Drafts that include price, payment, trade, a promise, a complaint, or legal wording would go to an approval queue. The manager would approve, edit, or reject with a note. The decision would be recorded. A person would then press Send. The queue would not send the message.

What it could help with

• The approval, the editor, and the time would be on the record before the rep sends.
• A rejection would come back with a note, instead of a hallway conversation that is easy to lose.

Compared with the desk today

A rep can hand a negotiation to a manager. A queue that records approve, edit, or reject, after which the rep still sends by hand, is not available.

Concept. Under consideration. Not available.

31. Lost-deal reason capture and non-punitive review

Coaching and training · . Research rank P2 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

Lost deals get a desk visit one by one, and the reasons are not collected in one place.

What it would do

A lost deal would take a structured reason (price, bought elsewhere, timing, or vehicle) and an optional note. A manager would review patterns on a weekly list, not as an alert on every note. "Bought elsewhere" would also write to the suppression ledger. The review would not rank or punish a rep. A person would still do any follow-up.

What it could help with

• The reason would be a choice plus a note, not an interrogation in the moment.
• "Bought elsewhere" would feed the suppression ledger so the next rep does not keep calling.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

32. Outcome-focused coaching dashboard, no keystroke monitoring

Coaching and training · . Research rank P2 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

A manager watches dial counts. Unanswered questions and overdue promises are harder to see.

What it would do

The idea would show unanswered buyer questions, overdue promises, opt-outs honored, and how long inbound messages waited for a reply. It would not collect keystrokes, screen images, or any covert tracking. Each rep would see their own view. A person would still send any follow-up. Nothing on this board would send a message.

What it could help with

• The manager view would be unfinished buyer work, not a dial tally.
• A rep could see the same rows that describe their own work.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

33. Sanctioned business channel with capture path

Governance and oversight · . Research rank P2 · . Research grouping Near-term

Problem it addresses

Reps text from a personal phone or another app. The record leaves when they do, and the store cannot see what was said.

What it would do

The idea would be a business number or inbox per rep inside the product, plus a documented way to forward or import a buyer thread from a personal device when the rep asks. Imported threads would be labeled imported, with the day. There would be no device monitoring. A person would still send. This needs a messaging provider the store chooses. It is not connected now.

What it could help with

• A work thread could live on a store inbox instead of only on a personal phone.
• An import would be labeled, with a date, instead of looking like it started inside the desk.

Compared with the desk today

The desk does not send messages. A store inbox per rep, plus a labeled import from a phone, is not available.

Concept. Under consideration. Not available.

34. Neutral review-request template

Messaging quality · . Research rank P3 · . Research grouping Parked · Exploratory, no confirmed match on the desk today

Problem it addresses

A review request asks the buyer for a perfect score.

What it would do

The store would approve a review request that does not ask for a specific score. A draft that asked for a score would be flagged. A person would still edit and send. The idea does not promise reviews, ratings, or a change in scores.

What it could help with

• The approved template would ask for a review without naming a score.
• A draft that pushes for a score would be flagged before send.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

35. New-rep guided mode

Coaching and training · . Research rank P1 · . Research grouping Near-term

Problem it addresses

A new hire has questions and no place to see why a draft is shaped a certain way. Asking a manager feels costly.

What it would do

For a ramp period the store set, drafts would show the playbook line they drew from, and a price draft would route to a mentor for approval before the new rep could send it. Questions to the mentor would be kept as learning notes the rep can see. A person would still press Send after approval.

What it could help with

• The new rep would see which playbook line the draft is using.
• A price draft in ramp mode would wait for a mentor, and the note would stay visible to the rep.

Compared with the desk today

A short drill can be stored for the store. A ramp mode that cites a playbook and holds a price draft for a mentor is not available.

Concept. Under consideration. Not available.

36. Coaching from real conversations, opt-in and visible

Coaching and training · . Research rank P3 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

Coaching stays generic, and people are unsure what is recorded or who can see the notes.

What it would do

A manager would pick threads to annotate. The rep would self-review first. Annotations would be visible to that rep. Any call recording would follow a policy the store discloses. There would be no hidden review. A person would still send any message. Nothing here would send on its own.

What it could help with

• Notes on a real thread would be visible to the rep whose thread it is.
• The rep would review first, before a manager's note is the only record.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

37. Store playbook library with sources and versions

Coaching and training · . Research rank P2 · . Research grouping Near-term

Problem it addresses

How the store handles a stop, or how it closes a loop, lives in a veteran's head and changes without a record.

What it would do

The store would keep approved entries, such as what a stop means here and close-the-loop wording, each with an author, a day, and a version. A draft could cite the entry it used. Editing an entry would create a new version. Earlier drafts would still cite the old version. A person would still send.

What it could help with

• A draft could point at the entry it used, including the version.
• An edit would not rewrite the citation on an older draft.

Compared with the desk today

Playbooks can be opened on the signed-in desk. There is no live community. Entries with an author, a day, and a version a draft cites are not available.

Concept. Under consideration. Not available.

38. Lead-source quality and complaint scorecard

Governance and oversight · . Research rank P2 · . Research grouping Exploring · Exploratory, no confirmed match on the desk today · Dealership framing

Problem it addresses

An owner cannot see which lead sources arrive with a missing consent note, wrong-person marks, or opt-outs.

What it would do

Once a month the owner could review each source the store entered: leads, wrong-person marks, opt-outs, and whether consent text was on file. Counts on the sketch are example labels, not results. The card would not rank buyers, and it would not contact anyone.

What it could help with

• Wrong-person marks and missing consent notes would sit on the source, not only on one lead.
• The owner would have one monthly view to review, without a live alert on every row.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Written for a dealership desk: reps, BDC, managers, and owners. Not presented as confirmed dealership evidence.

Concept. Under consideration. Not available.

39. Per-customer evidence timeline and export

Evidence and audit · . Research rank P1 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

When a complaint arrives, messages, quotes, approvals, and opt-outs are scattered or missing.

What it would do

One timeline per buyer would list messages, drafts, approvals, quote versions, preferences, opt-outs, and handoffs. A person could export a file with a generation date, for the store's own counsel to review. The export would match the on-screen timeline. It is a record, not legal advice, and it does not decide a dispute.

What it could help with

• The owner could pull one file in time order, with author and channel, instead of rebuilding the story.
• The file would be generated for counsel to review. The product would not give legal advice.

Compared with the desk today

Exploratory concept for scoping. The signed-in floor can build a dated timeline for one buyer, and message text is not kept in it. A downloaded file and a signed-in production exercise are not part of this idea yet.

Concept. Under consideration. Not available.

40. Change-request read-back loop

Evidence and audit · . Research rank P2 · . Research grouping Near-term · Dealership framing

Problem it addresses

A buyer asks by text to change a color, add or remove an option, or take a vehicle off the deal. Later, nobody can show that the change was confirmed.

What it would do

An inbound change request would create a task and a read-back draft that repeats the change in plain words. The task would close only when a person had sent a confirmation and recorded a verification note against the deal record. Nothing would change the deal by itself, and nothing would send on its own.

What it could help with

• The change the buyer asked for would be repeated in a draft before anyone treats it as done.
• The task would stay open until a confirmation and a verification note exist.

Compared with the desk today

A next step can be stored. A change request that stays open until someone verifies it, with a read-back draft a person sends, is not available.

Written for a dealership desk: reps, BDC, managers, and owners. Not presented as confirmed dealership evidence.

Concept. Under consideration. Not available.

41. Declined-recommendation acknowledgment record

Evidence and audit · . Research rank P3 · . Research grouping Parked · Exploratory, no confirmed match on the desk today · Dealership framing

Problem it addresses

A buyer declines an optional product in the finance office. Later, the conversation about what was offered is hard to reconstruct.

What it would do

The idea would record what was offered, what the buyer chose, and an optional acknowledgment (a reply or a signature the store already uses). Wording would be chosen by the store with its own counsel. The row would show in the timeline export. It is not legal advice, and it does not create a waiver by itself. A person would still handle any message.

What it could help with

• Offer, choice, and acknowledgment status would be a row, not a memory.
• The same row could appear in the timeline export.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Written for a dealership desk: reps, BDC, managers, and owners. Not presented as confirmed dealership evidence.

Concept. Under consideration. Not available.

42. Configurable retention and legal hold

Evidence and audit · . Research rank P3 · . Research grouping Parked · Exploratory, no confirmed match on the desk today · Dealership framing

Problem it addresses

An owner does not have a clear place to set how long texts and notes are kept, or to freeze one buyer's file during a dispute.

What it would do

The owner, with the store's own counsel, would set a retention window per record type. A person could place a legal hold on one buyer. That hold would stop deletion of that buyer's records and would log who placed it. This is a setting idea. It is not legal advice, and it does not by itself meet a retention duty.

What it could help with

• Deletion of a held file would wait, and the hold would name who placed it.
• Windows would be chosen by the store, not preset by this product as a legal rule.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Written for a dealership desk: reps, BDC, managers, and owners. Not presented as confirmed dealership evidence.

Concept. Under consideration. Not available.

43. Owner file-QC sampler

Governance and oversight · . Research rank P2 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today

Problem it addresses

Nobody routinely checks that a closed deal matches what was quoted or promised.

What it would do

Once a month the idea would pull a random sample of closed deals and a checklist: quote matches the contract, promises fulfilled, opt-outs honored. A person would review the sample. Findings would go to coaching by default, not to a public score. The sample size would be chosen by the store. Counts on the sketch are examples. This does not certify a file.

What it could help with

• A closed file would be checked against the quote, the promises, and the opt-outs, on a schedule the store picks.
• The result would record the reviewer and the day, and would default to coaching.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Concept. Under consideration. Not available.

44. Complaint intake and incident chronology

Governance and oversight · . Research rank P2 · . Research grouping Near-term · Exploratory, no confirmed match on the desk today · Dealership framing

Problem it addresses

A buyer complaint arrives and the store rebuilds the story from memory, with no consistent intake.

What it would do

A person would log a complaint. That would assemble a chronology from the buyer timeline, track deadlines the owner or the store's counsel set, and record who was notified. One action would link the chronology to that timeline. The product would not give legal advice, and it would not answer the complaint for the store.

What it could help with

• The chronology would be assembled from the timeline the store already kept, in one step.
• Deadlines and who was notified would be fields the store fills, not advice from the product.

Compared with the desk today

Exploratory concept for scoping. No confirmed match in the product a store can use today. Not a commitment to build.

Written for a dealership desk: reps, BDC, managers, and owners. Not presented as confirmed dealership evidence.

Concept. Under consideration. Not available.

45. Customer-supplied data accuracy check

Quote accuracy · . Research rank P3 · . Research grouping Near-term · Dealership framing

Problem it addresses

A fact the buyer supplied, such as mileage or a payoff, gets typed differently by staff, and the change is easy to miss.

What it would do

Fields the buyer supplied would keep their source. If staff changed one, the change would be flagged and a confirmation draft would be prepared, unsent, for a person to review. The idea would not infer private traits about a buyer. A person would still send any confirmation.

What it could help with

• The buyer's original figure and the edited figure would both stay visible.
• The confirmation would be an unsent draft, not a message that leaves on its own.

Compared with the desk today

A reply that names a listed color or a full mile count missing from the notes, the vehicle line, or the label is held. Navy, reddish, 12k, and a clock time are not treated as those facts. Buyer-supplied mileage and payoff keep source buyer; a staff change is flagged and needs an unsent confirmation draft before Copy. A signed-in production exercise is not recorded. Coverage for every buyer-supplied field type is not available.

Written for a dealership desk: reps, BDC, managers, and owners. Not presented as confirmed dealership evidence.