# The same call-back was booked twice

A commitment is recorded when it is made, so a promise restated three times in one call, made again on a second call, or attached to two different records for one person can land as more than one follow-up. Clearing it means deciding which one is the commitment, cancelling the rest, and fixing the cause — usually a split person record rather than the call itself.

- **Status:** Available
- **Audience:** both
- **Channels:** phone
- **In the app:** #/follow-ups, #/calls
- **Last verified:** 2026-09-10
- **Canonical:** https://connectbyjbrh.com/docs/troubleshooting/duplicate-follow-up/

## What you are looking at

Two rows in the follow-ups list for the same person, on the same channel, for what is obviously one thing: call back about the quotation. Sometimes they carry the same due time, which is easy to read. Sometimes one says Friday at three and the other says 11:00 tomorrow, which looks like two commitments and is not.

The second shape is worth recognising, because it comes from the way promised words are turned into a time. Phrases such as 'in ten minutes', 'tomorrow 11am', 'Friday 3pm' and 'today evening' resolve against the line's own timezone; words that carry nothing usable resolve to 11:00 the following day. So a vague promise and a specific one about the same thing can end up hours apart while meaning the same commitment.

## Causes, likeliest first

| Cause | How to recognise it | Where the fix is |
|---|---|---|
| The promise was restated during the call | Both follow-ups trace to one call, with due times minutes apart | Cancel the weaker one; nothing is wrong with the record |
| The caller rang twice | Two calls, two records, the same request | Cancel one and note the repeat contact on the person |
| The person exists as two records | Each follow-up sits under a different person, and neither list shows both | Merge the records — see [duplicates](/docs/relationships/duplicates/) |
| Somebody booked it by hand as well | One follow-up has a person's name against it | Keep the human one; it usually carries better wording |
| A call and its call-back both promised | The second call restated the first promise | Cancel the older one and keep the live commitment |

The split-record case is the one that repeats, because it is not really a follow-up fault. A number that resolves to two rows is resolved to the older of them, so a contact created before a number was attached to it can sit beside the one the calls now use. Two records are two people as far as any queue is concerned, and no amount of tidying the follow-ups list will stop the pair reappearing until the records are merged.

## What counts as the same commitment

**The same person** — Not the same name or number — the same record. This is the test that fails most often.
**The same channel** — A call-back sits on the phone channel and a person's work sits on the task channel. 'Call them' and 'send the quotation' are two commitments, not a duplicate.
**The same moment, once resolved** — Due times are resolved in the line's timezone before they mean anything. Compare the resolved times, not the phrases that produced them.
**The same reason** — The reason is written from what was actually said, so two rows with genuinely different reasons are usually two obligations that happen to fall on one afternoon.

> **Note** Reconciliation of follow-ups themselves is covered on [follow-up duplicates](/docs/follow-ups/duplicates/). This page is about the ones that arrive from a call, which is where the split-record cause and the resolved-time confusion both come from.

## What Connect completed

- Each promise was recorded with its own reason, due time and channel, and each is traceable to the call it came from.
- The transcripts prove what was said each time, so which promise is the live one is a matter of reading rather than judgement.
- Both follow-ups are in the queue and will be drained on their due times unless somebody intervenes.
- Where the follow-ups sit under two person records, both records exist with their own history intact — nothing was overwritten.

## What Connect did not complete

- Connect did not decide which of the two is the real commitment, and it did not cancel either one.
- Nothing was merged across person records; a duplicate person is a relationship problem and stays one until it is merged deliberately.
- The customer was not told they may be called twice.
- No commitment was silently dropped to tidy the list — a promise that was made stays on the record until a person closes it.

## Clearing it

1. Open both follow-ups and compare the resolved due times, the channel and the reason.
   - Result: You will usually find one commitment described twice rather than two.
2. Keep the one whose reason reads closest to what the caller asked for, and edit its due time if the resolved time is not what was meant.
   - Result: That row becomes the single commitment, and it carries the wording somebody will read before dialling.
3. Cancel or complete the other, and say why.
   - Result: The queue is clean and the reason survives, so nobody re-opens the question next week.
4. If they sat under two records for one person, merge the records.
   - Result: Future calls, mail and follow-ups collect against one person, and the pair stops reappearing.

## What an administrator can do

- Check the line's timezone. A wrong one turns every resolved promise into a time nobody recognises, which reads as duplication.
- Watch for repeated pairs on the same person: that is a merge waiting to be done, not a run of bad calls.
- Look at how the line closes a call. A voice that restates its commitment twice before hanging up will book twice as often as one that confirms once.
- Keep an eye on the volume page — [too many follow-ups](/docs/troubleshooting/too-many-follow-ups/) covers the case where the count itself is the problem.

## When to escalate

Escalate when duplicates appear for people whose records are already merged, when both rows trace to one call with identical due times and identical reasons, or when cancelling one is followed by its reappearance. Those three are not explained by a restated promise or a split record, and they need somebody to look at the calls behind them rather than at the queue.

## Questions

### Will both follow-ups actually dial?

If both are on the phone channel and both are due, yes — the drain executes what is due and does not adjudicate between two commitments. That is the reason to cancel one rather than to leave the pair and hope.

### Is a task and a call for the same person a duplicate?

No. They are different obligations: one is a call-back and one is work somebody has to do. They often arrive together from a single call and both belong in the queue.

### Why does one of them say 11:00 tomorrow?

Because the words behind it carried nothing usable as a time, and that is the fallback rather than dropping the promise. It is meant to be edited when the transcript shows what the caller actually expected.

## Related

- [Duplicate follow-ups](https://connectbyjbrh.com/docs/follow-ups/duplicates/)
- [Follow-ups from a call](https://connectbyjbrh.com/docs/phone/call-follow-up/)
- [Executing a follow-up](https://connectbyjbrh.com/docs/follow-ups/execution/)
- [Duplicate detection](https://connectbyjbrh.com/docs/relationships/duplicates/)
- [Merging duplicate people, end to end](https://connectbyjbrh.com/docs/workflows/duplicate-merge/)
- [The same person is being chased repeatedly](https://connectbyjbrh.com/docs/troubleshooting/too-many-follow-ups/)

## What this page is based on

- `docs-source/sources/PHONE.md` §10 — follow-up integrity and due times
- `docs-source/sources/CHANNELS.md` §1 — canonical records across channels
- Connect capability registry (docs-source/facts.py) — followups, duplicate_merge