Crate & Barrel3
Support & Service · observed September 2026 — a CX field note: what happened, the pattern behind it, and the principle it teaches.
“There was an error. Please Try Again.” — for days
A simple email change fails with the same generic message every time: no reason, no error code, no path forward. Days of retries — incognito windows, different browsers — ruled out everything on the customer's side, and the message still offers nothing but “try again,” which by then is a proven dead end.
The principle: An error message is an interface, not an apology. Say what failed, whose fault it is, and what to do next — or one bug becomes an endless loop.
Support that declares victory — repeatedly
Text support said it was fixed “now.” Then to wait 48 hours. Then to wait until a specific date. Each promise expired without the fix, and each new contact restarted the script from the top. A promised resolution that doesn't arrive teaches the customer to distrust the next one — and the brand behind it.
The principle: Never close the loop before the problem closes. Verify the fix, then say it's fixed — a slow honest answer beats a fast false one.
The official remedy: create a new account
After the lowest possible mark on their own CX survey, the response was a suggestion to create a new account — abandon the history and settings attached to the old one so the company wouldn't have to repair its own bug. That outsources the full cost of the defect to the person it already hurt.
The principle: When your system fails, the remedy must cost you, not the customer. “Start over” isn't support — it's surrender, billed to the user.