Get sharper output from Claude and other agents with these dealership tested techniques. Steal what works, ignore what does not.
Quick tips
πUse "please". It does not change the output, but it makes reviewing prompts nicer.
πSpecify file formats explicitly. Say .xlsx, not just "Excel". Say .docx, not just "Word".
πInclude the timezone when working with dates and times (Central, Eastern, etc.).
πΊοΈAsk Claude to explain its plan before executing complex tasks.
π¬Use quotes for exact text that should be preserved verbatim: "keep this exactly".
πRequest progress updates for long-running tasks.
βοΈ
Prompt Engineering
Write better prompts and you will get better output.
Be specific about output format
β Avoid
Summarize last month's variance.
β Better
Create a one page variance recap as a .docx with: Executive Summary (1 paragraph), Top 5 Misses by Department (bulleted with dollar impact), and Recommended Actions (numbered list). Save as variance_recap_YYYY_MM.docx.
Give context before the request
β Avoid
Fix my CRM export.
β Better
I exported leads from VinSolutions for the last 30 days. Column A is lead source, columns B through F are funnel stages, row 1 is headers. Reformat as a pivot showing conversion rate by source, currency for the dollar columns, and bold headers.
Use numbered steps for multi part work
β Avoid
Clean up the service files.
β Better
Please do the following in order: 1) Create subfolders named Open, Closed, and Warranty. 2) Move ROs from the last 30 days into Open. 3) Move ROs older than 90 days into Closed. 4) Move all warranty PDFs into Warranty. 5) Create an index.txt listing every file with its new location.
Say what NOT to do
β Avoid
Organize the inventory photos.
β Better
Organize the inventory photos by stock number into folders. Do NOT delete any files. Do NOT rename the originals. Do NOT touch any videos, only .jpg and .png images.
β‘
Efficiency Hacks
Work faster by batching, templating, and chaining.
Batch similar tasks into one request
β Avoid
Rename ro_1234.pdf. Now rename ro_1235.pdf. Now rename ro_1236.pdf...
β Better
Rename every .pdf in /ROs/Open using this pattern: RO_[stock]_[customer last name]_[YYYYMMDD].pdf. Read the customer name and date off the first page of each file.
Create reusable templates
β Avoid
Write a follow up to the customer who came in yesterday.
β Better
Create a sales follow up email template with placeholders for [CUSTOMER], [VEHICLE], [TEST DRIVE DATE], [OBJECTION RAISED], [NEXT STEP]. Save as follow_up_template.txt so I can reuse it.
Ask for a dry run before destructive work
β Avoid
Delete all dead leads.
β Better
Find every lead with no activity in 90 days in my CRM export. List them with name, source, and last touch date. Do NOT mark them dead yet. I want to review the list first.
Chain related work with "then"
β Avoid
Download the file... wait... now process it... wait... now report.
β Better
Pull the F&I PRU report from the shared drive for last month, clean any blank rows, calculate PRU by F&I manager, then build a one page chart sorted high to low and save as fi_pru_YYYY_MM.png.
π
File Organization
Keep store files structured and findable.
Establish naming conventions
β Avoid
Save the recap.
β Better
Save using YYYY-MM-DD_Store_DocumentType.ext. Example: 2026-06-01_Westside_VarianceRecap.docx. Use this convention for every file you create going forward.
Ask for an index file
β Avoid
Sort the deal jackets.
β Better
Organize the deal jackets into folders by month and stock number, and create an index.md listing every file with its new path, original path, and a one line description.
Use explicit folder structures
β Avoid
Archive old work.
β Better
Create this structure: /Archive/[Year]/[Department]/[DocumentType]. Move everything not modified in the last 12 months into the right folder. Do not move anything modified this year.
π‘οΈ
Safety and Best Practices
Protect customer data, deal jackets, and your sanity.
Always request a backup first
β Avoid
Rename all the customer photos.
β Better
First, copy /CustomerPhotos to /CustomerPhotos_backup_2026-06-04. Then rename the photos in the original folder. Confirm the backup completed before starting the rename.
Start with limited scope
β Avoid
Process all 1,200 ROs from last quarter.
β Better
Process just the first 10 ROs and show me the output. If it looks right, I will tell you to continue with the rest.
Confirm before sensitive actions
β Avoid
Delete duplicate customer records.
β Better
Find potential duplicates and list them in groups, with name, phone, email, and the date each record was created. Do NOT delete anything until I review the list and tell you which to keep.
Treat PII like cash
β Avoid
Send the lead list to the agent.
β Better
Strip Social Security numbers, dates of birth, and credit scores before processing. Replace each value with [REDACTED] in the working copy and log every redaction. Never send raw PII to a third party tool.
Use specific, full paths
β Avoid
Clean up Downloads.
β Better
Clean up only /Users/sara/Downloads. Do not touch any other Downloads folder. Only process files directly in this folder, not subfolders.
π
Advanced Techniques
Power moves for repeatable dealership workflows.
Combine multiple sources in one workflow
β Avoid
Pull the DMS export.
β Better
Pull the DMS deal log for last month, pull the CRM activity log for the same period, join on deal ID, and produce a one page report showing close rate by source with the top three sources highlighted. Save as monthly_close_rate.xlsx.
Spell out conditional logic
β Avoid
Process the deal files.
β Better
For every deal file: if total gross is below zero, flag it. If F&I product count is zero, flag it. If the deal has more than three CRM touches before close, tag it Long Cycle. Log every flag in a single review_log.csv.
Ask for verification at the end
β Avoid
Move old leads to archive.
β Better
Move leads with no activity in 180 days to /Archive. When done, return: total moved, total kept, any leads that could not be moved and why, and confirmation that the originals are intact.
Document the workflow for next month
β Avoid
Set up monthly composite prep.
β Better
Build my monthly 20 Group composite prep and write a docs/composite_workflow.md explaining: what folders it reads, what files it creates, what formulas it applies, and exactly how to re run it next month with new data.
Prompt cheat sheet
A simple structure that works for nearly any task.
# Context
[Describe the situation. What store, what data, what time period.]
# Task
[What you want done in one sentence.]
# Requirements
- Specific requirement 1
- Specific requirement 2
- Specific requirement 3
# Output
[How you want it delivered. Format, filename, where to save.]