Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / How Marketing Automation Misses SMS Consent Windows
Transcript
- Lucas: Let me paint a quick scenario. You run a mid-size e-commerce brand, let's call it 'Thread & Tonic' — organic cotton basics, decent repeat purchase rate. Six months ago, you ran a pop-up at checkout: 'Get 15% off when you text us your phone number.' Good conversion. You loaded those numbers into your SMS workflow in HubSpot. And then you just… let it run. Luna: I've seen that exact setup. One welcome text, one abandoned cart reminder, maybe a 'back in stock' alert. Feels clean at first. Lucas: Right. But here's the thing — the legal and relational shelf life of that consent is not infinite. In the US, the TCPA doesn't set a hard expiration date on a one-time opt-in, but the FCC's 2024 ruling on 'prior express consent' basically says that consent is tied to the context in which it was given. If six months have passed and you send a promotional blast without re-confirming, you're in a grey zone. Luna: And the bigger risk might be practical, not just legal. People forget they opted in. A text from a brand they barely remember feels like spam. Lucas: Exactly. There's a study from Tatango — the SMS marketing platform — that found 63 percent of US consumers revoke SMS permission within six months if they haven't received a re-confirmation message. Six months. So your list is quietly rotting, and you don't know it until your opt-out rate spikes. Luna: I remember one retailer — I think it was a DTC supplement brand — they sent a flash-sale blast to a list they hadn't touched in 90 days. Twenty-two percent opt-out rate in 48 hours. They essentially halved their SMS channel overnight. Lucas: That's the nightmare scenario. And the root cause isn't bad intent — it's a workflow design blind spot. Most marketing automation platforms, including HubSpot and Marketo, let you build an SMS journey based on a 'last contact date' or 'list membership,' but they don't natively flag the consent's age. You have to build that logic yourself. Luna: So the fix is basically a 'permission heartbeat' — a recurring workflow that checks the consent timestamp and triggers a re-confirmation before the window closes. Lucas: Yes. And I think the window should be shorter than most people assume. Based on that Tatango data, I'd set it at 90 days. Here's the workflow: You create a custom property on the contact record called 'SMS consent date.' Every time someone opts in, that field gets stamped. Then you build a quarterly workflow that filters for contacts where that date is older than 90 days and sends a single text: 'Still want to hear from us? Reply YES to stay, or STOP to unsubscribe.' Luna: And you pair that with a small incentive, right? A 10 percent off code or free shipping. Because if you just ask for re-confirmation with no value, a lot of people will say no or just ignore it. Lucas: Exactly. One brand I worked with — a skincare subscription company — they sent a 'Do you still love us?' text with a $5 credit. They got a 45 percent re-confirmation rate. And more importantly, the people who didn't re-confirm were suppressed from all future SMS. Their opt-out rate on subsequent campaigns dropped from four percent to under one percent. Luna: That's a massive deliverability improvement. And it protects your sender reputation with carriers, too. High opt-out rates can get you blocked at the network level. Lucas: Absolutely. Now, the counterargument I've heard is: 'We don't want to bother our customers with extra texts. They already gave us permission.' But I think that's a false efficiency. A quarterly re-confirmation text — that's four texts a year. If even one of those prevents a campaign that triggers a 20 percent opt-out, you've saved your list. Luna: And let's be honest — the platforms make it easy to set up, but they don't make it obvious. HubSpot's SMS workflow, for example, has a 'last engaged' filter, but that's based on any interaction, not specifically consent. You have to know to build that custom property. Lucas: That's the gap. The platform gives you the tool, but not the best practice. And in a fast-moving marketing department, nobody stops to audit the consent lifecycle until something goes wrong. Luna: Speaking of tools that help but don't get used — a quick tangent, if that's okay? Lucas: Sure, go ahead. Luna: This whole conversation actually reminds me of something. We put out these episodes every day, try to keep them ad-free, and it's only possible because of listener support. If these marketing conversations have sparked something you've actually used — a workflow tweak, a compliance check — a couple of dollars a month is genuinely what keeps these going. Buy me a coffee dot com slash fexingo. Lucas: Yeah, and it's not about a big ask. It's the people who chip in a little that let us stay independent, not chasing sponsors. So if it's made a difference for you, that link is there. Luna: Alright. Back to consent windows. So let's say you've built that quarterly re-confirmation workflow. What's the next step? Do you also audit your existing list for contacts older than a year? Lucas: You should. I'd run a one-time suppression campaign first. Export all contacts with an SMS consent date older than 12 months, send them a single re-confirmation, and if they don't respond within two weeks, suppress them permanently. It's a one-time list hygiene hit that pays off in the long run. Luna: And after that, the ongoing heartbeat keeps the list fresh automatically. You're not just complying with best practices; you're building a channel that actually works because the people on it want to be there. Lucas: Exactly. And that's the real point. SMS has the highest engagement rates of any channel — open rates above 90 percent within three minutes. But that only holds if the list is permission-based and actively maintained. Let it rot, and you lose the channel's core advantage. Luna: So the takeaway: don't just set and forget your SMS workflows. Build a consent-age filter, schedule a quarterly heartbeat, and pair it with a tiny incentive. Simple to do, but most teams don't. Lucas: And if you're on HubSpot or Marketo, the specific steps are: create the custom date property, build a list-based workflow that checks that date, and use a simple 'reply YES to stay' prompt. Marketo's trigger campaigns can handle this with a 'data value change' on the consent field. HubSpot's workflow tool has a 'if/then branch' based on date properties. Luna: Right. It's not a platform limitation — it's a design decision. And one that can save your deliverability, your sender reputation, and your relationship with customers. Lucas: One last number: the skincare brand I mentioned — after they implemented the heartbeat, their SMS revenue per contact actually went up 18 percent over the next six months. Because the remaining list was engaged and responsive. Smaller list, better performance. Luna: That's the kind of metric that makes the case. You're not losing revenue by suppressing people — you're focusing it. Lucas: Exactly. Next episode, I want to talk about something related: what happens when your SMS consent is obtained via a third-party pop-up or a partner app, and how that changes the compliance picture. Luna: Looking forward to it. For now, check your consent dates.