This is your place to share feedback, request new features, vote for the ideas that matter most to you and get updated on our progress.
Welcome to the Vero feedback portal.
Planned
Allow Batching with A/B Test Newsletters
After the initial A/B test group runs, let the remaining percent be batched.
Planned
MCP: Ability to schedule a Broadcast via the MCP server
Rather than requiring human approval, ability to schedule the Broadcast campaign using the MCP server.
Planned
MCP: Provide a CSV / list as the audience for a broadcast
As in the Vero 2.0 UI, support providing a list of users/CSV as exported from another tool (e.g. Snowflake or Metabase MCP).
Planned
MCP: Set up queries to match templates and schemas
Let the AI set up complex queries and ensure the data pulled from the warehouse matches their templates. If the MCP understood the schema of the data sources, it could help write the right query and then draft the broadcast template matching that query, ensuring everything works well end-to-end.
Completed
MCP: Message search tool (to find messages in journeys, etc.)
A way to search all messages across Vero to find the source of a message. E.g. based on a string or other details. Where users have a lot of journeys it can be difficult to locate certain messages.
Completed
MCP server v1.0
An official MCP server to enable AI assistants such as Claude and Gemini to interact directly with Vero. Our initial release, as covered by this feature request, will focus on the following functionality: Ability to list all campaigns (broadcasts and journeys). Ability to read-only query the contents of a journey, for interrogation of what a journey covers and what messages it contains. Ability to read and write broadcasts. Ability to read and write campaign content, for both messages inside journeys and broadcasts. We will then expand functionality to include querying campaign results, logs and user profiles. We’ll create follow-up feature requests for these to more easily track progress.
Backlog
Ability to disable Desktop/Mobile views in DND editor for entire email
Add the ability to toggle all elements in an email to “Both”, removing any differences between desktop and mobile for the entire campaign.
Backlog
Catch textual differences between desktop and mobile email views
Catch textual differences between desktop and mobile email views on save, and require editor approval.
In Progress
Vero 2.0
We're bringing everything you love about Vero to a completely rebuilt platform. Vero 2.0 is a ground-up rebuild designed to let us move faster and deliver the messaging automation features you've been asking for. This kind of transformation takes time — we're methodically migrating every capability while making meaningful improvements along the way — but the result is a platform that's more powerful, more reliable, and built to evolve with your needs. We appreciate your patience and think you'll love what's coming. You can try Vero 2.0 today and we’re looking forward to making it the default interface soon.
Completed
Profiles in Vero 2.0
We’re bringing fully editable profiles to Vero 2.0. Previously labeled ‘Subscriptions’, we’re updating the UI to include the same detailed profiles from Vero 1.0 into Vero 2.0, giving you full visibility to all the data stored about a user, as well as the ability to edit and see all user activity in one place. This is a crucial update that allows us to bring an entirely new Segmentation experience to Vero 2.0 later this year.
Backlog
Add a webhook for when a user's preferences have changed
For the Beta Preference feature, it would be great if there was a dedicated webhook for these changes. As of right now, only the user_updated webhook contains this data, but it’s extremely noisy because it gets triggered so frequently.
Backlog
Add the ability to toggle whether a newsletter allows duplicates to be sent
Some customers need to maintain multiple profiles with an identical email address in their projects. However, there are times when they want to send a newsletter that will only send once per email, regardless of how many profiles with that email address are in the newsletter audience. Adding the ability to toggle this on/off on a per newsletter basis would be an ideal solution.
Backlog
Reporting: improve project-level reporting
Help provide insight on the performance of Vero and the improvements driven by messaging across the business. Metrics that might be included: Total reach. Overall customer growth. Over unsubscribed customers growth. Metrics for the above vs. hold out group (who receives no messages). Insights into deliverability and movements. How often are customers messaged? How does this change over time? Compare a few groups/segments.
Backlog
A/B testing: create a global hold-out group
Ability to define a percentage of users that do not receive any campaigns at all and report on the performance of this group vs. other groups.
Backlog
User role: Customer support access to customer records but not campaigns
User role for customer support agents to search and see profile history but not campaigns.
Backlog
A/B testing: workflow improvements
Including: Ability to “pick a winner” and Vero automatically “handles” the other branches. Keep a history of what was there previously (see @Add versions to Workflows, Templates, etc. as this is related).
Backlog
Reporting: conversion reports improvements
Report on 1, 7 and 30 day windows. Report for multiple events. Ideally even “after the fact”.
Backlog
User role: Edit but not publish
Users that can edit campaigns but not publish changes. Relies on @Add versions to Workflows, Templates, etc.