[
  {
    "id": 1,
    "text": "CASE NOTE. Reference CS-2026-441907. Channel: inbound voice. Queue: technical support tier one. Handle time 21 minutes 40 seconds. Customer reported intermittent loss of connection over the past nine days, occurring mainly between six and nine in the evening and lasting between two and twenty minutes at a time. Identity verified against date of birth and the last four digits of the payment card. Line test run during the call returned a signal to noise margin of 4.2 decibels downstream, which is below the stable threshold of 6 decibels and is consistent with the pattern the customer describes. Attenuation measured at 41 decibels. I asked the customer to confirm the physical setup. The modem is connected to the master socket using the original filter, not an extension lead, so an internal wiring fault at the socket is less likely than a fault on the external line. Two other properties on the same cabinet have raised similar reports in the past fourteen days, which the system flagged while I was on the call. On that basis I have escalated to tier two rather than booking an engineer directly, because a cabinet level fault would be resolved for all affected properties at once and a home visit would find nothing. Escalation reference TT-88204 raised and linked to this case. Target response from tier two is within two working days. I explained to the customer what an escalation means in practice, that he will not need to repeat the history to anyone, and that he will be contacted by phone rather than email because he said he is often away from his computer. He asked whether he would be compensated for the disruption. I explained that a credit is applied automatically once a fault is confirmed and closed, calculated from the date the fault was first reported rather than from today, and that the first report on his account is dated the eleventh. He accepted this. No goodwill payment offered at this stage as the fault is not yet confirmed. Customer sentiment recorded as neutral to positive; he was frustrated at the start of the call but was satisfied with the plan by the end. Disposition: technical, broadband intermittent, escalated tier two. Follow up owned by the tier two queue, not by this agent."
  },
  {
    "id": 2,
    "text": "CHAT SESSION SUMMARY. Reference CS-2026-442118. Channel: web chat. Queue: billing. Session length 16 minutes. Concurrent sessions at time of contact: three. Customer opened the chat to dispute a charge of 47.99 taken on the third, which she stated she had not authorised and did not recognise. Identity verified through the account portal, so no additional security questions were required. I located the transaction and confirmed it related to an annual plan renewal rather than a new purchase. The renewal notice had been sent to the email address on file on the twentieth of the previous month, thirteen days before the charge, which meets the fourteen day notice requirement only if counted from the send date rather than from receipt. I checked the delivery log and the notice shows as sent but not opened. The customer stated that she had never received it and that she had intended to cancel before renewal. I applied the following judgement. The notice was technically sent within the required period but by a single day, and there is no evidence she received it. Given the borderline timing and a clean account history of four years with no previous disputes, I approved a full refund of 47.99 under the goodwill threshold available at agent level, which is 75.00 without supervisor approval. Refund processed during the session, reference RF-2026-19883. Funds will reach the original card within three to five working days. I then cancelled the renewed plan with effect from today, so that no further charge is taken, and confirmed that she keeps access until the end of the period already paid for, which is the third of next month. She asked whether the notice period could be changed on her account so that this cannot happen again. I have set the renewal reminder to thirty days and added a second reminder at seven days, and I have confirmed the email address is correct by reading it back. Customer sentiment recorded as positive at close. Disposition: billing, disputed renewal, refunded goodwill, plan cancelled. No complaint raised and no escalation required."
  },
  {
    "id": 3,
    "text": "CASE NOTE. Reference CS-2026-442350. Channel: inbound voice. Queue: billing disputes. Handle time 28 minutes 15 seconds. Customer called regarding three charges appearing on the account across the current and previous billing periods which he believes are duplicates. The amounts in question are 129.50 dated the second, 129.50 dated the ninth, and 64.75 dated the seventeenth. Identity verified. I reviewed the transaction history in full rather than only the disputed items, because a duplicate pattern usually indicates a payment method issue rather than three separate errors. Findings are as follows. The charges dated the second and the ninth are genuinely duplicated. The account holds two active payment mandates, one set up in March last year and a second added in January of this year when the customer replaced his card. The older mandate was never cancelled, so both were collected. The charge of 64.75 dated the seventeenth is not a duplicate; it is a separate part period charge arising from a mid month plan change that the customer requested himself on the fourteenth, and he accepted this once I explained the calculation. Action taken. The older mandate has been cancelled with immediate effect and I have confirmed with the customer which card should remain active by reading back the last four digits. A refund of 129.50 has been raised under reference RF-2026-19941 for the duplicated collection on the ninth. I did not refund the charge on the second because that is the correct scheduled payment for the period. I explained this distinction carefully, since from the customer perspective both look identical, and he confirmed he understood which one was being returned. I also checked the previous six billing periods to establish whether earlier duplicates had gone unnoticed, and found none, because the second mandate was only added in January. The customer asked for written confirmation of the duplicate mandate finding, which I have arranged by email to the address on file. Customer sentiment recorded as negative at open and neutral at close; he remained unhappy that the error occurred but accepted the resolution. Disposition: billing, duplicate mandate, refund issued, mandate cancelled."
  },
  {
    "id": 4,
    "text": "CASE NOTE. Reference CS-2026-442477. Channel: inbound voice. Queue: warranty and repairs. Handle time 19 minutes. Customer called to raise a warranty claim on a unit purchased on the eighth of October, model reference HX-4400, serial number confirmed as 8827-HX-441902. Purchase date verified against the order history, placing the unit at ten months old and therefore within the twenty four month warranty period. Fault described as the unit powering off without warning after approximately forty minutes of use, then refusing to restart for several hours. The customer has observed this on at least six occasions over the past three weeks and the pattern is consistent. Troubleshooting completed during the call. Confirmed the unit is not in an enclosed space and has clear ventilation on all sides. Confirmed it is connected directly to a wall socket rather than through an extension. Confirmed the power adapter is the original supplied unit and not a replacement. Firmware version checked and reported as current. A factory reset was performed during the call and the customer was asked to run the unit for forty minutes afterwards; he called back on the same reference to confirm the fault recurred. On that basis the fault appears to be a hardware thermal cutout rather than a configuration issue, and further remote troubleshooting is unlikely to help. Action taken. Warranty replacement approved under reference WR-2026-06612. A replacement unit will be despatched within two working days on a next day service. The faulty unit must be returned within fourteen days of the replacement arriving, using the prepaid label included in the box. I explained clearly that failure to return the original within that window results in the replacement being charged at full price, because that is the condition most often missed and most often disputed afterwards. The customer confirmed he understood. I also confirmed that the replacement carries the remainder of the original warranty rather than a fresh twenty four months, which is a common misunderstanding. Customer sentiment recorded as positive. Disposition: warranty, hardware fault, replacement approved."
  },
  {
    "id": 5,
    "text": "CASE NOTE. Reference CS-2026-442603. Channel: outbound voice, scheduled callback. Queue: retention and upgrades. Handle time 24 minutes. This was a scheduled callback arising from a web enquiry submitted on the nineteenth in which the customer asked about moving to a larger plan. Identity verified. Current position: customer is fourteen months into a twenty four month agreement on the standard plan at 42.00 per month, leaving ten months of committed term. Usage reviewed across the past six billing periods. The customer has exceeded the included allowance in four of those six periods, incurring additional charges of 18.40, 11.75, 26.20 and 9.50 respectively, a total of 65.85 over six months. This supports the case for an upgrade on cost grounds alone rather than on preference. Options presented. Option one, remain on the current plan and accept the overage charges, which averaged 10.98 per month over the period reviewed. Option two, move to the larger plan at 56.00 per month, an increase of 14.00, with an allowance that would have covered all six periods reviewed with margin to spare. Option three, move to the larger plan and extend the agreement by a further twelve months, which reduces the price to 49.00 per month for the remaining term. I presented all three including the option to do nothing, and I set out the arithmetic for each rather than only recommending one. The customer selected option three after asking whether the extension could be shortened, which it cannot. I confirmed the new monthly amount, the new end date, and the fact that the fourteen day cooling off period applies from today because this constitutes a new agreement. The change takes effect from the start of the next billing period rather than immediately, so the current period bills at the old rate. Written confirmation issued to the email address on file. Customer sentiment recorded as positive. Disposition: upgrade, plan change with term extension, completed on call. A note has been added for the next agent who speaks to this customer, recording that the term was extended today and that the cooling off period runs to the fourth of next month. If he calls to reverse the change within that window it must be actioned without challenge or retention offer, as the cooling off right is absolute and is not a negotiation point."
  },
  {
    "id": 6,
    "text": "CASE NOTE. Reference CS-2026-442718. Channel: inbound voice, transferred from general enquiries. Queue: account security. Handle time 33 minutes 05 seconds. Customer called after receiving a notification of a sign in from a device and location she does not recognise, dated the twenty first at 03:14. She had not attempted to sign in at that time. Identity verified using enhanced checks, as the standard checks are not sufficient where account compromise is suspected. Verification completed using date of birth, the answer to the security question, the last four digits of the registered payment card, and confirmation of the two most recent transactions on the account, all of which matched. Findings. The sign in did occur and was successful. The device is not one previously associated with the account. No changes were made to the account details during that session and no orders were placed. The session lasted four minutes. Two failed sign in attempts were recorded on the preceding day from the same address. Actions taken during the call. All active sessions terminated across all devices. Password reset link issued and the customer set a new password while on the line, which I confirmed by asking her to sign in successfully before we continued. Two step verification enabled and tested with a live code sent to her mobile. The recognised device list cleared so that every future sign in requires verification. A watch flag placed on the account for thirty days, which requires enhanced verification on any contact regardless of channel. I advised the customer to change the password on her email account as well, since a compromised email account is the most common route into a service account, and I explained why rather than simply instructing her. She confirmed she would do so immediately after the call. No financial loss occurred and no refund was required. The incident has been logged with the security team under reference SEC-2026-00418 for pattern analysis, as the failed attempts from the same address suggest a credential stuffing attempt rather than a targeted compromise. Customer sentiment recorded as anxious at open, reassured at close. Disposition: security, unauthorised access attempt, account secured."
  },
  {
    "id": 7,
    "text": "CASE NOTE. Reference CS-2026-442844. Channel: web chat, escalated to voice callback at customer request. Queue: general enquiries. Total handle time across both channels 41 minutes. This contact covered three separate matters and each is recorded below with its own outcome, as a single disposition would not capture the case accurately. Matter one, delivery. Customer reported that order 77-4419082 had been marked as delivered on the fifteenth but had not arrived. Courier records show a photograph taken at the point of delivery which shows a door that the customer confirmed is not hers. This is a misdelivery rather than a theft. Replacement despatched at no charge under reference RP-2026-08871, next day service, no requirement on the customer to wait for the original to be recovered. The courier has been notified of the misdelivery for their own investigation. Matter two, billing. While reviewing the account I noticed a failed payment on the eleventh which the customer was unaware of, as the notification email had bounced. The bounce is due to a typographical error in the email address introduced when the address was last updated in February. Corrected during the contact and read back for confirmation. The failed payment was retaken successfully during the call using the card on file, and I confirmed that no late fee had been applied because the account was within the grace period. Matter three, marketing preferences. Customer asked to stop receiving promotional messages by text while continuing to receive service messages such as delivery notifications. I explained the distinction between the two categories, as customers frequently opt out of everything by mistake and then miss delivery updates. Preferences updated accordingly and read back. Customer sentiment recorded as negative at open, positive at close. Disposition primary: delivery, misdelivery, replacement sent. Secondary dispositions recorded against the same reference for billing correction and preference update, so that the contact is counted once for volume but three times for issue analysis."
  },
  {
    "id": 8,
    "text": "EMAIL RESPONSE. Reference CS-2026-442960. Channel: email. Queue: service credits. Response time 4 hours 12 minutes against a target of 24 hours. Thank you for writing to us about the service interruption you experienced between the twelfth and the fourteenth of this month. I have reviewed the fault records for your address and I can confirm what happened, what you are owed, and what we have done about it. The interruption was caused by a failure at the local exchange which affected 214 properties in your area, including yours. Our records show your service was unavailable from 14:20 on the twelfth until 09:45 on the fourteenth, a total of 43 hours and 25 minutes. This is materially longer than the eight hour target set out in section 6 of your service agreement. Under the terms of that agreement you are entitled to a credit calculated at one thirtieth of your monthly charge for each full day of interruption. Your monthly charge is 54.00, giving a daily rate of 1.80. The interruption covers one full day and a substantial part of a second, and where a partial day exceeds twelve hours our policy is to round up rather than pro rate. The credit due is therefore 3.60. I recognise that this figure will look small against nearly two days without service, and I would rather explain that openly than let it arrive on your bill without comment. The contractual credit is calculated on the subscription cost alone and does not attempt to reflect inconvenience. For that reason I have also applied a discretionary goodwill credit of 25.00, which is separate from the contractual amount and is not something you needed to ask for. The total credit of 28.60 will appear on your next bill, dated the first, and you do not need to do anything to claim it. If you incurred direct costs as a result of the outage, such as mobile data charges you would not otherwise have paid, please reply with the evidence and I will consider those separately under our expenses process. Disposition: service credit, SLA breach, contractual plus goodwill applied."
  },
  {
    "id": 9,
    "text": "CASE NOTE. Reference CS-2026-443087. Channel: inbound voice. Queue: cancellations and retention. Handle time 26 minutes 50 seconds. Customer called to cancel with immediate effect, citing a competitor offer. Identity verified. I asked open questions before making any offer, as the reason given first is frequently not the operative one. The competitor price quoted was 38.00 per month against the 51.00 the customer currently pays. On further discussion two additional factors emerged. The customer has had two unresolved technical issues in the past four months, references CS-2026-398112 and CS-2026-421009, the second of which was closed without a call back that had been promised. He also stated that he had been unaware of a loyalty discount available at his tenure and felt that he should have been told. Both points are fair and both are recorded here without softening, because the retention outcome is less useful to the business than the reason behind it. Position on the account. The customer is out of contract with no exit fee payable, so he is free to leave today. Tenure is five years and two months. Payment history is clean with no missed payments. Offers made. First, an apology for the closed case with no call back, and confirmation that I have reopened case CS-2026-421009 and assigned it to a named engineer rather than to a queue. Second, the loyalty rate applicable at his tenure, which brings the monthly charge to 41.00, plus a fixed price guarantee for eighteen months, which the competitor offer does not include. I set out the total cost over eighteen months under both options so that he could compare like with like rather than headline against headline. Outcome: customer accepted and withdrew the cancellation. New rate effective from the next billing period. I have flagged the closed case without call back to the team manager, since that is a process failure rather than an individual one. Customer sentiment recorded as negative at open, positive at close. Disposition: retention, save completed, loyalty rate applied, related case reopened."
  },
  {
    "id": 10,
    "text": "CASE NOTE. Reference CS-2026-443204. Channel: inbound voice. Queue: complaints. Handle time 37 minutes 30 seconds. This contact has been logged as a formal complaint at the customer request and under our own criteria, as it concerns a repeated failure rather than a single event. Identity verified. Summary of the complaint as stated by the customer, recorded in her own framing rather than paraphrased. She has contacted us on four occasions about the same billing error, on the second, the ninth, the sixteenth and today. On each of the first three occasions she was told the matter would be corrected and that she would be contacted within forty eight hours. She was not contacted on any occasion. The error persists on the current bill. Verification of the account history confirms her account of events. Three previous cases exist under references CS-2026-431188, CS-2026-436702 and CS-2026-440015. All three were closed as resolved. None shows a completed follow up contact. The underlying billing error has not been corrected on any of the three occasions. The customer account is therefore accurate and our records support every element of it. Immediate actions. The billing error has been corrected on the account during this call rather than raised as a request, and I have verified the corrected amount by generating a preview of the next bill and reading the figure back to her. Overcharges across three billing periods totalling 87.45 have been credited in full, reference RF-2026-20114. Formal complaint raised under reference COMP-2026-01173 with the underlying cause recorded as repeated failure to complete follow up actions and premature case closure. This is a process complaint and will be reviewed by the team manager, not by the agents concerned. The customer was given the complaint reference verbally and it will be confirmed in writing today. I committed to a personal follow up call on the twenty ninth, after the next bill is issued, so that she can see the correction has held. That commitment is recorded here with a diary entry against my own name rather than against the queue. Customer sentiment recorded as angry at open, cautiously satisfied at close. Disposition: complaint, billing error, corrected and credited, formal complaint raised."
  }
]