Attentive AI in 2026: What AI Pro, Concierge, and AI Journeys Actually Do
If you searched “Attentive AI,” you probably meant one of two very different things, so start here: Attentive Mobile — the SMS and email platform DTC brands use — sells a family of paid AI add-ons under that name. Attentive.ai (the domain, formerly iBeam.ai) is an unrelated construction-tech company that generates takeoffs and estimates for contractors and landscapers. Same word, no relationship. If you’re reading this because your Attentive rep pitched you on “AI Pro,” you’re in the right place.
The short version for the marketing side: Attentive’s AI is real, it ships today, it is priced as a set of add-ons rather than included in your base contract, and it is almost entirely aimed at making the messages you already send perform better. What it does not do is the operational work around the program — the reporting pulls, the cross-tool reconciliation, the “did anyone follow up on this” work that eats a retention marketer’s week. That gap is the interesting part.
What Attentive actually sells under the “AI” name
Attentive has broken its AI out into separately-marketed products. As of mid-2026 these are the named ones:
AI Pro is the predictive bundle, and it’s the one most people mean. It contains four capabilities: Identity AI (recognizing shoppers beyond the browser cookie so profiles persist), Audiences AI (automatically adding subscribers likely to purchase to a campaign audience and removing those unlikely to buy), Send Time AI (per-subscriber send timing based on engagement history), and Brand Voice AI (copy generated from your own past top-performing messages rather than a generic model voice). Attentive’s own AI Pro page frames all four as campaign-performance levers, and its pricing page lists AI Pro as a flat monthly fee on top of your messaging contract.
AI Journeys applies the same idea to triggered messaging: instead of you hand-building a branch for every behavior, the AI decides timing, frequency, and the specific copy, images, and product recommendations per shopper, then adjusts as more behavior accumulates.
AI Grow works the acquisition end — the sign-up units, the offers, the on-site experiences that turn traffic into subscribers.
AI Essentials is the entry-level generative tier: on-brand SMS and email copy, plus retargeting campaign scaffolding. This is the descendant of what Attentive originally launched as “Magic Message” back in 2023.
Attentive Concierge is the odd one out and worth understanding separately. It is not purely AI — it’s a hybrid where conversational AI and live human agents share a two-way SMS thread (Attentive brands the channel LiveSMS). The AI handles routine buying questions, product recommendations from purchase and browse history, and checkout help; humans take the messy ones. Attentive positions it as a revenue channel, not a support cost center, and it’s sold as a managed service, which is why nobody publishes a price for it.
On pricing: Attentive does not publish numbers. Their pricing page says quotes are built from message volume, subscriber list size, number of channels, and which AI products you select. Treat every AI product above as a line item you will negotiate. If a rep tells you AI is “included,” ask specifically which of AI Pro, AI Grow, AI Journeys, and AI Essentials that covers — they are not the same SKU.
The honest limitation: all of it lives inside Attentive
Every feature above optimizes messages that Attentive is already sending. None of it reaches outside the platform. Send Time AI will not check whether your warehouse actually has the SKU you’re promoting. Audiences AI will not notice that your Shopify inventory feed broke last Tuesday. Brand Voice AI will not tell you your Klaviyo-era welcome flow is still running in parallel and double-messaging 3,000 people.
That’s not a knock on Attentive — it’s the shape of every in-app AI. The work that stays manual for a retention marketer is the connective work: pulling weekly campaign performance into the deck the CMO wants, cross-checking SMS revenue against the Shopify numbers, chasing the merchandiser about which drop needs a send next Thursday. Attentive’s AI does not touch any of it, and neither does Klaviyo’s — we covered the equivalent boundary in the Klaviyo MCP writeup.
Attentive’s public API: self-serve, and better than you’d expect
This is where Attentive is genuinely more open than a lot of vertical software. You can generate your own API key without talking to a partner manager.
The path: go to the integrations setup page at ui.attentivemobile.com/integrations/index, click + Create App in the top right, name it, add a contact email, then set per-API permissions — each of Custom Attributes, Custom Events, eCommerce, Privacy Request, Product Catalog, and Subscribers defaults to No Access and you grant Write where you need it. Click Create and a modal shows the key. Copy it then; Attentive’s docs are explicit that this is the only time it’s shown. Keys are managed afterward on the Built by you tab.
That key is a bearer token against api.attentivemobile.com, and there’s both REST and GraphQL. Rate limits are generous for most endpoints (150 requests/second) with tighter caps on the sensitive ones — Identity and Subscribe at 10/sec, Unsubscribe at 5/sec, Product Catalog uploads at 1/sec.
What you can do with it: create and update subscribers with attributes and identifiers, check a user’s subscription eligibility before you message them, unsubscribe users, push custom events and custom attributes, send ecommerce events (product view, add to cart, purchase), upload product catalogs, load discount codes into an existing offer, submit privacy deletion requests, and resolve identity across phone, email, Shopify ID, and Klaviyo ID.
What you can’t do: there is no endpoint to create or send a campaign, no endpoint to build or read a segment, and no reporting or analytics endpoint. The API is a data pipe into Attentive and an identity/subscription manager — it is not a remote control for the sending side. Anyone promising you an AI that “writes and sends your Attentive campaigns for you” via the API is describing something the API does not expose.
The genuinely useful bit is webhooks. Attentive lets you subscribe an endpoint to real events: sms.subscribed, sms.sent, sms.message_link_click, email.subscribed, email.unsubscribed, email.opened, email.message_link_click, and custom_attribute.set. You can create those subscriptions in the UI or through the API itself. Hold onto that — it matters below.
There are also legacy APIs still in circulation that use different tokens and require emailing Attentive to obtain. If you inherited an integration built on those, the current docs recommend moving to the modern APIs.
Can ChatGPT or Claude connect to Attentive?
No. Neither has a native Attentive connector, and there is no Attentive MCP server — the MCP registry returns nothing for it, and Attentive has not shipped one. Klaviyo has an official MCP server; Attentive has not followed.
What that leaves is the general-purpose path: an assistant that can make authenticated HTTP calls with your Attentive key. That works for reads and writes the API supports, and it inherits the API’s ceiling — you can look up whether a phone number is eligible for SMS, you can push a custom event, you cannot make it send a campaign.
The other thing worth being precise about is when an assistant can act.
Scheduled work is available in ChatGPT and Claude Cowork, but their ordinary schedulers are clock-driven rather than generic listeners for changes in connected business apps. ChatGPT Workspace Agents add API-triggered runs, with another system responsible for detecting the event and making the call.
For Attentive specifically, that limit bites in an obvious way. The events you care about are things like a subscriber opting in from a new sign-up unit, or a high-value customer clicking a link and not converting. Attentive publishes exactly those as webhooks. But a chat assistant has nowhere to receive a webhook — it has no always-on endpoint listening. So the richest signal Attentive gives you is one that ChatGPT and Claude structurally cannot consume. A scheduled task can poll and check things on a clock; it cannot wake up because sms.message_link_click fired.
Where an automation layer fits instead
The practical division of labor for a DTC retention team running Attentive looks like this:
- Attentive’s own AI decides what to say, who to include, and when to send. Pay for AI Pro if segmentation and send-time work is currently eating your week; that’s what it’s for.
- An outside automation layer handles everything that crosses tool boundaries and everything that needs to fire on an event rather than a clock.
That second category is where Carly sits. Attentive isn’t a native Carly connector, so you paste your own Attentive API key at carlyassistant.com/integrations and Carly works against the same REST and GraphQL endpoints described above — with your permissions, your rate limits, your scopes. Because Carly runs as always-on workflows rather than a chat session, it can be the endpoint an Attentive webhook posts to, which is the piece a chat assistant can’t provide.
Concrete shapes that fall out of that:
- A subscriber opts in through a new in-store QR sign-up unit; the
sms.subscribedwebhook fires; Carly tags the record in your CRM and drops a line in the growth team’s Slack channel so nobody has to check the sign-up report on Monday. - Every Friday at 4pm, pull the week’s campaign-level numbers, reconcile SMS-attributed revenue against Shopify orders, and email the merchandising lead the two-line summary they’d otherwise ask for on Monday.
- When your product feed marks a hero SKU out of stock, flag any Attentive campaign scheduled against it before it sends — the failure mode Send Time AI cannot see.
- Push loyalty tier or subscription status from your billing system into Attentive as a custom attribute nightly, so Audiences AI is segmenting on data that’s actually current.
Carly’s pricing is free Zapier-style workflows, with AI agents from $35/month — which matters here mostly because most of the work above is plumbing, not reasoning, and plumbing shouldn’t cost you per run. If you’re comparing the wider category first, the marketing AI agents roundup and the ecommerce sellers guide cover adjacent options.
SMS compliance is a real constraint on all of this
Two things to get right before you automate anything that touches subscribers.
Programmatic opt-in is not just an API call. Attentive’s docs on the Subscribe endpoint are explicit: when you opt someone in programmatically, a legal disclosure is required — the specified marketing disclosure language for marketing messages, or a transactional opt-in unit for transactional ones. Every request also needs either a sign-up source ID (visible in the ID column of the Sign-up Units tab) or a matching locale plus subscription type, and phone numbers must be in E.164 format. An automation that silently subscribes people from an imported list, without a real consent capture behind it, is a TCPA problem regardless of how clean the code is.
Send windows are not optional. TCPA restricts telemarketing messages to between 8 a.m. and 9 p.m. in the recipient’s local time — not yours, not your server’s. Several states impose tighter windows. This is a constraint Send Time AI already respects inside Attentive, but if you build any outside automation that triggers messaging, that timezone logic is now yours to get right. It’s a good reason to keep the actual sending inside Attentive and use the outside layer for the surrounding work.
Revocation propagates slowly if you let it. If a subscriber replies STOP, Attentive handles it inside Attentive. If your automation also writes that person into another messaging system, you own keeping the opt-out in sync. Note that Attentive’s webhook list includes email.unsubscribed but no equivalent SMS unsubscribe event, so for text opt-outs you’ll be checking subscription eligibility through the API rather than waiting to be told. Either way, don’t put a subscriber’s number into a second system you can’t keep in sync.
FAQ
Is Attentive AI included in my plan? Not by default. Attentive prices quotes on message volume, subscriber count, channels, and which AI products you select. AI Pro is listed as a flat monthly fee on top of your base contract, and AI Grow, AI Journeys, and AI Essentials are separately marketed products. Ask your rep to name the specific SKUs.
What’s the difference between AI Pro and AI Essentials? AI Essentials is generative — on-brand SMS and email copy plus retargeting campaign scaffolding. AI Pro is predictive: Identity AI, Audiences AI, Send Time AI, and Brand Voice AI, aimed at who gets a message and when.
Is Attentive Concierge fully automated? No. It’s a hybrid of conversational AI and live human agents on the same two-way SMS thread. The AI handles routine product and checkout questions; agents take the rest.
Can I get an Attentive API key myself?
Yes. Create a custom app at ui.attentivemobile.com/integrations/index via + Create App, set per-API permissions, and copy the key from the modal — it’s shown only once. No partner approval needed. If you can’t access the Attentive platform at all, Attentive’s docs point you to their API tokens contact address.
Can the Attentive API send a campaign? No. There is no campaign-send, segment, or reporting endpoint. The API covers subscribers, custom events and attributes, ecommerce events, product catalog, offers/discount codes, identity resolution, privacy requests, and webhooks.
Does Attentive have an MCP server? No. There’s no official Attentive MCP server and no native ChatGPT or Claude connector. Access is via your own API key through a tool that can make authenticated HTTP calls.
Is “Attentive AI” the same as Attentive.ai? No. Attentive.ai (formerly iBeam.ai) is a construction takeoff and estimating company serving contractors and landscapers. Attentive Mobile is the SMS and email marketing platform. Unrelated companies.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
