A telecom sale leaves more than one record. Treat it as a transaction audit: identify the records that should explain offer, disclosure, consent, order, activation and billing.
Build an evidence stack, not a single-document case
No single artefact necessarily tells the whole story. A contract summary can show key terms; a call recording can show what was said; an order record can show what the system submitted; an activation record can show what was provisioned; and the first bill can show what was actually charged.
Key points
- Sales call or chat: what was represented.
- Contract summary/information: what was supplied before agreement.
- Order audit: what the sales system submitted.
- Confirmation: what the provider says it accepted.
- Provisioning: what service actually went live.
- Billing: what the account was charged.
Records that may exist
Depending on provider, channel and retention, look for call metadata/recordings, chat transcripts, adviser notes, interaction codes, package configuration, eligibility checks, address/service-availability checks, personalised speed estimates, contract-summary generation and dispatch logs, order IDs, checkout events, credit-search records, confirmation emails/SMS, equipment dispatch, activation/provisioning events and complaint notes.
Do not state that every provider is legally required to retain every one of these records indefinitely. Ask what exists, what was searched and what retention rule applies to anything no longer held.
Request evidence by disputed fact
Instead of asking for “all records”, connect each request to a fact. If the dispute is the monthly price, request the point-of-sale price fields and contract summary. If it is consent, request the consent event and preceding summary-dispatch record. If it is a credit search, request the search date, type and decision trail. If it is activation, request the promised and actual activation records.
This makes omissions easier to identify and the eventual complaint easier to explain.
Use a SAR precisely
A SAR gives access to your personal data and supplementary information. It can capture personal data in call recordings, notes, account logs and order records. But the right is to the personal data, not automatically to every complete original document in the format you name. The provider must carry out a reasonable and proportionate search under the current UK right-of-access regime.
Create a transaction matrix
A simple matrix often exposes the dispute quickly:
| Stage | Provider record | What it should answer |
|---|---|---|
| Offer | Quote/package selection | Price, product, extras |
| Disclosure | Contract summary/information | What was supplied before consent |
| Consent | Call/checkout audit | What the customer agreed to |
| Order | Order ID/confirmation | What was accepted |
| Provision | Activation/network records | What went live and when |
| Bill | Invoice/ledger | What was charged |
Useful wording
Ask for the audit trail
“Please provide the personal data and transaction records that show the package presented, contract-summary/information dispatch, the consent event, order acceptance, activation and first billing. Where a requested record is no longer held, please identify the relevant retention position and what alternative audit data remains.”
Ask for identifiers and timestamps, not just screenshots
The strongest audit trail usually links records together. Ask for the order or interaction reference, account number used at the time, date and time of the sale, channel, adviser identifier where held, product code or package version, contract-summary generation time, confirmation time and activation/provisioning references. These details let you test whether separate extracts genuinely belong to the same transaction.
A cropped screenshot saying “accepted” or “completed” may be useful, but it can be ambiguous without the field names, surrounding events and timestamp. Ask the provider to explain what the status means in its system and which event changed it.
A missing call recording is not the end of the evidence trail
Providers do not necessarily retain every recording indefinitely, and a subject access request gives you access to your personal data rather than an automatic right to a particular original file. If audio no longer exists, ask about call metadata, interaction notes, wrap codes, order-event history, contract documents, outbound emails or texts, adviser notes and any quality/compliance record connected with the transaction.
If the provider says a recording existed but was deleted, ask for the retention rule that applied, the deletion date if known and whether a transcript, summary, quality score or linked interaction record survives. The aim is to establish the evidential position, not to assume that absence of audio proves either side's account.
Keep your request proportionate and searchable
A focused evidence request is often more effective than asking for “everything”. Give the date range, phone number used, account/order references, product involved and the disputed event. If you use a subject access request, describe the categories of personal data you want and likely locations, for example call recordings, account notes and sales audit entries around the order date.
Use evidence to answer a specific proposition
For each disputed point, write down the provider's proposition and the record that would logically support it. “You agreed to a 24-month term” calls for the pre-contract terms and consent event. “The service began on 5 May” calls for provisioning and activation records. “We warned you about the price rise” calls for the contract information actually supplied before agreement. This stops a dispute being drowned in documents that do not answer the issue.
Evidence worth keeping
Continue from here
Related telecom guidance
Official sources
Check the rules behind this guide
These are official or primary sources for this topic. Rules, scheme terms and deadlines can change, so check the live source before relying on a formal time limit or procedure.