Use cases
AI employee for sales follow-up
Tobiloba Odejinmi · 22 Nov 2025 · 6 min · 1,314 words
Direct answer
A sales follow-up employee looks up the lead, writes the first note, and flags the ones worth a call. Good looks like a CRM row a rep can act on in two minutes. Escalate pricing, legal, and anyone who asked for a person. Do not automate discounting or contract redlines first. Measure meetings booked from flagged leads, not email opens.
- The job is the first pass: context, a note, and a reason to call or wait.
- A good output is a CRM record a rep can trust, not a long email.
- Pricing, legal, and “call me” are handoffs. The employee does not close.
- Measure meetings and stage movement from flagged leads, not open rates.
What is the actual job in sales follow-up?
Most follow-up is not selling. It is looking up who just filled the form, writing a note a future you can read, and deciding if a person should call today. That pile sits in inboxes and Slack. Reps skip it when they have a live deal. Then the lead goes cold and everyone blames “the top of funnel”.
The employee should sit in the CRM you already use. It reads the inbound, pulls the account if it exists, and writes the first note: who they are, what they asked, what we already know. Then it either drafts a reply or flags the row. That is the job. A new sequence tool is not the job.
I have seen this go wrong the same way APIs go wrong. Teams build a clever writer and forget the lookup. At Zeeh, adoption grew 890% because another team could plug in before lunch. Follow-up works the same way. If the employee cannot read the CRM, it will guess. Guessing in sales email is how you burn a domain.
What does a good follow-up employee do?
Good looks like a row a rep can open and act on in two minutes. The note is short. The source fields are visible. The next step is one of three things: send the draft, call, or wait. If the output is a 400-word email and a mystery score, you built a dashboard. Reps will ignore it.
The first reply should use one fact you actually have. The form field. The last webinar. The page they were on. If you do not have a fact, ask one question. Do not invent a pain. I will not ship a writer that fabricates a “noticed you are scaling”. That sentence has never closed a deal I respect.
Keep the voice plain. Short. Same as the rest of this site. If your brand guide is a novel, pick three rules and stop. Follow-up is not a thought-leadership channel. It is a courtesy and a filter.
- CRM note written before any email goes out
- Draft cites a field the team can see
- Flag reason is a sentence, not a score from 0 to 100
- No second inbox for “AI leads”
When should a human take the lead?
A person takes the lead when the buyer asks for a call, a price, a security review, or a legal change. Also when the account is already in a late stage. The employee can collect the question. It should not answer with a number you have not approved.
Treat this as a state handoff. The rep gets the account, the last touch, the draft if any, and why it stopped. “Hot lead” is not a reason. “Asked for annual pricing and named a competitor” is a reason. If you paste a transcript into Slack and call it a handoff, you will lose the thread.
BCG’s 2026 read has agents in 30% of workflows, up from 13%. Sales follow-up is one of the workflows that actually fits, because the first pass is repetitive. Closing is not. Do not let the adoption number talk you into an employee that “owns the deal”. It owns the morning pile. That is enough.
What should you leave alone at the start?
Do not automate discounting. Do not automate contract redlines. Do not automate “we can do that by Friday” unless Friday is a field in the system. Those promises move money and trust. They need a name.
Skip cold outbound as the first job. Cold is a different process with a different miss cost. You will spend weeks arguing about tone while inbound sits unanswered. Inbound follow-up is the pile. Start there.
Also skip lead scoring theatre. If your team does not already act on a score, a model will not make them start. A flag with a sentence they can disagree with is more useful than a 92.
How do you measure follow-up that is not vanity?
Time from form submit to first touch. Share of new leads with a CRM note in an hour. Meetings booked from the flagged set. Opportunities that move a stage in two weeks. Those numbers tell you if the pile shrank and if the flags were real.
Ignore open rate as a success metric. You can game it with a subject line. Reply rate is better. Meeting rate is better still. If flagged leads do not convert better than the unflagged pile, the flag is decoration.
Once a week, sit with a rep and read ten drafts. Ask two questions: is the fact true, and would you send this. The noes are the work. If you cannot explain a bad draft, do not turn on autosend.
- Inbound to first touch
- Usable CRM notes per lead
- Meetings from flagged leads
- Stage movement in 14 days
Where should this sit so reps actually use it?
In the CRM. In the inbox they already live in. Not a new tab with a cute name. I have the same rule I used for bank APIs: if another team cannot use it before lunch, you still have work to do. Reps will not learn a new religion for a draft.
Write the escalate path the same way. The flag creates a task on the right person, with the reason in the description. If that requires a manager to forward an email, you have not finished the workflow.
When I sold Insurpass, buyers did not ask about our sequences. They asked whether the records were clean and whether one person could explain the system. Follow-up automation gets the same questions. If the notes are sloppy, the employee made the CRM worse. That is a failed install, even if the emails went out.
Questions people ask
What is the first job for a sales follow-up employee?
Read the inbound, look up the company in the CRM, write a short note, and either send a first reply or flag it. If your reps already do that by hand every morning, that is the process. Do not start with a full outbound sequence.
Should it send the email or only draft it?
Draft first. Let a person send until the miss rate on facts is boring. Then send the obvious ones: thank you, booking link, “we got this”. Never send a price or a custom term without a person.
What should it never do?
It should not invent a discount, promise a date you cannot keep, or rewrite a contract. Those are hard gates. It also should not create a second CRM. If the note is not in the system the team already lives in, it did not happen.
How do we keep it from sounding like spam?
One fact from the form or the last call. One next step. No slogans. If you cannot point to the field it used, do not send. That is how you stay out of the junk folder and out of a complaint.
What do we measure?
Time from inbound to first touch. Share of leads with a usable CRM note. Meetings booked from the flagged pile. Stage movement in fourteen days. Open rate is a vanity number. Treat it as such.
Written by
Tobiloba Odejinmi
Head of Engineering at 10mg Health. I have run engineering at Zeeh Africa and sold Insurpass and Shopl. I still write the code. If you have one process that still runs on people copying things, we can look at it in thirty minutes.
