# How Car Dealerships Stop 'Spam Likely' SMS > Why multi-location dealers move to iMessage follow-up to escape carrier filtering — and what actually changes operationally. *By Bharadwaj Giridhar · Published 2026-01-29T00:00:00.000Z* *Last updated: 2026-05-20T00:00:00.000Z* **Canonical URL:** https://tuco.ai/blog/how-car-dealerships-can-prevent-spam-likely-while-doing-sms-marketing **Tags:** automotive groups, multi-location messaging, dealership operations, SMS spam likely, iMessage follow-up ## Summary Multi-location dealer groups lose 30%+ of SMS to 'Spam Likely' carrier filtering. iMessage follow-up on dedicated Apple hardware travels Apple's network. --- *Disclosure: I'm the founder of Tuco AI, an iMessage follow-up platform that supports multi-location deployments including automotive groups. The numbers below come from operating Tuco's infrastructure across these customers; where I cite external data, I link sources.* **Last updated: May 2026** Friday afternoon. A customer replies to a text from your dealership: *"What was the out-the-door price on that Tahoe?"* If you run SMS at multi-location scale, the bigger problem isn't which BDC number sent it — it's that one of your numbers is probably already flagged "Spam Likely" by AT&T, Verizon, or T-Mobile this week. Carrier filtering at multi-location scale isn't an edge case; it's the central operational headache. This post walks through what's actually causing the "Spam Likely" tag, why iMessage follow-up on dedicated Apple hardware sidesteps it, and the real line-budget model for multi-location dealer groups. The earlier version of this writeup framed Apple Business Chat as the consolidation answer; that was wrong (ABC is inbound-only and doesn't do follow-up campaigns). The honest answer is operational, and it's below. ## What's Actually Causing "Spam Likely" Carrier-side filtering (AT&T's Hiya, Verizon's Call Filter, T-Mobile's Scam Shield) flags numbers based on three signals: **1. Volume per number.** A single SMS number sending hundreds of texts per day to never-before-contacted recipients matches the carrier definition of a marketing blast — even if you're a legitimate dealership with A2P 10DLC approval. Multi-location groups hit this fast because each BDC team's volume stacks on one location's numbers. **2. Content similarity.** Carriers run content hashing across messages from each number. Five BDC reps sending the same template ("Hi {{name}}, this is {{rep}} from {{store}} — saw you looked at the {{vehicle}}…") trip similarity filters quickly. Templates that work great in your CRM look like a marketing blast to the carrier. **3. Recipient complaints.** "Report Junk" / "STOP" responses get aggregated per number. Five complaints in a week from a single number's recipients is usually enough to trigger filtering for the next 30+ days, regardless of whether the rest of the recipients want the messages. Once a number gets flagged, the carrier doesn't tell you. Delivery just drops 30-50%. You find out from your team noticing reply rates fall. Switching to a fresh number resets the timer but doesn't solve the root cause — the new number gets flagged on the same patterns within 4-8 weeks. A2P 10DLC registration *helps* — registered numbers face less aggressive filtering than unregistered ones — but it doesn't make a high-volume marketing-template number look not-like-marketing. It just lowers the false-positive rate. ## Why iMessage follow-up Sidesteps the Whole Problem iMessage follow-up on dedicated Apple hardware doesn't travel the carrier networks. It travels Apple's iMessage network, which has no equivalent of "Spam Likely." Three structural reasons it doesn't apply: - **No carrier in the path.** AT&T, Verizon, and T-Mobile aren't between you and the recipient on iMessage. Their filtering rules can't apply. - **No registration model.** There's no A2P 10DLC equivalent for iMessage. Apple has its own anti-spam system, but it's a behavioral cap (~50/day per Apple ID, send-to-reply ratio) rather than a content-and-volume filter that surfaces a warning on the recipient's screen. - **No "this looks like marketing" badge.** iMessage follow-up messages arrive as native consumer iMessage — blue bubble, no business checkmark, no Spam Likely tag, no "Likely Marketing" badge. Whether the recipient reads it as marketing depends entirely on how the copy is written, not on a carrier flag. The Apple anti-spam side does have its own constraints — the ~50/day cap per line being the main one — but the failure modes are different. An overloaded line gets throttled silently, not surfaced to the recipient as "Spam Likely." ## The Multi-Location Line Math (Real Numbers) The earlier version of this post claimed iMessage follow-up lets you consolidate 38 SMS numbers into "one business identity." That's wrong for iMessage follow-up — each line is one Apple ID with one phone number. Here's the actual math: **8-location dealer group, ~50 follow-up messages per location per day (400/day total):** | Approach | Numbers needed | Monthly cost (rough) | Per-message economics | |---|---|---|---| | SMS A2P 10DLC, isolated per location (BDC + service + sales + backup) | 30+ numbers | $90-$150 lease + $300+ A2P campaigns | $0.01-$0.02/msg + 30-50% filtering loss = effective $0.02-$0.04 | | iMessage follow-up (Tuco Starter $149/line) | 8-10 lines = 8-10 numbers | $1,200-$1,500 (no A2P fees, no per-message) | ~$0.10/msg sent, 94%+ delivery, effective $0.10/delivered | iMessage costs more per delivered message at this scale. The justification isn't cost-per-message — it's the conversion lift from 94% delivery vs ~60-70% effective SMS delivery once filtering takes its cut, plus the 25-35% iMessage reply rate vs ~2% SMS reply rate. **The operational savings are real but they come from different places than the earlier post claimed:** - Skipping A2P 10DLC campaign fees ($10/mo per number × 30 numbers = $300/mo saved) - Skipping carrier reputation management (no need to keep "burner" backup numbers warm in case primaries get flagged) - Skipping the management overhead of moving traffic between numbers when one gets flagged - Avoiding the lost-conversion cost of carrier filtering (the $5K-$50K/month figure varies by group size) You still pay per-line for the iMessage infrastructure. You don't get a magic single-identity-per-group consolidation. Anyone telling you otherwise is conflating lead-to-close consumer iMessage with Apple Business Chat (a different product that *does* use a single business identity but is inbound-only and can't run BDC campaigns). ## What Customers Actually Experience Customer test drives at North location Saturday. BDC sends a follow-up via the North BDC iMessage line — `+1 555 123 4567`, which corresponds to "Smith Auto - North BDC" in their phone if they save it as a contact, or just the number if they don't. Customer schedules service Tuesday at South location. Service team messages via South service line — `+1 555 765 4321`, a different number. This is the *same* multiple-numbers problem SMS has. iMessage follow-up doesn't make the multiple-number problem disappear; it makes the *carrier-filtering* problem disappear. The number sprawl per location is still there, just with fewer total numbers needed and zero A2P fees on each. The reason this is operationally easier than SMS isn't fewer numbers — it's that each iMessage line has a predictable 50/day budget that doesn't fluctuate based on carrier reputation, and the line management UI in platforms like Tuco shows per-line health (utilization, delivery, reply rate, opt-out rate) so you know which line is in trouble before customers do. ## Implementation Timeline for a Multi-Location Group Realistic timeline for an 8-location group switching follow-up traffic from SMS to iMessage follow-up: - **Week 1**: Provision 4-5 lines (start with BDC for top-volume locations). Each line ships in 1-3 days and warms in 2-3 days of progressive sending. - **Week 2**: Connect dealer-management-system (DMS) integration via webhook or native CRM. Run a 100-300 lead pilot through the new lines. Validate delivery (target 94%+) and reply rate. - **Week 3**: Scale to remaining locations. Add lines for service and sales tracks if volume justifies it. - **Week 4**: Migrate inbound replies fully into the platform's unified inbox. Train BDC team on per-line attribution. Total: 3-4 weeks from signup to full multi-location coverage. No Apple approval gate, no D-U-N-S, no CSP partnership. You provision Apple IDs and hardware through the platform's hosting infrastructure (Tuco hosts on shared and dedicated Macs depending on plan). ## When iMessage follow-up Doesn't Fit Multi-Location Groups A few cases where the math doesn't work in iMessage's favor: - **Pure transactional volume** (order shipped, appointment confirmed) at very high scale where engagement upside doesn't matter. SMS is cheaper per delivered message. - **Android-dominant customer base**. iMessage falls back to SMS for Android, which removes the structural advantage. If your customer base is 70%+ Android, the conversion math doesn't pencil. - **Single-location with low daily volume** (< 50/day). At one line of 50/day on Tuco, $149/mo is more than SMS's per-number cost at that volume; SMS may make sense until you outgrow it. For most multi-location dealer groups doing 200-1,500 follow-up messages/day across BDC, service, and sales, the iMessage line model wins on conversion economics even if it costs more on hard infrastructure per month. ## The Honest Multi-Location Summary "Spam Likely" is a carrier-network problem. iMessage follow-up doesn't travel the carrier network, so the problem doesn't apply. Each iMessage follow-up line is one Apple ID with one phone number — multi-location groups still need multiple numbers, just fewer than SMS's per-location reputation-isolation forces, and without the A2P campaign fees stacked on top. The earlier version of this post claimed Apple Business Chat collapses the whole group to one verified business identity. ABC does do that — but ABC is inbound-only and doesn't handle BDC follow-up follow-up, so it doesn't solve the actual problem dealer groups have. The right model for multi-location follow-up is: a line per location's primary use case (BDC), additional lines as daily volume demands, daily line-health monitoring, and routing logic in the CRM to send each lead through the right line. Tuco handles the routing and per-line health automatically; if you're operating manually, those are the levers to watch. **[Book a 15-minute multi-location demo](/demo)** — I'll walk through line-budget math for your specific store count and daily volume. **Related reading:** - [How to scale iMessage follow-up past 50/day — line budget math](/blog/how-to-scale-imessage-outreach-beyond-50-messages-per-day) - [Car dealers switching to iMessage for lead follow-up](/blog/why-car-dealers-and-sales-teams-are-switching-to-imessage-for-lead-follow-up) - [iMessage vs SMS for personalized sales sequences](/blog/why-imessage-beats-sms-for-personalized-sales-sequences-a-dealership-and-local-b) - [A2P 10DLC approval delays and costs](/blog/why-waiting-4-6-weeks-for-a2p-10dlc-approval-is-costing-you-sales-and-what-smart) - [See pricing](/pricing) | [Book a demo](/demo) ## Frequently Asked Questions ### What causes "Spam Likely" SMS filtering for car dealerships? Carrier-side filtering (AT&T, Verizon, T-Mobile) based on three signals: high send volume from a single number, content patterns that match marketing-blast templates, and recipient complaints ("Report Junk" reports). Multi-location dealer groups trip all three because BDC teams send high volume, content is repetitive across leads, and any complaint on a number poisons it for the whole location. Once a number is flagged, delivery drops 30-50% and switching to a new number resets the clock without solving the root cause. ### Does iMessage follow-up avoid the "Spam Likely" problem? Yes, because iMessage follow-up doesn't travel the carrier networks. It travels Apple's iMessage network, which doesn't have the "Spam Likely" filter at all. Apple has its own anti-spam system (the ~50/day cap per Apple ID, behavioral pattern matching), but it's not the same as carrier filtering and it doesn't surface a "Spam Likely" warning on the recipient's screen. Delivery on healthy iMessage follow-up lines averages 94%+. ### Does iMessage follow-up really need fewer phone numbers per location? Sometimes yes, sometimes no — it depends on volume per location. Each iMessage follow-up line is one Apple ID with one phone number and caps at ~50/day. A dealership group sending 200/day across all locations needs 4-5 lines = 4-5 numbers. A group sending 50/day can run on one shared line. Compare to SMS where each location typically runs 3-4 separate numbers (BDC, service, sales, backup) to isolate carrier reputation, plus A2P 10DLC campaign fees per number. The savings are real but they come from skipping the per-number A2P fees and the carrier-reputation isolation, not from collapsing to a single business identity. ### How much does iMessage follow-up cost vs SMS for a multi-location dealer group? On Tuco, $149/mo per Starter line (one dedicated phone number, ~50 sends/day) with no per-message fees. An 8-location group sending 300-400 follow-up messages/day across all stores needs 6-8 lines = $900-$1,200/mo. SMS with A2P 10DLC at the same scale runs ~$140 in number leases + ~$200-$400 in A2P campaign fees + the operational time of managing carrier reputation across 25-30 numbers. Tuco's higher monthly is paid back in carrier-fee savings, management time, and the conversion lift from avoiding "Spam Likely" filtering. ### What about Apple Business Chat as a multi-location solution? Apple Business Chat (Messages for Business) is a different product — gated by Apple, inbound-only, designed for customer service. ABC does use a single verified business identity across locations, which is what older posts on this topic describe. But ABC can't be used for follow-up campaigns at all (customers must initiate via a Message Us entry point), so it doesn't solve the BDC follow-up problem multi-location dealers actually have. The right model for the right model is consumer iMessage on dedicated Apple hardware — one line per Apple ID, multiple lines for scale.