Skip to main content
IrisAgent Outbound lets you send SMS campaigns to customers who have explicitly opted in to receive text messages from your business. You can connect an existing Twilio number or request a dedicated IrisAgent-managed US number. Each campaign keeps its message, audience, and sending results together.
For a customer-owned Twilio number, IrisAgent verifies the credentials, SMS capability, Messaging Service, and sender-pool membership. You are responsible for the number’s carrier registration, campaign approval, consent, and Twilio billing.

​
Before you begin

For either setup method, you need:
  • IrisAgent administrator access
  • A CSV file containing only contacts who have explicitly opted in
If you request an IrisAgent-managed number, prepare:
  • A notification email and your company’s legal, tax, address, and authorized-contact information
  • A description of the messages you plan to send and representative message samples
  • An explanation of how recipients opt in, with supporting evidence and relevant website links
Business registration and messaging-use-case registration are separate steps. You do not need to create your own Twilio account for an IrisAgent-managed number. If you connect your own Twilio number, you also need:
  • The Twilio Account SID for the account or subaccount that owns the number
  • An SMS-capable US phone number in that same account or subaccount
  • A Twilio Messaging Service whose sender pool contains that number
  • A restricted Twilio API key SID and secret created in that same account or subaccount
  • The applicable approved carrier registration associated with that Messaging Service

​
Set up your text channel

In IrisAgent, open Deploy → Text channels, then choose one of the following setup methods.

​
Connect your existing Twilio number

Use this option when your company already owns a Twilio number and manages its Twilio registration and billing.

​
1. Confirm the Twilio resources use the same account

The phone number, Messaging Service, and restricted API key must belong to the Twilio account or subaccount identified by the Account SID you enter in IrisAgent. Credentials created in a parent account cannot automatically access resources owned by a subaccount, and the reverse is also true. In the Twilio Console:
  1. Select the account or subaccount that owns the phone number.
  2. Copy its Account SID, which begins with AC.
  3. Under Phone Numbers, confirm the number is SMS capable.

​
2. Configure the Messaging Service

  1. Open Messaging → Messaging Services in Twilio.
  2. Create a Messaging Service or select the service you want IrisAgent to use.
  3. Copy its Messaging Service SID, which begins with MG.
  4. Open the service’s Senders tab.
  5. Add the phone number to the sender pool if it is not already listed.
An approved Twilio Business Profile or Brand does not by itself register a number for application-to-person messaging. For a US local 10DLC number, open the Messaging Service’s Compliance → 10DLC tab and ensure the service is associated with an approved A2P campaign that covers the messages you intend to send. If the page says Start 10DLC A2P campaign registration, the service is not registered.
For other sender types, such as toll-free numbers, complete the applicable Twilio verification shown under the Messaging Service’s Compliance tab.

​
3. Create a restricted API key

  1. In the same Twilio account or subaccount, open Settings → API keys and tokens.
  2. Create a restricted API key following Twilio’s restricted API key documentation.
  3. Grant the least privileges needed to read the owned phone number and Messaging Service, read its sender pool, and create outbound messages.
  4. Copy the API Key SID, which begins with SK, and the secret.
Twilio displays an API key secret only when the key is created. Store it securely. Do not send it through email or chat. IrisAgent stores the submitted secret encrypted, and you can revoke the key in Twilio at any time.

​
4. Connect the number in IrisAgent

  1. Open Deploy → Text channels.
  2. Select Use your Twilio number, then 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.
IrisAgent confirms that it can access the number and Messaging Service, that the number supports SMS, and that the number belongs to the Messaging Service sender pool. A successful connection does not independently confirm A2P campaign approval or that the approved use case covers the campaign you create in IrisAgent.

​
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.
  4. Click Get number.
IrisAgent provisions a dedicated number for your workspace in a customer-specific Twilio subaccount. Number provisioning is separate from carrier approval: receiving a number does not mean it is ready to send.
The managed registration experience below requires the updated Text channels feature to be enabled for your workspace. If you do not see these controls, contact IrisAgent support. Connecting your own Twilio number remains a separate setup option.

​
1. Register your business

After your number is provisioned:
  1. Enter the email address that should receive registration updates.
  2. Click Start / resume registration.
  3. Complete the secure embedded business registration form with accurate company and tax information.
  4. Submit the form and wait for brand review.
If you close an unfinished form, use Start / resume registration to continue. Submitting the form does not activate sending. Recently submitted information can take a few minutes to appear in the status shown by IrisAgent.

​
2. Register your messaging use case

After the brand is approved:
  1. Click Register messaging use case on Text channels.
  2. Complete the separate embedded campaign-registration form, including the purpose of your messages, representative samples, and opt-in information.
  3. Ensure the opt-in description matches the actual experience recipients see.
  4. Submit the form for campaign review.
You do not need to enter the business notification email again to open this step. An approved brand alone is not enough to send messages.
A messaging-use-case registration is the Twilio A2P registration associated with your Messaging Service. An Outbound campaign in IrisAgent is a particular message and CSV audience. Creating an Outbound campaign does not create or approve a carrier registration.

​
3. Wait for number activation

After campaign approval, IrisAgent waits for confirmation that the selected number is registered to that campaign. The managed sender becomes Active only after the business, messaging use case, and number have completed the required approvals. Text channels displays these stages: The status banner summarizes the current state: Click Refresh status to retrieve the latest registration state. The page also refreshes approximately every 30 seconds while no registration form or setup action is open. You do not need to leave the page open for provider updates to be processed.

​
Correct a rejected registration

If a brand or campaign is rejected, IrisAgent shows the available rejection reason. Click Correct registration to reopen the appropriate form and address the requested changes. Registrations awaiting review cannot be edited. For number-registration problems or a status without a correction button, contact support.

​
Get help with registration

When a registration action is available, use View required details to review Twilio’s business-information checklist, or Email us details to open a prefilled email to IrisAgent support. You can also email support directly. Share general business and messaging details by email. Do not email API secrets, tax identifiers, or identity documents; ask support for a secure way to provide sensitive information.
Purchasing a number, approving a Business Profile, approving a Brand, or enabling Twilio Compliance Embeddable access does not by itself authorize outbound SMS. Embeddable access only enables the registration forms; each managed customer’s brand, campaign, and number still need the applicable approvals. Mock/demo approvals do not authorize real messages.

​
Prepare a contacts CSV

Create a CSV with a phone_number column. You can optionally add first_name for personalization.
CSV requirements:
  • phone_number is required. IrisAgent also recognizes phone, mobile, and mobile_number as phone-column headings.
  • first_name is optional. first name, firstname, and name are also recognized.
  • Numbers must be valid US numbers. Formatting characters are allowed; IrisAgent normalizes accepted numbers to E.164 format.
  • Duplicate phone numbers are included once.
  • Invalid rows are skipped and reported after import.
  • A campaign can contain up to 1,000 unique recipients in the initial release.
Upload only recipients who explicitly agreed to receive texts from your business. A prior purchase, support interaction, or possession of a phone number is not automatically SMS consent. Maintain your own consent records and honor opt-out requests.

​
Create a campaign

  1. Open Outbound from the IrisAgent sidebar.
  2. Click Create campaign.
  3. Enter a campaign name. This is visible only to your team.
  4. Write the message recipients should receive.
  5. Upload the contacts CSV.
  6. Review the number of valid and skipped contacts.
  7. Confirm that every recipient has explicitly opted in.
  8. Click Save draft.
Click any campaign row to review its message, audience size, consent confirmation, and delivery metrics. Use Configure at the top of the Outbound page to return to Deploy → Text channels.

​
Send and monitor a campaign

  1. Open the saved campaign and review its message, audience, and consent confirmation.
  2. Ensure your text channel is active, then click Send campaign.
  3. Monitor the delivery metrics and any recipient-level failures on the campaign details page.
For managed numbers, IrisAgent rechecks registration before dispatching a campaign. If registration cannot be confirmed, sending is blocked. For customer-owned Twilio numbers, you remain responsible for registration and use-case approval even when the connection is active. API acceptance or a sent message is not proof of delivery. Twilio can report a later carrier failure. The campaign details page displays reported delivery errors with recipient information, a failure description, and a Twilio error-code link when available. A completed send operation does not mean every recipient received the message.

​
Personalize a message

Use {{first_name}} wherever the recipient’s first name should appear:
The campaign preview substitutes a sample name so you can check the finished message. Contacts without a first name should be reviewed before sending a personalized campaign.

​
Message length and opt-out language

The editor shows the message length and an estimated SMS segment count. Messages longer than a single segment may be split by the carrier and can cost more to deliver. Non-GSM characters can also change segment length. Include clear sender identification and opt-out language appropriate for your program, such as Reply STOP to opt out. Carrier and legal requirements vary by use case and jurisdiction; your organization is responsible for ensuring its campaign and consent process comply with applicable requirements.

​
Troubleshooting

​
I received a number, but sending is not available

Number provisioning and carrier registration are separate. Open Deploy → Text channels, click Refresh status, and check the current stage. After brand approval, you must complete Register messaging use case. Campaign approval is followed by number registration; sending remains unavailable until the managed sender is Active.

​
My business was approved, but I still cannot send

Check which approval you received. A Twilio Business Profile approval or Compliance Embeddable enrollment is not a completed customer campaign registration. Brand approval unlocks the messaging-use-case form; it does not activate the number. Follow the remaining stages in Text channels.

​
I submitted a form, but the page still offers registration

Submission is not approval, and provider records may take a few minutes to appear. Click Refresh status before retrying. If the form is still a draft, the registration action resumes it. If the discrepancy persists, contact support rather than creating a new number.

​
Status refresh or registration is unavailable

Read the inline error and retry shortly. If the error says embedded registration is not enabled, contact IrisAgent support to confirm access for the managed account. Do not purchase another number or assume that an existing business-profile approval resolves this error.

​
Twilio connection fails

Confirm that:
  • The Account SID begins with AC, the API Key SID begins with SK, and the Messaging Service SID begins with MG.
  • The restricted API key was created in the same account or subaccount that owns the number and Messaging Service.
  • The phone number is SMS capable.
  • The phone number appears under the selected Messaging Service’s Senders tab.
  • The restricted API key has permission to read those resources and create outbound messages.

​
Twilio reports error 30034 or an undelivered message

Twilio error 30034 means a US local 10DLC message was sent from an unregistered number. Open Messaging → Messaging Services, select the service connected to IrisAgent, and check Compliance → 10DLC. Associate the service with the applicable approved A2P campaign or complete its registration before sending again. Activating an outbound campaign in IrisAgent does not create or enable a Twilio A2P campaign. They are separate:
  • An IrisAgent campaign defines the message and recipients and starts the send operation.
  • A Twilio A2P campaign registration tells US carriers who is sending, the approved use case, and which Messaging Service is authorized.
Twilio may initially accept an API request and later mark the message Undelivered after receiving a carrier response. Check the campaign details page in IrisAgent for reported delivery errors. If the final state has not appeared yet, refresh the campaign and compare it with Twilio → Messaging → Logs. Contact support if the discrepancy persists; include the campaign and error code, never your API secret.

​
My CSV was rejected

Confirm that the file:
  • is saved as CSV
  • includes a recognized phone-number heading
  • contains valid US phone numbers
  • contains no more than 1,000 unique valid recipients

​
Some rows were skipped

IrisAgent skips rows with missing or invalid phone numbers and removes duplicates. Correct the source file and upload it again if those contacts should be included.

​
Registration is taking longer than expected

Business and campaign reviews are separate, and timing varies; the UI does not guarantee an approval date. Monitor the notification email and the current stage under Deploy → Text channels. If the status changes to Needs attention, read the reason and use Correct registration when offered. If the number remains pending after campaign approval, contact support to check number-registration updates rather than retrying campaign sends. For help, contact IrisAgent support.