Customer follow-up system: ownership and cadence

Follow-up is not only a sales matter

The word follow-up is usually associated with selling: a proposal went out and an answer is awaited. In practice a company has dozens of points that require a follow-up, and most of them have no owner.

The service was delivered — were they satisfied? The order arrived — was it complete? The complaint was resolved — does the customer know? The meeting happened — what is the next step? Each of those needs a contact, and none of them belongs to the sales process.

This article builds the operating model for follow-up: the three types, the ownership rule, the cadence, the escalation ladder, choosing a channel and the rules for stopping. Why lead follow-up fails and what gets built in the CRM is a separate subject, covered in sales lead follow-up automation.

Three types of follow-up

Managing all of them with one rule does not work, because the three differ in purpose, frequency and owner.

1. 1Sales follow-upAfter a proposal, after a meeting, while a decision is pending. The purpose is to set the next step. The owner is the salesperson and the cadence follows the decision cycle.
2. 2Service follow-upAfter delivery, after installation, after a complaint is resolved. The purpose is confirmation: is everything as it should be. The owner is the service team and the cadence is fixed — a set period after the event.
3. 3Relationship follow-upPeriodic contact: before a season, at renewal, after a long silence. The purpose is keeping the relationship alive. The owner is the account manager and the cadence is the widest.

Separating the three has a practical consequence: service follow-up can be fully automated, relationship follow-up partly, and the decision part of sales follow-up always stays with a person.

Ownership: every follow-up needs a name

The first reason a follow-up system fails is that nobody owns it. «The team will look at it» means, in practice, that nobody will.

• Each type has a default owner, decided in advance
• Where the owner changes for a specific case, that is recorded — no verbal agreements
• If the owner is on leave or has left, the follow-up is reassigned automatically
• Where one customer has several open follow-ups, they are merged — the customer should not receive three separate calls
• When ownership changes, the context travels with it

The fourth line matters most for the customer's experience. Three departments calling the same customer in one week is an organisational problem, but the customer sees it as disorder and forms their opinion accordingly.

The practical fix is simple: follow-up tasks appear together on the customer record. Looking at departmental lists hides the collision; looking at the customer record shows it immediately.

Cadence: when and how often

There is no universal answer, but two dimensions are enough to set one: the nature of the event and the customer's decision cycle.

• After a service: 24–72 hours — if there is a problem, it can still be fixed
• After a delivery: the day of delivery or the day after
• After a complaint: the day it was resolved, then a check a week later
• After a proposal: one or two days, then according to the decision cycle
• Periodic relationship contact: quarterly or seasonal, not monthly
• After a long silence: once after six months, as a campaign

The first line is worth pausing on. The value of a post-service follow-up depends directly on timing: if something is wrong and you ask within three days, you can fix it; ask a month later and the customer has already decided and will not tell you.

The escalation ladder

The mechanism that makes a follow-up system work is escalation, and it needs three rungs.

1. 1First rung: the reminderWhen a task comes due, its owner is notified. This is the core of the system and is often enough on its own.
2. 2Second rung: the delay signalA task not done within a period joins the overdue list and appears on a team lead's screen. This is not a punishment — it is visibility.
3. 3Third rung: reassignmentAfter a longer delay the task moves to another owner. A customer should not wait because of who happens to be busy.

The timings should differ by type: hours for a complaint follow-up, days for a sales one. A single timing makes the system either too sensitive or meaningless.

Choosing the channel

The channel changes the result, and the choice should follow the content rather than habit.

• A call: for anything requiring a decision, an explanation, or on a sensitive subject
• A message: for confirmations, reminders, short information
• Email: for documents, invoices, longer information
• Whatever channel the customer chose always takes precedence
• When the channel changes, the context travels — the customer should not explain themselves twice

The most common mistake is running every follow-up on one channel. Use a call for everything and the customer tires; use a message for everything and the things needing a decision stay unresolved.

When follow-up should stop

This is the least written-down part of the system, and it is the principal source of customer irritation.

• The customer declined explicitly — stop and record it
• The attempt cap is reached — move to the campaign list, out of the daily queue
• The matter was resolved another way — close it
• The customer is in conversation with another department — wait for that contact
• A complaint is open — sales follow-up stops

The last line matters particularly. Contacting a customer with an unresolved complaint to offer them something generates more complaints than anything else, and the system itself should prevent it rather than leaving it to human attention.

Measurement

The key measure of a follow-up system is execution discipline rather than outcome, because the outcome also depends on other things.

• Execution rate: what share of planned follow-ups happened on time
• Average delay: how long after the planned time
• Escalation count, and at which rung
• Age of open follow-ups: how old is the oldest
• Open follow-ups per customer — more than one means a merge is needed
• Problems surfaced by service follow-up — the real value of the system

The last line is worth pausing on. The purpose of a post-service follow-up is not to make the customer happy — it is to find fixable problems before the customer leaves. If the number of problems found is zero, either everything is perfect or the question is being asked wrongly.

Limits

A follow-up system does not create a relationship — it protects an existing one. If the customer is unhappy with the service, more contact does not improve the situation; it does the opposite.

The second limit is volume. In a small team this system can be overhead: a calendar and some discipline do the same job. It earns its place with several departments, hundreds of customers and more than one type of follow-up.

How Vexvon supports this system

On the Vexvon side follow-up is supported from both the record and the call side.

• Reminders live on the lead and customer record, and the system checks them every minute
• A follow-up reminder fires after six hours, and the 23:00–09:00 window is protected
• The call step can be built as a campaign — «customers served three days ago» becomes a target list from a CRM filter
• One timeline shows every contact — call, message, note, status change — so open follow-ups per customer are visible
• Outcome codes and close reasons make the stopping rules applicable
• Triggers can send a notification — an overdue task to Telegram, for instance

The structure of the customer record is on the CRM page, and the call side on the call center page.

First step

Write three lines on one page: after a service, who contacts the customer, when, and on which channel. Then run it for one event type only — after delivery, say. Two weeks is enough to see what the system finds.

To build the follow-up model for your own processes, get in touch.