Add a "Wait until" node in Workflows
Rather than a straight delay, add a node in Workflows that "waits until" a user has triggered an event (or other action).
Trigger Workflow based on email events (sent, delivered, opened, clicked)
Trigger Workflows based on email events, not just the events that you trigger manually.
Prevent email from sending based on Fusion data
Some campaigns can be hard to (reliably) implement because they're dependant on state that's difficult to piece together from events alone. For example, an "Abandoned cart" campaign might trigger based on adding something to a cart without placing an order. But what if the cart content was removed, expired, or otherwise unavailable due to some other action there might not be any events for (or there are too many events to make a reliable workflow/automated campaign). A simple Fusion endpoint that queries the current state of the cart, and that could prevent the sending of email in the case of empty carts would make implementing this kind of campaign trivial. (Abandoned cart is simply an example, another one could be reminder mails for discounts that are about to expire but that might have been redeemed by another user)
"Converge" branches in Workflows
When using a branch node in a workflow, add the ability to take customers back to the main path. This would reduce the need to replicate parts of the workflow in many cases.
Ability to remove suppression from user profile
Review and remove suppression status on a user profile in the Vero UI.
Liquid/Fusion error Notification
Receive notification if email doesn't send due to Liquid/Fusion errors.