Redesigning SMS tracking for clearer, timely notifications—Catherine Bryce Skip to main content
Catherine Bryce Knowledge systems · Information architecture · AI enablement

Redesigning SMS tracking for clearer, timely notifications

Problem

SMS tracking updates used internal operations language, shared copy with web and email, and had a 160-character limit. They were about to launch for the holidays.

My role

Content lead, working with the product owner and solutions architect.

The decision

Push back on "ship as-is." I built a case with an audit, a competitive analysis, and a prototype, and took it to leadership.

Result

18,000+ clearer messages sent in the first 2 days of launch.

Before and after

Phone showing the original terse tracking message
Before: an internal scan event, sent as-is.
Phone showing the redesigned tracking message with merchant name, new delivery date, and opt-out
After: merchant name, what changed, and what to do next.

The hard call: not accepting "do nothing"

The product owner and solutions architect were hesitant: technical limits, no budget for big changes, and worry about reworking the messages. I audited every message across web, email and SMS and showed that unclear SMS would mean frustrated customers and more support calls.

Workshop scoring board rating the existing messages, average score 4.2 out of 10
Team scoring of the existing messages: 4.2 out of 10.
Competitive analysis table scoring Canada Post against seven other delivery services
Competitive analysis: Canada Post against seven other carriers.

What changed within the constraints

  • Nearly doubled the character limit, negotiated with the product owner and architect.
  • Overrode key event descriptions and added the merchant name.
  • Added support guidance where customers would otherwise get stuck.
Miro board used to collaborate on the final SMS prototype
Async reviews in Miro kept decisions moving before the holiday deadline.

Results

18,000+
Clearer messages sent in the first 2 days
~2×
SMS character limit, within the same system

It also set a precedent for content governance: teams now treat message clarity as part of launch, not an afterthought.

← All projects Next: Chatbot fallback redesign →