31 ready-to-send templates across 13 lifecycle flows, a compliance pack built on real TCPA/PDPA discipline (opt-in, quiet hours, STOP in 7 languages), a consent-gated Twilio sender you fully control, plus ROI and segmentation tools. Paste into any provider — or run your own pipeline with your key.
Instant download after checkout · 14-day refund if it's not for you · One-time payment, no subscription
Cart abandonment is where e-commerce loses most of its revenue, and SMS reaches buyers in minutes. But the same speed that recovers carts punishes sloppy programs: wrong consent, wrong hour, one text too many. This kit builds the discipline in from message one.
Every file is usable the moment you unzip: importable templates, a flow blueprint, the compliance gate, the tools, and the honest math. No fluff chapters, no upsells inside.
Welcome with double opt-in, abandoned cart ×3 touches, browse, price drop, back-in-stock, win-back ×2, shipping, delay, delivered, review, replenish, payment recovery, VIP, birthday, referral — each with send timing, goal, and compliance notes.
CSV import-ready · character budgets verified (GSM-7 single segment) · merge-field based
Every standard e-commerce flow mapped: trigger, touches, timing, suppression rules, and the one goal each flow may have — plus 1:1 instructions for Twilio, Postscript, Klaviyo, or manual sending.
Frequency caps · rest periods · vertical variants for fashion, beauty, supplements, home, electronics
A pre-flight checklist in the TCPA / PECR / PDPA tradition: logged consent with source and timestamp, double opt-in, quiet hours per region, instant STOP, monthly audit — and the migration checklist for stores that just left a dead platform.
Operational best practice, not legal advice — the kit says so plainly
Web-form disclosure, double opt-in copy, and STOP / HELP / confirm keywords for EN, ES, PT-BR, DE, FR, IT and TH — with the keyword master table to map in any provider.
Encoding-aware: GSM-7 vs UCS-2 explained, Thai character budget included
flow-send.mjs (zero npm dependencies, Node 18+) checks every send against the consent log, the STOP list, quiet hours, and a 2-per-week cap — then calls the Twilio API with your key. Dry-run plan mode is the default.
You own the pipeline and the log — your number, your sender of record
An offline calculator with conservative, editable recovery-rate defaults — and a sanity panel that tells you when your assumptions are flattering you. Plus 12 pre-built segments with rules and suppression logic.
Plans with your numbers, not our promises — nothing is a guarantee
Already on Postscript/Klaviyo/Omnisend? Import the templates into their flow editors with the blueprint's timing. Want your own pipeline? Configure the Twilio sender with your key (SETUP.md walks both).
Install the right opt-in language, create your consent log, set quiet hours. The checklist takes ~15 minutes and every later send depends on it — by design.
Run plan mode and read the pass/skip reasons per message, send yourself one test per flow, then schedule. Measure with the calculator's real inputs at day 30.
Secure checkout by Stripe · cards, wallets and local methods · your download link works forever via your email + password
No, and no. The compliance pack is operational best practice compiled from public regulator and carrier guidance (TCPA, PECR, PDPA traditions). It is not legal advice and cannot guarantee any legal outcome. It does give you the records and habits you'd need to show you ran a clean program — and for your specific market, run the final wording past a lawyer.
All of them, by design. The templates are plain text you paste into Postscript, Klaviyo, Omnisend, TxtCart or anything else. The included sender uses the Twilio REST API with YOUR account and key (A2P 10DLC registration for US traffic is covered in SETUP.md). If you have under ~200 contacts, the manual path works fine too.
Not for Path A (existing SMS app): it's copy-paste and flow settings. For Path B (your own Twilio pipeline): you run one command per send batch — if you can use a terminal, you can run it. The tool has zero npm dependencies; Node 18+ is all it needs.
Free lists give you messages; this gives you the system around them: timing and suppression logic, consent records, quiet hours, frequency caps, segment rules, and a sender that enforces all of it. The templates alone are maybe 30% of the value.
Plan with the calculator's conservative defaults (3% / 1.5% / 1% cart-touch recovery — editable), then trust your own dashboard. We promise no numbers. If a partner guarantees marketing results, keep your wallet closed.
14 days, no interrogation: reply to your Stripe receipt within 14 days and you get your money back. The download stays yours to delete.
Yes: the consent pack includes Thai opt-in copy and the ยกเลิก keyword, quiet hours cover Thailand, and the PDPA-style consent discipline is in the checklist. Templates are English by default with merge fields; the swap guide shows how to localize while keeping the character budget.