Skip to content
Victoria AI
Automations

Describe the workflow in plain English and it gets built.

A visual editor, creation by natural language and a simulator that tests every branch of the workflow without sending anything to any customer.

Book a demoSee Quotes and sales

24 triggers · Messaging, AI, lead, sales and flow control actions · A time window per workflow

The problem

Automating is scary, and rightly so.

It depends on somebody technical, it cannot be tested beforehand, and when something goes wrong the error shows up on the customer side.

  • It depends on somebody technical having time

    The person who knows the sales process does not build the workflow, and the person who builds the workflow does not know the process.

    Victoria solves:

    You describe the automation in plain English and the AI builds it. To change it, you ask in conversation: the changes are painted over the current workflow.

  • Nobody turns a workflow on without fear

    The only way to test it is to send real messages to real customers and cross your fingers.

    Victoria solves:

    The simulator replays the whole conversation without sending anything. The "test every branch" mode enumerates every combination of conditions.

  • When it fails, nobody knows why

    The workflow switches off, the message does not go out and the diagnosis is an error code that says nothing.

    Victoria solves:

    A run history with the conditions evaluated, the expected value against the real one and the outcome of each action explained in plain language.

  • The workflow and the AI talk to the customer at once

    Two different replies to the same message, thirty seconds apart.

    Victoria solves:

    Per workflow you choose whether the AI stays quiet while the workflow writes, whether it does not reply for the whole run, or whether it replies anyway.

On screen

Build it, test it, measure it.

app.victoriassistant.com
Victoria CRM visual workflow editor: the node palette on the left and, on the canvas, the chain that goes from the "message received" trigger to the time window condition and from there to sending the message, with the minimap in the corner

You drag the node onto the canvas and connect it with a line. Zoom, minimap, inserting a node in the middle of an existing connection, duplicating and deleting by dragging.

Ready-made templates are cloned with one click and are always created inactive, as drafts, so they can be reviewed before being turned on.

  • 24triggers available
  • 7action categories
  • 2simulator views
Control

Automatic does not mean without rules.

The workflow runs when it should, talks to the customer when it should, and is fired by whoever should fire it.

Every run is logged with its outcome, the conditions it evaluated and the reason for the error in plain language.

  • Living alongside the AI

    Per workflow you choose whether the AI stays quiet while the workflow writes, whether it does not reply for the whole run, or whether it replies anyway. The system coordinates who talks to the customer.

    Workflow settings window: the question "What does the AI do while this workflow runs?" with its three options — automatic, always quiet and always active — the first one selected, and the note that this only controls whether the AI replies

  • Execution time window

    Hours, days of the week and time zone, with 10 time zones supported. The workflow does not send messages at three in the morning.

  • Simple mode and advanced mode

    Simple mode hides the technical actions for business users. Advanced leaves everything on show.

  • Manual execution from the chat

    You define which users can fire each workflow by hand on one specific lead, without waiting for the trigger.

  • Ready-made templates

    They are cloned with one click and are born inactive, as drafts: they are reviewed and only then turned on.

  • Success and error branches

    Every action has its green branch and its red branch, connectable separately. You decide what happens when something goes wrong.

Fine detail

What gets checked in the first demo.

30 days

No workflow is left hanging

Time waits have a hard cap of 30 days and event waits carry a mandatory timeout, 24 hours by default.

HTTPS

Webhooks require HTTPS

An address starting with http:// is blocked, with a warning that the customer data would travel unencrypted.

Filter required

It does not fire at the whole base

The time window trigger requires at least one lead filter: stage, tag or source.

24 h to 90 days

You know what breaks, and how much

A recent failure counter per workflow, with a window of 24 hours, 7, 30 or 90 days, and the option to clear the failure history.

Per node

The statistics live on the canvas

Each node shows how many runs went through it, the conversion rate and the most frequent failure reason.

Plain language

The error reads in plain language

The history shows the condition evaluated, the expected value, the real value and what each action returned.

Keep going

The module that comes next.

Next step

We build your first workflow in the demo.

You tell us about a follow-up somebody does by hand today, we describe it in plain English and we test it in the simulator right there.

Book a demoChat on WhatsApp

The simulator sends nothing to any real customer.

WhatsApp