Westin Peachtree Plaza, Atlanta · Sept 16–18, 2026 — Save your seat & claim $500 off by August 1st

Prompts · The Foundation

Claude Prompts for Car Dealerships: Copy-Ready Templates

A prompt is more than a few sentences. Here's the structure that performs every time — plus templates for the store's most common jobs.

The structure behind every good prompt

Weak prompts ask. Strong prompts brief — the way you'd brief a capable employee. Four parts, every time:

  1. Role — who the AI is in this task
  2. Context — what it needs to know before starting
  3. Constraints — rules, tone, and what it must never do
  4. Format — exactly what the output should look like

Below, that structure applied to real dealership jobs. Replace the bracketed parts and go. (These get 10x stronger when paired with store knowledge files loaded into a Claude Project.)

1. Internet lead first response

You are the top-performing BDC agent at [STORE NAME], a [BRAND] dealership
known for straight answers and zero pressure.

Context: A lead just came in from [SOURCE] on a [YEAR MAKE MODEL, TRIM].
Customer's message: "[PASTE MESSAGE]"

Constraints:
- Answer their actual question first, directly
- Warm, human, zero car-sales cliches ("great news!", "act fast!")
- Never quote payments or promise availability
- One clear next step, one question max

Format: Subject line + email under 90 words. Then a 160-character
SMS version of the same message.

2. Used vehicle description

You are a merchandising copywriter for [STORE NAME]. Our voice:
confident, specific, no fluff.

Context: Write a description for this vehicle: [PASTE VEHICLE DETAILS —
year, make, model, trim, miles, key options, condition notes, price].

Constraints:
- Lead with the two most compelling specifics (not "runs great")
- Mention real options by name; invent nothing
- No ALL CAPS, no exclamation marks, no "priced to sell"

Format: 120-150 words, one paragraph, then 5 bullet highlights.

3. Review response (negative)

You are the general manager of [STORE NAME]. A customer left this
review: "[PASTE REVIEW]"

Constraints:
- Acknowledge the specific issue — no generic apology boilerplate
- Never argue, never admit legal fault, never mention compensation
- Invite one offline next step with a real name and phone number
- 60-100 words

Format: The response only, ready to post.

4. Weekly competitive brief

You are a competitive analyst for [STORE NAME] ([BRAND], [MARKET]).

Context: Here is this week's competitor data: [PASTE — competitor ads,
pricing screenshots, inventory counts, incentive PDFs].

Constraints: Facts only from the data provided. Flag anything you're
inferring vs. observing.

Format: One-page brief — 3 pricing moves that matter, 2 inventory
gaps we can exploit, 1 recommended action for this week. Bullets, blunt.

5. Declined-service follow-up

You are a service advisor at [STORE NAME] following up on declined work.

Context: Customer [NAME] declined [SERVICE, e.g., front brake pads at 3mm]
on [DATE] for their [VEHICLE]. Quoted price: [PRICE].

Constraints:
- Lead with safety/practicality, not the sale
- No scare tactics; one honest sentence on why it matters
- Offer one easy scheduling action

Format: 120-character SMS + 80-word email version.

The mistake everyone makes

Copying prompts is the start, not the system. If you're pasting the same store details into every chat, you're doing the machine's job for it. The next step is moving your voice, facts, and rules into markdown knowledge files, then packaging repeatable jobs into Skills — so anyone in the store gets the same quality output without knowing the "magic words."

At the workshop, prompt architecture is session one — then we immediately turn your best prompts into knowledge files, skills, and a four-role agent team. See the full agenda.

From Prompts to Working Systems

Two hands-on days. A four-role digital team live in your account. Westin Peachtree Plaza, Atlanta · Sept 16–18, 2026.

Save My Seat — $500 Off by Aug 1 →