The Missing Renewal Record

By half past four, the easy tickets had begun to thin out. Around Adam, chairs scraped back and people called brief goodbyes across the office, but the disputed renewal remained open on his screen.

He read the customer’s message again. They were certain they had not authorised it. The account history showed a renewal charge, but not the usual sequence of confirmation notes. Adam checked the visible billing record, then the older support entries, comparing dates and payment references. He refreshed the account twice, more from uncertainty than expectation.

There was enough evidence to make a confident accusation against the customer, and not enough to make a confident refusal. That was the problem.

Adam leaned back and rubbed at his eyes. The scripted response sat in a template beside him: explain the renewal, direct the customer to the terms, close the case. It would take less than a minute. Instead, he opened an internal billing query and attached the records he could verify, carefully separating what the system showed from what it did not.

When he finally drafted his reply, he avoided promising a refund or insisting that the charge was valid. He told the customer he was reviewing the renewal history and had asked for the billing details to be checked. He would update them once the record was clearer.

The message looked plain on the screen. Not impressive. Not particularly safe, either. But it was accurate.

Adam sent it through the normal support system and watched the case status change to pending investigation. The disputed renewal was still unresolved, and the extra work had left him with a dull pressure behind his eyes. Even so, he felt less uneasy than he would have after sending the standard answer.

He closed the billing tabs one by one, leaving the case open for the next response. Outside, Manchester was turning blue in the early evening light. Adam reached for his mug, found it cold, and stayed at the desk a moment longer before standing.