SMS deliverability, spam filters & opt-out

When customers do not see your texts, it is rarely one simple bug on our side. Inbox placement depends on several things at once: how you write and send messages, carrier and registry rules in the United States (including 10DLC), and how each person’s phone treats unknown numbers, such as filters for unknown senders, spam folders, and whether your number is saved as a contact. RouteFlow SMS runs 10DLC registration for you and processes inbound opt-out replies automatically (for example STOP and END). You still need to send clear message content that states who you are and includes the opt-out wording carriers expect. Even with correct setup, no platform can guarantee that every message appears in the main inbox on every device.

Opt-out, STOP, and why it matters

For business texting, a clear opt-out path that you honor is part of carrier rules, customer expectations, and long-term deliverability. It is more than a small legal footnote. When people feel trapped or misled, they report spam. Reports and blocks hurt your numbers’ reputation and can lead to filtering or suspension of traffic.

RouteFlow SMS processes inbound opt-out keywords for you, including STOP, END, and other supported keywords. You do not need to track each keyword reply by hand in a spreadsheet. You still need the right wording in outbound messages so people know they can opt out and so your traffic reads as normal, compliant business messaging.

What to do in practice

• Include opt-out language in your templates. Use plain wording such as “Reply STOP to opt out” or “Reply STOP to unsubscribe” where it fits your program. Exact phrasing may depend on your registered campaign type. Align that wording with your RouteFlow onboarding team and your counsel.
• Repeat when it fits the conversation. For recurring or promotional-style programs, include opt-out language in the first message and again when it still makes sense for the customer experience, per your use case and legal guidance.
• Respect the platform’s opt-out state. RouteFlow enforces opt-outs for supported keywords. Your team should not try to work around that from other channels, for example by putting someone back on marketing texts without new consent.
• Separate operational from promotional where it makes sense. Urgent job updates (“We’re on the way”) are different from marketing blasts. If a customer has opted out of marketing, do not blur the line in a way that looks like you are getting around their choice without fresh consent.
• Train your team. Everyone with access to the inbox should understand how opt-outs work in RouteFlow and when not to restart messaging without documented consent.

This article is practical guidance, not legal advice. Rules vary by region and campaign type; work with qualified counsel for your specific programs.

Consent, identification, and message trust

Phones and carriers often treat unknown, generic, or “link-only” texts as risky. You get better placement and more replies when messages clearly look like your business and match what the customer agreed to receive.

• Document consent. Know how each number was obtained (web form, contract, verbal with note, etc.) and what they agreed to receive: appointment reminders only versus marketing, for example.
• Identify yourself early. In the first message of a conversation or campaign, state the business name and why you are texting (“This is Acme HVAC about your Tuesday service window”).
• Use stable sending numbers. Frequent number changes confuse customers and weaken trust signals.
• Links and shorteners. Bare shortened URLs with no context look suspicious. Prefer your own domain links where possible, and always pair links with plain-language context.
• Ask customers to save your number. A saved contact moves you from “unknown sender” to a recognized sender on many devices, which reduces filtering into secondary or unknown inboxes.

Example compliant introduction messages

Strong openers name the business, say why you are texting, and include opt-out language. When it applies to your program, add a short line on message and data rates. Change names, dates, and details to match your workflow. Keep wording consistent with how your traffic is registered and with what the customer agreed to receive.

These lines are illustrations. They are not a guarantee that every carrier will approve every message for every campaign. Your legal and compliance advisors and your RouteFlow onboarding team should confirm wording for your use cases and regions.

iOS (Apple Messages)

On iPhone, Apple’s Messages app combines carrier delivery with Apple’s own handling of unknown senders, filters, and (where available) reporting as junk. Exact menu names move between iOS versions, but the concepts stay the same.

Unknown senders and filters

• Apple can split or filter conversations from people who are not in the recipient’s contacts, especially when Filter Unknown Senders (under Settings → Messages) is enabled. Those threads may appear under a separate list such as “Unknown Senders” instead of the main conversation list.
• If a customer says “I never got your text,” ask whether they use unknown-sender filtering and whether your number is saved as a contact.

Junk and reporting

• Recipients can report SMS/MMS as junk. Over time, reports contribute to how aggressively future messages are scrutinized.
• If a message landed in Junk, the customer can often move it back and add you to contacts to improve future delivery to the primary list.

What you should tell customers (support script)

1. Open Settings → Messages and review Filter Unknown Senders and any filter/unknown-sender options.
2. Check under Unknown Senders (or equivalent) for your thread.
3. Add your business number to Contacts with your company name.
4. If a message is in Junk, mark it as Not Junk where that option exists.

Apple updates labels and paths from time to time; if a step does not match their current UI, use Apple’s support documentation for “Filter Unknown Senders” or “report junk” for the customer’s iOS version.

Android (Google Messages and others)

Many Android phones ship with Google Messages. It includes spam protection, blocking, and categorization that can affect whether a thread is front-and-center or buried under “Spam and blocked” or similar.

Google Messages (typical path)

• Open the app’s Spam and blocked (or similar) area to see if your number was misclassified.
• If your message is there, the user can mark it as Not spam / unblock and optionally create a contact for your business.
• Spam protection can be tuned in app settings; overly aggressive third-party security apps can also intercept SMS.

Samsung and other OEMs

Samsung and other manufacturers sometimes bundle their own SMS apps with different names and menus. The same ideas apply: check blocked/spam folders, unblock, mark as not spam, and save the contact. If steps differ, use the device maker’s help for “block messages” or “spam folder” on that model.

Carriers, 10DLC, and what you control

In the United States, application-to-person (A2P) traffic on local 10-digit numbers follows carrier 10DLC rules: brand and campaign registration, declared use cases, and throughput policies. RouteFlow handles 10DLC registration for you and keeps the carrier-side setup aligned with what you registered. Traffic that does not match your declared use case or consent can still face filtering, throttling, or blocking before it reaches the handset.

For a short FAQ on how this fits your business, see Field service and CRM: 10DLC and business texting compliance.

What you control and what you cannot

• You control: accurate information during onboarding, message content (including identification and opt-out lines), frequency and tone, training staff, and asking customers to save your number.
• RouteFlow handles: 10DLC registration on your behalf and automatic processing of supported opt-out keywords (such as STOP and END) on inbound messages.
• You cannot control: each carrier’s real-time filters, each user’s block list, or each phone vendor’s unknown-sender and spam algorithms.

Related links

• Support & FAQ
• Privacy Policy
• Terms of Service