job: lead-follow-up · weeknights

Automate car dealership lead follow-up

Tell dassi which leads to work and what to say. It opens each one in the CRM you're signed into, reads the history, sends the email from your login, and sets the status the way your store does it. Leads that have opted out, already bought, or asked about price come back to you untouched.

Give dassi this job

Free credits, good for 7 days — no card required

Trusted by 30,000+ Chrome users Rated 4.8/5 on Chrome Web Store Works with Claude, GPT, Gemini, and more

One run, start to finish

Every dassi job has the same shape: an input, work done on real pages and accounts, output you can verify, and exceptions flagged — never guessed. This one is an illustrative example of the job.

run · lead-follow-up on demand · weeknight illustrative example
input

“Work the internet leads on the desk log for the last 7 days. Email every vehicle inquiry and sell-my-car lead, subject line with their first name and the vehicle, and ask for an appointment tomorrow or Thursday. No texts, it's almost 9pm. Anything untouched for 10 days gets the last-chance email and then goes to inactive.”

typed into dassi with the CRM desk log open

run
  1. 20:15 your dealer CRM set the desk log to the last 7 days with your saved filters: 64 internet leads
  2. 20:17 your dealer CRM opened each lead and read the notes, emails and texts already on it
  3. 20:58 your dealer CRM sent 41 appointment emails from the CRM's email window, each with the customer's first name and vehicle in the subject
  4. 21:20 your dealer CRM sent the last-chance email to 14 leads idle for 10 days or more, then set each one to inactive and saved
  5. 21:31 your dealer CRM wrote the summary: who was emailed, who was closed out, and the 9 it left alone
output
  • verified: 41 appointment emails sent and logged on the lead
  • verified: 14 stale leads given a last-chance email and moved to inactive
  • verified: A list of the 9 leads it did not touch, with the reason for each
exceptions
  • flagged: 3 leads had a note saying the customer already bought elsewhere. No email sent; listed so you can close them with the right reason
  • flagged: 2 leads were marked do-not-email in the CRM. Skipped
  • flagged: 4 customers had replied asking for an out-the-door price or a payment. No reply drafted; those are first on your list
next

Tomorrow night, the same instruction on the new day's leads. Saved as a Skill, it starts from one line.

What you can hand off

Reads the lead before writing to it

Notes, past emails, texts, the vehicle of interest, whether it's a purchase inquiry or a sell-my-car offer. The email it sends refers to what's actually on the lead.

Sends from your CRM login

Email goes out through the CRM's own compose window, so it's logged on the lead under your name like anything you'd send by hand.

Closes out the dead ones your way

The status dropdown, the reason, the save button: whatever sequence your store uses to clear a lead from follow-up. You show it once.

Flags the price talk

A customer naming a number, asking for out-the-door, or asking about payments is a negotiation. dassi lists those and leaves the reply to a manager.

Follows your hours and channels

Email only after a time you set, texts only when you say so and only to leads your CRM shows as opted in.

Sixty-four leads at 8:15 on a weeknight

This example is illustrative. It follows how a used-car manager at a franchise store works leads with dassi, with the names and counts changed.

The store closes at nine and the desk log still shows a week of internet leads. Some are people who asked about a specific car. Some are sell-my-car offers that came in through an instant-offer form. A good share haven’t been touched in ten days and are only on the list because nobody has cleared them.

The instruction is the one at the top of this page. dassi opens the desk log with the manager’s own filters, then goes lead by lead. On each one it reads what’s already there before it writes anything, since “just checking in” lands badly on a customer who replied yesterday.

Forty-one leads get the appointment email. The subject line carries the customer’s first name and the vehicle, because that was the instruction, and the body asks for tomorrow or Thursday. Fourteen stale leads get the last-chance email, and then dassi opens the status dropdown, picks inactive and saves, which is how this store takes a lead off the follow-up list.

No texts went out. The instruction said it was almost nine.

The nine it left alone

Three leads had a note from a salesperson saying the customer bought somewhere else. Sending them an appointment ask would have been embarrassing, so dassi sent nothing and listed them. Two were marked do-not-email.

The other four are the ones worth a manager’s time. Each customer had written back with a number: an out-the-door price, a monthly payment, a counter on a trade. dassi can draft a reply to those, and we’d still leave them with a person. The store’s desk decides what a car sells for.

What it costs you to set up

One evening. You open the list, paste the email you’d normally send, and walk through closing one lead so dassi sees the dropdown and the save button. After that, “save this as a Skill” turns the whole routine into something you start with a sentence.

Expect to correct it once or twice. In the usage behind this page, the manager had to point out that the close-out step had been skipped on one batch, and dassi went back through the list. Check the first few runs against the CRM before you trust the summary.

Limits

Your browser has to be open, and you have to be signed into the CRM. If the CRM logs you out mid-run, dassi stops and tells you.

Every lead it opens is read by a model, so customer names, phone numbers and messages on that screen go to the AI provider you picked. If your group has a policy on that, read it first.

Long runs get expensive. A backlog of six hundred leads is better worked as twelve runs of fifty than as one, both for cost and because a mistake in a short run is easier to spot.

Teach it once

01

Open the list you work from

The desk log, a dashboard, a saved search. Set the filters the way you normally do and tell dassi the date range.

02

Give it the words and the rules

Paste the email you'd send, or describe it. Say what the subject line carries, what counts as a stale lead, and which leads it should never touch.

03

Show the close-out once

Walk through one lead: dropdown, reason, save. Then say “save this as a Skill” and the next run needs one sentence.

Your accounts. Your machine. Your call.

Runs on your machine

The agent works in your browser on your computer, local by design. It never runs in our cloud.

Your logins stay yours

It works in the sessions you're already signed into. No password handoff, no credential vault.

You approve what leaves

Messages, submissions, payments — anything outbound waits for the approvals you set.

Your model, your choice

Claude, GPT or Gemini with your own key or included credits, or a fully local model. On your own key, prompts go straight to your provider; included credits pass through dassi's relay.

Frequently asked questions

Which dealer CRMs does it work with?

dassi works in the browser tab you're signed into and clicks the same screens you do, so there's nothing to integrate. The usage this page is based on was in Elead. We haven't run it in VinSolutions or DealerSocket ourselves, so treat those as untested.

Can it text customers too?

It can use the CRM's text window the same way it uses the email window. Texting is the part to be careful with. Marketing texts in the US need the customer's consent and are restricted outside 8 a.m. to 9 p.m. in the customer's time zone. Tell dassi your cutoff and to text only leads the CRM shows as opted in.

Will it answer a customer who's negotiating?

It will if you tell it to, and we'd advise against it. In the example run, four customers had asked about price or payments and all four were handed back with no reply. A wrong number in writing is harder to walk back than a slow answer.

Who sees my customers' information?

dassi runs in your browser, but the model has to read a lead to write to it. What's on the screen for each lead it opens goes to the AI provider you chose: under your own key if you brought one, or through dassi's relay on included credits. Check that against your store's customer-data policy before the first run.

Our group manages our browsers. Can I install it?

Ask IT first. dassi is a browser extension, and some dealer groups block or review extensions on work machines.

How many leads can one run handle?

Sixty-odd in a sitting is comfortable. Several hundred in one conversation gets slow and uses credits quickly, because every lead it reads adds to what the model carries. Split a big backlog into batches of fifty and start each batch fresh.

Give dassi its first run

Install dassi, open the pages this job lives in, and show it the work once. It runs from then on — your way, on your machine.

Add dassi to your browser

Free credits, good for 7 days — no card required

More jobs dassi runs

Continue to dassi

Sign in or create an account.

or