We use cookies to ensure you have the best browsing experience on our website.

Secure access for AI assistants to customer accounts

Customers plug in the assistant they already use and run the platform by talking to it, with consent, data isolation and instant revocation.

Attentive
Client
Attentive
Industry
MarTech / SaaS
Country
United States
Project type
AI product · Security and compliance

At a glance

Before

Attentive was left out of its customers' AI workflows and had no way to give a third-party assistant safe access to an account.

After

Customers now plug in the assistant they already use and create campaigns, segments and journeys by talking to it, with consent, isolation, auditing and instant revocation.

The client

A US conversational marketing platform (SMS, MMS, RCS, email and push) for retail and e-commerce brands. The channel is used by its customers' marketing teams and by agencies.

The product and our role

Two fronts, both built from scratch:

  • The platform's AI channel (MCP): the customer's assistant pulls reports and creates or edits campaigns, journeys and segments, always within what the user could already do.
  • An authorization server: "connect your Attentive account to your AI assistant", with sign-in, app approval, short-lived credentials and disconnection.

The channel has been in beta since August 2026.

The challenge

  • Customers wanted Attentive inside the workflows they already ran with AI agents, and competitors had already launched the equivalent.
  • There was no safe way for a third-party AI app to access a customer's account: no consent, no trail, no revocation.
  • The launch depended on passing the security review.

What we delivered

  • Account connection to any assistant that follows the standard (MCP and OAuth), with no point-to-point integration. Validated with Claude Code and ChatGPT Codex.
  • Reports and analyses by talking to the assistant.
  • Campaigns (SMS, MMS, RCS, email): create, schedule, pause and resume.
  • Automated journeys, reviewed before they are published.
  • Segments, templates and brand identity.
  • Read-only connections by default, with explicit confirmation before writing.
  • Auditing and observability of every action.
  • Security, as already published in Attentive's Help Center: OAuth with per-app approval, no password handed to the assistant, and existing permissions respected. Attentive receives only the tool call, never the conversation.

Results

  • The channel went from zero to production.
  • An open, self-service beta, at no extra cost to customers.
  • Recurring adoption from the first month.

Let's talk about how we can help you and your team

After you get in touch, one of our team members will reach out to schedule a time to talk.

What is your budget?*
Prefer email? You can write us directly at