How to schedule a callback the customer has agreed to

The short answer

A callback appointment is a promise agreed with the customer: "we'll call you tomorrow between 10:00 and 12:00". For it to work, five elements are needed: a precise time window, a responsible person or team, the customer's time zone, a rule for what happens if the customer does not answer, and a CRM record with a status.

The most common mistake is promising a callback without building a process behind it. The customer waits, nobody calls, or the call comes outside the agreed time. This article shows step by step how to set up a callback appointment.

When to offer a callback

• Operators are busy and the wait will be long
• The call came in out of hours
• The question needs a specialist who is not available now
• The customer prefers to talk later
• The answer needs an extra check — a document, stock, a price

The same rule applies in every case: the customer gets to choose the time, and a promise is only made for a time that can actually be kept.

The time window: a range, not an exact time

"Tomorrow at 11:00" sounds precise, but the operator's previous call may run over. A one- or two-hour window is more realistic: "tomorrow between 10:00 and 12:00". The window depends on the customer's choice and the team's real schedule. The agent or operator should only offer windows with capacity; otherwise fifteen callbacks pile up at 10 a.m.

Information to collect

1. 1Name and numberIf the number differs from the one the customer called from, confirm it separately.
2. 2TopicOne sentence: what the call will be about.
3. 3WindowDate and time range, in the customer's time zone.
4. 4LanguageWhich language the customer prefers.
5. 5Context collectedWhat was already said on the call — so the person calling back does not ask again.

How the agent should word the offer

A callback offer should sound like a choice, not a refusal. Rather than "nobody is available right now", it is better to say "Shall a colleague call you at a time that suits you?" Then offer two concrete windows — an open question ("when suits you?") makes the caller think and often leads them to pick a time the team is not working.

At the end, repeat three things: the number, the window and the topic. If the caller misheard anything, this is the last chance to correct it.

Time zone

When customers call from another city or country, the time zone is the most forgotten detail. "10 a.m." in Baku time might be 7 a.m. somewhere else. The rule is simple: agree the window in the customer's time, and show both the customer's and the team's time in the system. For a business operating in one country this is a small problem, but for travel, education and B2B companies taking calls from abroad it matters.

The responsible person

If a callback is promised to "the team", often nobody makes it. Every callback should be assigned either to a named person or to a team with a rota, and it should appear on that person's list when the window opens. If the owner is on holiday or ill, a fallback rule is needed: the task returns to the team automatically.

When the customer does not answer

1. 1Attempt 1At the start of the window.
2. 2Attempt 230–60 minutes later, within the same window.
3. 3NoteIf possible, a short message: "We called as agreed — let us know a time that suits you."
4. 4CloseAfter the second attempt the status is "not reached", and the customer's next contact is awaited.

Limit the number of attempts. Calling a customer five times in a day is not service, it is a nuisance.

CRM statuses

• Scheduled — window and owner assigned
• Done — contact made, outcome recorded
• Not reached — two attempts, no answer
• Rescheduled — the customer asked for another time
• Cancelled — the customer said it is no longer needed

The status should be chosen from a closed list, not typed as free text — only then can reports be built.

No-shows and rescheduling

A customer not answering does not always mean lack of interest: they may be in a meeting or not recognise the number. Make the callback from the company's recognisable number, and tell the customer on the call which number the callback will come from. If the share of "not reached" callbacks is high, look at how windows are chosen and at the number.

Illustrative example: a night call

Not a real customer case. At 10:40 p.m. a customer calls about enrolling on a course. The agent gives the opening hours, asks about the course and level, then offers a callback: "Tomorrow 10:00–12:00 or 14:00–16:00 — which suits you?" The customer picks the second. The note reaches the team in the morning with the fields course, level, window and "caller's language: Russian".

The responsible manager calls at 14:10 and gets no answer; the second attempt at 15:00 succeeds. The manager does not ask again about the course and level and goes straight to the schedule. Status: "done"; outcome: "enrolment documents sent".

What to measure

• The share of callbacks made on time — within the window
• The share reached on the first attempt
• The share with status "not reached"
• The outcome after the callback — enrolment, order, resolution
• Load per window — which hours collect the most callbacks

Common mistakes

• Promising an exact time and not being able to keep it
• Not assigning an owner
• Ignoring the time zone
• Not passing the collected context to the person calling back
• Endless repeat calls when there is no answer

Limits

The callback process depends on the team's real capacity; without capacity, offering a window turns into a broken promise. Customer consent and local requirements must be considered for repeat attempts and messages. This article describes a recommended workflow based on industry practice.

A callback flow with Vexvon

In Vexvon AI Call Center this flow is built from existing capabilities: fields such as "callback window", "topic" and "language" are defined in the scenario, and the agent extracts them from the call and writes them to the customer card — a field that was not found stays empty rather than being made up. For a night call, the caller's number and request are on the team's panel in the morning. The callback can be made by an operator, or the agent can call itself using a list built from a CRM filter; this is a recommended flow that requires configuration.

Recovering missed calls is covered in missed-call recovery, and when to offer a callback in the queue in call queue experience.

First step

Pull last week's list of promised callbacks: how many were made within the window, and how many had an owner? Those two figures show where the process should start. More articles are in the human handoff & CRM section; to set up the flow together, get in touch.