platform / the assistant
Ask for it like you'd ask a teammate.
“Draft the launch email for enterprise trial accounts and set it up as a batch send.” That sentence is a complete, executable campaign brief — and watching the assistant execute it is the fastest way to understand veloquent.
Every step is a real tool call you can expand — no black box.
It does the work, visibly
The assistant isn't a chat window bolted onto the side — it uses the same primitives you do. It queries your warehouse, previews and sizes the audience, drafts the email, wires the workflow, runs QA, and submits the result for review, narrating each step. You can watch it, interrupt it, or take over in the UI at any point: hand-built and assistant-built are the same objects.
What it hands you is a normal email you can edit by hand — tokens intact.
Your data, the right model
Generation runs through Vercel's AI Gateway, which means the right model for each job and no lock-in to a single vendor — and it draws on the sources you connect, so emails, workflows, and audiences come out grounded in your actual data rather than generic.
In Slack too
A paired Slack agent extends the surface: approvals and status checks today, with a conversational agent — ask for a change, get a draft back in the thread — next on the roadmap. The rule never changes: whatever the agent builds waits at the review gate until a human approves it.
Questions operators ask
- Can AI send marketing emails without approval in veloquent?
- No. The assistant can build everything — audience, email, workflow — but what it builds enters the same review queue as human work. A person approves before anything sends or enrolls.
- What can the veloquent assistant actually build?
- Campaigns, emails, audience segments (including from warehouse queries), batch sends, and evergreen journeys. It also runs QA checks and submits its own work for review.
- Which AI models does veloquent use?
- veloquent routes model calls through Vercel's AI Gateway, so different jobs can use different models and the platform is never locked to one provider.
Follow the build.
One email when something ships. Or better: bring us the thing your MAP won't fix.