Manor
HomeScoreboard
Work
Needs meNo person 48h+VisitsVideosMy listApprovalsTurnoverRepliesCallsPromisesHotFollow-upQueueOpportunitiesLeadsLost auditDesk
Floor
ShowroomAppointmentsScheduleDeliveries
Numbers
SourcesRepsUsagePerformanceMetricsMoneyPricingLease
Machine
JobsAgentsWatcherHealthControlAI Control
More
ToolsTrainingHot dealsService deskReportsTo-doBoard

Training

Confirmed

Operations Hub

Owner: Will

Operations Hub

Operations and team training hub, Leif Johnson Ford of Manor. Version 1.1, Mon Oct 12 2026, 12:34 PM CT. Everything below is a draft until Will approves it. This chapter and the six draft SOPs are in the /training book as drafts (Will OK'd the push Mon Oct 12 2026). Nothing has been announced to the team.

How to use this book

Ask a question, find the process ID (for example APPT-001 for appointments), and open that page. The ID starts with the area (LEAD, REPLY, APPT, SALES, INV, KEYS, DLV, MKT, SVC, SYS, DAY). Approved means Will ruled it on a date or the page is already confirmed: follow it. Draft means written but not approved: it shows what we think the process is, and only the lines tagged Approved are enforceable. Needs Clarification means the page conflicts with a ruling or with what the machine does, or a decision is missing: do not treat it as a rule. Retired means replaced. Each page carries its status, owner and approver at the top.

The four sections

1. Team Handbook

Approved pages only. This is what reps and managers can follow today. Right now it holds 7 pages: INV-002 Inventory Finder; LEAD-005 New-lead texter; REPLY-003 Auto-responder; LEAD-006 Follow-up engine; REPLY-004 Approvals; REPLY-005 Working one customer (desk-send); LEAD-007 What the machine can write in the CRM. The rules list also holds 40 Approved items (Will rulings and confirmed pages) that are not yet written up as handbook pages. See the table of contents below.

2. Management Review Board

Every Draft and Needs Clarification page (33 existing pages and 6 new SOPs), plus the approval queue below (90 items). Managers read these. Will approves, edits or rejects.

3. Daily and Weekend Operating Board

Where the day is run from, on the dashboard: Follow-up board, Deliveries (manager thank-you calls, DDT, survey), Team scoreboard (standings for the huddle, goal 125). Weekend readiness audit, Fri Oct 9 2026: a separate document; add its link here when Will publishes it.

4. Training and Change Log

This book (/training) is the training home. Three pages still need a video: FordPass activation, new lead call inside the hour, and the daily walkaround script. The change log is at the end of this page.

Status inventory

  • Documents counted: 46 (40 existing pages and 6 new SOPs). Approved: 7. Draft: 19. Needs Clarification: 20. Retired: 0.
  • Existing pages only: Approved 7, Draft 13, Needs Clarification 20.
  • Rules list (73 items): Approved 40, Draft 24, Needs Clarification 8, Retired 1. Plus 25 conflicts, all Needs Clarification.
  • Areas with nothing documented: none, all 11 areas have at least one page.
  • Areas with no Approved page yet (8 of 11): Appointments and follow-up; Sales process and manager involvement; Keys recon photos merchandising; Finance delivery after-sale; Marketing and communication; Service-to-sales; Systems and onboarding; Daily expectations.
  • 20 pages show as confirmed in the book today but rate Needs Clarification here. They were not changed in this version.

Table of contents by area

1. Lead handling and CRM

ID prefix: LEAD

  • LEAD-000 | Customer first hour | Needs Clarification | Will | first-hour/index
  • LEAD-001 | New lead to a person: assignment, first human touch, phone-ups and walk-ins | Draft (Needs Approval) | Will | first-hour/new-lead-handoff
  • LEAD-002 | Phone-up (customer calls in) | Draft (Needs Approval) | Will | first-hour/phone-up
  • LEAD-003 | Walk-in greeting | Draft (Needs Approval) | Will | first-hour/walk-in
  • LEAD-004 | Keep in touch | Needs Clarification | Will | first-hour/keep-in-touch
  • LEAD-007 | What the machine can write in the CRM | Approved | Will | tools/crm-writes
  • LEAD-008 | New lead: call inside the hour | Needs Clarification | Will | first-hour/lead-response

2. Automations and handoffs

ID prefix: REPLY (and machine pages filed as LEAD)

  • LEAD-005 | New-lead texter | Approved | Will | tools/first-touch
  • LEAD-006 | Follow-up engine | Approved | Will | tools/follow-up-engine
  • REPLY-001 | Who owns a customer reply (machine hold to human answer) | Draft (Needs Approval) | Will | first-hour/customer-reply-ownership
  • REPLY-002 | Reply Desk | Needs Clarification | Will | tools/reply-desk
  • REPLY-003 | Auto-responder | Approved | Will | tools/auto-responder
  • REPLY-004 | Approvals | Approved | Will | tools/approvals
  • REPLY-005 | Working one customer (desk-send) | Approved | Will | tools/desk-send
  • REPLY-006 | Read the notes first | Needs Clarification | Will | texting-rules/read-the-notes

3. Appointments and follow-up

ID prefix: APPT

  • APPT-000 | Appointments and showroom | Needs Clarification | Will | appointments/index
  • APPT-001 | Appointments: set, confirm by phone, prepare, arrive, no-show, unsold visit | Draft (Needs Approval) | Will | appointments/appointment-lifecycle
  • APPT-002 | Confirm the day before | Needs Clarification | Will | appointments/confirm-day-before
  • APPT-003 | Running the showroom visit | Draft (Needs Approval) | Will | appointments/showroom
  • APPT-004 | Set the appointment | Needs Clarification | Will | appointments/set-appointment

4. Sales process and manager involvement

ID prefix: SALES

  • SALES-001 | Manager involvement: TO on every write-up, stalled deals, documenting commitments | Draft (Needs Approval) | Will | appointments/manager-involvement
  • SALES-002 | Desk | Needs Clarification | Will | tools/desk-log
  • SALES-003 | Lease Calculator | Needs Clarification | Will | tools/lease-calculator
  • SALES-004 | AutoFi | Needs Clarification | Will | tools/autofi

5. Trades and inventory

ID prefix: INV

  • INV-001 | Check the unit before you promise it: availability, location, store ownership, trade info | Approved (Will 10/29/26) | Will | tools/check-before-you-promise
  • INV-002 | Inventory Finder | Approved | Will | tools/inventory-finder
  • INV-003 | Inventory truth | Needs Clarification | Will | tools/inventory-truth

6. Keys recon photos merchandising

ID prefix: KEYS

  • KEYS-000 | Trade-ins and keys | Draft (Needs Approval) | Will | trade-in-keys/index
  • KEYS-001 | Used-vehicle key control (sticker, register, keybox, check-out, return) | Draft (Needs Approval) | Will | trade-in-keys/key-control
  • KEYS-002 | Trade-in keys: 8 steps | Draft (Needs Approval) | Will | trade-in-keys/process

7. Finance delivery after-sale

ID prefix: DLV

  • DLV-000 | Delivery | Draft (Needs Approval) | Will | delivery/index
  • DLV-001 | DDT | Draft (Needs Approval) | Will | delivery/ddt
  • DLV-002 | Survey / Google review | Draft (Needs Approval) | Will | delivery/survey
  • DLV-003 | Manager CSI call | Draft (Needs Approval) | Will | delivery/csi-call
  • DLV-004 | FordPass activation at delivery | Draft (Needs Approval) | Will | connected-services/fordpass-activation
  • DLV-004 (intro) | Connected services | Draft (Needs Approval) | Will | connected-services/index
  • DLV-005 | Deliveries | Draft (Needs Approval) | Will | tools/deliveries

8. Marketing and communication

ID prefix: MKT

  • MKT-001 | Texting and messaging rules | Needs Clarification | Will | texting-rules/index
  • MKT-002 | Voice and timing | Needs Clarification | Will | texting-rules/voice-and-timing
  • MKT-003 | Daily VIN walkaround script | Needs Clarification | Will | tools/walkaround-script

9. Service-to-sales

ID prefix: SVC

  • SVC-001 | Sales-to-service intro | Draft (Needs Approval) | Will | delivery/service-intro

10. Systems and onboarding

ID prefix: SYS

  • SYS-001 | If something looks wrong | Needs Clarification | Will | tools/if-something-wrong
  • SYS-002 | Tools we use | Needs Clarification | Will | tools/index

11. Daily expectations

ID prefix: DAY

  • DAY-001 | The day at a glance | Needs Clarification | Will | tools/day-at-a-glance
  • DAY-002 | Team Scoreboard | Needs Clarification | Will | tools/team-scoreboard
  • DAY-003 | TV board | Needs Clarification | Will | tools/tv-board

Format of each line: ID | title | status | owner | path under docs/training.

Renumbered because the new SOPs took their proposed IDs: set-appointment (APPT-004), lead-response (LEAD-008), read-the-notes (REPLY-006), trade-in process (KEYS-002).

Management approval queue

90 items. Decider is Will Robbins unless another name is shown.

A. New SOP drafts (6)

  • S1 KEYS-001 Used-vehicle key control (sticker, register, keybox, check-out, return) | Draft | Decision: Approve as written or edit. 11 open decisions. Main ones: Name who registers keys, the key-management system, who holds the keybox key, and who approves a missing-key replacement. | Decider: Will Robbins
  • S2 REPLY-001 Who owns a customer reply (machine hold to human answer) | Draft | Decision: Approve as written or edit. 11 open decisions. Main ones: Name a cover manager per day off; set the response standard for urgent replies and for pod-manager action after a ping; approve call-first. | Decider: Will Robbins
  • S3 LEAD-001 New lead to a person: assignment, first human touch, phone-ups and walk-ins | Draft | Decision: Approve as written or edit. 10 open decisions. Main ones: Is call-inside-the-hour a rule or a goal; Desk or VinSolutions for walk-ins; who creates phone-ups for Oscar's pod. | Decider: Will Robbins
  • S4 APPT-001 Appointments: set, confirm by phone, prepare, arrive, no-show, unsold visit | Draft | Decision: Approve as written or edit. 13 open decisions. Main ones: Rep, manager or both call the day before; who marks shown, no-show, cancelled; no-show timing; Monday handling. | Decider: Will Robbins
  • S5 SALES-001 Manager involvement: TO on every write-up, stalled deals, documenting commitments | Draft | Decision: Approve as written or edit. 12 open decisions. Main ones: Must a manager see every deal before the customer leaves; stalled-deal clock; who covers when a pod manager is off. | Decider: Will Robbins
  • S6 INV-001 Check the unit before you promise it: availability, location, store ownership, trade info | Draft | Decision: Approve as written or edit. 9 open decisions. Main ones: Who appraises trades and how fast; who confirms a sister-store unit and brings it to Manor; merge with the inventory-truth page. | Decider: Will Robbins

B. Conflicts between rulings, pages and the machine (25)

  • C01 Orlando: "floor only" but still in the lead rule and roster | Needs Clarification | Decision: What 'floor only' means for lead assignment, roster and goals. Remove him from the VS round-robin and roster? Who takes his open leads? | Decider: Will Robbins (Eric French takes the leads)
  • C02 Porter name: Tre Templeton (roster) vs Tre Dunham (brief) | Needs Clarification | Decision: Confirm the porter's name and role so Receive Leads and the roster match. | Decider: Will Robbins
  • C03 Goals disagree: 125 vs 90/100 vs 137; rep goals 195 vs 203 | Needs Clarification | Decision: One store goal. Roster note and rep goals corrected. Rep goals stay between each rep and their manager. | Decider: Will Robbins (rep goals: each pod manager)
  • C04 Finance manager surname: ruling vs VinSolutions | Needs Clarification | Decision: Confirm the correct name in the roster and VS so reports match. | Decider: Will Robbins
  • C05 Old appointments left "Set" after their date | Needs Clarification | Decision: Who marks status (rep) and who checks (pod manager), by when; bulk-close the old Sets or leave them. | Decider: Will Robbins (pod managers enforce)
  • C06 Who confirms the day before: rep (page) vs manager (ruling) | Needs Clarification | Decision: Manager only, or rep with manager check? Update the confirmed page to match. | Decider: Will Robbins
  • C07 Floor sheet says a rep is off, but he logged work (Will Goodwin, Thursday) | Needs Clarification | Decision: Is the sheet stale for him? Who updates schedule overrides, and when? | Decider: Eric French (his pod), then Will Robbins edits the file
  • C08 Held drafts have no named approver and expire at 8:02am | Needs Clarification | Decision: Who approves a hold, whether a customer-reply hold may expire at all, and who gets the morning list. | Decider: Will Robbins
  • C09 No named cover when a rep and the pod manager are both off | Needs Clarification | Decision: Name a cover manager for each day off and an after-close check owner. | Decider: Will Robbins (each pod manager owns the list for their pod)
  • C10 Escalation ladder as described vs what ran | Needs Clarification | Decision: Confirm the ladder Will wants. The 45-minute Will escalation in the audit is a proposal only. | Decider: Will Robbins
  • C11 Machine promises a human follow-up with no task created | Needs Clarification | Decision: What the machine may promise, whether a promise creates a task for a named person, and where delivery-stage buyers' replies go. | Decider: Will Robbins
  • C12 Texting window end and Sunday rule | Needs Clarification | Decision: One window for staff and machine, and a Sunday rule. | Decider: Will Robbins
  • C13 Floor hours vs store hours (Friday close) | Needs Clarification | Decision: OK the Friday and Saturday 19:00 line in the file, and a rule for appointment times after close. | Decider: Will Robbins
  • C14 Staff email domain: which one people read | Needs Clarification | Decision: Which domain staff actually read; correct the list before Saturday's send. | Decider: Will Robbins
  • C15 Manager thank-you call: Tracker columns blank | Needs Clarification | Decision: Confirm the sheet is the one record, and who in each pod fills it. | Decider: Will Robbins
  • C16 Pod totals off team pages vs the 8:05am email | Needs Clarification | Decision: What the 8:05 email may show: rep-level counts, pod-level, or both. | Decider: Will Robbins
  • C17 What sends the 8:05am morning email | Needs Clarification | Decision: Confirm what sends the 8:05 email and that it is running. | Decider: Will Robbins
  • C18 Spanish speakers: two names in the ruling, more in the roster | Needs Clarification | Decision: Keep two names, or confirm Emely and Cesar. Where Eric's pod sends Spanish speakers. | Decider: Will Robbins
  • C19 Non-sales users texting customers with Receive Leads off | Needs Clarification | Decision: Who these users are and whether they may text customers. | Decider: Will Robbins
  • C20 Richard has no VinSolutions login but holds leads | Needs Clarification | Decision: Reassign his VS leads to Cesar, or write the note rule when working his leads. | Decider: Oscar Pulido, with Will Robbins
  • C21 Departed-rep leads still open or double-owned | Needs Clarification | Decision: Who checks for leads on departed names, how often, and which record is authoritative. | Decider: Will Robbins (Eric French for Faust's)
  • C22 Stale status (Lost, Sold, Duplicate) closing live replies | Needs Clarification | Decision: Does a fresh inbound reopen a Lost, Sold or Duplicate lead for a human, and who fixes the status. | Decider: Will Robbins
  • C23 Appointment goal of 10 per rep vs the actual pace | Needs Clarification | Decision: Is 10 per rep a hard target or a stretch? What counts as 'set'? | Decider: Will Robbins
  • C24 What counts: unit, show rate, weekend target | Needs Clarification | Decision: One definition of unit and of show rate, used in the huddle and emails. | Decider: Will Robbins
  • C25 Documented daily items vs what runs (lane lists, Duo tap, text-chief) | Needs Clarification | Decision: Who owns the 7:56am hidden-failures list each day, and who taps Duo. | Decider: Will Robbins

C. Existing pages that are Draft or Needs Clarification (33)

  • P01 APPT-000 Appointments and showroom (appointments/index) | Needs Clarification | Decision: Replace the 16%, 2% and 4-in-10 figures with the 9/30 appointment rule, or label them as data. Fold into APPT-001. | Decider: Will Robbins
  • P02 APPT-004 Set the appointment (appointments/set-appointment) | Needs Clarification | Decision: Keep the two-times habit as a rule? Add goal 10 / floor 1 and the same-day VinSolutions entry. Retire or cross-link to APPT-001. | Decider: Will Robbins
  • P03 APPT-002 Confirm the day before (appointments/confirm-day-before) | Needs Clarification | Decision: Page says the rep calls; the 9/30 ruling says the manager. Pick one, rewrite, then fold into APPT-001. | Decider: Will Robbins
  • P04 APPT-003 Running the showroom visit (appointments/showroom) | Draft | Decision: Keep "manager on every shown appointment"? Move status to VinSolutions per 9/30. Fold into APPT-001 and SALES-001. | Decider: Will Robbins
  • P05 DLV-004 (intro) Connected services (connected-services/index) | Draft | Decision: Verify against Ford's current process; separate Ford requirements from store policy. | Decider: Will Robbins
  • P06 DLV-004 FordPass activation at delivery (connected-services/fordpass-activation) | Draft | Decision: Who does it (salesperson or delivery person), by when, and which Tracker column logs it. Verify against Ford's checklist. | Decider: Will Robbins
  • P07 DLV-000 Delivery (delivery/index) | Draft | Decision: Align the list to the 10/7 ruling (manager call, DDT or survey, Google review, daily rep email, day-4 red, Monday email). Is the service intro a required item? | Decider: Will Robbins
  • P08 DLV-001 DDT (delivery/ddt) | Draft | Decision: Who does the DDT and by when. State new units only (10/7 ruling). | Decider: Will Robbins
  • P09 DLV-002 Survey / Google review (delivery/survey) | Draft | Decision: Matches the 10/7 ruling. Approve once an owner per role and timing are named. | Decider: Will Robbins
  • P10 DLV-003 Manager CSI call (delivery/csi-call) | Draft | Decision: Align to the 10/7 ruling: 2 days, day-4 red to Will and Gary, add "happy?". Drop the top-score question. Used units too? Name the cover. | Decider: Will Robbins
  • P11 SVC-001 Sales-to-service intro (delivery/service-intro) | Draft | Decision: Is the service intro required at delivery? Name advisor rotation, add the Tracker column, use roster names in the example. | Decider: Will Robbins
  • P12 LEAD-000 Customer first hour (first-hour/index) | Needs Clarification | Decision: The 90-day figures are data, not rulings. Label as a snapshot or remove. | Decider: Will Robbins
  • P13 LEAD-008 New lead: call inside the hour (first-hour/lead-response) | Needs Clarification | Decision: Is "call inside the hour" a rule or a goal? Name the after-hours owner. Fold into LEAD-001. | Decider: Will Robbins
  • P14 LEAD-002 Phone-up (customer calls in) (first-hour/phone-up) | Draft | Decision: Are three rings a rule? Change "log on the Desk" to VinSolutions per 10/7. Fold into LEAD-001. | Decider: Will Robbins
  • P15 LEAD-003 Walk-in greeting (first-hour/walk-in) | Draft | Decision: Is the one-minute greeting a rule? Log in VinSolutions per 10/7. Fold into LEAD-001. | Decider: Will Robbins
  • P16 LEAD-004 Keep in touch (first-hour/keep-in-touch) | Needs Clarification | Decision: Are "no lead a week without a call" and five calls a day rules? Name where the list lives and who checks. | Decider: Will Robbins
  • P17 MKT-001 Texting and messaging rules (texting-rules/index) | Needs Clarification | Decision: Split: approve rules 1 to 3 (no rates or dollar amounts, no holds or deposits, never name another store). Decide rules 4 and 5 (reply within the hour, log every call). | Decider: Will Robbins
  • P18 MKT-002 Voice and timing (texting-rules/voice-and-timing) | Needs Clarification | Decision: Set the window end (page says 9pm; machine and first-touch page say 8pm) and the Sunday rule. Confirm 25 a day and the voice rules. | Decider: Will Robbins
  • P19 REPLY-006 Read the notes first (texting-rules/read-the-notes) | Needs Clarification | Decision: Approve "read the notes first" and "lost with a reason is dead" as rules; name roles and where recorded. Fold into REPLY-001. | Decider: Will Robbins
  • P20 KEYS-000 Trade-ins and keys (trade-in-keys/index) | Draft | Decision: Remove or source the "costs money at wholesale" claim. Fold into KEYS-001. | Decider: Will Robbins
  • P21 KEYS-002 Trade-in keys: 8 steps (trade-in-keys/process) | Draft | Decision: Replace with Will's 10/9 workflow (KEYS-001) or keep the 8 steps as trade-in add-ons. The Tracker "Trade keys" column does not exist; the stock-number rule is inferred. | Decider: Will Robbins
  • P22 SYS-002 Tools we use (tools/index) | Needs Clarification | Decision: Confirm the dashboard address belongs on a team page. Add /todo, /training, /health, /pricing. Fix the Deliveries line. | Decider: Will Robbins
  • P23 REPLY-002 Reply Desk (tools/reply-desk) | Needs Clarification | Decision: Replace "first thing and after lunch" with the response standard. Add the 8:35am list and 2-hour escalation. Name the owner per pod. | Decider: Will Robbins
  • P24 DAY-003 TV board (tools/tv-board) | Needs Clarification | Decision: Decide what the TV shows (add the manager call per 10/7). Goal shown must be 125. Name who owns the board data. | Decider: Will Robbins
  • P25 DAY-002 Team Scoreboard (tools/team-scoreboard) | Needs Clarification | Decision: Pod standings in the huddle vs "pod totals stay off team-facing pages": decide. Goal 125; no bonus content. | Decider: Will Robbins
  • P26 DLV-005 Deliveries (tools/deliveries) | Draft | Decision: Rewrite: the page is live. Say managers use it, the daily rep email, day-4 red, Monday email. | Decider: Will Robbins
  • P27 SALES-002 Desk (tools/desk-log) | Needs Clarification | Decision: Who must tap which stage and when. Keep Desk stage separate from VinSolutions status. Fix the "Sold" stage wording. | Decider: Will Robbins
  • P28 SALES-003 Lease Calculator (tools/lease-calculator) | Needs Clarification | Decision: Is Q4 data loaded? Name the owner of the quarterly update. Separate Ford requirements from store policy. | Decider: Will Robbins
  • P29 MKT-003 Daily VIN walkaround script (tools/walkaround-script) | Needs Clarification | Decision: Name the rep and the reviewing manager; where it is posted and when. | Decider: Will Robbins
  • P30 DAY-001 The day at a glance (tools/day-at-a-glance) | Needs Clarification | Decision: Correct times to the scheduler (reminders 9:13 and 1:13, extracts, follow-up). Add 7:55, 8:35, 8:45, 11:30, 5:30. Rewrite after the Mini facts are confirmed. | Decider: Will Robbins
  • P31 INV-003 Inventory truth (tools/inventory-truth) | Needs Clarification | Decision: Reword "unknown means not available" to "unverified, never gone". Note the paused Facebook items. | Decider: Will Robbins
  • P32 SALES-004 AutoFi (tools/autofi) | Needs Clarification | Decision: Approve the hand-typed, read-back rule. Add "check AutoFi before a price complaint". Who may change a pencil. | Decider: Will Robbins
  • P33 SYS-001 If something looks wrong (tools/if-something-wrong) | Needs Clarification | Decision: Add a backup contact and the restart rule. Is routing everything to Will right? | Decider: Will Robbins

D. Rules not yet approved (26)

From the rules list. Items that are the same as a page row above are not repeated.

  • R01 Rule list DAY-003: A morning email goes out at 8:05am with counts, appointments and pods. | Draft | Decision: Say what each person must do with the 8:05am email and who owns it. Confirm what sends it. | Decider: Will Robbins (names the owner)
  • R02 Rule list DAY-004: At 8:45am the machine texts Will the day's questions (daily-questions job). | Draft | Decision: Keep the 8:45am text to Will as a documented daily item? | Decider: Will Robbins
  • R03 Rule list DAY-005: Lane lists at 7:55am give each pod its call list, with replies never answered first. | Draft | Decision: Name an owner for lane lists and fix the failure (code import error 10/8 and 10/9). | Decider: Will Robbins (names the owner)
  • R04 Rule list DAY-007: The October goal shown to the team is 125 (never Axcessa's 137). | Needs Clarification | Decision: Confirm one team goal (125) and correct the roster note. | Decider: Will Robbins
  • R05 Rule list DAY-008: Reps set their own goals with their manager. | Draft | Decision: Confirm rep goals are set with the manager and pod totals stay off team pages. | Decider: Will Robbins
  • R06 Rule list SYS-004: Facebook Marketplace price editor, mark-sold and closer are paused. | Draft | Decision: Date the Facebook pause as a ruling. Who removes sold units while mark-sold is paused? | Decider: Will Robbins
  • R07 Rule list LEAD-010: The machine first-touches new internet leads by text inside the texting window. | Draft | Decision: Confirm this as the first-touch rule. Who calls the leads the machine skips? | Decider: Will Robbins
  • R08 Rule list LEAD-011: A follow-up cadence texts open leads on a schedule. | Draft | Decision: Confirm the follow-up cadence and its gates as team policy. | Decider: Will Robbins
  • R09 Rule list LEAD-012: Credit-app leads (AutoFi, Upstart) get no machine first-touch; a response clock is built but the live... | Needs Clarification | Decision: Who calls credit-app leads and how fast? Switch on the clock pilot? | Decider: Will Robbins (names the owner)
  • R10 Rule list REPLY-001: The auto-responder answers inbound customer texts every 2 minutes with a guarded draft. | Draft | Decision: Confirm the auto-responder description as team policy. | Decider: Will Robbins
  • R11 Rule list REPLY-002: The machine HOLDS anything it is not allowed to say for a human: rates, dollar amounts, holds,... | Draft | Decision: Confirm the hold list (rates, dollar amounts, holds, unverified availability, other-store names). | Decider: Will Robbins
  • R12 Rule list REPLY-003: Who approves or answers a held draft. | Needs Clarification | Decision: Who approves or answers a held draft, by pod. | Decider: Will Robbins (names the owner)
  • R13 Rule list REPLY-004: Held drafts expire (sweep 8:02am) and roll into the 8:35am 'Replies we never answered, call first' list. | Draft | Decision: Who works the 8:35am list? May a customer-reply hold expire at all? | Decider: Will Robbins (names the owner)
  • R14 Rule list REPLY-005: An urgent inbound (customer arriving, ready to buy, asks for a call) pings the pod manager immediately and... | Draft | Decision: Confirm the urgent-reply ladder (pod manager at once, Will at 10 minutes). | Decider: Will Robbins
  • R15 Rule list REPLY-006: Pod-manager escalation at 2 hours on anything still held. | Draft | Decision: Name the pod-manager owner of the 2-hour escalation. | Decider: Will Robbins (names the owner)
  • R16 Rule list REPLY-007: Reps get a text when their customer replies. | Draft | Decision: Is "act within the hour" a rule or a goal? | Decider: Will Robbins (names the owner)
  • R17 Rule list REPLY-008: Rep texts are suppressed on the rep's day off and routed to the cover manager. | Draft | Decision: Confirm day-off routing to the cover manager. | Decider: Will Robbins (names the owner)
  • R18 Rule list REPLY-009: Who the cover manager is for each rep and pod manager day off. | Needs Clarification | Decision: Name the cover manager for each rep and pod-manager day off. | Decider: Will Robbins (names the owner)
  • R19 Rule list REPLY-010: Impel owns website chat. | Draft | Decision: Confirm Impel owns website chat and name the human owner for its handoffs. | Decider: Will Robbins
  • R20 Rule list MKT-002: When the texting window closes, and Sunday texting. | Needs Clarification | Decision: One texting window for staff and machine, and a Sunday rule. | Decider: Will Robbins
  • R21 Rule list INV-002: CARFAX is printed for every unit being evaluated. | Draft | Decision: Confirm CARFAX is printed for every unit being evaluated. | Decider: Will Robbins
  • R22 Rule list KEYS-001: Used-vehicle key: gets a stock-number sticker, is registered in the key-management system, goes in the... | Draft | Decision: Confirm Will's 10/9 key workflow as written. | Decider: Will Robbins (names the owner)
  • R23 Rule list KEYS-003: Open keys decisions: who registers the key, how exceptions are recorded, what happens when a key is... | Needs Clarification | Decision: Decide the five open key questions: who registers, exceptions, missing key, other-store keys, stock-number rule. | Decider: Will Robbins (names the owner)
  • R24 Rule list APPT-004: Appointment status (shown / no-show / cancelled) is marked in VinSolutions the same day. | Needs Clarification | Decision: Who marks shown, no-show or cancelled in VinSolutions, and who checks. | Decider: Will Robbins (names the owner)
  • R25 Rule list APPT-007: The machine sends appointment confirm and reminder texts (evening before and morning of). | Draft | Decision: Confirm the machine confirm and reminder texts as described. | Decider: Will Robbins
  • R26 Rule list SALES-004: Spanish-speaking customers are handed to Eddie or Matt. | Needs Clarification | Decision: Spanish-speaking customers: who gets them and how fast. | Decider: Will Robbins (names the owner)

Retired, no decision needed: rule list DLV-008: The nightly delivery-log job is retired; the delivery emails and the live delivery sheet replace it.

Five most urgent processes to document next

  1. Customer-response ownership: who answers a held or after-close customer reply. Evidence: Rules list, 4 high items. Hot customers waited 13+ hours after being told a person would follow up. Holds expire at 8:02am with no named owner. A booked buyer's 8:49pm text sat 13 hours. Coverage: Partly covered by REPLY-001 (rep, then pod manager, then cover chain). Not covered: a named after-close and Sunday check owner, a rule that a machine promise creates a task, named cover managers.
  2. Lead handoffs: missed calls, credit-app leads, the one-hour check, departed owners. Evidence: Rules list, 4 high items. 43 missed calls on 10/8 (41 unknown numbers) with no callback owner. 11 of 20 credit-app leads had no human touch. Only about half of in-hours digital leads got a human touch inside an hour. A departed rep's lead sat open since 9/22. Coverage: Partly covered by LEAD-001 (assignment, phone-ups and walk-ins in VinSolutions, departed-rep reassign). Not covered: missed-call callback owner, credit-app lead owner and response time, a named checker for the one-hour standard.
  3. Appointments: close out old "Set" appointments and mark status the same day. Evidence: Rules list, high. 33 past-dated Sets and 78 more older than 30 days make show rate, close rate and the weekend forecast unreliable. The 9/30 ruling does not say who marks status. Coverage: Partly covered by APPT-001 (set, confirm by phone, status same day, no-show, unsold visit). Not covered: who bulk-closes the old Sets and who checks daily.
  4. Manager involvement: be-back follow-up and deal approval limits. Evidence: Rules list, 2 high items. 7 visits and 3 TOs on 10/8; four named be-backs with no TO and no logged follow-up; four visits left open. Approval limits for negative-front deals have no written authority. Coverage: Partly covered by SALES-001 (manager and TO on every write-up, stalled deals, commitment notes) and APPT-001 step 29 (manager calls the next day). Not covered: approval limits (Unassigned, must come from Will).
  5. Delivery follow-through: same-day DDT, the manager thank-you call, booked buyer to pickup. Evidence: Rules list, 2 high items. 5 of 10 October new Fords have no DDT. The Mgr Call columns are blank on all 276 rows. A booked buyer's pickup question went unanswered for 13 hours. Coverage: Not covered by any of the six SOPs. Delivery draft pages exist (DDT, survey, CSI call, deliveries) and conflict with the 10/7 ruling in places.

Evidence changes the order you asked for. Vehicle readiness (recon, which units are ready for the weekend) is rated medium in the rules list, while delivery follow-through is rated high and backed by counts, so delivery takes slot 5 and vehicle readiness is next. INV-001 covers the availability and location checks (and leaves the other-store move as an open decision); KEYS-001 covers key control; neither gives the floor a weekend readiness list. Also rated high and not in the top five: daily systems owner (7:56am failures list), who taps the CallRevu Duo prompt, role-change checklist, who opens the store each day.

Change log

  • v1.1, Mon Oct 12 2026, 12:34 PM CT: Will OK'd pushing the hub chapter (HUB-000, HUB-001) and the six draft SOPs to the Mini /training book. All six show the draft ribbon. No status changed. Nothing announced.
  • v1, Fri Oct 9 2026, 11:55 AM CT: Hub built. All content is Draft; nothing is approved yet and nothing is published to the team.
  • Added: this Operations Hub page (HUB-000) and the Process status table (HUB-001).
  • Added six draft SOPs: KEYS-001 key control, REPLY-001 who owns a customer reply, LEAD-001 new lead to a person, APPT-001 appointments, SALES-001 manager involvement, INV-001 check the unit before you promise it.
  • Counted 40 existing pages and 6 new SOPs against the rules list (73 items) and 25 conflicts. No existing page was edited.
  • Four existing pages got new process IDs because their proposed IDs now belong to the new SOPs: set-appointment is APPT-004, lead-response is LEAD-008, read-the-notes is REPLY-006, trade-in process is KEYS-002.

Intake: facts Will must supply

These block approval. 12 lines.

People and coverage

  • Cover manager for each rep and pod-manager day off, and who reads customer texts after close and on Sunday.
  • Roster facts: what "floor only" means for Orlando's leads, the porter's name, the finance manager's correct name, whether Emely and Cesar are Spanish speakers, where Richard's leads and notes go.
  • Daily owners: who opens the store each day, who reads the 7:56am failures list, who taps the CallRevu Duo prompt.

Standards

  • Is "call inside the hour" a rule or a goal; the response standard for urgent replies; how long a pod manager has after a ping.
  • Appointments: manager only, or rep and manager, for the day-before call; who marks shown, no-show, cancelled; who closes the old Sets; what counts as "set".
  • The texting window end and the Sunday rule, one window for staff and machine.
  • Stalled-deal clock; what the TO button does; whether the manager always desks the numbers.

Money and numbers

  • Negative-front deal approval limits: who signs at what level.
  • What goes public: the one store goal (125) and what the 8:05am email may show (rep counts, pod totals, or both).

Vehicles, keys and delivery

  • Keys: system name, who registers, who holds the keybox key, who approves a missing-key replacement, the stock-number rule, other-store keys.
  • Trades and units: who appraises and how fast; who moves a unit from another group store and tells the customer.
  • Delivery records: confirm the Tracker as the one record for the manager thank-you call and who fills it per pod; where the used-car Google review ask is marked; which staff email domain people read.
Confirmed

Process status table

Owner: Will

Process status table

One line per page. Format: ID | title | status | owner | path under docs/training. Update a line when a page changes status. Version 1, Fri Oct 9 2026, 11:55 AM CT. Approved 7, Draft 19, Needs Clarification 20, Retired 0 (46 documents).

1. Lead handling and CRM

  • LEAD-000 | Customer first hour | Needs Clarification | Will | first-hour/index
  • LEAD-001 | New lead to a person: assignment, first human touch, phone-ups and walk-ins | Draft (Needs Approval) | Will | first-hour/new-lead-handoff
  • LEAD-002 | Phone-up (customer calls in) | Draft (Needs Approval) | Will | first-hour/phone-up
  • LEAD-003 | Walk-in greeting | Draft (Needs Approval) | Will | first-hour/walk-in
  • LEAD-004 | Keep in touch | Needs Clarification | Will | first-hour/keep-in-touch
  • LEAD-007 | What the machine can write in the CRM | Approved | Will | tools/crm-writes
  • LEAD-008 | New lead: call inside the hour | Needs Clarification | Will | first-hour/lead-response

2. Automations and handoffs

  • LEAD-005 | New-lead texter | Approved | Will | tools/first-touch
  • LEAD-006 | Follow-up engine | Approved | Will | tools/follow-up-engine
  • REPLY-001 | Who owns a customer reply (machine hold to human answer) | Draft (Needs Approval) | Will | first-hour/customer-reply-ownership
  • REPLY-002 | Reply Desk | Needs Clarification | Will | tools/reply-desk
  • REPLY-003 | Auto-responder | Approved | Will | tools/auto-responder
  • REPLY-004 | Approvals | Approved | Will | tools/approvals
  • REPLY-005 | Working one customer (desk-send) | Approved | Will | tools/desk-send
  • REPLY-006 | Read the notes first | Needs Clarification | Will | texting-rules/read-the-notes

3. Appointments and follow-up

  • APPT-000 | Appointments and showroom | Needs Clarification | Will | appointments/index
  • APPT-001 | Appointments: set, confirm by phone, prepare, arrive, no-show, unsold visit | Draft (Needs Approval) | Will | appointments/appointment-lifecycle
  • APPT-002 | Confirm the day before | Needs Clarification | Will | appointments/confirm-day-before
  • APPT-003 | Running the showroom visit | Draft (Needs Approval) | Will | appointments/showroom
  • APPT-004 | Set the appointment | Needs Clarification | Will | appointments/set-appointment

4. Sales process and manager involvement

  • SALES-001 | Manager involvement: TO on every write-up, stalled deals, documenting commitments | Draft (Needs Approval) | Will | appointments/manager-involvement
  • SALES-002 | Desk | Needs Clarification | Will | tools/desk-log
  • SALES-003 | Lease Calculator | Needs Clarification | Will | tools/lease-calculator
  • SALES-004 | AutoFi | Needs Clarification | Will | tools/autofi

5. Trades and inventory

  • INV-001 | Check the unit before you promise it: availability, location, store ownership, trade info | Approved (Will 10/29/26) | Will | tools/check-before-you-promise
  • INV-002 | Inventory Finder | Approved | Will | tools/inventory-finder
  • INV-003 | Inventory truth | Needs Clarification | Will | tools/inventory-truth

6. Keys recon photos merchandising

  • KEYS-000 | Trade-ins and keys | Draft (Needs Approval) | Will | trade-in-keys/index
  • KEYS-001 | Used-vehicle key control (sticker, register, keybox, check-out, return) | Draft (Needs Approval) | Will | trade-in-keys/key-control
  • KEYS-002 | Trade-in keys: 8 steps | Draft (Needs Approval) | Will | trade-in-keys/process

7. Finance delivery after-sale

  • DLV-000 | Delivery | Draft (Needs Approval) | Will | delivery/index
  • DLV-001 | DDT | Draft (Needs Approval) | Will | delivery/ddt
  • DLV-002 | Survey / Google review | Draft (Needs Approval) | Will | delivery/survey
  • DLV-003 | Manager CSI call | Draft (Needs Approval) | Will | delivery/csi-call
  • DLV-004 | FordPass activation at delivery | Draft (Needs Approval) | Will | connected-services/fordpass-activation
  • DLV-004 (intro) | Connected services | Draft (Needs Approval) | Will | connected-services/index
  • DLV-005 | Deliveries | Draft (Needs Approval) | Will | tools/deliveries

8. Marketing and communication

  • MKT-001 | Texting and messaging rules | Needs Clarification | Will | texting-rules/index
  • MKT-002 | Voice and timing | Needs Clarification | Will | texting-rules/voice-and-timing
  • MKT-003 | Daily VIN walkaround script | Needs Clarification | Will | tools/walkaround-script

9. Service-to-sales

  • SVC-001 | Sales-to-service intro | Draft (Needs Approval) | Will | delivery/service-intro

10. Systems and onboarding

  • SYS-001 | If something looks wrong | Needs Clarification | Will | tools/if-something-wrong
  • SYS-002 | Tools we use | Needs Clarification | Will | tools/index

11. Daily expectations

  • DAY-001 | The day at a glance | Needs Clarification | Will | tools/day-at-a-glance
  • DAY-002 | Team Scoreboard | Needs Clarification | Will | tools/team-scoreboard
  • DAY-003 | TV board | Needs Clarification | Will | tools/tv-board
Confirmed

Customer first hour

Owner: Will

The first hour decides the deal. Numbers are from our own last 90 days.

  • Half of buyers buy within a day of first contact. 8 in 10 buy within a week.
  • Walk-ins, calls, referrals and repeat customers close at 37%. Website marketplace leads close at 5%.
  • We called 63% of new leads inside the hour in August. In September it was 31%. That is the number to bring back.

Pages here: new lead, phone-up, walk-in, keep in touch.

Confirmed

New lead: call inside the hour

Owner: Will
Video coming: 60-second walkthrough of calling a new lead inside the hour

The rule: a new lead comes in, the phone call happens first. Goal: back to 6 in 10 called inside the hour.

  1. Open the lead and read the full profile and notes before you dial.
  2. Call. If no answer, leave a short voicemail with your name and the car they asked about.
  3. Right after the call, send a text from your phone. Offer two times: "Saturday at 10 or Monday at 2?"
  4. Log the call on the profile the same minute.

The machine texts new leads on its own, but it does not replace your call. Texts that offer two times get answered twice as often as a check-in.

Draft, Will to confirm

Phone-up (customer calls in)

Owner: Will
Video coming: Taking a phone-up and getting the appointment
Draft built from the team sheet habits. Will to confirm the steps.
  1. Answer within three rings. Say the store name and your name.
  2. Get their name, number and the vehicle they are calling about before anything else.
  3. Check the car is still here (Inventory Finder). Never say a unit is gone unless the system says so.
  4. Ask for the appointment, with two times.
  5. Log it as a phone-up on the Desk so it counts as a real lead.
  6. Text them the address and the two times you agreed on.

Phone-ups and walk-ins are the people we already know: they close far better than website leads.

Draft, Will to confirm

Walk-in greeting

Owner: Will
Video coming: Greeting a walk-in at the door
Draft. Will to confirm.
  1. Greet them inside the first minute. Smile, handshake, your name, ask theirs.
  2. Ask what brought them in and what they are driving now.
  3. Tap "Up" on the Desk so the walk-in is logged and a manager knows.
  4. Walk the car they came for before pitching anything else.
  5. Before they leave, get a phone number and set the next step, with two times.

Walk-ins close at 37%. Do not let one leave without a next step.

Confirmed

Keep in touch

Owner: Will
  • No lead goes a week without a call. Check your list. Anyone quiet for a week gets a call today.
  • Work your own book. People who bought from you 1 to 3 years ago are the next buyers. Five calls a day.
  • Repeat customers are 22% of this year's deals. 3 in 10 returning customers bought from a different salesperson, so stay in touch with yours.
Draft, Will to confirm

REPLY-001 Who owns a customer reply (machine hold to human answer)

Owner: Will

REPLY-001 Who owns a customer reply (machine hold to human answer)

Tags: [Approved: ...] = a Will ruling or a confirmed page. [Machine behavior] = what the automation does today. [Proposed] = not approved yet, do not enforce.

Identification

  • ID: REPLY-001
  • Status: Draft - Needs Approval (only the tagged-Approved and Machine behavior lines are in force today)
  • Roles: sales rep, pod manager, cover manager, Will Robbins (GSM)
  • Owner: Will
  • Approver: Will Robbins
  • Version: 1.0
  • Effective: Proposed
  • Source: see front-matter

When to use

  • A customer texts or emails back to an automated text, a rep text, or a follow-up.
  • The machine shows a HELD draft for that customer.
  • A customer appears on the 8:35am "Replies we never answered, call first" list.

What you need

  • VinSolutions login (to read the profile and notes, and to log the note).
  • The Reply Desk (/replies) and Home page, where held drafts wait with an Approve button.
  • Inventory Finder, to check a unit before saying anything about it.

Steps

  1. You get a text that your customer replied (or you see it on /replies). [Machine behavior] The text goes to the assigned rep.
  2. Act inside the hour. [Approved: confirmed page reply-desk]
  3. Read the full profile, notes and the thread before you answer. [Approved: confirmed page read-the-notes]
  4. Nothing goes to a customer before 8:30am. [Approved: Will ruling 9/28/26] A reply that landed overnight waits for 8:30am.
  5. Call the customer first. If no answer, leave a short voicemail, then text with two times ("Saturday at 10 or Monday at 2?"). [Approved: confirmed page lead-response for new leads] [Proposed] for every other reply: same order, unless the customer asked only a yes/no text question.
  6. If the machine shows a HELD draft for this customer, pick one of three (never more than one):
  7. Approve: sends the draft exactly as written. [Approved: confirmed page approvals]
  8. Edit: open the customer and send your own words. [Approved: confirmed page approvals]
  9. Call: phone the customer, then let the draft lapse. [Proposed]
  10. Never approve AND send your own text. That double-sends. [Approved: confirmed page approvals] If you answered another way, the draft shows "superseded" and will not send. [Machine behavior]
  11. In any text you write, do not: offer a hold or deposit, quote a rate, payment or Ford program, or tell the customer a unit is at Austin or Buda (say "our group"). Unit you cannot match = "unverified", never "gone". [Approved: Will standing rulings; Will ruling 10/4/26]
  12. Log the call on the profile the same minute. [Approved: confirmed page lead-response, for new leads] [Proposed] for other replies. Add a one-line note under your name: what they asked, what you said, next step. [Proposed]
  13. If it is urgent (customer is arriving, ready to buy, or asks for a call), phone them now, do not wait for the hour. [Proposed for the rep; the manager ping is Machine behavior]

Where it is recorded

  • VinSolutions profile: your call log and a one-line note under your name. [Approved: confirmed page lead-response] for the call log on new leads; the reply note format is [Proposed].
  • Reply Desk (/replies): shows what the machine did and the next step. [Approved: confirmed page reply-desk]
  • The machine adds its own short note after every send it makes. [Approved: confirmed page crm-writes]

Handoff (who receives it)

  • Normal: the assigned rep.
  • Urgent reply: the pod manager is pinged at once, Will at 10 minutes. [Machine behavior]
  • Held and still unanswered at 2 hours: pod manager is pinged. [Machine behavior]
  • Rep's day off: the rep text is suppressed and goes to the cover manager. [Machine behavior]
  • Pods: Matt = LaMarcus, Henry, Eddie, Tariq. Oscar = AJ, Emely, Cesar, Richard. Eric = Shane, Will Goodwin, Pedro, Orlando. [Approved: Will rulings 10/2 and 10/6/26]
  • Backup chain when the rep is off or silent: pod manager, then another manager, then Will. [Proposed] Who is "cover manager" on a given day: Unassigned.
  • Finance managers (Jeff Ledesma, Brian Calderon) never receive a sales reply decision. [Approved: Will ruling 10/2/26]

Done when

  • The customer has a real answer (call or text) from a person, or the held draft was approved. [Proposed]
  • The call is logged and the note is on the profile. [Proposed]
  • The Reply Desk item no longer shows as waiting on you. [Proposed]

Timing (only approved timing, else "Proposed")

  • Rep acts inside the hour. [Approved: confirmed page reply-desk]
  • Check the Reply Desk first thing and after lunch. [Approved: confirmed page reply-desk]
  • Texting window opens 8:30am. [Approved: Will ruling 9/28/26]
  • Machine holds 4 hours after you or a rep touched the thread, so the person runs it. [Approved: confirmed page auto-responder]
  • 8:35am: expired held drafts roll into "Replies we never answered, call first". [Machine behavior]
  • Urgent: pod manager at once, Will at 10 minutes. [Machine behavior]
  • Held: pod manager at 2 hours. [Machine behavior]
  • Any response-time standard tighter than "inside the hour" (for example minutes for urgent): Proposed, none set.
  • How long a pod manager has to act after a ping: Proposed, none set.

Exceptions

  • Thread touched by a human in the last 4 hours: machine holds and stays out. [Approved: confirmed page auto-responder]
  • Customer says stop, wrong number or not interested: stop texting. [Approved: confirmed page voice-and-timing]
  • Customer asks about money, credit, legal, or is angry: machine always holds; a person answers, preferably by phone. [Approved: confirmed page auto-responder] "Preferably by phone" is [Proposed].
  • Customer shopped another group store: write ONLY on the Manor record. [Approved: Will ruling 10/4/26]
  • Spanish-speaking customer: hand to Eddie or Matt Cavaness. [Proposed] (the two Spanish speakers are named by Will; the routing rule is not approved)
  • Richard has no VinSolutions login and his deals run through Cesar: the note goes on Cesar's login. [Proposed]
  • Website chat is owned by Impel, not this process. [Machine behavior]

Escalation

  1. Urgent reply: pod manager pinged at once, Will at 10 minutes. [Machine behavior]
  2. Held draft still waiting at 2 hours: pod manager pinged. [Machine behavior]
  3. Pod manager does not act: another manager, then Will. [Proposed]
  4. A held draft that expires unanswered rolls into the 8:35am "never answered, call first" list. [Machine behavior] The rep and pod manager call that list each morning. [Proposed]

Common mistakes

  • Waiting for the machine to answer a held draft. It will not; held means a person acts.
  • Approving the draft and also texting your own version (double send).
  • Texting only. The machine's texts do not replace the rep's call. [Approved: confirmed page lead-response]
  • Saying "that unit is gone" because Inventory Finder found no match. Say "let me confirm". [Approved: Will standing ruling]
  • Mentioning a rate, payment, Ford program, hold, or another store's name in your own edit.
  • Ignoring a rep text because it is a day off and assuming the cover manager has it, without checking.

Manager check

  • Pod manager looks at the Reply Desk for their pod's items waiting more than an hour, at the same first-thing and after-lunch checks. [Proposed]
  • Pod manager works the 8:35am list with the rep each morning. [Proposed]
  • Will reviews numbers at 11:30 and 5:30 (his stated habit); whether reply wait time is part of that review: Proposed.

Example / checklist / script

Fictional: a customer answers a follow-up text with "Can you do better on the Explorer?"

  1. The machine holds the draft (money). The rep gets the ping.
  2. Rep reads notes and thread, calls the customer. No answer, leaves voicemail with name and the Explorer.
  3. Rep texts: "Hey [first name], [your name] at Leif Johnson Ford of Manor. Just tried you about the Explorer. Can you come in Saturday at 10 or Monday at 2?"
  4. Rep does not approve the held draft. It shows superseded.
  5. Rep logs the call and adds: "Customer replied asking about price on Explorer, called, VM, texted two times. Next: call again tomorrow morning."

Checklist: read notes, call, text with two times, no hold or rate or other-store name, log the call, add the note.

Open decisions

  • Approve the backup chain (pod manager, another manager, Will) and name the cover manager for each day off.
  • Set a response standard for urgent replies (minutes, not an hour) and for how fast a pod manager must act after a ping.
  • Approve "call first, then text" for all replies, or only for urgent and money replies.
  • Approve the one-line reply note format in VinSolutions.
  • Contradiction to settle: the Reply Desk page says check "first thing and after lunch" but the rule is act inside the hour; confirm the pings are what trigger action and the two checks are a backstop.
  • Contradiction to settle: the store is closed Sunday (Will 10/7/26), but the voice-and-timing page allows Sunday texts after noon; who answers Sunday replies?
  • Evening replies: the voice-and-timing page stops marketing texts at 9pm, but the store closes 8pm Mon-Thu and 7pm Fri-Sat; may reps text customers after close?
  • Does the 8:35am list rule replace the 2-hour pod-manager escalation, or do both stay?
  • Spanish-speaking customers: approve routing to Eddie or Matt Cavaness.
  • Richard (no VinSolutions login): confirm notes go on Cesar's login.
  • Whether the Reply Desk page "easy answers go out on their own" wording should be tightened to match the auto-responder page.
Draft, Will to confirm

LEAD-001 New lead to a person: assignment, first human touch, phone-ups and walk-ins

Owner: Will

LEAD-001 New lead to a person: assignment, first human touch, phone-ups and walk-ins

Tags used below: [Approved: ...] = Will's ruling or a confirmed page, enforceable now. [Machine behavior] = what the automation does today. [Proposed] = suggested, not yet a rule.

Identification

  • ID: LEAD-001
  • Status: Draft - Needs Approval (some lines below are already Approved, see tags)
  • Roles: Sales rep, pod manager, Will Robbins (GSM)
  • Owner: Will
  • Approver: Will Robbins
  • Version: 1.0
  • Effective: Proposed
  • Source: Will ruling 9/28/26 (texting window); Will ruling 10/3/26 and 10/6/26 (departed reps, lead distribution); Will ruling 10/4/26 (Manor record only); Will ruling 10/7/26 (phone-ups and showroom visits, store hours); confirmed page first-hour/lead-response; draft pages first-hour/phone-up and first-hour/walk-in; confirmed pages tools/first-touch, tools/crm-writes, texting-rules/read-the-notes; machine behavior as of 10/9/26

When to use

  • A new internet lead lands in VinSolutions.
  • A customer calls in (phone-up).
  • A customer walks in without an appointment (showroom visit).
  • A lead has no owner, has a departed owner, or exists twice.

What you need

  • Your VinSolutions login (Oscar's pod: no login, deals go through Cesar).
  • The Desk page (/desk) for walk-in "Up" and stage taps.
  • Inventory Finder, to check a unit before you say anything about it.
  • Your manager's number.

Steps

A. Who gets the lead

  1. VinSolutions assigns each internet lead by the rep's floor schedule. [Approved: Will ruling 10/6/26]
  2. A lead that arrives after close goes to whoever opens the next morning. [Approved: Will ruling 10/6/26]
  3. If no rule matches, the lead goes to Will Robbins. [Approved: Will ruling 10/6/26]
  4. Anyone not in sales (rental, delivery, acquisitions, service advisors, retired) has Receive Leads turned off. [Approved: Will ruling 10/6/26]

B. What the machine does first

  1. A new internet lead gets a first text inside the texting window, signed as the assigned rep. [Machine behavior]
  2. Nothing goes to a customer before 8:30am CT. [Approved: Will ruling 9/28/26]
  3. The machine skips sold, lost, opted-out and do-not-contact leads. [Machine behavior]
  4. The machine text does not replace your call. [Approved: confirmed page first-hour/lead-response]

C. What you do (first human touch)

  1. Open the lead. Read the full profile and notes before you dial. [Approved: confirmed page first-hour/lead-response]
  2. Call. No answer: leave a short voicemail with your name and the car they asked about. [Approved: confirmed page first-hour/lead-response]
  3. After the call, text from your phone and offer two times, for example "Saturday at 10 or Monday at 2?" [Approved: confirmed page first-hour/lead-response]
  4. Log the call on the profile the same minute. [Approved: confirmed page first-hour/lead-response]
  5. Goal: 6 in 10 new leads called inside the hour. This is a goal, not a pass/fail rule. [Approved: confirmed page first-hour/lead-response]
  6. If the hour was missed, the call still happens the same day. [Proposed]
  7. When the customer replies, the machine texts you. Act within the hour. [Machine behavior]

D. Phone-ups and walk-ins

  1. Create the phone-up or showroom visit in VinSolutions under the rep, with a note, the same day. This lets the machine follow up. [Approved: Will ruling 10/7/26]
  2. The machine is authorized to create phone-ups and showroom visits too. It does not replace the rep's same-day entry. [Approved: Will ruling 10/7/26]
  3. Phone-up: answer, get name, number and vehicle, check Inventory Finder, ask for the appointment with two times, text the address and times. [Proposed: draft page first-hour/phone-up]
  4. Walk-in: greet inside the first minute, tap "Up" on the Desk, walk the car they came for, get a phone number, set the next step with two times. [Proposed: draft page first-hour/walk-in]
  5. Never say a unit is gone unless a VinSolutions sold flag or VinCue status says so. If you cannot match it, it is "unverified". [Approved: Will, standing]

E. Departed or retired reps

  1. Their open leads are reassigned the same day with the reassign tool. The tool keeps a ledger. [Approved: Will ruling 10/3/26 and 10/6/26]
  2. Robert Carreon's leads and past buyers go to AJ (Ajay Malani). [Approved: Will ruling 10/3/26 and 10/6/26]
  3. Robert Faust's leads went to Shane, Will Goodwin, Pedro and Javier on 10/3. [Approved: Will ruling 10/3/26]

F. Duplicates

  1. One person with several records: work the newest record. Leave a note on the others saying where the work is. [Proposed]
  2. If the customer also shopped Austin or Buda, write ONLY on the Manor record. Never tell a customer a unit is at Austin or Buda; say "our group". [Approved: Will ruling 10/4/26]
  3. A person decides which record to keep. Ask your pod manager if unsure. [Proposed]

G. Overdue tasks

  1. Clear or reschedule your overdue CRM tasks every day. Your manager checks. [Proposed]

H. Lead with no owner

  1. The default owner is Will Robbins, so an unowned lead lands on Will. [Approved: Will ruling 10/6/26]
  2. Will places it with a rep or pod manager the same day. [Proposed]
  3. Anything still held or unanswered goes to the pod manager at 2 hours. Urgent inbound (customer arriving, ready to buy, asks for a call) pings the pod manager at once and Will at 10 minutes. [Machine behavior]

Where it is recorded

  • VinSolutions lead profile: call log, notes, tasks, phone-up and showroom entries.
  • Desk (/desk): walk-in "Up" and stage.
  • Reassign tool ledger: every departed-rep move.
  • Morning email 8:05am: counts. "Replies we never answered, call first" list, 8:35am: unanswered replies.

Handoff

  • Rep to pod manager: any live deal, any urgent reply, any lead you cannot reach by phone.
  • Pod managers: Matt (LaMarcus, Henry, Eddie, Tariq), Oscar (AJ, Emely, Cesar, Richard), Eric (Shane, Will Goodwin, Pedro, Orlando). [Approved: Will 10/2 and 10/6/26]
  • No owner: Will.
  • Never route a sales decision to finance (Jeff Ledesma, Brian Calderon). [Approved: Will 10/2 and 10/6/26]

Done when

  • The lead has a named rep (not blank, not a departed rep).
  • The first call is logged on the profile.
  • A text with two times has gone out from your phone.
  • Phone-ups and walk-ins exist in VinSolutions with a note.
  • Duplicates have a note pointing to the working record.

Timing

  • Customer texts start 8:30am CT. [Approved: Will ruling 9/28/26]
  • Machine texts to customers go out 8:30am to 8pm only. [Approved: confirmed page tools/first-touch]
  • Store close: 8pm Mon-Thu, 7pm Fri-Sat, closed Sunday. [Approved: Will ruling 10/7/26]
  • Call inside the hour: goal only. [Approved: confirmed page first-hour/lead-response]
  • Departed-rep reassignment and phone-up entry: same day. [Approved: Will ruling 10/6/26 and 10/7/26]
  • Same-day call when the hour was missed; daily overdue task cleanup; same-day no-owner placement: Proposed.

Exceptions

  • Rep on a day off: rep texts are held and sent to the cover manager. [Machine behavior]
  • Lead already live (appointment today or tomorrow, showroom visit, message in last 4 hours): the machine stays out and the rep runs it. [Approved: confirmed page texting-rules/read-the-notes]
  • Website chat is owned by Impel, not the rep. [Machine behavior]
  • Spanish-speaking customer: Eddie Cavaness or Matt Cavaness. [Proposed]
  • Lost with a reason is dead. Do not restart it. [Approved: confirmed page texting-rules/read-the-notes]

Escalation

  1. Rep cannot reach the customer or the lead is live: pod manager.
  2. Pod manager does not act: the machine pings Will at 10 minutes on urgent replies. [Machine behavior]
  3. No owner, no manager, or a rule does not fit: Will Robbins.

Common mistakes

  • Leaving the call to the machine text.
  • Logging a walk-in on the Desk only and not in VinSolutions, so the machine never follows up.
  • Writing on an Austin or Buda record instead of the Manor record.
  • Telling a customer a unit is "gone" or at another store.
  • Quoting a payment, rate or dollar amount, or offering a hold or deposit. [Approved: Will, standing]
  • Working the old duplicate record.

Manager check

  • Pod manager scans new leads daily for blank or departed owners. [Proposed]
  • Pod manager checks that phone-ups and walk-ins from the day are in VinSolutions with a note. [Proposed]
  • Will reviews the numbers at 11:30 and 5:30 (his stated habit, 10/9). [Approved: Will, stated 10/9]

Example / checklist / script

Example (fictional): A customer fills out a web form at 9:12pm Thursday for a used Escape.

  1. 9:12pm: after close, so VinSolutions gives it to whoever opens Friday.
  2. The machine text waits until 8:30am.
  3. Friday morning: the rep reads the notes, calls, leaves a voicemail.
  4. The rep texts: "[Rep name] at Leif Johnson Ford of Manor. Got your Escape request. Can you come Saturday at 10 or Monday at 2?"
  5. The rep logs the call. Done.

Checklist: read notes, call, voicemail, text with two times, log the call.

Open decisions

  • Is "call inside the hour" a rule or a goal, and what is the standard for leads that arrive after hours?
  • Do missed-hour leads get a same-day call, and who checks?
  • Who places leads that land on Will, and by when?
  • Confirm the duplicate rule: work the newest, note the others.
  • Overdue tasks: what counts as overdue, and who checks?
  • Which is the record for walk-ins: the Desk "Up" tap or VinSolutions? The old phone-up page says Desk, the 10/7 ruling says VinSolutions.
  • Oscar's pod has no VinSolutions login: who creates phone-ups and walk-ins for AJ, Emely and Richard?
  • Spanish-speaking leads: assign to Eddie or Matt, or call them in?
  • Confirm the phone-up steps (three rings, two times) and the walk-in steps.
  • Who covers a rep's leads on days off, beyond the cover manager getting texts?
Confirmed

Set the appointment

Owner: Will

Ask for the appointment every time, with two times.

  • Good: "Saturday at 10 or Monday at 2?"
  • Weak: "When can you come in?"

Saturday is our biggest day: about 31% of deals. Offer Saturday first.

Confirmed

Confirm the day before

Owner: Will
  1. The afternoon before, call the customer. A call, not a text.
  2. Lock the time and the vehicle. Say both back to them.
  3. Make sure the car is on the lot, clean and findable.
  4. Log the call.

The machine also sends reminder texts (the evening before and the morning of). They help but do not replace your call.

Draft, Will to confirm

Running the showroom visit

Owner: Will
Draft. Will to confirm.
  1. Meet them at the door at the appointment time. Have the car out front.
  2. Tap the customer's stage on the Desk as they move: Appointment, Shown, Write-up, Pending.
  3. A manager is on every shown appointment.
  4. If they leave without buying, tap Left on the Desk. Left customers go into a save-a-deal follow-up that evening.
  5. Always set the next step before they walk out.
Draft, Will to confirm

APPT-001 Appointments: set, confirm by phone, prepare, arrive, no-show, unsold visit

Owner: Will

APPT-001 Appointments: set, confirm by phone, prepare, arrive, no-show, unsold visit

Every rule line is tagged. [Approved: Will ruling <date>] is enforceable now. [Machine behavior] is what the automation does today. [Proposed] is not a rule until Will approves it.

Identification

  • ID: APPT-001
  • Status: Draft - Needs Approval (the core lines tagged Approved are already in force)
  • Roles: Salesperson (sets, prepares, greets), pod manager (confirms by phone, joins every shown visit), Will Robbins (numbers, escalations)
  • Owner: Will
  • Approver: Will Robbins
  • Version: 1.0
  • Effective: Proposed
  • Source: Will rulings 9/30/26, 9/28/26, 10/7/26, 10/4/26 and standing rulings; confirmed pages set-appointment, confirm-day-before, desk-log, voice-and-timing; draft page showroom; machine behavior

When to use

  • Any time a customer agrees to come in on a set day and time.
  • From the moment you set it until the visit ends in a sale, a no-show, or an unsold visit.
  • Customers who walk in with no appointment: tap "Up" on the Desk to log the walk-in, then follow Step 18 onward here.

What you need

  • The lead open in VinSolutions, with notes read first.
  • The unit checked in Inventory Finder.
  • The Desk (/desk) for customer stage.
  • Your pod manager's name and phone.

Steps

Set it

  1. Ask for the appointment every time, with two times: "Saturday at 10 or Monday at 2?" Offer Saturday first. [Approved: existing confirmed page]
  2. Offer times only when we are open: close 8pm Mon-Thu, 7pm Fri-Sat, closed Sunday. [Approved: Will ruling 10/7/26]
  3. Check the unit in Inventory Finder first. Not found = "unverified". Never say "gone" unless the VinSolutions sold flag or VinCue says so. [Approved: Will standing ruling]
  4. Never hold the car or take a deposit. Never quote a rate, payment or Ford program unless Will gave this month's. [Approved: Will standing ruling]
  5. If the car is at another group store, say "our group". Never say Austin or Buda. Write only on the Manor record. [Approved: Will ruling 10/4/26]
  6. Put the appointment date and time on the lead in VinSolutions the same day. [Proposed] The machine reads appointments from the lead. [Machine behavior]
  7. Goal: 10 appointments set per rep per week. Floor: 1 per day. [Approved: Will ruling 9/30/26]

Confirm the day before

  1. The afternoon before, call the customer. A call, not a text. [Approved: existing confirmed page]
  2. The manager also confirms by phone the day before. [Approved: Will ruling 9/30/26]
  3. Say the time and the car back to them. [Approved: existing confirmed page]
  4. Log the call in VinSolutions. [Approved: existing confirmed page]
  5. Monday appointment: confirm on Saturday, because Sunday is closed. [Proposed]
  6. Customer cancels or moves it: update VinSolutions, offer two new times. [Proposed]

Prepare the vehicle

  1. Car is on the lot, clean and findable. [Approved: existing confirmed page]
  2. Before the appointment time: pull it up front, key in hand from the keybox, tank not empty. [Proposed]
  3. Car not on the lot or not confirmed: call the customer before they drive in and offer a close match. Never call it gone unless the VinSolutions sold flag or VinCue says so. [Proposed]

Arrive

  1. Meet them at the door at the appointment time. [Proposed, from the draft showroom page]
  2. Tap Shown on the Desk when they arrive. [Approved: existing confirmed page tools/desk-log]
  3. A manager joins every shown appointment. [Proposed, from the draft showroom page]
  4. Every write-up gets a manager and a TO. Press TO in VinSolutions. [Approved: Will ruling 9/30/26]

Mark the result

  1. Mark the status in VinSolutions the same day: shown, no-show or cancelled. [Approved: Will ruling 9/30/26]

No-show

  1. Call within one hour of the appointment time. No answer: leave a voicemail. [Proposed]
  2. Text from your phone with two new times. [Proposed] Nothing goes to a customer before 8:30am CT. [Approved: Will ruling 9/28/26]
  3. Rebook, and put the new date on the lead. Then confirm the new date the day before, as in Steps 8 to 11. [Proposed]
  4. The machine checks the appointment status on the lead before proactive texts, so keep the status current. [Machine behavior] The exact cadence rule for no-shows is not verified. See Open decisions.

Unsold visit

  1. They leave without buying: tap Left on the Desk. [Approved: existing confirmed page tools/desk-log]
  2. At 7:05pm Mon-Sat the machine sends managers a list of customers tapped Left that day. Rep texts go out only if switched on. It does not text the customer. [Machine behavior]
  3. Write a same-day note in VinSolutions: why they left, what they need, next step. [Proposed]
  4. The manager calls the customer the next day. [Proposed]
  5. Always set the next step, with two times, before they walk out. [Proposed, from the draft showroom page]

Where it is recorded

  • VinSolutions: appointment date, call log, status (shown / no-show / cancelled), TO, notes.
  • Desk (/desk): Appointment, Shown, Write-up, Pending, Left.
  • 8:05am morning email: public set count. [Approved: Will ruling 9/30/26]
  • Machine texts (below) are not a record of the call.

Handoff

  • Rep to manager: the confirm call (Step 9) and every shown visit (Step 19). Confirming manager = the rep's pod manager. [Proposed]
  • Manager to finance: never route a sales decision to finance. [Approved: Will ruling 10/2/26]
  • Rep departed or retired: open leads are reassigned the same day. [Approved: Will ruling 10/3/26] The new owner keeps the appointment and confirms it. [Proposed]
  • Machine texts the rep when their customer replies, and sends it to the cover manager on the rep's day off. [Machine behavior]

Done when

  • The visit ended as a sale, a rebooked appointment, or a dated next step. [Proposed]
  • The status is marked in VinSolutions the same day. [Approved: Will ruling 9/30/26]
  • Write-ups have a manager and a TO. [Approved: Will ruling 9/30/26]

Timing (approved timing only, else "Proposed")

  • Confirm call: the afternoon before. [Approved: existing confirmed page]
  • Manager phone confirm: the day before. [Approved: Will ruling 9/30/26]
  • Status marked: same day. [Approved: Will ruling 9/30/26]
  • Set count in the email: 8:05am. [Approved: Will ruling 9/30/26]
  • Customer texts: not before 8:30am CT. [Approved: Will ruling 9/28/26]
  • No-show call within 1 hour; unsold-visit manager call next day: [Proposed]

What the machine sends (do not rely on it)

  • Confirm text at 5:07pm, retry at 6:20pm. Reminder texts at 9:13am and 1:13pm Mon-Sat, 12:05pm Sunday. [Machine behavior]
  • An appointment set after a pass misses that pass. Example: a Friday appointment set after 1:13pm gets no 1:13pm reminder. [Machine behavior]
  • Texts never replace the call. [Approved: existing confirmed page]

Exceptions

  • Customer asks you to hold the car for the appointment: say no, offer the time instead. [Approved: Will standing ruling]
  • Customer asks about rate or payment: no number unless Will gave this month's. Check AutoFi before answering a price complaint. [Approved: Will standing ruling] The manager answers. [Proposed]
  • Customer shopped another group store: work on the Manor record only. [Approved: Will ruling 10/4/26]
  • Customer texts "stop", "wrong number" or "not interested": no more texts. [Approved: existing confirmed page texting-rules/voice-and-timing] Whether you still call is the manager's decision. [Proposed]
  • Rep with no VinSolutions login (Richard): who logs the appointment is not set. See Open decisions.

Escalation

  • Customer says they are arriving or ready to buy: the machine pings the pod manager at once and Will at 10 minutes. [Machine behavior]
  • Held reply still open at 2 hours: the machine pings the pod manager. [Machine behavior]
  • Unit problem, angry customer, or pricing question: pod manager first. [Proposed]
  • Pod manager unreachable: Will Robbins. [Proposed]

Common mistakes

  • Texting to confirm instead of calling.
  • Offering one time, not two.
  • Appointment not on the lead in VinSolutions, so it is missing from the count.
  • Status left blank at end of day.
  • Write-up with no manager or no TO.
  • "I'll hold it for you."
  • Naming Austin or Buda.
  • Counting on a machine reminder for an appointment set after the last pass.

Manager check

  • Morning: read the 8:05am set count. Who is under the floor of 1? [Proposed check of the Approved rule, Will ruling 9/30/26]
  • Every appointment for tomorrow has a manager phone confirm. [Proposed check of the Approved rule, Will ruling 9/30/26]
  • Every appointment from today has a status in VinSolutions. [Proposed check of the Approved rule, Will ruling 9/30/26]
  • Every write-up today has a TO. [Proposed check of the Approved rule, Will ruling 9/30/26]
  • Weekly: set count against the goal of 10 per rep. [Proposed check of the Approved rule, Will ruling 9/30/26]
  • Will reviews the numbers at 11:30 and 5:30 (his stated habit, 10/9). Not a rule for the team. [Proposed]

Example / checklist / script

Confirm call

"Hi [name], this is [your name] at Leif Johnson Ford of Manor. Calling to lock in tomorrow, Saturday at 10, to see the white Escape. Still good? ... Great, the car will be out front and I'll meet you at the door. Anything you need me to have ready?"

Then: log the call, check the car is up front, leave your manager the time.

Checklist for the day before

  1. Called, not texted.
  2. Time and car said back.
  3. Call logged.
  4. Car on the lot and clean.
  5. Manager knows the time.

Open decisions

  1. Does the rep call, the manager call, or both the day before? The old confirmed page says the rep calls; the 9/30 ruling says the manager confirms.
  2. Who is the confirming manager: the rep's pod manager, or whoever is on the floor?
  3. Monday appointments: confirm Saturday, or a manager phone call on Sunday while we are closed?
  4. Does the floor of 1 per day apply on a rep's day off and on Sundays?
  5. Approve the vehicle prep list: front, key, fuel, clean.
  6. Approve the no-show timing: call within 1 hour, rebook with two times.
  7. Approve the unsold-visit follow-up: same-day note, manager call the next day.
  8. Is a manager required on every shown appointment (the showroom page is still a draft)?
  9. How many rebook tries after a no-show before the lead goes back to the cadence?
  10. Richard has no VinSolutions login: who logs his appointments and status?
  11. Which appointments does each machine pass pick up? Confirm the 5:07pm and 1:13pm coverage on the Mini before telling the team.
  12. Machine cadence for a no-show or a stale "Set": confirm the real rule on the Mini before the team relies on it.
  13. Retire or cross-link the overlapping pages (set-appointment, confirm-day-before, showroom, index) once this is approved.
Draft, Will to confirm

SALES-001 Manager involvement: TO on every write-up, stalled deals, documenting commitments

Owner: Will

SALES-001 Manager involvement: TO on every write-up, stalled deals, documenting commitments

Identification

  • ID: SALES-001
  • Status: Draft - Needs Approval. Only lines tagged [Approved] or [Machine behavior] are enforceable today. Lines tagged [Proposed] are not rules yet.
  • Roles: Salesperson, pod manager, cover manager. Finance managers are not part of this process.
  • Owner: Will
  • Approver: Will Robbins
  • Version: 1.0
  • Effective: Proposed
  • Source: Will rulings 9/30, 10/2, 10/4, 10/6, 10/7/26; standing rulings; machine behavior. Full list in the front-matter.

Tag key:

  • [Approved: Will ruling <date>] = Will said it. Enforceable.
  • [Machine behavior] = what the automation does today. Not a rule for people.
  • [Proposed] = a draft idea. Not enforceable until Will approves.

When to use

  1. A customer is written up on a vehicle. [Approved: Will ruling 9/30/26]
  2. A customer wants to leave before a manager has seen the deal. [Proposed]
  3. Numbers went out and the customer has gone quiet. [Proposed]
  4. A customer says what they will do next (come back, bring a spouse, get a payoff, think about it). [Proposed]
  5. The pod manager is off or out of the building. [Proposed]

What you need

  • The customer's lead or visit open in VinSolutions, under the rep. [Approved: Will ruling 10/7/26]
  • Your pod manager (Matt, Oscar or Eric; pods are in the Managers list). [Approved: Will ruling 10/2 and 10/6/26]
  • The Desk (/desk) to see the customer's stage. [Proposed: the Desk stages come from the draft page appointments/showroom.md, not confirmed]
  • The current month's Ford programs from Will, if a program is to be mentioned. Without them, say nothing about programs. [Approved: Will standing]

Steps

  1. Write up the deal. Get your pod manager before the customer is told anything on numbers. [Approved: Will ruling 9/30/26 for manager and TO; the "before numbers" timing is Proposed]
  2. Press TO in VinSolutions on that write-up so the manager is on the deal. [Approved: Will ruling 9/30/26]
  3. Move the customer to Write-up on the Desk. [Proposed: the Write-up stage is listed on the draft page appointments/showroom.md, not confirmed]
  4. Do not quote a rate, payment or Ford program unless Will gave the current month's. [Approved: Will standing] The manager desks the numbers. [Proposed for who presents]
  5. Never offer to hold the unit or take a deposit. [Approved: Will standing]
  6. If the customer shopped another group store, write only on the Manor record. Never say a unit is at Austin or Buda; say "our group". [Approved: Will ruling 10/4/26]
  7. If a customer wants to leave before a manager has seen the deal, the rep gets the manager to the customer first. [Proposed]
  8. Before the customer leaves, write a VinSolutions note: what they said they will do, and the next step with a day. [Proposed]
  9. If the deal is negative front, the manager writes the reason in the Desk log. [Proposed: raised in 10/9 one-on-ones, not yet ruled]
  10. Numbers out, no answer after a set time (Will decides): the manager calls the customer. [Proposed]
  11. After the customer leaves, move them on the Desk (Pending or Left) and set the next step. [Proposed: stages from the draft page appointments/showroom.md]

Where it is recorded

  • TO: pressed in VinSolutions on the write-up. [Approved: Will ruling 9/30/26]
  • Customer's commitment and next step: a short note in VinSolutions. [Proposed]
  • Stage: the Desk. [Proposed: see the draft page appointments/showroom.md]
  • Negative-front reason: the Desk log. [Proposed. Whether the Desk has a field for it is not confirmed.]
  • Stalled-deal call: a VinSolutions note by the manager. [Proposed]

Handoff

  • Rep to pod manager at the write-up. [Approved: Will ruling 9/30/26]
  • Pod manager to cover manager when the pod manager is off. [Proposed. No cover manager is assigned: Unassigned.]
  • Decisions stay with sales managers. Never route a sales decision to Jeff Ledesma or Brian Calderon. [Approved: Will ruling 10/2 and 10/6/26]
  • Finance manager handles finance only, after the sales manager and customer agree on the deal. [Proposed wording]

Done when

  • The write-up has a manager and TO is pressed. [Approved: Will ruling 9/30/26]
  • The VinSolutions note shows the customer's commitment and a next step with a day. [Proposed]
  • The customer is on the right Desk stage. [Proposed]
  • If it stalled, the manager's call is noted. [Proposed]

Timing

  • Manager and TO on every write-up: no clock stated in the ruling. [Approved: Will ruling 9/30/26]
  • Note before the customer leaves: [Proposed]
  • Stalled deal call after numbers go out: no clock set, Will decides. [Proposed]
  • Store hours: close 8pm Mon-Thu, 7pm Fri-Sat, closed Sunday. [Approved: Will ruling 10/7/26]
  • Texts to customers do not go before 8:30am CT. [Approved: Will ruling 9/28/26]
  • Urgent inbound reply (customer arriving, ready to buy, asks for a call): pod manager is pinged at once, Will at 10 minutes. [Machine behavior]
  • Anything still held at 2 hours goes to the pod manager. [Machine behavior]

Exceptions

  • Rep is off: reply-alert texts are held back from the rep and go to the cover manager. [Machine behavior]
  • Pod manager is off: who steps in is not set. [Proposed: another sales manager on the floor. Unassigned.]
  • Customer will not wait for a manager: see Step 7 and Escalation. [Proposed]
  • Oscar's pod: Richard has no VinSolutions login and deals through Cesar. Press TO under Cesar's record. [Approved: Will ruling 10/2 and 10/6/26 for the pod facts; "under Cesar's record" is Proposed]

Escalation

  1. Rep to pod manager. [Approved: Will ruling 9/30/26]
  2. Pod manager off or unreachable: rep goes to another sales manager on the floor. [Proposed. Unassigned.]
  3. Nobody reachable: rep tells Will. [Proposed]
  4. Machine side: urgent inbound goes to the pod manager at once and Will at 10 minutes. [Machine behavior]

Common mistakes

  • Telling the customer a payment before a manager has seen the deal. [Proposed]
  • Writing up the deal and not pressing TO. [Approved: Will ruling 9/30/26]
  • Leaving a note that says "will think about it" with no next step or day. [Proposed]
  • Offering to hold the car or take a deposit. [Approved: Will standing]
  • Saying a unit is at Austin or Buda. [Approved: Will ruling 10/4/26]
  • Quoting a Ford program from memory. [Approved: Will standing]
  • Writing a note on the other store's record. [Approved: Will ruling 10/4/26]
  • Sending a sales question to finance. [Approved: Will ruling 10/6/26]

Manager check

  • Every write-up has a manager and TO pressed. [Approved: Will ruling 9/30/26 for the rule; the check itself is Proposed]
  • Every customer who left has a note with a next step. [Proposed]
  • Every deal with numbers out and no answer past the stalled-deal time has a manager call noted. [Proposed]
  • Every negative-front deal has a reason in the Desk log. [Proposed]
  • Who checks and how often: Unassigned. Will reviews numbers at 11:30 and 5:30 (his stated habit, 10/9); that is not a rule for managers.

Example / checklist / script

Fictional customer, test drove a used truck. Example only, not a script to copy word for word.

Rep to manager (in person): "Customer likes the truck, wants to know the monthly. Has a trade. I wrote it up and pressed TO. Can you desk it?"

Rep to customer: "My manager is running your numbers now. Give me a few minutes."

Note before they leave: "Wants the truck. Needs to show spouse. Coming back [day] at [time] with them. Manager [name] has the numbers. Trade noted."

Manager call if no answer: "This is [manager] at Leif Johnson Ford of Manor. Did you and your spouse get a chance to talk? Does [day and time] still work?"

Checklist:

  1. Write-up done
  2. Manager has it
  3. TO pressed
  4. Numbers desked by the manager
  5. No hold, no deposit, no rate talk
  6. Note with next step and day
  7. Desk stage moved

Open decisions

  1. Approve this SOP (SALES-001) as written, or edit it.
  2. Confirm what the TO button does in our VinSolutions setup, and that "TO on every write-up" means the same thing for used and new.
  3. Must the rep get a manager before the customer leaves the building? Yes or no.
  4. Does the manager always present numbers (desk them), or can a rep present in some cases?
  5. Stalled deal rule: how long after numbers go out before the manager calls, and does the manager always call?
  6. Customer's commitment note: required before the customer leaves, and what must it contain?
  7. Negative-front deals: confirm the manager reason rule, and where it goes (Desk log field, or a VinSolutions note).
  8. Who covers when a pod manager is off? Name the cover for Matt, Oscar and Eric.
  9. Who checks the Manager check list, and how often?
  10. Richard in Oscar's pod: confirm TO goes under Cesar's record.
  11. Showroom page (appointments/showroom.md) says "manager on every shown appointment". Keep that line, or replace it with this SOP?
  12. Confirm the Desk stages (Appointment, Shown, Write-up, Pending, Left) as listed on the draft showroom page.
Draft, Will to confirm

Ten minutes, then the desk (the ten minutes and the desk debrief)

Owner: Will

Ask TPCC and Timing. Say every answer back. Pick three cars. At ten minutes, touch the desk with the facts and the cars. You bring the facts and the cars, the desk brings the numbers. That is how we help you and the store close more.

Cheat sheets: Salespeople: the ten minutes (PDF) · Managers: the desk debrief (PDF) · Phone version (image)

Full versions with the wording and the why: salespeople · managers

Nothing here is a form to fill out. The desk is a conversation. The cheat sheets are what to ask.

The ten-minute window

  • 0:00 Meet. Name, what they drove in, what brought them in. "Welcome in, I'm [name]. What brought you in today?"
  • 1:00 Trade. "You're thinking about trading in your current vehicle, is that what you drove in today? About how many miles are on it? Do you owe anything on it? How much do you owe? How did you arrive at that number, was that your last statement, your app, or a payoff quote?" Say it back: "So exactly $[their number]?" Then: "Who's the loan with, and how do you like them?"
  • 4:00 Payment. "What are you paying now on your current vehicle?" Then: "What kind of price range or payment range are you trying to achieve?" Say it back: "So you're at $[current] now, and you're trying to stay at $[their number] a month, no more than $[their number plus $100], is that what I understand?" Their number. Never ours.
  • 6:00 Credit. "On a scale of 1 to 10, with 10 being the best, how would you rate your credit?" 7 or below: "Why a 7 and not a 10?" Then listen. 8 to 10: "Perfect, thank you for making my job easier."
  • 7:00 Timing. "When are you trying to make your buying decision? What are your time constraints?" Say it back: "So basically, when you find the right vehicle at the right price, is that what I understand?"
  • 9:00 To the desk. "Give me two minutes. I'm going to grab my manager so we can pull the right ones for you and get you real numbers."
  • 10:00 At the desk. Customer stays put. Give the debrief. The desk picks the units with you and gets the T.O. going.
At ten minutes you go to the desk no matter where you are in the conversation. Nobody is in trouble for coming to the desk early. You are in trouble for coming late, or for coming with no information.

The units: the desk picks them with you

You bring the information. The desk picks the units: their pick (what they came for, or the closest thing on the ground), one that fits the payment (a trim, a year or a model down, or a certified used one), one step up. You can look units up on your own, but the guidance comes from the desk, and that is what gets the T.O. going.

  • The first unit doesn't work (payment, trade gap, it's not here, wrong color)? Don't argue it. Don't cut the price. "Based on what you told me, I've got two more that fit. Let me show you." Walk to the next one.
  • Switch the car, never the price. The listed price is the best price on every car we have.
  • You don't quote a payment on any of them. The desk pencils the one that fits.

Come to the desk now if

  • They like a car after the walkaround or the drive.
  • They ask price, payment, best deal or incentives.
  • They say today or this week.
  • They ask trade value or payoff, or want numbers.
  • An objection shows up: price, payment, trade, availability.
  • They are about to leave or say "we'll think about it."

The debrief at the desk

"[Manager], this is [customer]. They're here for the [vehicle]. Must-have is [one or two]. Trade [yes or no], about [miles] miles, owes about $[number] with [lender], from their [statement, app or payoff quote]. Paying $[current] now, wants to stay at $[their number], no more than $[plus $100], [money down]. Credit a [1 to 10], [why], okay with a credit check. Timing: [what they said to right vehicle, right price]. They drove [what] and like [what]. Main hold-up is [price, payment, trade or decision maker]."

Then the desk picks the units, runs the app, pencils the first one, and comes out to meet the customer.

Do not

  • Wait until they are leaving.
  • Bring a manager in cold with no facts and no cars.
  • Blame anyone. Never "my manager won't let me."
  • Debate numbers alone. The desk owns the trade and payment talk.

After the desk steps in

  • Stay with the customer. Back the manager up.
  • VinSolutions note: trade, current payment, timeline, the three cars, outcome, next step with a date and time.
  • Set the follow-up task before they leave.

Never

  • A payment, rate, program or discount from a rep.
  • Tying a credit number to a rate or an approval.
  • A hold or a deposit.
  • A second price number or "the price will move."
  • A trade value without seeing it. Say "without seeing it, I'd just be guessing."
  • Austin or Buda by name.
  • A Social Security number, license image, insurance card or card number by text or email.

Nothing on this page goes to a customer.

Draft, Will to confirm

Delivery

Owner: Will
Draft. Will to confirm each step.

A delivery is not done when the customer drives off. It is done when the four follow-through items are closed:

  1. DDT (Ford Delivery Day Tool)
  2. Survey (New) / Google review (Used)
  3. Manager CSI call
  4. Sales-to-service intro

Also at delivery: connected services activation and, if there was a trade, the trade-in keys.

The open items for every delivery are tracked on the Deliveries board and the TV board.

Draft, Will to confirm

DDT

Owner: Will
Video coming: Doing the DDT step on a new delivery
Draft. Will to confirm who does it and by when.

DDT is Ford's Delivery Day Tool. Every new Ford delivery needs it done.

  1. Finish the DDT step for the VIN on delivery day.
  2. Mark DDT done (Y) on the delivery tracker.
  3. Anything still open shows on the TV board, so check it before you leave for the day.
Draft, Will to confirm

Survey / Google review

Owner: Will
Draft. Will to confirm.

New cars get the Ford survey. Used cars, we just ask for a Google review.

New

  1. At delivery, tell the customer a short Ford survey is coming by email or text.
  2. Ask them to call us first if anything is not right, so we can fix it.
  3. When the survey is confirmed complete, mark it Y on the delivery tracker (Survey returned).

Used

  1. At delivery, ask the customer for a Google review.
  2. Mark it Y in the Tracker's Google review asked column (L). You are marking that you asked, not that they posted.

Do not coach scores. Ask for honest feedback and fix real problems.

The emails follow the same split: a New unit's open items are DDT and the manager call, a Used unit's are the Google ask and the manager call. A Used unit never gets a DDT or survey item.

Draft, Will to confirm

Manager CSI call

Owner: Will
Draft. Will to confirm.

The manager owns the after-sale call, not the salesperson. The call goes out within 48 hours of delivery, before the survey lands.

Who calls

By pod: Matt's pod, Oscar's pod, Eric's pod. Will and Gary cover.

Why 48 hours

Ford's OneCX sales survey goes out by email or text within a few days of the delivery being reported to Ford (typically 2 to 5 days, confirm with Ford). A call in the first 48 hours gets there first. If something is wrong, we fix it before the customer writes it on a survey.

The call

  1. Thank them for buying from us.
  2. "Did everything get explained to you?"
  3. "Is there anything that would keep you from giving us a top score? Tell me now and I will fix it."
  4. Fix whatever they say before the survey arrives.

Listen and fix. Never tell them what score to give. See Survey.

Log it on the Tracker sheet

  • Mgr Call (who): your name
  • Date: date of the call
  • Result: Spoke, Voicemail or No answer
  • Expects good survey?: Y, N or ?
  • Note: what they said, what you are fixing

The rule

A No or a ? gets a same-day call from Will or Gary.

Where it is tracked

The Tracker sheet is the only log. The Deliveries board mirrors it by pod, and the nightly email shows what is missing. If it is not on the sheet, it did not happen.

Will to confirm

  • Typical survey timing from Ford: 2 to 5 days.
  • Do used deliveries get the call too? Used cars do not get the Ford survey (we ask for a Google review instead), but the customer still bought from us.
  • Question 3 mentions a "top score". The Survey page says do not coach scores, and Ford can penalize that. Keep the question, or reword it as "is there anything we could have done better?"
  • The Mgr Call columns are not on the Tracker sheet yet, so the Deliveries board and the nightly email cannot show them until they are added.
Draft, Will to confirm

Sales-to-service intro

Owner: Will
Video coming: Walking a customer to meet their service advisor
Draft. Will to confirm.

A customer who has met service comes back. The handoff happens at delivery, before they drive off.

  1. Walk them over. The salesperson walks the customer to the service drive. Do not point. Walk.
  2. Introduce by name. "This is [advisor name]. [He/She] will take care of you after the sale."
  3. Advisor books the first service. The advisor puts the first visit on the calendar right there. If the customer would rather do it themselves, the advisor shows them how to schedule in the FordPass app.
  4. Set expectations. Tell them roughly when the first oil change is due. For pickup, drop-off and loaner questions, say "ask your advisor" and let the advisor answer. Do not promise a loaner.
  5. Give them the advisor's name and number. Save it in their phone before they leave.
  6. Log it. On the Tracker sheet, in the "Service intro (who/date)" column.

What gets logged

  • Service intro (who/date): the advisor's first name and the date, like Sam 10/7.
  • Not done: write why in the notes (customer in a hurry, advisor out). Do not leave it blank.

The "Service intro (who/date)" column is not on the Tracker sheet yet. Will to confirm adding it.

20-second script

"Before you go, I want you to meet [advisor name]. [Advisor name], this is [customer first name], just picked up the [vehicle]. Can you get their first service on the calendar? [Customer first name], when you need anything after today, [advisor name] is your person. Your first oil change will come up around [timing the advisor gives]. Any questions about pickup or a loaner, [advisor name] will go through it with you."

Will to confirm

  • Who is on the advisor rotation for introductions, and what hours?
  • What the first oil change timing is (it depends on the vehicle).
  • The pickup and loaner policy. Until then the answer is "ask your advisor."
Draft, Will to confirm

Trade-in keys: 8 steps

Owner: Will
Video coming: Trade-in keys: tag it, log it, box it
Draft. Will to confirm. Open questions at the bottom.

Every key from the trade goes in the box, tagged with the stock number, and the folder says who took it in. Here is the order.

  1. Stock it in the moment you take it. The salesperson who takes the trade stocks it in VinCue the same day and gets the stock number. Do not wait for the deal to finish.
  2. Use the stock number rule. The number is what ties the car, the keys and the folder together, so get it right. See "How our stock numbers look" below. If you are not sure, ask the used car manager. Do not make one up.
  3. Tag every key and fob. Write the stock number on the key tag, plus the count (example: "2 keys + 1 fob"). Every key from the trade, all of them.
  4. Run and print the CARFAX. It is free in VinCue. Print it and put it in the deal folder with the title, the odometer statement and the appraisal.
  5. Write on the folder. Who took the trade in, the date, which customer (last name only), the mileage and the key count. Then check that everything is in the folder: CARFAX, title, odometer statement, appraisal.
  6. Keys go in the key box. In the slot for that stock number, before the end of the day. Whoever tagged the keys boxes them.
  7. Log it on the Tracker sheet. "Trade keys" column: the date the keys went in the box and your initials.
  8. Weekly check. Once a week the used car manager matches the Tracker sheet "Trade keys" column to what is actually in the box. Every stocked-in trade has its keys in the box.

How our stock numbers look

Pattern as seen in VinCue (Manor used lot, 58 units on 10/7/26). This is what the data shows, not a written company rule yet.

  • 3 letters + 5 digits + A (TKE45428A): Ford-style stock number, with an A when the car is stocked in again as a used unit. The most common look for a trade.
  • 6 or 7 digits + R or RA (6200587RA, 924758R): R is the Manor store letter (Manor was Riata). An extra A means stocked a second time.
  • digits + T or TA (924680TA, 5607448TA): T is the Buda store letter (Buda was Truck City). TA on our lot is a car that came over from Buda.
  • C + 6 digits (C924714): Austin style number, mostly seen on Austin's lot.

What the data does NOT show: the digits are not the last digits of the VIN. We checked, and only 5 of 27 Manor numbers matched the VIN. Do not build a stock number from the VIN.

Will to confirm: the exact rule for each part (what the three letters stand for, when the A is added, what 924### means, what the C means), and who hands out the number when a trade is stocked in.

If a key is missing

  • At the appraisal (count is short): tell the customer right then, write it on the appraisal, and tell the sales manager before the deal is written.
  • After stock-in (key not in the box): check the Tracker sheet for the last initials, then the appraiser's desk, service, detail and the car itself. Tell the used car manager the same day.
  • Write MISSING and the date in the "Trade keys" column. Do not order a replacement without a manager's OK.

Open questions for Will

  • Is the stock number rule above right, and who owns it?
  • Who holds the key to the key box?
  • Is weekly the right check, and is the used car manager the owner?
  • Do we always make and print the CARFAX on a trade, or only on ones we keep?
  • The "Trade keys" column is not on the Tracker sheet yet. Add it?
Draft, Will to confirm

KEYS-001 Used-vehicle key control (sticker, register, keybox, check-out, return)

Owner: Will
Draft. Nothing here is a rule until Will approves it. Tags show what is enforceable: [Approved: Will ruling <date>], [Machine behavior], [Proposed]. Lines marked "Will's stated workflow" are what Will described on 10/9 and are still waiting on his sign-off.

KEYS-001 Used-vehicle key control (sticker, register, keybox, check-out, return)

Identification

  • ID: KEYS-001
  • Status: Draft - Needs Approval
  • Roles: whoever takes the key in; used car manager (person Unassigned); whoever checks the key out for inspection or other work; sales manager (missing key at appraisal)
  • Owner: Will
  • Approver: Will Robbins
  • Version: 1.0
  • Effective: Proposed
  • Source: Will's stated key workflow 10/9/26 (chat); existing draft pages trade-in-keys/index.md and trade-in-keys/process.md (10/7 draft); Will ruling 10/7/26 (store hours); Will ruling 10/4/26 (never name Austin or Buda to a customer)

When to use

  • Any used-vehicle key that comes into the building: trade-in, purchase, auction, anything we will inspect or sell. [Proposed]
  • The purpose: always know who has the key, so nobody wonders who received it. [Proposed: Will's stated workflow]

What you need

  • A stock number from VinCue for the vehicle. Never make one up and never build it from the VIN. [Proposed]
  • Stock-number stickers. [Proposed: Will's stated workflow]
  • Access to the key-management system. Name of the system: Will to confirm. [Proposed]
  • Access to the keybox. Who holds its key: Will to confirm. [Proposed]
  • For trades: the deal folder, key tags, a printer for the CARFAX. [Proposed]

How our stock numbers look (data, not a rule)

Seen in VinCue, Manor used lot, 58 units on 10/7/26. This is what the data shows, not a written company rule.

  • 3 letters + 5 digits + A (example TKE45428A): Ford-style number, A added when stocked in again as a used unit. Most common look for a trade.
  • 6 or 7 digits + R or RA (examples 6200587RA, 924758R): R is the Manor store letter (Manor was Riata). Extra A = stocked a second time.
  • digits + T or TA (examples 924680TA, 5607448TA): T is the Buda store letter (Buda was Truck City). TA on our lot = a car that came over from Buda.
  • C + 6 digits (example C924714): Austin style number, mostly on Austin's lot.
  • The digits are NOT the last digits of the VIN (only 5 of 27 Manor numbers matched). Do not build a stock number from the VIN.

Steps

A. Will's stated workflow (10/9) - every used-vehicle key

  1. Key comes in. Put a stock-number sticker on it. [Proposed: Will's stated workflow]
  2. Register the key in the key-management system. Who registers: Unassigned. [Proposed: Will's stated workflow]
  3. Put the key in the keybox. [Proposed: Will's stated workflow]
  4. When the key is needed for the used-car inspection or other work, check it out so the system shows who has it. [Proposed: Will's stated workflow]
  5. When that work is finished, return the key to the keybox and record the return. [Proposed: Will's stated workflow]

B. Trade-in keys: the 8 steps from the existing draft (nothing dropped)

Do A1 to A3 for every trade key too. These are the added trade-in steps. Original step numbers in brackets.

  1. [1] Stock the trade in VinCue the day you take it in. The salesperson who took it stocks it and gets the stock number. Do not wait for the deal to finish. [Proposed]
  2. [2] Use the stock number rule (see "How our stock numbers look"). The number ties the car, the keys and the folder together. Not sure? Ask the used car manager. [Proposed]
  3. [3] Tag every key and fob: stock number plus the count (example: "2 keys + 1 fob"). Every key from the trade, all of them. [Proposed]
  4. [4] Run and print the CARFAX (free in VinCue). Put it in the deal folder with the title, odometer statement and appraisal. Where this step sits in the order: see Open decisions. [Proposed]
  5. [5] Write on the folder: who took the trade in, date, customer last name only, mileage, key count. Then check the folder holds CARFAX, title, odometer statement, appraisal. [Proposed]
  6. [6] Keys go in the keybox slot for that stock number before the end of the day. Whoever tagged the keys boxes them. This is A3. [Proposed]
  7. [7] Log it on the Tracker sheet, "Trade keys" column: date the keys went in the box and your initials. [Proposed]
  8. [8] Weekly check: the used car manager matches the Tracker "Trade keys" column to what is in the box. Every stocked-in trade has its keys in the box. [Proposed]

C. Suggested improvements (Claude's suggestions, NOT Will's - all Proposed)

  1. One record, not two. If the key-management system and the Tracker "Trade keys" column both exist, pick one as the record and drop the other. [Proposed]
  2. Name one person who registers keys, and one backup. [Proposed]
  3. Used car manager looks at the "checked out" list at close and asks about any key still out. [Proposed]
  4. A key checked out overnight gets asked about the next morning. [Proposed]
  5. Weekly check (B8) also compares the system's "in keybox" list to the box. [Proposed]

Where it is recorded

  • Key location and who has it: key-management system (name Unassigned). [Proposed: Will's stated workflow]
  • Stock number: VinCue. [Proposed]
  • Trade paperwork and key count: the deal folder. [Proposed]
  • Trade key date and initials: Tracker sheet "Trade keys" column. The column is not on the sheet yet. [Proposed]
  • The machine does not track keys. No automation reads or writes key records. [Machine behavior: none is listed for keys]

Handoff

  • Key in keybox: the used car manager is the contact for the box (named owner Unassigned). [Proposed]
  • Key checked out: the person doing the inspection or other work holds it until it is returned. [Proposed: Will's stated workflow]
  • Missing key at appraisal: the sales manager before the deal is written. [Proposed]

Done when

  • Every key has a sticker or tag with the stock number. [Proposed]
  • Every key shows in the system as in the box or checked out to a named person. [Proposed: Will's stated workflow]
  • Every key that is not checked out is in the keybox. [Proposed]
  • Trades also: stocked in, CARFAX printed, folder written up, Tracker logged. [Proposed]

Timing (only approved timing, else "Proposed")

  • Store hours: close 8pm Mon-Thu, 7pm Fri-Sat, closed Sunday. [Approved: Will ruling 10/7/26]
  • Stock the trade in VinCue the same day. [Proposed]
  • Keys in the box before the end of the day. "End of day" has no approved time yet; the closing times above are the only approved hours. [Proposed]
  • Check out and return: no time limit set. [Proposed]
  • Weekly check, once a week. Day: Unassigned. [Proposed]

Exceptions

  • Missing key at the appraisal (count is short): tell the customer right then, write it on the appraisal, tell the sales manager before the deal is written. [Proposed]
  • Missing key after stock-in (not in the box): check the Tracker sheet for the last initials, then the appraiser's desk, service, detail, and the car itself. Tell the used car manager the same day. [Proposed]
  • Write MISSING and the date in the "Trade keys" column. Do not order a replacement without a manager's OK. [Proposed]
  • Key for another store's unit: no procedure yet (see Open decisions). [Proposed]
  • If a customer asks about another store's unit, never say it is at Austin or Buda; say "our group." [Approved: Will ruling 10/4/26]
  • Exceptions to this process (key cannot go in the box, key leaves the building): how they are recorded is Unassigned. [Proposed]

Escalation

  • Missing key: used car manager the same day. [Proposed]
  • Used car manager out: Unassigned.
  • Key still missing after the manager's search: Will. [Proposed]

Common mistakes

  • Keys in a pocket or on a desk, not in the box. [Proposed]
  • Taking a key out and not recording it, so nobody knows who has it. [Proposed]
  • Returning the key to the box without recording the return. [Proposed]
  • Tagging the key but not the fob, or not writing the count. [Proposed]
  • Making up a stock number or building it from the VIN. [Proposed]
  • Waiting for the deal to finish before stocking in the trade. [Proposed]

Manager check

  • Weekly: used car manager matches the Tracker "Trade keys" column to what is in the box. [Proposed]
  • Any key checked out and not returned gets asked about. How often: Unassigned. [Proposed]
  • Missing-key reports are read by Will. Frequency: Unassigned. [Proposed]

Example / checklist / script

Fictional example. A customer trades in a used Escape.

  1. The salesperson stocks it in VinCue today and gets the stock number.
  2. Puts the sticker on the key and the fob, writes "1 key + 1 fob" on the tag.
  3. Registers both in the key-management system.
  4. Prints the CARFAX, puts it in the folder with the title, odometer statement and appraisal. Writes on the folder: name, date, customer last name, mileage, "1 key + 1 fob".
  5. Puts the keys in the keybox slot for that stock number before close.
  6. Logs the date and initials in the Tracker "Trade keys" column.
  7. Next day the inspection starts. The technician checks the key out in the system. When the work is done, it goes back in the box and the return is recorded.

Short check before you leave the key: sticker on, registered, in the box or checked out to a name.

Open decisions

  1. Who registers the key in the key-management system? (Unassigned.)
  2. How are exceptions recorded (key cannot go in the box, key leaves the building)?
  3. Missing-key procedure: is the draft procedure above right, and who orders a replacement and who approves it?
  4. Keys for another store's unit: who registers them, where do they live, who is the contact?
  5. Stock-number rule: what the three letters stand for, when the A is added, what 924### means, what the C means, and who hands out the number at stock-in.
  6. CARFAX print step: keep it inside this process for trades, or move it to the appraisal/inspection step, and do we print one on every used unit or only ones we keep?
  7. What is the key-management system called, and does it replace the Tracker "Trade keys" column? (If yes, drop B7. If no, add the column to the Tracker.)
  8. Sticker or key tag: does Will's stock-number sticker replace the tag with the count?
  9. Who holds the key to the keybox?
  10. Weekly check: is weekly right, and is the used car manager the owner?
  11. Does this cover all used keys (purchases, auction) or trade-ins only?
Draft, Will to confirm

Buyers Guide on every used car

Owner: Will
Draft. Will to confirm who owns this step.

Every used car offered for sale needs a Buyers Guide hanging in a side window. It is a federal rule (FTC Used Car Rule). A car on the lot without one is a fine waiting to happen.

When: the day the car is front-line ready, before it goes on the lot or online.

Printable 2-page version: Buyers Guide how-to (PDF)

How (2 minutes, in VinCue):

  1. Type the stock number in the VinCue search bar, click Open Vehicle.
  2. Click the Stickers tab. Buyers Guides opens first.
  3. Click + SYSTEM.
  4. Click As Is - Front/Back.
  5. Check the year, make, model, VIN and stock number match the car, and that AS IS is checked.
  6. Click the printer icon and print both pages.
  7. Hang it in a side window.

Rules:

  • Never click New Preset. It makes a new template for the whole store.
  • Certified (Blue Advantage) cars carry a warranty, so As Is is the wrong box. Ask a manager which guide to print.
  • New cars do not get a Buyers Guide. They have the Ford window sticker.
  • Nothing saves in VinCue. Lost or faded guide? Print it again.
Draft, Will to confirm

FordPass activation at delivery

Owner: Will
Video coming: Connected services / FordPass activation at delivery
Draft, from Ford's standard activation steps. Verify against Ford's current delivery checklist before confirming.
  • ☐ Before the customer arrives: confirm the vehicle has the connected modem and the VIN on the deal is the VIN on the car.
  • ☐ Install the app: the customer downloads FordPass (the Ford app) from the App Store or Google Play and signs in, or creates a Ford account on the spot.
  • ☐ Add the vehicle: in the app, add the vehicle by VIN (typing it or scanning it) and pick "I own this vehicle".
  • ☐ Consent: the customer reads and accepts the terms and the connected services data consent themselves. We never tap it for them. If they decline, note it and move on.
  • ☐ Activate the modem: vehicle on, outside with a clear view of the sky, ignition on. Accept any connected services prompt on the SYNC screen. It can take several minutes. Wait for the app to confirm.
  • ☐ Pair the phone: Bluetooth pairing with SYNC. If the vehicle has Phone as a Key, set that up too.
  • ☐ Test one remote command: lock or unlock (or remote start if equipped) from the app while the customer watches.
  • ☐ Explain the plan: tell the customer what is included and when any trial ends. Do not quote prices.
  • ☐ Privacy: tell them they can change location and data sharing in the vehicle's privacy settings at any time.
  • ☐ Log it: mark connected services done on the delivery tracker.

If activation does not finish at delivery, tell a manager and put the reason on the tracker. Do not tell the customer it will definitely work later.

Confirmed

Texting and messaging rules

Owner: Will

The same rules the machine follows. A person texting from their phone follows them too.

  1. No dollar amounts or rates in texts. No payments, no rates, no incentive programs. Rates and programs only when Will has given you this month's number.
  2. No holds, no deposits. We do not hold used vehicles or take deposits on new. Say: "when you're ready, we'll write it up."
  3. Never name another store. Do not tell a customer a unit is at Austin or Buda.
  4. Reply within the hour. A customer who texted you is waiting.
  5. Log every call on the profile.

More: voice and timing, read the notes first.

Confirmed

Voice and timing

Owner: Will
  • Short and flat, like you typed it on your phone. No dashes, no "truly", no drama.
  • Name the store as Leif Johnson Ford of Manor.
  • No marketing texts before 8:30am or after 9pm. On Sunday, not before noon.
  • New groups of leads go out 25 a day, never a flood.
  • If a customer says stop, wrong number, or not interested in their own words, stop. Do not text again.
Confirmed

Read the notes first

Owner: Will
  • Read the full profile, notes and history before you write anything.
  • Lost with a reason is dead. Lost because they went quiet is fair game.
  • If a manager or another rep touched the thread in the last 4 hours, leave it alone.
  • If the customer is in a live deal (appointment today or tomorrow, in the showroom), the machine stays out and you run it.
  • If you cannot tell whether a unit is still here, check Inventory Finder. Do not guess.
Confirmed

Tools we use

Owner: Will

Dashboard address (store network): http://100.116.91.37:3000

How the machine works for the store, in plain English: the day at a glance, new-lead texter, auto-responder, follow-up engine, approvals, desk-send, inventory truth, what it can write, AutoFi, if something looks wrong.

Also: daily VIN walkaround script.

Confirmed

Reply Desk

Owner: Will

Address: /replies

Every customer reply from the last 7 days, what the machine did with it, and the next best step.

  • Easy answers are sent on their own. Anything about money, credit, anger or a deal in motion is held for a person.
  • Check it first thing and after lunch. Answer anything waiting on you inside the hour.
Confirmed

TV board

Owner: Will

Address: /tv

The showroom wall screen: month-to-date sold and the delivery follow-through items still open (DDT, survey). It refreshes itself every minute. Nothing to click.

Confirmed

Team Scoreboard

Owner: Will

Address: /teams

The pod standings and team numbers. Use it in the huddle to see where each team stands.

Confirmed

Inventory Finder

Owner: Will

Address: http://100.116.91.37:8787

Ask for a vehicle the way you would ask a person: "crew cab diesel under 60k". You get live matching units with stock number, VIN, price, miles and a link you can send the customer.

Check it before you tell any customer a car is here or gone.

Confirmed

Desk

Owner: Will

Address: /desk

Everyone in play today, by stage: Appointment, Shown, Write-up, Pending, Working, Credit app, Sold, Left.

  • Tap a stage to move a customer.
  • "Up" logs a walk-in.
  • Tapping Left starts a save-a-deal follow-up that evening.
Confirmed

Lease Calculator

Owner: Will

Address: /lease

Type a stock number and it fills the unit and MSRP. Add selling price, money down, trade and rate. You get the payment, cash due, and a grid by term and miles. Residuals come from the current Ford Credit quarterly table.

Confirmed

Daily VIN walkaround script

Owner: Will
Video coming: Shooting the daily VIN walkaround

A daily ~60 second walkaround video of one desirable unit, shot by a salesperson. The machine drafts the script; a person says it in their own words.

Format, in order:

  1. Hook (first 3 seconds): the one thing that makes people stop.
  2. Three or four feature beats: what you can see and touch on this exact car.
  3. Value: the history report, price, and how we do it here.
  4. Call to action: "ask for me."

Rules: stand at the car and read the window sticker on camera. Check the powertrain, range and history report before you post. Never say an option or history item you did not see.

Confirmed

The day at a glance

Owner: Will

All of this runs on its own. Times are Central.

  • Overnight: new leads get an email right away and a text on the first run after 8:30am.
  • 6:05am: lead extract from the CRM. 6:30am: inventory refresh for all three stores.
  • 8:05am: the Manor Morning email (new leads, top ten, live deals).
  • 8:30am: day-of appointment reminders.
  • 8:30am: texting window opens (Sunday from noon).
  • Daytime: new-lead texter every 2 minutes, follow-up engine hourly, replies watched all day.
  • 5pm: day-before appointment confirmations.
  • 6pm: rep digest of unanswered replies and tomorrow's appointments.
Confirmed

New-lead texter

Owner: Will

Sends the first message to a brand-new lead as soon as it lands, so nobody waits. It reads the profile and notes first and signs as the assigned rep.

It never sends to sold, lost, opted-out or do-not-contact leads. Texts go out 8:30am to 8pm only.

You still call. See call inside the hour.

Confirmed

Auto-responder

Owner: Will

Answers customers who text or email back.

  • Easy questions ("is it still available?") are answered on their own.
  • Money, credit, legal, anger, and anything tagged for a human are held for a person.
  • If you or a rep touched the thread in the last 4 hours, it holds and lets the person run it.
  • It never quotes a price or rate and never offers to hold a vehicle.
Confirmed

Follow-up engine

Owner: Will

Keeps touching leads who have not bought and have not gone dead, on a slow rotation of texts and emails.

It steps aside for new leads and for anyone in a live deal: an appointment today or tomorrow, a showroom visit, or any message in the last 4 hours. No machine text lands in the middle of a negotiation.

Confirmed

Approvals

Owner: Will

Held drafts wait on Home and on Replies. Each shows the message, who it is to, and an Approve button.

  • Approve to send it as written, or open the customer and send your own words. Never both, that double-sends.
  • Opening an approval link only shows a confirm page. Nothing happens until you press the button on it.
  • If the customer was answered another way, the draft shows as superseded and will not send.
Confirmed

Working one customer (desk-send)

Owner: Will

Works one customer start to finish: read everything, draft one message in your voice, send it only when you say so.

Every send runs the guards: inventory, pricing posture, no holds, no rates, pacing. The machine will not override a do-not-contact note. It opens the customer so you send it yourself.

Confirmed

Inventory truth

Owner: Will

A daily honest list of what is for sale at Manor, Austin and Buda.

  • Anything On Hold, Wholesale, Sold, or missing a status counts as not available everywhere: texts, Facebook, the glasses.
  • Unknown means not available. The system never guesses "probably fine".
  • Facebook Marketplace posting rotates the three stores. "Throttled" means Facebook slowed us down, not that anything broke.
Confirmed

What the machine can write in the CRM

Owner: Will

The CRM is read-only for the machine except:

  • A short note after every send: Status, Sent, Next.
  • Mark Lost, only when the customer said they are done, or a manager says to close it.
  • Reassigning leads from a rep who has left.
  • Filling a blank County field with Travis.

It never edits a deal, a price, or a status beyond Lost.

Confirmed

INV-001 Check the unit before you promise it: availability, location, store ownership, trade info

Owner: Will

INV-001 Check the unit before you promise it

Identification

  • ID: INV-001
  • Status: Approved by Will Robbins 10/29/26 as written
  • Roles: Salesperson, pod manager, used car manager (Eric French desks used), Will
  • Owner: Will
  • Approver: Will Robbins
  • Version: 1.0
  • Effective: 2026-10-29
  • Source: Will ruling 10/4/26 (Manor record only, say "our group"); Will standing rulings (inventory availability, no holds or deposits, no rates or programs unless current month given, best price up front); existing pages tools/inventory-finder (confirmed), tools/inventory-truth (confirmed), tools/auto-responder (confirmed), texting-rules/index (confirmed), trade-in-keys/process (draft); machine behavior as of 10/9/26
  • Tags used below: [Approved: ...] = Will ruling or confirmed page, enforceable now. [Machine behavior] = what the automation does today. [Proposed] = suggestion, not a rule until Will approves.

When to use

  • A customer asks if a car is here, available, or where it is.
  • You are about to tell a customer a car is here, sold, or gone.
  • A customer from another group store is being worked from Manor.
  • A customer has a trade, or you are about to ask for trade info.

What you need

  • Inventory Finder (the live search page the Mini serves). [Approved: existing page tools/inventory-finder, confirmed]
  • VinSolutions (CRM) record for the customer. Manor record only.
  • VinCue status for the unit (a VinCue status of sold is one of the two things that can call a unit gone). [Approved: Will ruling, standing, inventory availability]
  • For trades: the info list in Step 9.

Steps

  1. Look the unit up in Inventory Finder in plain words (or stock number) before you answer anyone. [Approved: existing page tools/inventory-finder, confirmed]
  2. Found and listed as for sale: you can say it is here. Check VinCue status once more before an appointment is set. [Proposed]
  3. Not found or cannot be matched: it is "unverified". Never say "gone" or "sold". [Approved: Will ruling, standing, inventory availability] Suggested wording: "let me confirm that for you." [Proposed]
  4. Only a VinSolutions sold flag or a VinCue status of sold may be called gone. [Approved: Will ruling, standing, inventory availability]
  5. Status On Hold, Wholesale, Sold, or no status counts as not available in texts and posts. [Machine behavior; existing page tools/inventory-truth, confirmed]
  6. Before you promise a car for a set time, also check: photos ready, keybox/key location, recon status (is it still in prep?). [Proposed]
  7. Unit is at a sister store (Austin or Buda): never name the store to the customer. Say "our group." [Approved: Will ruling 10/4/26]
  8. Working a customer who shopped another store: write notes and activity ONLY on the Manor record. Read the other store through Customer Search; do not switch stores. [Approved: Will ruling 10/4/26, cross-store rule]
  9. Trade-in: collect year, make, model, trim, miles, VIN, condition (good or problems), photos (front, back, both sides, interior, odometer, dash lights), and loan payoff if any. Write it on the Manor record. [Proposed]
  10. Send the trade info to the appraiser. Appraiser: Unassigned. [Proposed]
  11. Print CARFAX for every unit being evaluated, trade or purchase. [Proposed: the keys process that says this is still Draft, Will to confirm]
  12. Never offer to hold a unit and never take a deposit to hold one. [Approved: Will ruling, standing; existing page texting-rules/index, confirmed]
  13. Never quote a rate, payment or Ford program unless Will gave this month's. Price: give the best price up front, never imply negotiation. Before answering a price complaint, check AutoFi. [Approved: Will ruling, standing]
  14. Customer pushes for a hold, a payment, an exact trade number, or a car you cannot verify: bring in your pod manager. [Proposed]

Where it is recorded

  • Customer contact, what you promised, next step: short note on the Manor record in VinSolutions, written on the Manor record only. [Approved: Will ruling 10/4/26 for Manor-only writes; note wording and timing Proposed]
  • Trade info: note on the Manor record, photos attached to the note or the trade folder. [Proposed]
  • Unit status: VinCue. Keep no separate list of your own. [Proposed]

Handoff

  • Unit is at a sister store or in recon: pod manager decides how to bring it or when it will be ready. [Proposed]
  • Trade info: appraiser (Unassigned) via the pod manager. [Proposed]
  • Held machine reply about availability, rates or holds: the pod manager answers it. [Machine behavior]

Done when

  • Customer was told something true: here, or "let me confirm," never a guess. [Approved: Will ruling, standing, inventory availability]
  • The note on the Manor record says what was promised and the next step. [Proposed]
  • Trade (if any): all items in Step 9 are on the record, or the missing ones are listed. [Proposed]

Timing

  • When the customer texted you, reply within the hour. [Approved: existing page texting-rules/index, confirmed]
  • Availability answer for a call, walk-in or email: no time approved. [Proposed]
  • Appraisal turnaround: Proposed. No time is approved. [Proposed]
  • Machine holds on availability it cannot verify, escalates to the pod manager at 2 hours. [Machine behavior]

Exceptions

  • Unit cannot be matched in our data: "unverified," not "gone." [Approved: Will ruling, standing]
  • Customer asks which store has it: "our group has it, I will confirm it for you." Do not name Austin or Buda. [Approved: Will ruling 10/4/26]
  • Customer is at another store's lot or asks about that store: same rule, then hand to your manager. [Proposed]
  • Key not in the keybox: do not promise a time. Tell your manager. [Proposed]

Escalation

  1. Pod manager first. [Proposed]
  2. Used units: Eric French. [Proposed]
  3. Anything on pricing, programs or a possible hold: Will. [Proposed]
  4. Finance managers (Jeff Ledesma, Brian Calderon): not for sales decisions. [Approved: Will ruling 10/2/26, managers roster]

Common mistakes

  • Saying "sorry, it sold" because Inventory Finder showed nothing.
  • Naming Austin or Buda in a text, email or on the phone.
  • Writing notes on the other store's record.
  • Saying "I'll hold it for you" or "we'll put a deposit on it."
  • Quoting a payment, rate or program from memory.
  • Telling a customer a car is ready when photos, recon or the key are not.
  • Giving a trade number before the appraiser has seen the info.

Manager check

  • Spot check some availability answers (how many and how often: Unassigned): was the unit checked, and does the note match? [Proposed]
  • Search recent texts for "Austin" or "Buda": must be zero. [Proposed]
  • Search recent notes for "hold", "deposit", rates: must be zero. [Proposed]
  • Trade requests: every one has all items in Step 9 or a listed gap. [Proposed]

Example / checklist / script

Customer asks: "Is the white Escape still there?"

  1. Look it up in Inventory Finder. Not found.
  2. Say: "Let me confirm that for you." (Not "it's gone.")
  3. Check VinCue and VinSolutions for a sold flag. None found: it stays "unverified," not "gone."
  4. Only if VinCue shows the unit at a group store: "Yes, our group has it. When would you like to come see it?" Do not name the store. Do not offer a day or time until your pod manager confirms when it will be here.
  5. Note on the Manor record: "Asked about white Escape. Unit confirmed in our group. Pod manager to confirm arrival time. Next step: call customer back."

Trade ask: "What year, make, model and trim is it, about how many miles, any problems or warning lights, and do you still owe on it? Send me photos of all four sides, the inside and the odometer, and I will get it looked at."

Open decisions

  1. Who appraises trades (names or role)? Currently Unassigned.
  2. Appraisal turnaround time (same hour, same day)?
  3. Who may confirm a unit is at a sister store and how it is brought to Manor?
  4. Is the keybox check required before any appointment is promised?
  5. Is photos-ready a required step before promising a unit?
  6. Wording for a unit still in recon.
  7. Existing inventory-truth page says "unknown means not available"; this page says "unverified." Keep both, or merge into one rule?
  8. May reps say anything about trade value before the appraiser sees it? Proposed: no.
  9. Retire or cross-link the overlapping pages (tools/inventory-finder, tools/inventory-truth, tools/auto-responder, texting-rules/index).

All videos

Every video in the book, with the page it lives on. Pages marked to record have a placeholder, not a video yet.