The Account Manager Who Never Forgets To Check In

Nobody forgets the loud clients

The accounts that get attention are the ones that ask for it. That is not negligence, it is how a full inbox works. Whatever arrived most recently sets the agenda, and a client who is quietly satisfied generates nothing to react to.

The problem is that quiet and satisfied are not the same thing, and by the time the difference becomes visible it usually arrives as a cancellation. The team knew this and had tried the usual fixes: reminder tasks, a shared spreadsheet, a recurring calendar block. All of them worked for a few weeks.

Every one of those solutions failed the same way. They required someone to maintain them during exactly the weeks they were too busy to maintain anything.

Working from the inbox, not beside it

The system connects to each account manager mailbox and reads the actual record of contact. Not a CRM field somebody was supposed to update, but the messages that genuinely went back and forth.

That distinction is the whole design. A last-contacted field is only as good as the discipline of the person maintaining it, and the people who let accounts go quiet are the same people not updating the field. Reading the mailbox removes the dependency on the behaviour we were trying to fix.

Every morning it sweeps every account, compares the real last contact against that account threshold, and produces a list of relationships going cold.

Context is what stops it reading like a robot

A check-in that says only that it has been a while is transparently automated and slightly insulting. Before drafting, the system pulls what the CRM knows: recent work, open items, what the last conversation was actually about, and where the account stands.

The draft uses that. It asks about the specific thing that was in flight, references the work that shipped, and raises the question a manager who had been paying attention would raise. It goes out under the account manager name, from their mailbox, in their voice.

Threshold length is set per account, not globally, because a strategic client and a small retainer do not need the same rhythm and a single blanket rule produces either nagging or neglect.

No new software

Worth being clear about what this was, because it is smaller than it sounds. There is no product here. The whole thing runs inside the Claude account the client already paid for, connected to Gmail and to their CRM.

We considered building something and could not justify it. Everything the job needed already existed in tools they were subscribed to. Adding a system would have meant another login, another vendor, and another thing to maintain, in exchange for nothing the automation could not already do.

That is frequently the right answer with agent work and it is rarely the one being sold. The interesting part was the design of what it checks and what it says, not the infrastructure underneath it.

What it changed about the team

The value the team named first was not the emails. It was no longer carrying the list in their heads. Remembering who has gone quiet is a low-grade background task that occupies attention all week and gets dropped the moment anything urgent lands.

Handing that to something that runs every morning removed the drop. Coverage stopped being a function of how busy the week had been.

The replies were the second surprise. A meaningful share of check-ins came back with actual work attached, because the client had been meaning to ask about something and had not gotten around to it either.