Skip to main content
Send SMS campaigns to customers who explicitly opted in to texts from your business. Use your own Twilio number or request a dedicated IrisAgent-managed US number.

​
Before you begin

You need:
  • IrisAgent administrator access
  • A CSV of contacts who explicitly opted in
For an IrisAgent-managed number, also prepare:
  • A notification email, plus your company’s legal, tax, address and authorized-contact details
  • A description of the messages you will send, with sample messages
  • How recipients opt in, with evidence and website links
You do not need your own Twilio account for a managed number. For your own Twilio number, also have:
  • The Twilio Account SID of the account or subaccount that owns the number
  • An SMS-capable US number in that account
  • A Twilio Messaging Service whose sender pool contains the number
  • A restricted Twilio API key (SID and secret) created in that same account
  • An approved carrier registration (for example, an A2P 10DLC campaign) linked to the Messaging Service
For your own Twilio number, IrisAgent checks the credentials, SMS capability, Messaging Service and sender pool. You are responsible for carrier registration, campaign approval, consent and Twilio billing.
Both setup options start in Deploy → Text channels.

​
Connect your existing Twilio number

The number, Messaging Service and API key must all belong to the account or subaccount whose Account SID you enter. Parent-account credentials cannot reach subaccount resources, and the reverse.

​
1. Gather Twilio details

In the Twilio Console, in the account that owns the number:
  1. Copy the Account SID (starts with AC).
  2. Under Phone Numbers, confirm the number is SMS capable.
  3. Open Messaging → Messaging Services, create or select a service, and copy its Messaging Service SID (starts with MG).
  4. On the service’s Senders tab, add the number if it is not listed.
An approved Business Profile or Brand does not register a number for sending. For a US local 10DLC number, open the Messaging Service’s Compliance → 10DLC tab and make sure it is linked to an approved A2P campaign that covers your messages. If you see Start 10DLC A2P campaign registration, the service is not registered. For toll-free and other sender types, complete the verification shown under Compliance.

​
2. Create a restricted API key

  1. In the same account, open Settings → API keys and tokens.
  2. Create a restricted key (Twilio guide) with only the permissions to read the number, the Messaging Service and its sender pool, and to create outbound messages.
  3. Copy the API Key SID (starts with SK) and the secret.
Twilio shows the secret only once. Store it securely and never send it by email or chat. IrisAgent stores it encrypted, and you can revoke the key in Twilio at any time.

​
3. Connect in IrisAgent

  1. Open Deploy → Text channels.
  2. Under Use your Twilio number, click Connect Twilio.
  3. Enter the Account SID, Restricted API Key SID, Restricted API Key secret, US phone number and Messaging Service SID.
  4. Click Connect number.
A successful connection confirms access, SMS capability and sender-pool membership. It does not confirm A2P campaign approval or that your approved use case covers your IrisAgent campaigns.

​
Get an IrisAgent-managed number

  1. Open Deploy → Text channels.
  2. Under Get an IrisAgent number, click Get a new number.
  3. Enter a preferred three-digit US area code and click Get number.
IrisAgent provisions a dedicated number in a customer-specific Twilio subaccount. The number cannot send until carrier registration is approved.
Managed registration must be enabled for your workspace. If you do not see these controls, contact IrisAgent support.

​
1. Register your business

  1. Enter the email that should receive registration updates.
  2. Click Start / resume registration and complete the embedded business form with accurate company and tax details.
  3. Submit and wait for brand review.
Use Start / resume registration to continue an unfinished form. New submissions can take a few minutes to show up in IrisAgent.

​
2. Register your messaging use case

After the brand is approved:
  1. Click Register messaging use case.
  2. Complete the form: message purpose, sample messages and opt-in details. The opt-in description must match what recipients actually see.
  3. Submit for campaign review.
A messaging use case is the Twilio A2P registration for your Messaging Service. An Outbound campaign in IrisAgent is one message sent to one CSV audience. Creating an Outbound campaign does not create or approve a carrier registration.

​
3. Wait for number activation

After campaign approval, the number must be registered to that campaign. The sender becomes Active only when the business, use case and number are all approved. Click Refresh status for the latest state. The page also refreshes about every 30 seconds when no form is open. You do not need to keep it open. Rejected registration: IrisAgent shows the reason. Click Correct registration to fix and resubmit. You cannot edit a registration under review. For number-registration problems, contact support. Need help? Use View required details for Twilio’s business-information checklist, or Email us details to email IrisAgent support. Never email API secrets, tax IDs or identity documents. Ask support for a secure way to share them.
Buying a number, an approved Business Profile or Brand, or Twilio Compliance Embeddable access does not by itself authorize outbound SMS. The brand, campaign and number all need approval. Mock or demo approvals do not authorize real messages.

​
Prepare a contacts CSV

  • Phone column (required): phone_number, phone, mobile or mobile_number.
  • First name (optional): first_name, first name, firstname or name.
  • Numbers must be valid US numbers. Formatting is fine. IrisAgent converts them to E.164.
  • Duplicates are included once. Invalid rows are skipped and reported.
  • Up to 1,000 unique recipients per campaign.
Upload only people who explicitly agreed to receive texts from your business. A purchase, support contact or known phone number is not consent. Keep your own consent records and honor opt-outs.

​
Create and send a campaign

  1. Open Outbound → Text Campaigns and click Create campaign.
  2. Enter a Campaign name (visible only to your team) and the Message.
  3. Upload the CSV and check the valid and skipped counts.
  4. Confirm that every recipient has explicitly consented, then click Save draft.
  5. Open the saved campaign, review it, and click Send campaign once your text channel is active.
  6. Track delivery metrics and recipient-level failures on the campaign page.
Configure text at the top of Text Campaigns takes you to Deploy → Text channels. For managed numbers, IrisAgent rechecks registration before sending and blocks the send if it cannot confirm it. For your own Twilio number, registration stays your responsibility. A sent message is not proof of delivery. Twilio can report a carrier failure later. The campaign page shows reported errors with the recipient, a description and a Twilio error-code link when available.

​
Personalize and format messages

Use {{first_name}} to insert the recipient’s first name:
The preview fills in a sample name. Check contacts without a first name before sending. The editor shows an estimated SMS segment count. Longer messages and non-GSM characters can use more segments and cost more. Include sender identification and opt-out language such as Reply STOP to opt out. You are responsible for meeting carrier and legal requirements.

​
Troubleshooting

I have a number but cannot send. Provisioning and registration are separate. In Deploy → Text channels, click Refresh status and check the stage. After brand approval you must complete Register messaging use case. Sending stays off until the sender is Active. My business was approved but I still cannot send. Brand approval only unlocks the use-case form. A Business Profile approval or Compliance Embeddable enrollment is not a campaign registration. Follow the remaining stages. I submitted a form but still see the registration button. Submission is not approval, and updates can take a few minutes. Click Refresh status. If the form is still a draft, the button resumes it. If it persists, contact support. Do not get a new number. Status refresh or registration fails. Read the error and retry. If it says embedded registration is not enabled, contact support. Do not buy another number. Twilio connection fails. Check that:
  • The SIDs start with AC (Account), SK (API key) and MG (Messaging Service).
  • The API key was created in the account that owns the number and Messaging Service.
  • The number is SMS capable and appears on the service’s Senders tab.
  • The API key can read those resources and create outbound messages.
Twilio error 30034 or undelivered messages. Error 30034 means a US 10DLC message came from an unregistered number. In Twilio, open the Messaging Service, check Compliance → 10DLC, and link it to an approved A2P campaign. Sending an IrisAgent campaign does not create a Twilio A2P registration. Twilio can accept a message and later mark it Undelivered. Compare the campaign page with Twilio → Messaging → Logs, and contact support with the campaign and error code (never your API secret). CSV rejected. Make sure it is a CSV, has a recognized phone heading, contains valid US numbers and has no more than 1,000 unique valid recipients. Rows skipped. Rows with missing or invalid numbers are skipped, and duplicates removed. Fix the file and upload again. Registration is slow. Review times vary and are not guaranteed. Watch your notification email and the stage in Deploy → Text channels. If the number is still pending after campaign approval, contact IrisAgent support instead of retrying sends.