Why Shopify merchants leave Postscript
Cost visibility during sale weeks tops complaints — cart recovery SMS pays for itself; fourth promotional text in five days does not, but bills the same. Email gap is structural: Postscript is SMS-native, so stores run Klaviyo or Shopify Email separately — duplicate suppression mistakes send text and email cart recovery within an hour.
Attribution arguments flare when finance compares SMS-attributed revenue against message spend and finds 0.8x ROAS on blasts but 4x on automations — yet volume skews toward blasts because they are easy. Compliance anxiety during list imports or keyword changes pushes risk-averse teams toward Attentive's enterprise hand-holding.
Postscript migration checklist
- Export SMS subscribers with consent timestamp, source, keyword history.
- Document active automations — cart, browse, back-in-stock, campaigns.
- Choose port vs new short code — legal review for TCPA continuity.
- Pause Postscript promotional sends during migration window.
- Rebuild cart SMS on new platform with purchase suppression.
- Align email platform suppression — one owner per trigger type.
- Test two-way reply handling if customer support relies on SMS replies.
- Monitor opt-out rate first 30 days — migration fatigue spikes complaints.
Merchant scenario: beauty brand's $4,200 BFCM SMS bill
A $95k/mo skincare shop ran Postscript hard through BFCM — four promotional blasts, daily cart nudges, VIP early access texts. SMS attributed $31k revenue but message costs hit $4,200 for November alone. Finance asked whether Klaviyo SMS consolidation or stricter frequency caps made more sense than switching entirely. They kept Postscript but moved email winback to Sequenzy, implemented 72-hour promotional caps, and suppressed anyone who received email cart recovery that day. December SMS COGS fell 38% with flat recovery revenue.
90-day rollout: Postscript to Klaviyo SMS consolidation
Weeks 1–2: Export SMS consent with keyword history. Map Postscript automations to Klaviyo flow equivalents. Identify promotional sends to cut, not migrate.
Weeks 3–6: Rebuild cart and back-in-stock SMS in Klaviyo with shared email suppression. Test checkout events against email flows.
Weeks 7–10: Port number or warm new sender. Reduce blast volume 50% during transition.
Weeks 11–12: Compare revenue per message and opt-out rate against Postscript baseline. Cancel Postscript only after two clean promotional cycles.
Margin math: SMS ROAS by message type
Split automations (cart, shipping, back-in-stock) from campaigns. A $2,800/mo Postscript bill where automations return 5.2x and blasts return 0.9x means the fix is frequency discipline, not necessarily platform change. Klaviyo consolidation saves duplicate suppression labor — model 3 hours/month ops time at $70/hr = $210/mo hidden savings plus reduced double-send complaints.
Failure rehearsal: Postscript exit risks
Email+SMS pileup. Cart email and cart SMS fire within 30 minutes from different platforms. Document one owner per trigger.
Port-week deliverability dip. Plan reduced volume; do not run biggest promo during port.
Consent gap on import. Never text imported subscribers without TCPA source validation.
Post-migration optimization: SMS frequency discipline
Most Postscript exits that succeed do not require leaving — they require frequency caps. Document promotional versus automation revenue split monthly. If blasts return under 1.2x ROAS for three consecutive months, cut blast volume before evaluating Attentive or Klaviyo consolidation. Merchants who leave Postscript for cost reasons often recreate blast-heavy habits on the new platform within two quarters. The platform changes; the behavior does not. Set hard caps: maximum two promotional texts per subscriber per month, 72-hour gap after cart recovery SMS, suppress anyone who received email cart same day. These rules travel with you regardless of ESP.
Coordinate with email platform using shared suppression spreadsheet during first ninety days: column for trigger type, column for email owner, column for SMS owner, column for quiet hours. Postscript plus Sequenzy split works when the spreadsheet exists; fails when each platform optimizes channel metrics independently. Weekly fifteen-minute review of opt-out rate and revenue per message type catches drift before BFCM invoice shock repeats.
Integration audit: Postscript dependencies
Before disconnecting Postscript, inventory every Shopify flow, Klaviyo segment, Gorgias macro, and Recharge webhook referencing Postscript subscriber tags or SMS events. Popup tools may pass UTM parameters tied to Postscript keyword campaigns — update before canceling. Subscription apps sending Postscript shipping notifications need replacement on new SMS platform. Loyalty apps triggering SMS on points earn may integrate only with Postscript — map API dependencies. Two-way SMS customer support workflows in Gorgias or Zendesk break during port unless reply routing is reconfigured on Postscript replacement.
Integration dependency audit before Postscript disconnect
Platform exits fail operationally when connected apps keep pushing data into a system you partially deactivated. Before disconnecting Postscript from Shopify, inventory every integration: subscription tools, loyalty apps, review platforms, helpdesk systems, popup capture tools, and SMS coordination partners. For each integration document data direction, events triggered, segments or tags modified, and business criticality. Critical integrations must reconnect on the replacement platform before core automations go live. Low-value integrations from deprecated apps should sunset rather than migrate — most merchants accumulate integration debt that amplifies migration risk beyond the core SMS economics transition itself.
Capture tools feeding Postscript list IDs require theme and checkout audit. Grep storefront theme files, checkout extensions, and post-purchase pages for hardcoded list identifiers or webhook URLs pointing at Postscript. SMS coordination with email recovery needs documented suppression owner per trigger type — email platform and SMS platform optimizing independently creates customer complaints within days of overlap. Export UTM and campaign naming conventions if analytics dashboards depend on Postscript campaign structure; attribution reporting resets during migration quarter unless naming discipline transfers deliberately.
Quarterly optimization after leaving Postscript
First thirty days post-migration focus on suppression integrity and deliverability stability. Days thirty through ninety focus on revenue optimization by flow type. Archive Postscript baseline metrics during migration — attributed revenue by automation, send volume, complaint rate, recovery timing — and compare weekly against new platform performance. Cart recovery should reach parity within two weeks; winback and replenishment should exceed old platform performance if migration rationale was capability upgrade rather than pure cost reduction. Underperformance triggers suppression audit before creative audit — overly aggressive recent-buyer exclusions silently prevent enrollment more often than weak subject lines.
Segment hygiene at day sixty prevents repeating billing or deliverability problems under new platform model. Sunset unengaged contacts regardless of how new platform bills — per-contact, per-send, or flat tier. Quarterly review documents which automations required manual intervention versus ran untouched; increasing untouched percentage indicates playbook stabilization. Deliverability seed tests at day thirty and ninety on Gmail and Outlook catch reputation issues before they compound across peak promotional calendar.
Building the business case and choosing replacement timing
Finance approves migration with conservative revenue projections, not feature checklists. Present twelve-month cost of staying on Postscript including platform fees, operator labor, agency support, and opportunity cost of flows the current platform cannot run. Present migration cost: labor, agency rebuild, deliverability ramp risk, and three-month conservative incremental revenue projection from flows enabled on replacement platform. Break-even month calculation determines urgency — fee-only savings with twelve-month payback rarely justify migration; revenue lift with four-month payback usually does. Negotiate with Postscript once before migrating if contract renewal is near; documented competitive quotes sometimes reduce renewal cost enough to fund hybrid improvement without full exit.
Replacement timing should avoid peak revenue weeks — post-BFCM January, post-Valentine March lull, mid-summer for seasonal categories. Never port SMS numbers during highest promotional month. Never run parallel cart recovery through busy sale weekend without named kill-switch owner available in real time. Migration is operational project with revenue risk; schedule it deliberately rather than reacting to invoice frustration with rushed cutover that costs more in duplicate sends and deliverability damage than platform fees ever did.
Operator playbook: who owns what after migration
Every migration succeeds technically and fails organizationally when ownership is unclear. Assign named owner for: welcome and post-purchase copy edits, cart recovery timing and discount escalation rules, winback and replenishment calendar, popup and capture integration health, SMS compliance and opt-out monitoring, deliverability and complaint rate review, and platform billing audit. One person can own multiple roles on small teams but names must exist in writing — not "marketing" as abstract entity. During first ninety days post-migration, owner sends weekly three-line status to leadership: attributed revenue versus baseline, any duplicate-send incidents, and planned flow changes next week. This rhythm catches drift before it becomes quarterly surprise.
Agency relationships need explicit scope reset after migration. If agency maintained previous platform flows, clarify whether agency rebuilds on new platform, trains internal owner, or exits automation scope entirely. Hybrid agency-internal ownership fails when both assume the other edits suppression rules before sale week. Document which flows agency may touch without approval versus which require internal sign-off — typically cart discount escalation and winback offer depth are internal decisions while template formatting is agency-appropriate. Contractor access should expire automatically ninety days post-migration unless renewed deliberately.
Deliverability and compliance continuity
Platform migration is deliverability event even when sending domain unchanged. New ESP routes mail through different infrastructure with different reputation pools. Ramp plan: days one through seven send only to engaged forty-five-day openers at fifty percent of normal campaign volume; days eight through fourteen expand to ninety-day engaged at seventy-five percent volume; day fifteen onward resume normal segmentation if complaint rate stays below threshold. Cart and transactional automations can run at full volume earlier if enrolled segments are purely behavioral purchase triggers rather than bulk marketing lists — but monitor complaint rate daily regardless.
Compliance continuity for SMS migrations requires legal review of exported consent records before first send on new platform. Document opt-in source, timestamp, and keyword for every SMS subscriber. Exclude records with ambiguous consent rather than risk TCPA exposure — losing ten percent of list is cheaper than single class-action exposure. Email marketing consent similarly requires documented source; GDPR and CAN-SPAM both care about provable opt-in even when platforms technically allow import. Archive consent export files seven years minimum. Unsubscribe and preference center links must work before any broadcast — test on mobile devices where eighty percent of Shopify customers read email.
Revenue attribution reset and reporting discipline
Accept attribution reset during migration quarter — comparing new platform attributed revenue against old platform last-quarter numbers is directionally useful but not pixel-perfect. UTM schemas, attribution windows, and click-definition differ across platforms. Build new baseline from week six onward rather than demanding week two matches old platform peak. Track flow-level revenue weekly: welcome, cart, browse, post-purchase, winback, replenishment, campaigns — each should trend independently. If total attributed revenue rises but cart recovery falls, investigate suppression collision before celebrating aggregate number.
Finance reporting should separate platform cost as percentage of attributed email revenue monthly — target under three percent for mature DTC, under five percent during growth phase, investigate above seven percent regardless of platform choice. Include operator labor hours in total cost of ownership calculation quarterly. Platform that saves two hundred dollars monthly but adds eight hours maintenance is more expensive than platform costing two hundred more monthly with two hours maintenance. Migration business case validation happens at day ninety with real numbers, not projected numbers from sales demos — update internal ROI model with actuals and decide whether to deepen investment in chosen platform or plan next transition if goals missed.
Keyword campaign sunset inventory
Postscript keyword campaigns accumulate over years — BFCM2022, SUMMER15, COLLAB_X — each may still be printed on packaging or influencer content. Before canceling Postscript, inventory active keywords with physical-world references. Port or redirect keywords to new SMS platform or influencer content continues driving opt-ins to dead keyword. Legal and marketing both care about this inventory; technical migration teams often miss it until influencer posts broken keyword link mid-campaign.
Postscript shipping notification automations may integrate with Recharge or Skio — map subscription shipping SMS dependencies before port. Subscribers expect shipping texts; accidental silence during port week generates churn in subscription base separate from marketing SMS concerns.
Document quiet hours and frequency caps from Postscript before migration — these operational rules are not automatic defaults on Klaviyo SMS or Attentive and must be manually configured on replacement platform during rebuild week. Export Postscript analytics CSV for trailing twelve months before cancellation; historical revenue-per-message data informs frequency cap decisions on new platform.