Build the template library before you need it
The templates you can send in an incident are the ones approved weeks earlier. A practical starting set, and how to keep it from rotting.
The journal
Notes from the work itself.
What we have learned running a WhatsApp Business platform and an apparel label — written down while it is still specific enough to be useful.
Measuring for a made-to-order piece
Most fit problems are decided at the measuring stage, not in the workshop. How to take measurements that survive contact with a pattern, and what to tell us.
How the OutfitFashion 30-day returns window works
Thirty days from delivery, not from order. What that means in practice, what condition we expect items back in, and how exchanges differ from returns.
Reading delivery and read rates without fooling yourself
Sent, delivered, read, clicked. What each number in a messaging dashboard can support, what it cannot, and the comparisons that quietly mislead.
Collecting WhatsApp opt-in that holds up
Template approval is not consent. What a defensible opt-in record contains, where businesses collect it badly, and why the evidence matters more than the checkbox.
The character budget of a WhatsApp template
Header 60, body 1,024, footer 60. Drawn to scale, the budget is smaller than it sounds — and the constraint is more useful than it first appears.
Why your WhatsApp template was rejected
The rejection reasons we see most often, what each one actually means, and the habits that keep a template library moving through review without drama.
Marketing, utility, authentication: pick the category first
Every WhatsApp template belongs to exactly one category. That single choice sets your review strictness, your content rules and your price tier at the same time.