By morning the customer-support floor had filled with ordinary problems: forgotten PINs, delayed reversals, cash-outs and balances that were not abstract to the people calling.
Aisha sat beside a support agent named Peter.
“Confirm only the status of the number,” she said. “Do not tell whoever answers that we are investigating a dead customer's account.”
Peter called.
A man answered after two rings.
Peter introduced himself and asked whether he currently used the number ending in 4811.
“Yes. I've had it about two weeks.”
“Do you know Atieno Akoth?”
“No. Who is that?”
Aisha shook her head. No more questions. The new subscriber had not consented to be pulled into someone else's financial history.
“Thank you,” Peter said. “We don't need anything further right now.”
After the call, Aisha requested a privacy-limited activation extract: date, status change and partner-feed reference only.
Then she called Ruth Atieno, Mama Atieno's daughter.
Ruth insisted on video. “The last time the company called, three different people asked us the same questions.”
On screen, Ruth sat beside her uncle Ouma. Mama Atieno's old handset was on the table.
“This phone stays here,” Ruth said.
“I am not asking for it,” Aisha replied. “I only need to verify the closure receipt and a limited period of account history. You can keep every original.”
Ruth held the closure receipt to the camera. Its reference matched SawaLink's record.
“Did your mother have a PesaFasta loan?”
“She had savings-group advances. Supplier debt. Maybe a hospital loan. PesaFasta? I don't know.”
“Then we won't guess.”
When the telecom-feed extract arrived, it showed that the old number had been deactivated after the death closure and reactivated for a new subscriber thirteen days earlier.
Peter relaxed. “So it was recycled. That explains it.”
Aisha opened the borrower profile.
It did not.
The borrower ID was still **ATN-004811**, Mama Atieno's historical customer identity. Yet the field `profile_opened_at` showed a date after her death.
Wekesa joined them.
“What does borrower creation do when a newly active number matches an old wallet?”
He found the configuration. “It links the existing customer key unless the closure reason is excluded.”
“Is death excluded?”
“In the documentation, yes.”
“In production?”
Wekesa searched again.
The old closure code had been `DCS1`. A newer migration expected `DECLOSED`.
Some legacy records had never been remapped.
That could explain why an old customer identity had attached itself to a new subscriber's number. It did not explain why three new loans had appeared or why reserve journals were repaying them.
Aisha asked Ruth for limited consent to review closure, origination and disputed repayment records. She wrote the scope in plain language. No handset extraction. No unrelated messages. No open-ended access to the family's life.
Ruth agreed.
Meanwhile, the new subscriber called support back because he had noticed the missed call. Peter told him only that his recently assigned number was undergoing a historical-identity review and that he did not need to provide any information.
The man said he had begun receiving debt messages he did not understand.
Aisha immediately suspended collections communication on the disputed profile. The new subscriber could be harmed too. He had inherited a phone number, not the moral or financial history attached to it by mistake.
The loan list opened on Aisha's screen.
Three loans.
All originated after Mama Atieno's death.
The name was hers. The phone number now belonged to someone else. The repayment engine had already begun pulling reserve-linked entries.
Peter stared at the screen.
Aisha created a new case category: **recycled-number identity collision**. She did not call it deceased fraud. She did not want support teams to treat everyone with a recycled number as suspicious.
Victor posted on the operations channel:
**Why is one dead-account exception holding repayment reporting? Fix the mapping and release the figures.**
Aisha replied with the case link and three facts: old identity retained, phone number reassigned, post-death loan profiles created.
“Fix the mapping” might eventually be the correct repair. But before any correction erased the path, they had to know whose money had been used and who might receive future reversals.
The borrower profile was active.
Peter then reviewed how the collections platform would behave while the identity collision remained open. If they merely changed the customer name but left the loan objects active, the new subscriber could still receive automated calls. He placed a temporary suppression tied to the case, with an expiry and review owner. Aisha insisted the suppression itself leave an audit trail. A protection that silently erased communications could later look like someone had hidden debt notices. Ruth received the same case reference so the family could ask what had changed without needing to retell the entire death-closure story each time.
The person whose name sat on it had died before the new account was opened.