AI email for financial advisors: follow-up that doesn't sound like a bot

A financial advisor I hear from is rarely short of knowledge. They're short of the hour between the last meeting and the school run, which is when the follow-up was supposed to go out. The client doesn't experience that as "my advisor is busy." They experience it as silence, and silence is where the other firm gets a look-in.

That's the job AI email is actually for. Not a newsletter. Not a model inventing a view on the rand. A message you already know how to write, sent on the day you promised.

The emails worth automating, and the ones that aren't

The left column is admin wearing an email header. The right column is the job clients pay for. Mix them up and you've built a compliance problem with good grammar.

What "in your voice" actually means

Take five emails you were happy to send. Not the best prose of your career. The normal ones. Note the length (usually shorter than you think), whether you use the client's first name, and the sentence you always include about what happens next. That handful of samples is the instruction. A model with no samples will write like a bank. A model with your last five real emails will get close enough for a person to skim and send.

For the first month, skim all of them. The financial services work we do assumes a human still sees anything unusual. "Unusual" includes a client who replied with a question the template wasn't built for. That reply routes to you. It does not get a second automated answer that guesses.

A small practice, one sequence

Picture eighty households and one advisor in Durbanville. Reviews are meant to be annual. In practice they happen when someone feels guilty on a Sunday. The sequence is four touches, all logistics:

1. Six weeks out: a note that the review is due, with two time options
2. Once booked: what to send before the meeting, in a list, not a paragraph
3. Three days prior: a nudge only if the documents haven't arrived
4. The morning after: a short recap of what you agreed, drafted from the meeting notes, edited by you before it goes

That last one is the dangerous one if you let it run wild. The recap can list dates and documents. It should not invent a recommendation you didn't make. If the notes are thin, the draft should be thin. You fill the judgment in yourself.

I wrote more about the wider practice, beyond email, in what this means for advisors and their clients. The picking-a-first-job method is the same one in how to integrate AI. Email is just the job that shows up most often in this industry.

The line I wouldn't cross

Don't connect a model to the client base and tell it to "engage them." You will get cheerful emails that are wrong in a way that's hard to spot, because the tone is warm. Warm and wrong is worse than silence. Keep the templates boring. Keep product talk in the meeting. Keep a record where your compliance process already expects one.

If you want that sequence mapped against the way your practice already diaries reviews, that's a discovery call, not a pile of sample emails I write for free and you paste into a tool neither of us will maintain.