Field Sales Assistant: plan, debrief and prepare by voice
One place for a dealer-facing sales team to plan each visit, record what happened by talking it through, and walk into the next one prepared. Built on the team’s existing CRM, then extended with voice.
- CLIENT
- Finance and insurance products sold through car dealerships
- BUILT ON
- Existing field-sales CRM on AWS, speech-to-text, Claude API
- WORKS IN
- The phone’s browser, nothing to install
Debrief by voice, and ask the assistant
Two parts of the app, running live on sample data. Record a debrief after a dealer visit and see the suggested updates, or switch to the Assistant to ask about your meetings and book one by voice.
Every visit meant filling in a long, manual form
Client type, date, time, dealership, contacts, attendees, five goal dropdowns, notes and materials, all typed by hand on a phone between dealer visits.
- 1Time-consumingTyping up each visit on a phone took time from the next dealer, so entries were delayed or skipped.
- 2Details got lostNotes were written from memory hours later. What the dealer said and what was agreed didn’t make it in.
- 3Goals went staleStatuses were only as current as the last manual update, so nobody could see what was really open.
- 4No meeting summaryThere was no single record of what was covered and what happens next.
- 5Prep was manualBefore a visit, the rep pieced together history, open goals and past promises themselves.
- 6Not built for the roadThe team works between dealerships. A form needs both hands and full attention.
One place to plan, record and prepare
- 1Plan the visitSchedule it in one place instead of Outlook: dealer, date and time, attendees and goals.
- 2Record what happenedAfter the meeting, talk it through. The assistant fills in who was met, the outcome and next steps.
- 3Get the recapThe assistant writes a short summary of what was covered, what was agreed and what happens next.
- 4Walk in preparedBefore the next visit, a brief pulls together open goals and promises, read aloud on the drive in.
The AI only suggests. Every change quotes the words it came from, and nothing is saved until the salesperson confirms.
One debrief, several updates
Back in the car, the salesperson talks through the whole meeting once. The assistant picks out each goal that moved and any follow-up mentioned, and turns them into one-tap updates.
Customer complaints follow-up · Tue 20 Oct, 11:00 AM
Briefs that remember, and booking by voice
Metro Honda · Thu 15 Oct, 2:30–3:30Clash
See who went where, and who is going where
Managers get one calendar of the whole team’s visits with what came out of each one, plus a weekly summary written from the recaps. Visits without a debrief stand out.
9:00 · ✓ Recap
10:00 · ✓ Recap
4:00 · Brief ready
11:00 · Brief ready
10:30 · ✓ Recap
2:00 · No debrief yet
1:30 · ✓ Recap
9:30 · Brief ready
11:00 · ✓ Recap
3:00 · ✓ Recap
2:00 · Brief ready
17 visits, 11 completed and 9 with a recap. Westbrook Ford agreed new payment terms and Metro Honda’s warranty backlog is cleared. Two visits have no debrief yet: Pinecrest Toyota and Sunrise Honda.
Before vs. with the Field Sales Assistant
| Area | Before | With the Field Sales Assistant |
|---|---|---|
| Scheduling | Outlook plus a separate long form | One place to plan the visit: dealer, time, attendees and goals |
| After the visit | Notes typed from memory, later | A voice note straight after, in their own words |
| Goals | Five dropdowns, each updated by hand | AI suggests a status for each goal from what was said; the rep confirms |
| Meeting summary | None | Written automatically and kept with the visit |
| Next-visit prep | Search old entries | A brief from past summaries and open goals, read aloud |
| Managers | Chase the team for updates | A team calendar, weekly AI summary and scorecard |
Core app and summaries first, then voice
The team works between dealerships, on a phone, often in the car, so the record had to come from talking rather than typing. Phase 1 made the existing CRM useful after every visit; Phase 2 added voice, starting with a field test on real visits. Everything runs in the client’s own AWS account, using the Claude API rather than a chat plan, to meet their privacy and financial-regulation requirements.
- Code moved to Git with automated tests and deployment
- Separate test and live environments
- Fixes to existing issues
- Goals and activities aligned to the original visit form
- New prospect flow and conversion to dealer
- Richer appointment details
- A recap of every past meeting
- A brief for the next visit, read aloud
- Manager calendar and weekly insights
- Voice debriefs on every appointment
- Suggested goal updates and follow-ups
- A voice assistant to look up, book and log visits
- Browser recorder saves audio on the phone as it records and uploads to AWS with automatic retries
- Speech-to-text with a custom vocabulary: product terms like F&I and GAP, plus every dealer and contact name in the CRM
- Claude API extracts goal updates and follow-ups against a fixed goal schema, each with its source quote; dates resolved from the day of the recording
- Briefs and summaries are cached and regenerated only when something new is recorded
- Voice booking uses the CRM’s own appointment flow, with clash and past-date checks and a separate spoken “yes”
- Separate test and live environments, automated deployment, and an audit trail of recordings and confirmations