Introduction

Xenia is the AI Marketer for Commerce. You tell it what you want to achieve, and it plans the audiences, writes the content, builds the journey, simulates it, and keeps optimizing after launch. All of it happens in one workspace, on top of the customer, order, and content data you already have.

What Xenia does#

A traditional marketing stack splits the work across a segmentation tool, a content tool, an email or SMS platform, an experimentation tool, and a spreadsheet holding it all together. Xenia collapses that into a single decisioning layer:

• Unify the data. Connectors pull customers, orders, checkouts, products, content, and behavioral events into one normalized profile per person.
• Build the audience. Segment on traits and behavior, or describe the audience you want in plain language.
• Create the content. Generate email, SMS, push, and storefront copy that is aware of the persona and your brand voice.
• Orchestrate the journey. Compose multi-step, cross-channel lifecycle journeys in a visual builder, with branching, waits, and experiment nodes.
• Govern the launch. Route work through approvals, simulate the logic before anyone receives a message, and enforce consent and frequency caps at send time.
• Measure and optimize. Attribute conversions per channel and per journey, then shift traffic toward what wins.

How the work flows#

Every piece of work in Xenia moves through the same eight stages. You can enter at any point, and you can stop after any of them.

Core concepts#

The workspace#

The sidebar groups every module into four sections.

Overview#

Workspace is the landing surface: a role-aware summary of what needs your attention and what to do next.

Orchestrate#

Where campaigns get built.

Operate#

Where campaigns are validated, shipped, and measured.

Govern#

Where access, identity, and billing are administered.

Roles#

Access is role-based, and the sidebar only shows what your role can reach.

Channels#

Journeys deliver through the channels you have connected:

• Email via SendGrid, Amazon SES, or any SMTP provider
• SMS via Twilio, Amazon SNS, or a custom HTTP gateway
• Push and in-app via Firebase Cloud Messaging, OneSignal, or APNs
• WhatsApp via the WhatsApp Business Cloud API
• Voice via generated calls
• Web and storefront experiences, including on-site personalization and served page variants on Shopify

Beyond delivery, connectors cover commerce and content platforms (Shopify, Contentful, Content Cloud, Cloudinary, Amazon S3), CRM and marketing platforms (HubSpot, Klaviyo, Meta), analytics (Google Analytics 4, Amplitude), and forwarding conversions on to Meta, TikTok, and LinkedIn.

Two ways to run Xenia#

Guardrails#

The rules that keep campaigns safe are applied automatically when a message is about to go out, not left to whoever built the journey:

• Consent. Anyone who has not agreed to marketing is not messaged, whatever the journey says.
• Frequency caps. Limits per person and per channel stop several journeys landing on the same customer at once.
• Approvals. Work can require sign-off before it goes live, and decisions are recorded.
• Separation. Each workspace's data stands on its own, and so does each environment.
• Your data is not used to train AI models. It is used to produce your content and decisions, nothing else.

Next steps#