The call promised a call-back that never happened
Saying a time on a call and booking it are two separate acts, and the second one can refuse. The usual reason a promised call-back does not exist is that the voice proposed a time the caller never said and never agreed aloud, so recording it was refused and the tool answered that nothing was recorded. The call review names this as a promise with nothing behind it.
The symptom#
A customer says they were told someone would call back this afternoon. The transcript agrees — the voice did say it. The follow-ups list has nothing for that person, nothing was dialled, and nobody was told.
The gap is deliberate rather than accidental. A spoken sentence is cheap and a booking is a commitment on a date, so the booking is a separate recorded act with its own rules. When those rules refuse, the tool answers that the follow-up was not recorded, in those words, so the model cannot go on to tell the caller it is done. What it cannot do is un-say a sentence already spoken.
Causes, likeliest first#
| Cause | Evidence to look for | What to do |
|---|---|---|
| The time did not come from the caller | The refusal is recorded against the call; the review finding is a promise with nothing behind it | Book it by hand, then read the fix below |
| The promise was in the closing line | The call ended immediately after the sentence | Book it by hand; have the voice confirm before closing |
| The call decided no follow-up was needed | Nothing scheduled and no refusal recorded | A judgement call — book one if the transcript warrants it |
| It was booked as work, not as a call | A follow-up exists on the task channel rather than phone | Nothing is broken: a person's task is not a dialled call-back |
| It was booked, later than expected | A due time of 11:00 the next day | The spoken words carried nothing usable; edit the due time |
| The call was never a conversation | The outcome says it never rang, or that nobody picked up | No lead and no follow-up come from either; nothing to recover |
| The digest had not run yet | The call's summary is marked pending | Look again shortly; the digest runs once in the background |
The rule that refuses a time#
A follow-up time must share a time word with what the caller actually said, in their most recent time-bearing line — the check reads English, Telugu and Hindi. The one exception is a time the voice said aloud and the caller then agreed to, which counts as the caller's own. If neither is true the record is refused, and the voice is asked to read a time back rather than invent one.
This exists because of a real call that looped three times, each turn confirming a booking that had never happened. A model allowed to assert a time it made up will do it again on the next turn, and the caller has no way to tell.
What Connect completed#
- The call ran, and its record carries the ring, answer and end times with the outcome and who ended it.
- The transcript holds both sides, so what was promised is provable rather than remembered.
- The lead and contact were created where the call was a real conversation, with the caller's number attached from the start.
- The refusal itself is on the record, along with the review finding that names an unbooked promise.
- The summary and the review ran in the background after the row was closed, so the call was never held open waiting on two model calls.
What Connect did not complete#
- No follow-up row was created, so nothing is due, nothing is queued and nothing will be dialled.
- Nobody was notified beyond the review finding on the call itself.
- The customer was not told that the call-back was not booked — they were told the opposite, on the call.
- Nothing was retried quietly. A refused booking stays refused until a person acts.
What you can do#
Open the call and read the last few lines of the transcript.
Result You will see the promise, and whether the caller named a time or only agreed to a vague one.
Create the follow-up yourself, on the phone channel, with the reason written in the caller's terms.
Result The obligation is now on a date and in the queue, and it will be drained like any other.
Check the due time against the line's timezone.
Result Spoken words such as 'tomorrow 11am' or 'today evening' are resolved in the line's timezone, not the reader's.
If the same thing keeps happening on one line, tighten the closing behaviour so the voice confirms a time before promising one.
Result A time the caller says back is a time that books, because agreement to a spoken time counts as the caller's own.
What an administrator can do#
- Review the findings, not the transcripts
- The call review lists unbooked promises deterministically. That list is faster than reading calls and does not depend on anybody's memory of what was said.
- Check the line's timezone
- Every promised phrase is resolved against the line, so a line with the wrong timezone books real follow-ups at the wrong hour rather than refusing them.
- Watch the drain
- A booked call-back is executed by the phone follow-up drain. A follow-up that exists but never runs is a different fault with its own page.
- Mind the language coverage
- The time-word check reads English, Telugu and Hindi. A caller naming a time in another language may be refused even though they did say it — a limit to know about, not a setting to change.
When to escalate#
Escalate when refusals are recorded against times the caller plainly did say in a covered language, when unbooked promises appear on a line that was quiet before a change, or when a follow-up exists, is due, and is never executed. The first two are the rule reading the conversation wrongly; the third is about execution and belongs with follow-ups that do not run.
Questions#
Why not book whatever time the model says?
Because it will say a plausible one when it did not hear one, and a booking is a commitment with a date on it. Requiring the time to come from the caller — or to be one the caller agreed to aloud — is what stops a call from confirming an appointment nobody made.
The follow-up exists but it is a task, not a call. Is that wrong?
No. A call-back goes on the phone channel; work a person has to do — sending a quotation, checking something — goes on the task channel. Both are follow-ups with a due time and a reason; only one of them dials.
What happens if the caller's words gave no usable time at all?
The promise still books, at 11:00 the following day, rather than being dropped or invented. That default is visible on the follow-up and is meant to be edited when the real intent was different.