“We’ve kept it for you” sounds friendly in a basket reminder. It also makes a promise. If the shop has saved only the product links, a customer may return expecting stock that has already sold out.
Before writing the email, ask what the system actually preserves: the basket contents, a price, a discount, stock, or none of these reliably across devices. The wording should describe that behaviour precisely.
Give each promise a technical owner
Imagine a small shop selling handmade mugs. Its reminder links back to a basket, but inventory is not allocated until payment. A useful message might say, “Your basket is saved so you can pick up where you left off. Availability and prices are confirmed at checkout.” That is a sample, not a claim about any particular platform.
If the store genuinely reserves an item, establish when the reservation starts, when it ends and which time zone applies. The email team should not invent a countdown because the template includes one. Someone responsible for checkout needs to confirm that the stated deadline matches the actual release of stock.
Make the return visit work
Test the link after the item has sold out, after a variant has changed and after a discount has expired. The shopper should see an explanation of the current situation instead of a broken page or an unexplained price jump. A reminder is only helpful if the route back survives ordinary changes in the catalogue.
Keep the main action clear and provide an easy way to stop reminders. If a customer has already purchased through another session, check whether your system can suppress the follow-up before it is sent.
Review the email as a customer
Read every sentence as a factual statement about the order. “Saved,” “reserved,” “discounted” and “waiting” are not interchangeable. Accurate copy can still be warm: explain what is available, show the product clearly and let the customer decide without an invented obligation to buy.