An enquiry arrives, a quote is accepted, an invoice goes overdue — and the response happens without anyone having to remember it. You set the rule up once; from then on it sits in the list as a single sentence.
7-day free trial · no credit card · live in minutes

Three steps, no coding — your first rule takes a few minutes.
New enquiry, quote sent or accepted, quote expired, invoice paid or overdue, contract signed, event confirmed or cancelled, webshop order paid, email received — or a date: so many days before the start, or after the end.
Exactly the moment someone would otherwise have to catch
Narrow the rule down if it should only apply to certain cases — guest count, amount, event type, language. Then the actions: send an email from a template, notify the team, set a field, change tags, assign someone, wait.
The finished rule reads as one sentence
“Test rule” evaluates it against the most recent matching record and shows which path would apply, who would receive the email and with what subject — while nothing actually happens. Only then do you switch it on.
No blind first run on real customer data
When X happens, do Y.
Every rule carries that sentence above it: “When an invoice is overdue, send an email.” Skim the list and you know what is running by itself in your business — without opening a single rule.
Each rule can be switched on and off on its own, and its history shows when it fired and what every action did. Switching off and deleting always works, on any plan.

Install, review, adapt — it starts switched off.
Acknowledge a new enquiry, tell the kitchen once an invoice is paid, create tasks after a quote is accepted, follow up on an expired quote, inform the team about a cancellation. Install a template, look at the finished rule, adapt it to how you work. Three of the five run on any plan; the two that create tasks need Growth.
Univents warns you when a template overlaps with something already running: if your booking page already replies to enquiries automatically, that note sits on the template — otherwise the same customer would get two confirmations.

Several paths in one rule — the first match runs.
From Growth a rule can carry several paths, each with its own conditions: corporate events from 50 guests get a different reply and a callback task, everyone else gets the standard confirmation. The default path catches whatever fits none of the paths before it.
The canvas shows trigger, branch and actions as a flow instead of a chain of forms. A path's name shows up again in the history later and explains why the rule took that particular route.

Task, function sheet, production list, quote, run sheet.
From Growth a rule creates what someone would otherwise create by hand: tasks from a template, the function sheet for a confirmed event, the production list for the kitchen, a quote from your own quote template, or the run sheet. Status changes and sending your own email templates come with it.
If you would rather not click at all, describe the rule in one sentence and have it built: Univents assembles trigger, conditions and actions, you check the result and save. That route ends in an ordinary rule you can edit like any other.

Not for the simple rule. One trigger, conditions, actions, one path — that is included in every plan, the free one as well. Growth is what you need for branches, for rules that create tasks, function sheets, production lists, quotes or run sheets, for status changes, for your own email templates and for the AI rule builder.
Existing rules keep running, even the ones using capabilities from the larger plan. You can view, switch off and delete them; editing them requires the plan that includes them. New rules can then be created as simple single-path rules again.
Sending email is the point — but never unchecked. “Test rule” evaluates the rule against a real record and shows recipient, subject and the matching path while nothing goes out. Every installed template starts switched off, and any rule can be switched off again in one click.
Yes, through the “email received” trigger on your connected mailbox. Only non-sending actions are allowed there, plus the AI reply draft: Univents writes the draft but never sends by itself — a person reads it and hits send. That is deliberate, otherwise a rule could reply to its own reply.
Yes, by minutes, hours or days. When it resumes, the conditions can be checked again against the current state — so the payment reminder stays put if the invoice has been paid in the meantime.
Every rule keeps a history: when it fired, which path applied and what each action did. For branched rules the path name is right there — which is why it pays to name paths in plain language.
No. You pick a trigger from a list and actions from a list; the finished rule then reads as a sentence you could say out loud. From Growth you can describe it in one sentence instead and let the AI build it.
Those AI actions are skipped — classifying an incoming email and drafting a reply — and the rest of the rule still runs. No other action consumes AI credit.
Try Univents for free and see how simple event management can be.
Product news and practical tips for event and catering businesses. Roughly once a month, no more.
We use cookies for statistics and — with your consent — for marketing (Google, Meta, LinkedIn) to improve our advertising. Details: Cookie Policy