AI Agents for Text

AI agents that run on SMS. They send proactive outbound campaigns to opted-in lists, and they resolve inbound customer conversations. Replies are grounded on your knowledge base, ticket history, and procedures, so the conversation is personalized, not a blast template. Overlay on the helpdesk you already have.

No. IrisAgent stays on Zendesk, Salesforce, Intercom, Freshworks, HubSpot, and the rest of the stack you already run. Text is an additional channel on that overlay.

The agent is grounded on your knowledge and uses procedures to run the conversation, not just fire a one-line blast. Outbound campaigns and inbound replies share that same grounded context.

Yes. You own 10DLC and A2P registration, consent records, and Twilio billing. IrisAgent verifies the credentials, SMS capability, Messaging Service, and sender-pool membership. Connecting a number is not A2P approval. Twilio integration: https://irisagent.com/twilio/

IrisAgent can provision a dedicated US number for your workspace as soon as you request it. Carrier registration is separate and often takes 1 to 2 weeks. Sending waits until the number is Active.

Upload only contacts who explicitly agreed to receive texts from your business. A prior purchase, support ticket, or having a phone number is not SMS consent. US numbers only. A campaign can include up to 1,000 unique recipients. Include STOP language such as Reply STOP to opt out.

No. SMS is a separate channel. Voice AI answers and places phone calls on https://irisagent.com/voice-ai/. Do not reuse a Voice procedure as a text campaign.

Open Deploy, then Text channels in IrisAgent. Full steps: https://docs.irisagent.com/deploying-irisagent/Outbound-SMS