Reframing a Retail Reservation Flow for The Mobile Shop

CONTENT DESIGN · UX WRITING · MULTI-TOUCHPOINT

CONTEXT 

Brand: The Mobile Shop
Parent Company: Loblaws
Platform: Web flow + email
Audience: New device customers

TL;DR

The Mobile Shop's online reservation flow had been built with standard e-commerce language — including a "cart" — but there was no payment step anywhere in the flow. Payment happened in store. For users expecting to purchase online, this created confusion at every turn.

I renamed "cart" to "reservation basket" and rewrote the entire flow — six steps online plus seven emails — around a single consistent framing: this is a reservation, not a purchase. The word "reservation" appears at every step deliberately, so users internalize the mental model before they reach a moment that might confuse them. The email system covered every outcome: one confirmation, five error states for different availability scenarios, and one status update for items being transferred from another location.

THE PROBLEM

The Mobile Shop is a wireless retailer operated by Loblaws across Canada. During the pandemic, the business introduced an online reservation system so customers could select a device ahead of visiting a store — to control the flow of customers, save time at the counter and reducing in-store wait times.

The problem was that the flow had been built using standard e-commerce language. Users encountered a "cart," moved through a "checkout," and completed what looked like a purchase — but there was no payment step anywhere in the flow. Payment happened in store. For a customer expecting to buy online, this created confusion at best and distrust at worst.

Beyond the naming issue, the flow had additional complexity: after submitting a reservation, a Mobilist would call the customer to process a Zendesk ticket before a confirmation email could be sent. If users didn't understand why they were being called or what they were waiting for, they might show up at the store before their reservation was ready.

THE APPROACH

The core strategy was to use the word "reservation" so consistently and deliberately throughout the flow that users would internalize the mental model before they reached a step that might confuse them. Unlike "cart" — which carries a strong purchase expectation — "reservation" signals that something is being held, not bought. Payment is implied to come later.

"Cart" became "reservation basket." Every CTA, heading, confirmation, and email was rewritten around this framing. The word "reservation" appears at every step — not as repetition for its own sake, but as a continuous signal about what kind of transaction this is.

Cart → Reservation Basket 
"Cart" implies a purchase is coming. "Reservation basket" signals the user is holding something — not buying it yet.

THE FLOW 

The reservation experience spanned six steps online, followed by several email outcomes. Each step required copy that oriented the user, set expectations for what came next, and reinforced the reservation — not purchase — framing.

1. Add to basket
Entry point. "Basket" rather than "cart" signals from the first interaction that this is not a standard e-commerce flow.
2. Select reservation details
Colour, memory, carrier, and store selection. The word "reservation" is introduced here to begin building the mental model.
3. Review reservation details
CTA reads "Add to basket" — deliberately held back until this confirmation step so users understand their item is not reserved until they explicitly confirm their choices.
4. Your reservation basket
CTA reads "Continue reservation" — reinforcing the framing and signalling the process is not yet complete.
5. Complete your reservation
Name, email, and phone number form. CTA reads "Reserve now" — making clear that submission is the moment the reservation becomes real. Next-steps copy is introduced here so users know what to expect after they submit.
6. Reservation submitted
Confirmation screen with reference number. Next steps are repeated — a deliberate redundancy to reduce the chance of customers arriving at the store before their reservation is processed.

THE MOBILIST PROBLEM 

After submission, a Mobilist — or store specialist — would call the customer to create the ticket in the backend system before the confirmation email could be sent. This step was non-negotiable, but it couldn't be explained in technical terms to the customer.

The solution was a single line of copy that made the call feel like a benefit rather than a process requirement:

 Here's what you can look forward to next:

- A Mobilist™ will call you to fast-track your pick up.
- You will receive an e-mail when your reservation is ready.
- Bring your reference number to your selected store to pick up your item(s) and pay.

"To fast-track your pick up" reframes a mandatory backend step as something done on the customer's behalf. It's accurate — the call does enable a faster pick-up — without exposing unnecessary technical detail.

THE EMAILS

The reservation flow required seven distinct email scenarios — one confirmation, one update and five error states, each addressing a different reason a reservation might not proceed as expected. Together they form a complete error state content system: every possible failure mode mapped to a specific message, calibrated to the severity of the situation and the customer's likely emotional state. Writing five variations of bad news — each distinct, each accurate, each designed not to frustrate a customer who just completed a multi-step flow — was a systems problem as much as a writing problem.

The central content challenge was consistency of tone across very different situations. A customer whose item needs to be transferred from another store is in a different position than one whose reserved item sold out during the reservation process — the language needed to reflect that without tipping into alarm or indifference. Every error email leads with the subject line "Your reservation with The Mobile Shop requires your attention" to keep the opening neutral, then calibrates the body copy to the specific scenario.