Live

VeLens Cloud

The web app: an AI workspace for your org, a morning Org Health snapshot, and the controls that decide what your whole team can do. Any browser, nothing to install.

Ask it what you'd have raised a ticket for

The agent plans, calls real tools against your org, and answers with live data. Anything that changes something is proposed first and runs only when you confirm.

Debug what broke

"Did the Welcome Series run last night?" It reads the automation's run history and tells you which runs failed and which step failed in them, so you start from the answer instead of the click-maze.

Explain the numbers

Send rollups and bounce categories in plain words: what went out, how it performed, and whether a spike is a hard bounce problem, a block, or something temporary.

Reach across business units

Ask about any business unit your connection can reach, and switch between them in the same conversation. Every answer says which unit it came from.

Answer the "how does this work" ones

Built-in Marketing Cloud knowledge covers the vocabulary and AMPscript basics, so you can ask what a term means or how a piece fits together without leaving to search.

Draft the email

Describe the email and it builds a real one in Content Builder, or edits an existing asset block by block. It shows you the change and waits for your confirm before writing.

Never about one person

The agent works in aggregates. It can tell you hard bounces tripled and which send caused it; it cannot look up an individual. Subscriber lookups run outside the AI entirely and never reach a model.

One place to govern both surfaces

Set it here and the Chrome extension follows, so you are not configuring people's browsers one at a time.

  • Turn a feature off and it leaves your team's extensions within minutes
  • Five roles, and only an owner can change them
  • Every AI action and every write lands in an audit log

Org Health, waiting for you each morning

One snapshot per day: contacts against your limit, sends over 24 hours, 7 days and month to date, overnight automation failures, and how many journeys are running. Read-only for everyone on the team.

Collecting it writes nothing into your org. No Query Activity, no target data extension, no automation is created to gather any of it.

The same app, inside Marketing Cloud

VeLens Cloud isn't only a browser tab. The same web app opens from Marketing Cloud's own app menu, one click from the navigation your team already uses. Useful for teams that can't add extensions to managed machines.

STEP 01

An admin enables it once

An administrator adds the VeLens app component to your Marketing Cloud tenant through the Installed Package, and enables the package in each business unit you want reachable. One-time setup, done by one person.

STEP 02

It appears in the app menu

VeLens shows up alongside Email Studio, Journey Builder and the rest, right where your team already looks.

STEP 03

Click it and you're in

Sign-in happens silently against your SFMC identity as the app loads. No second login, no password, and nothing installed on the machine.

The same brain as the extension

VeLens Cloud isn't a separate product with its own logic. The workspace here calls the same server-side agent loop and the same Marketing Cloud tools as the Chrome extension, with the same business-unit scoping and the same confirm-gated writes. Learn a workflow in one and it behaves the same in the other.

See how the platform works →

  • One account, one connection. Connect your org once through your own SFMC Installed Package. If you already connected the extension, VeLens Cloud recognizes the same org with no second setup.
  • Same guardrails everywhere. No subscriber row data ever reaches the model, tokens stay server-side and encrypted at rest, and you can revoke from SFMC Setup at any time.