Bulk SMS Campaigns for Marketing Agencies Running Multiple Clients

TL;DR: Bulk SMS campaigns for marketing agencies break at client separation long before they break at send volume. The rule that decides most of it is an industry rule, not a preference. CTIA’s Messaging Principles and Best Practices state that a consumer opt-in “should not be transferable or assignable” and “should apply only to the campaign(s) and specific Message Sender for which it was intended or obtained.” Read that operationally. A number that opted in to your retail client did not opt in to your dental client, so one shared master list is not an efficiency. It is the fastest way to send a message nobody agreed to receive. The registration layer pushes the same direction. Twilio’s A2P 10DLC guidance for ISVs says to create a Secondary Customer Profile and register a Brand under each customer’s subaccount, filling in “that customer’s details rather than your own ISV’s details,” which means your agency does not get to send as itself on behalf of nine clients. Federal rules sit underneath all of it. 47 CFR 64.1200(c)(1) bars telephone solicitations before 8 a.m. or after 9 p.m. local time at the called party’s location, 64.1200(f)(9) defines prior express written consent as a signed agreement that cannot be made a condition of purchase, and 64.1200(a)(10) requires revocation requests made in any reasonable manner to be honored within a reasonable time not to exceed ten business days. Then there is the unglamorous detail that quietly doubles a bill. A segment holds 160 characters on GSM-7 and 70 on UCS-2, and a single emoji or curly apostrophe flips the whole message to UCS-2 at 67 characters per segment once it concatenates. Build the workflow around per-client brands, per-client suppression, a documented approval on the exact audience and copy, a tested opt-out, and reporting that separates delivery from conversions. Volume is the last thing to optimize, not the first.

An agency signs its ninth client. Somebody exports a list, picks a template that worked last month, and schedules the send for 9 a.m. Two days later a client asks why their customers are getting texts about a different company’s promotion.

That is the failure mode. Not bad copy. Not a weak offer. How did that happen? One export, one shared account, one approval nobody gated. The list crossed a boundary that should never have been crossable, and nobody noticed until a customer did.

Running bulk SMS campaigns for marketing agencies is a different job from running them for one brand. A single business sends to its own audience under its own name. An agency sends on behalf of businesses that never agreed to share anything with each other, and the controls that keep them apart have to be structural rather than careful. This is operational guidance, not legal advice. Requirements for commercial messaging vary by jurisdiction, carrier, sender type, and campaign, so run the specifics past qualified counsel.

What a Bulk SMS Campaign Actually Is for an Agency

Bulk SMS means sending one campaign to a group of recipients. That is the whole definition, and it describes the distribution method only.

It is not permission to send the same generic message to everyone you have a number for. The word gets read as “big” when it should be read as “scheduled,” and that misreading is where agency programs go wrong. So what does a managed campaign look like in practice? A named client objective with a recipient action attached. Permission documented for the specific thing you are about to send. Contact lists and suppression records that belong to one client and cannot reach another. Segments built on data the client actually owns. Copy, offer, links, and timing that somebody approved and signed off on. A QA pass before launch. And a measurement plan tied to the client’s business objective rather than to how many messages left the queue.

Miss any one of those and you still have a send. You just do not have a campaign you can defend.

Bulk SMS Campaigns vs Segmented SMS

Three models get grouped under one label, and they behave differently enough that the grouping causes real problems.

Bulk SMS Broadcasts

A broadcast goes to a broad eligible audience on a schedule you set. Everyone who subscribed to a retailer’s promotions, for example, gets the sale announcement at the same time. Broadcasts earn their keep on genuine announcements, and they decay fast when the audience gets wider than the news. So how do you know when that has happened? Watch the opt-out rate on consecutive broadcasts. That number tells you whether the list is bored before the client does.

Segmented SMS Campaigns

Segmentation splits an eligible audience on something that changes the message. Which split? Location, lifecycle stage, purchase category, stated interest, last engagement. Whichever one changes what the offer should say. The offer then adapts to the group. This is usually the highest-return change an agency can make, because it costs nothing but a definition and it removes the “why am I getting this” reaction that drives opt-outs.

Triggered SMS Campaigns

A trigger fires on an event instead of a calendar. A lead takes a defined action, a customer hits a lifecycle milestone, a form gets submitted. The message goes out without anyone scheduling it. So why are triggers the riskiest of the three? Nobody is watching when they fire. That is exactly why they need the most review before launch and the least attention afterward. Check the trigger condition, the consent basis, and the suppression logic before it goes live, because an unattended workflow sending to a list nobody re-checked is the one that runs for six weeks past the point it should have stopped.

Most mature programs run all three. The mix follows the client’s objective and data quality, not a preference for one model.

Marketing Agency SMS Campaign Use Cases

What is the recipient supposed to do? Start there. Starting with a channel feature instead produces campaigns that demo well and convert badly.

• Generate timely demand. A limited promotion to an eligible, relevant segment. The deadline has to be real or the next one gets ignored.
• Support lead engagement. Follow up with prospects who took a defined action and agreed to this kind of message. Speed matters more than polish here.
• Drive event attendance. Information and reminders to people who registered, under the permissions that registration actually granted.
• Reactivate quiet customers. An eligible segment that has not engaged recently, with frequency caps and suppression rules attached before the first send.
• Coordinate channels. SMS alongside calling and email rather than three teams texting, dialing, and emailing the same person in the same week. If you want the comparison in detail, our breakdown of SMS versus email for sales teams covers where each one earns its place.

Each one needs its own audience definition, its own success metric, and its own review. And permission for one of these does not carry to the others. Someone who agreed to appointment reminders did not agree to promotions, and treating those as the same permission is the most common way an agency inherits a complaint that belongs to its client.

How Agencies Launch Client SMS Campaigns

Write the SMS Campaign Brief First

Document the objective, the audience, the offer, the call to action, the send window, the owner, the approver, the tracking plan, and the stop conditions. Name which client supplied the contact data and which system is the source of truth for it. That last one sounds like paperwork until two systems disagree at 8:55 a.m. on send day.

The brief has one job. What should an eligible recipient understand and do after reading this message? If the brief cannot answer that in a sentence, the campaign is not ready.

Verify SMS Audience Consent Before You Import

Before a single contact moves, make the client show you how and when the audience gave permission, what disclosures they saw, and how withdrawals get recorded. Then dedupe and apply the suppression list.

Purchased, scraped, shared, or vaguely sourced lists are not campaign-ready. Ever. And the standard here is written down: 47 CFR 64.1200(f)(9) defines prior express written consent as an agreement in writing bearing the signature of the person called, clearly authorizing the messages, with disclosures that signing is not a condition of purchase. A spreadsheet with no provenance does not meet that. If the permission trail is unclear, the launch stops and compliance review starts. Our rundown of the 2026 TCPA changes to consent and opt-out goes deeper on what changed and what it means for outbound programs.

Build SMS Campaign Segments the Client Can Defend

Use fields the client owns and handles under its own data policy. A local promotion needs a geographic segment. A lifecycle campaign needs new leads separated from established customers. That is usually the whole requirement.

Skip personalization that depends on unreliable fields. A merge tag firing “Hi {FirstName}” at 400 people does more damage than no personalization at all, and a correct, relevant message beats a first name stapled to a generic blast every time. If you are pulling segments straight out of a CRM view, the mechanics are covered in our walkthrough on sending bulk personalized SMS from a Salesforce list view.

Write Copy That Identifies the Sender

Say who is texting, why, and what happens next. Verify claims, prices, deadlines, eligibility conditions, and every destination link with the client before the copy is locked.

Now the part that surprises people on the invoice. A single segment holds 160 characters in GSM-7 encoding and 70 in UCS-2. Include one emoji, one curly apostrophe, or one non-Latin character and the entire message switches to UCS-2. Concatenated messages lose more, because seven characters go to segment metadata: 153 per segment on GSM-7, 67 on UCS-2. A 300-character message with a smart quote in it is not two segments. It is five. Preview the actual encoded message in the platform rather than counting characters in a document.

Run Approval and QA on the Exact Send

Route the final audience criteria, copy, links, timing, and offer through a documented approval, and keep the approved version attached to the campaign record. When a client asks who authorized the discount, the answer should take ten seconds to find.

Then send real tests to real reviewers. Check sender identification, personalization fallbacks, spelling, link destinations, the mobile landing page, tracking parameters, opt-out handling, time-zone logic, and suppression behavior. Test the opt-out by actually opting out. A STOP keyword nobody has exercised is an assumption, not a control.

Schedule Against the Recipient’s Clock

The federal floor is specific. Under 47 CFR 64.1200(c)(1), no telephone solicitation may be initiated to a residential subscriber before 8 a.m. or after 9 p.m. local time at the called party’s location. Note which clock that is. It is the recipient’s, not the agency’s, and an agency in one time zone scheduling for a national list is one careless send away from a 6 a.m. delivery. State rules can be stricter and they change, so confirm current requirements with authoritative sources and counsel rather than with a template from last year.

Monitor the Send While It Runs

Confirm the audience, message, and schedule match the approved brief, then watch it. Who is watching, and what makes them stop the send? Answer both before launch. Unexpected delivery failures, wrong content, a broken link, or an opt-out rate above the client’s normal range all need a defined escalation path and a pause procedure that someone has actually used.

Manage Multiple Agency SMS Clients Safely

This is the section that separates agency SMS from everything else, and it is the one most often handled by good intentions.

Start with the rule that makes separation non-negotiable. CTIA’s Messaging Principles and Best Practices state plainly that a consumer opt-in “should not be transferable or assignable” and “should apply only to the campaign(s) and specific Message Sender for which it was intended or obtained.” So a number is not an asset your agency owns. It is permission a specific client holds for a specific program, and it does not travel.

The registration layer enforces a version of the same idea. Twilio’s A2P 10DLC onboarding guidance for ISVs instructs you to create a Secondary Customer Profile under the customer’s subaccount and register a Brand there, filling in “the business details of that specific customer” and using “that customer’s details rather than your own ISV’s details.” Each use case then maps to its own Messaging Service in that subaccount. Read what that means for an agency: you are not one sender with nine campaigns. You are nine registered brands that your agency happens to operate. Our 10DLC compliance checklist for outbound sales texting covers the registration steps in order.

Structural controls worth putting in place:

• Separate workspaces or subaccounts per client, not separate folders inside one account
• Access granted by job responsibility, so a copywriter cannot export a contact list
• Naming conventions that make a wrong-client selection visually obvious at the moment of send
• Contact exports blocked unless there is an approved business reason on record
• Consent and suppression records held per client and never merged
• An audit trail of who imported, edited, approved, scheduled, and paused each campaign
• Access reviewed whenever an employee or contractor changes roles or leaves
• Test contacts kept out of production audiences

These are not bureaucracy. Each one blocks a specific incident: the wrong list selected, one client’s data surfacing in another client’s report, a departed contractor still holding access to nine audiences. Capabilities differ by platform, so verify each of these during evaluation instead of assuming.

SMS Campaign Platform Features for Agencies

Pick software for the operating model, not for the maximum send rate. So what do you actually test? Make vendors demonstrate the following on a live account rather than describe it on a slide.

• Account separation. Can data, campaigns, users, and reporting be isolated per client, and can that isolation survive an admin in a hurry?
• Permission controls. Can you define distinct roles for strategists, copywriters, analysts, and client reviewers?
• Consent and suppression handling. How are permission records, opt-outs, duplicates, and imports stored, and is suppression enforced per client at send time?
• Approval gates. Can the system stop an unapproved draft from launching, or does it just record that someone should have approved it?
• Segmentation. Which fields and events are usable, and how is audience membership validated before the send?
• Scheduling. How are recipient time zones, frequency caps, and campaign conflicts handled?
• Reporting. Can you hand a client an export or dashboard with no trace of any other account in it?
• Data connections. How does it exchange data with the CRM and analytics tools the client already runs?
• Incident process. What actually happens when a campaign has to be paused mid-send at 9 p.m. on a Friday?

Get feature claims, pricing, usage rules, registration processes, geographic availability, and data-handling terms in writing. Product capabilities and carrier requirements change, and a sales call is not documentation.

Measure SMS Campaign Results for Agencies

Agency reporting fails in a predictable way. It reports what the platform makes easy instead of what the client hired you for.

So what belongs in the report? Split it in two. Operational metrics cover the audience selected, messages attempted, delivery status categories from the provider, clicks through governed tracking links, replies, opt-outs, and complaint indicators. Business results cover conversions under the client’s attribution method and the revenue or pipeline associated with them. Keep the two apart on the page, because a delivery rate presented next to a revenue number implies a causal chain that the data does not support.

Delivered does not mean read. A click does not mean incremental revenue. Document the attribution window, the tracking limitations, and any offline conversions you cannot see, and do it inside the report rather than in a footnote nobody opens. For ROI, agree the formula with the client in advance and include the full program cost, carrier fees included. And skip the universal benchmark claims unless the source, methodology, date, industry, and sample genuinely match the client in front of you. They usually do not.

One metric deserves more attention than it gets: opt-out rate by client, tracked over time. It is the earliest honest signal that a program is over-sending, and it moves before revenue does.

Common SMS Campaign Mistakes Agencies Should Avoid

• Running one master list across clients. The opt-in was not transferable. Separate audiences and suppression data, structurally.
• Optimizing for volume. A bigger eligible audience is not the same as a bigger relevant one, and the second one is what converts.
• Treating approval as a formality. Confirm the exact message, audience, offer, and timing, and keep the record attached.
• Assuming old permission still covers you. Check the scope and the date against the campaign you are about to send.
• Ignoring channel overlap. Check whether the same person is getting emails and calls from the same client that week.
• Reporting clicks as outcomes. Connect activity to the client’s objective and state the attribution limits out loud.
• Having no error procedure. Define pause, escalation, correction, and client notification before the first send, not during the first incident.
• Counting characters in a text editor. Encoding decides segment count, and the platform preview is the only count that bills.

Agency SMS Campaign Preflight Checklist

• Objective and KPI approved by the client
• Audience source and eligibility reviewed
• Consent records and suppression lists applied
• Client brand registration and sender configuration confirmed
• Copy, offer, and every link approved
• Personalization fallbacks tested on records with missing fields
• Encoding and segment count checked in the platform preview
• Tracking parameters validated end to end
• Send window checked against recipient time zones
• Opt-out tested by actually sending STOP
• Test messages reviewed on representative devices
• Monitoring owner named and pause procedure assigned
• Reporting date, format, and attribution method agreed in advance

Add SMS Campaigns to Marketing Strategy

SMS is one channel inside a client’s wider motion, and it works best when calling, email, and CRM tasks are coordinated rather than run by three teams who do not compare calendars.

Kixie is sales engagement software for business calling and texting, and like any platform an agency is evaluating, it should be measured against the list above: workspace separation, roles, consent and suppression handling, approvals, scheduling, reporting boundaries, integrations, and current product documentation for the regions the client operates in. Do not take a category label as an answer to any of those questions.

The takeaway is unglamorous. Agency SMS is won on separation, documentation, and QA, not on send volume. Get the brief, the consent trail, the per-client boundaries, the approval record, and the encoding check right, and the campaign becomes repeatable. Skip them, and every new client multiplies the same unresolved risk.

Frequently Asked Questions

Is bulk SMS legal for marketing agencies?

Yes, with consent and within the rules. For telemarketing messages, 47 CFR 64.1200(f)(9) requires prior express written consent: a signed agreement clearly authorizing the messages, with a disclosure that signing is not a condition of purchase. Solicitations to residential subscribers are restricted to the window between 8 a.m. and 9 p.m. local time at the called party’s location under 64.1200(c)(1). Revocation requests made in any reasonable manner must be honored within a reasonable time not to exceed ten business days under 64.1200(a)(10). State rules can be stricter. Treat this as the floor and your counsel as the authority.

Can an agency use one SMS list across several clients?

No. CTIA’s Messaging Principles and Best Practices state that a consumer opt-in “should not be transferable or assignable” and “should apply only to the campaign(s) and specific Message Sender for which it was intended or obtained.” Permission belongs to the client and the program the recipient agreed to, so lists, consent records, and suppression data stay separated per client.

Does each agency client need its own 10DLC registration?

Under the ISV model, yes. Twilio’s A2P 10DLC guidance directs ISVs to create a Secondary Customer Profile under each customer’s subaccount and register a Brand there using that customer’s business details rather than the ISV’s own, with each use case mapped to its own Messaging Service. Confirm the specifics with your messaging provider, since requirements and architectures differ.

How long can a bulk SMS message be?

One segment holds 160 characters using GSM-7 encoding or 70 using UCS-2. Longer messages split, and concatenation costs seven characters of metadata per segment, leaving 153 on GSM-7 and 67 on UCS-2. A single emoji or curly apostrophe forces the whole message into UCS-2, which is how a message that looked like two segments arrives as five. Check the encoded preview in the sending platform before approving copy.

What should an agency report to a client after an SMS campaign?

Two sections, kept apart. Operational: audience selected, messages attempted, delivery status categories, clicks, replies, opt-outs, and complaints. Business: conversions and revenue or pipeline under the client’s agreed attribution method, with the attribution window and tracking limits stated in the report. Add opt-out rate tracked over time, because it warns you a program is over-sending before the revenue line does.

Sources

How this article was built: the consent, timing, and revocation rules are quoted from the federal regulation itself rather than from a secondary summary, the opt-in transferability rule comes from the messaging industry’s own published principles, and the registration and encoding behavior comes from current published carrier-facing platform documentation, each read directly on the review date.

• 47 CFR 64.1200, Delivery restrictions, Cornell Law School Legal Information Institute, primary regulatory text, for the 8 a.m. to 9 p.m. local-time restriction on telephone solicitations at paragraph (c)(1), the definition of prior express written consent at paragraph (f)(9), and the requirement to honor revocation requests within a reasonable time not to exceed ten business days at paragraph (a)(10).
• CTIA Messaging Principles and Best Practices, July 2019, CTIA, primary industry guidance, for section 5.1.2.2 stating that a consumer opt-in should not be transferable or assignable and should apply only to the campaigns and specific message sender for which it was obtained, and for the section 5.1.3 opt-out handling guidance.
• ISV A2P 10DLC Onboarding Overview, Twilio documentation, vendor documentation, for creating a Secondary Customer Profile and registering a Brand under each customer’s subaccount using that customer’s business details, and for mapping each use case to its own Messaging Service.
• What is the SMS character limit, Twilio documentation, vendor documentation, for the 160-character GSM-7 and 70-character UCS-2 single-segment limits and the 153-character and 67-character per-segment limits once a message is concatenated.

Sources verified and content reviewed by the Kixie Research Team on September 23, 2026. All source links checked on September 23, 2026.