Buying a phone from a network can create more than one legal relationship. Separate the handset credit, airtime service and sales process before choosing the complaint route.
Key points
- Identify whether the handset agreement is regulated credit.
- Do not assume the airtime and device agreements share the same regulator or ombudsman.
- Preserve the exact document presented for signature.
- Order confirmations, payments and internal status records can matter to contract formation.
- A later “declined” label should be tested against the contemporaneous audit trail.
Map the transaction before arguing about it
List each component: handset/device, airtime/SIM, upfront payment, monthly device instalment, monthly service charge and any insurance/add-ons. Record the legal entity named in each agreement and the complaint body named in its terms.
Regulated handset credit can sit beside an Ofcom-regulated service
Some network handset plans use regulated consumer-credit agreements. That can bring FCA rules and the Financial Ombudsman Service into play for the credit element, while Ofcom/telecom ADR remains relevant to communications-service issues. The correct route depends on the agreement and the substance of the complaint.
What proves that an order was accepted?
There is rarely one magic screen. Relevant evidence can include the credit decision, agreement text, electronic-signature event, upfront payment, order confirmation, dispatch status and internal staff notes. Contract formation is fact-sensitive; a confirmation can be conditional depending on the wording.
When “accepted” and “declined” both appear in the record
Put the records side by side. An internal acceptance code may refer to credit assessment while a later order status refers to fulfilment, so do not assume contradiction until the provider explains the fields. But if staff expressly say the application was successfully accepted and the provider later says it was always going to be declined, that requires a coherent account of what each stage meant and why the consumer was allowed to proceed.
Ask for the transaction-specific audit
Useful records include the loan/finance application, credit and affordability checks where accessible, product eligibility decision, version of the agreement shown, digital signature metadata, order status history, cancellation reason and refund record. A SAR can help obtain personal data within those systems.
Do not let jurisdiction erase the underlying factual problem
A communications ombudsman may not be the correct body to determine a regulated-credit issue; a financial ombudsman may not determine every pure contract claim in the same way a court would. That does not make the disputed facts disappear. Present each forum with the issues it can actually determine and preserve the record for any remaining route.
Start with the documents, not the provider’s later label
A mobile purchase can involve an airtime agreement, a handset credit agreement, an upfront payment and optional insurance or accessories. Read the heading, creditor/supplier identity, amount of credit, repayment schedule and governing terms of each document. A customer-service shorthand such as “Flex Pay”, “device plan” or “upgrade” does not replace the legal document actually presented.
Credit approval and contract formation are related but not identical questions
A credit decision marked “accept” can be powerful evidence of what happened at one stage, but it does not by itself prove that every condition for contract formation and fulfilment was completed. Likewise, a later cancellation status does not prove there was never an agreement. Reconstruct the sequence.
| Event | Why it may matter |
|---|---|
| Eligibility/spend-limit advice | What the consumer was told before ordering and relied upon. |
| Credit search/decision | Shows assessment activity; not automatically final contract acceptance. |
| Agreement presented | Identifies the legal product and terms offered. |
| Electronic signature event | Evidence that a signing process was completed. |
| Upfront payment | May be part of the agreed transaction; check the contract wording. |
| Order confirmation | Its wording may show acceptance or may reserve further checks. |
| Cancellation/decline event | Requires a reason and chronology consistent with the earlier stages. |
A hard credit search is evidence, not a complete legal answer
A hard search can show that a lender carried out a credit application, but it should not be treated as conclusive proof that credit was granted or that a contract became binding. Use it as one part of the transaction chronology alongside the agreement, decision record, payment and confirmation.
If the provider says the order was “always going to be declined”
Compare that explanation with what the consumer was told and what the system allowed to happen. If a customer was told they were eligible, shown a regulated agreement, permitted to sign, charged an upfront amount and sent an order confirmation, the provider should be able to explain which stage remained conditional and why the process progressed that far.
The point is not that every one of those events necessarily creates a binding contract. The point is that the later explanation must coherently account for the contemporaneous evidence.
If “accepted” and “declined” appear in different records
Ask the provider to define the systems and fields. “Credit accepted” may describe lending assessment; “order declined” may describe a later product-eligibility or fraud stage. But if staff expressly confirmed successful acceptance after the order was cancelled, ask what record they relied on and why the provider’s final position differs.
Refund the upfront payment promptly, but keep the evidence
If the transaction is cancelled, preserve proof of any upfront payment and its refund. A refund may restore the money without answering whether the cancellation was contractually or regulatorily justified. Do not let a straightforward refund obscure the separate complaint about the sales/credit process.
Choose the forum issue by issue
| Issue | Likely framework/route to check |
|---|---|
| Regulated handset credit | Consumer-credit rules, lender complaint and potentially Financial Ombudsman Service. |
| Airtime/service billing or telecom contract | Ofcom rules and the provider’s telecom ADR scheme. |
| Personal-data access/accuracy | UK GDPR/Data Protection Act and ICO route. |
| Contract formation/breach claim beyond ombudsman scope | General contract law and, where appropriate, court route. |
A single factual sequence can engage more than one route. Avoid asking one body to determine an issue outside its jurisdiction simply because it already has part of the complaint.
Common provider responses, and what to request
| Provider says | Ask for |
|---|---|
| “You were not eligible.” | The eligibility stage, rule applied and transaction status history. |
| “No agreement was completed.” | Agreement version, signature metadata and contract-execution record. |
| “The confirmation was automated.” | What legal/status meaning that confirmation had in the checkout journey. |
| “The credit team accepted but the order failed.” | The later failure event and contractual basis for cancellation. |
| “We cannot disclose lending criteria.” | You may not be entitled to confidential models, but still ask for your personal data, decision outcome and a sufficient explanation of the transaction. |
Evidence
Build a minute-by-minute order chronology where the sequence is disputed.
Put the sales advice, application, search, decision, agreement, signature, payment, confirmation, cancellation, refund and later staff explanations in timestamp order. Then identify exactly which transition the provider cannot yet explain.
Continue from here
Related telecom guidance
Official sources