Somewhere in your automation platform is a message about to be sent, and a decision that gets less thought than it deserves: does this go out as a text or an email? Most businesses answer by habit, or worse, by both-every-time. The channels get treated as interchangeable pipes, when they are actually different rooms in the customer's life with different rules posted on the door.
Getting the routing right is not a nicety. SMS misused burns the hottest permission a customer can grant. Email misused just gets ignored. The asymmetry of those failure modes is the beginning of the framework.
Three questions route every message
Urgency: does this message matter in the next few hours? Appointment reminders, technician-on-the-way notices, a reply to an inquiry made minutes ago, a schedule change for tomorrow morning. These are texts, because texts are read in minutes and email is read at email time, which might be Thursday. Send the non-urgent by SMS often enough and you teach the customer that your texts can wait, which destroys the channel's one superpower.
Depth: does this message need space? Quotes with context, onboarding maps, seasonal advice, anything with attachments, anything the customer might forward to a spouse or re-read next week. These are emails, because email is where documents live and where forwarding is natural. A five-part text thread carrying what should have been one clean email reads as chaos.
Permission: what did the customer actually agree to receive, on which channel? SMS consent and email consent are separate grants with separate legal regimes, and the texting rules are strict enough that the conservative reading is the only sane one. Transactional service messages to a customer who gave their number in the course of business sit on firm ground; promotional texts require explicit, documented opt-in; and every text needs a working way out. Permission is not a checkbox at signup, it is an ongoing read of what the customer treats as welcome.
The coordination layer most setups skip
Routing individual messages well is half the job. The other half is making the channels aware of each other, because the customer experiences them as one relationship.
That means sequencing, not duplicating: the quote goes by email, the did-you-see-it nudge two days later can be a text, and a reply to either stops both. It means a shared quiet-hours and frequency budget across channels, so a customer never gets an email, a text, and a call before lunch. And it means every message, whatever the channel, writes to the same record, so the human who eventually picks up the thread sees the whole conversation instead of one channel's half. This coordination is precisely what a real automation layer provides and what platform-by-platform setups structurally cannot.
Where each channel is quietly underused
Two opportunities show up repeatedly in audits. Businesses under-text on service logistics: confirmations, reminders, arrival windows, review links after a completed job, the operational messages customers actively want as texts. And they under-email on substance: the useful seasonal note, the plain-language explainer that makes the next upsell feel like advice, the nurture that keeps unclosed quotes warm. The pattern is the same mistake twice: promotional instincts hogging both channels while the service messages that build trust go unsent.
The third channel: when the message should be a call
The framework has a third output that neither inbox handles: some messages should be a human voice, and the routing logic ought to know it.
The tells are consistent. Anything with genuine emotional weight, a complaint response, a serious service failure, bad news about scope or timeline, belongs to voice, because text of any kind reads colder than intended exactly when warmth matters most. Anything requiring negotiation or judgment in real time, where the next sentence depends on their last one, outgrows asynchronous channels quickly; three rounds of carefully composed texts accomplish what ninety seconds of conversation would have. And the high-stakes moments in a customer's lifecycle, the big quote's follow-up, the save conversation when a longtime account wobbles, deserve the effort signal that only a call carries. Everyone knows a call costs more attention than a template, which is precisely why it lands differently.
Automation's role in these moments is not to send the message but to arrange the human one: detect the trigger, create the task, propose times, place the context in front of the caller. The customer experiences a personal call that arrived at a suspiciously perfect moment; the operation experiences a task queue rather than a memory test.
The send log audit from above gains a third column, then: messages that went out as text or email that a voice should have carried. The complaint answered by template, the churn-risk touched by newsletter. Those are not channel mistakes; they are relationship mistakes, and they are the most expensive rows in the log.
Reading your own send log
The fastest audit is to pull last month's outbound messages and sort them against the three questions. Urgent things sent by email, deep things crammed into texts, anything promotional sent by SMS without explicit opt-in, and any day a customer got both channels on the same topic within hours. Each miss is fixable in configuration; the win is a customer who learns, from experience, that your texts are always worth opening and your emails are always worth something.
We design channel routing as part of every messaging system we operate, including the consent handling and the coordination rules. If your current setup treats SMS as cheap email, book a review before the channel teaches your customers to ignore it.