Hi all,
Following up on my earlier posts regarding orders getting flagged the day after launch pre-orders. After an exhaustive 4.5-hour escalation today through frontline sales, a team manager, and finally Executive Complaints (Darlington), here is the exact low-level operational breakdown of what is actually happening behind the scenes so others can avoid losing their queue position.
1. The Root Cause: Catalog & Provisioning Mismatch
• The Glitch: There is an API/catalog sync failure between the customer-facing frontend web portal and EE’s internal backend provisioning engine.
• The Mechanism: The frontend successfully published and permitted the selection of the Unlimited Full Works Plus for iPhone plan (e.g. £38/mo with EE One multi-product discount) alongside Flex Pay for the new devices at launch (13:00). Checkout was completed, agreements signed, and initial pre-order confirmation references issued.
• The Failure: When the order hit the backend fulfillment/order-management layer, the internal provisioning engine failed to validate the SKU/tariff code against the handset device profile. To frontline agent systems, this throws a generic error showing the price plan as "invalid" or "not available with this device."
2. The Operational Flaw: Frontline "Re-Keying" Trap
• The automated trigger: The system generates an automated SMS: "We're sorry, there's an issue with your recent order... contact us... to get your order back on track."
• What frontline agents try to do: Standard sales and digital guides cannot manually edit or patch lines on an in-flight order. Their standard workflow script is to treat the original order as "cancelled/dead" and offer to "sort it" by re-keying a brand-new order from scratch.
• The consequence: Do not let them re-key it. A re-keyed order generates a completely new order ID with a current timestamp. In pre-order logistics, device allocation is tied to order validation timestamps. Re-keying immediately dumps you from the 13:00 launch allocation right to the very back of the queue (which is currently quoting dispatch times in excess of 28 days / well into next year).
3. What Was Formally Confirmed by Executive Complaints
After escalating past the frontline team and team managers to Executive Complaints, they contacted the Digital Sales back-office operations team who confirmed:
• The deal was valid online, but the backend systems failed to present the plan properly to the processing guides.
• This is a known internal configuration issue affecting multiple orders placed on specific tariffs.
• The orders affected by this catalog error are on hold, not hard-deleted.
• The back-office technical teams are working on a fix to correct the plan availability on their side so the held orders can be processed.
4. Advice for Anyone in the Same Boat
• Do NOT accept a frontline re-order: If an agent says "I just need to place a new order for you," stop them immediately.
• Insist the order remains on hold: Request explicitly that your existing order reference is marked "ON HOLD pending back-office Digital Sales tariff resolution" and not cancelled.
• Protect your timestamp: Ask the agent/manager to record on your file that you require your original launch-day pre-order submission timestamp preserved for stock allocation once the technical fix is deployed.
• Get an Executive Complaint reference: If frontline guides push back, open a formal complaint and escalate.
Will update once the back-office team pushes the backend fix early next week
