Skip to content
Nexus

Let rules handle the follow-up

Say when something happens, check the details, then let Nexus do the routine work so nothing waits on someone remembering.

Free trial. No card needed. Cancel any time.

When a quote request arrives

Example rule, draft

  1. When

    A quote request form is submitted

  2. If

    The answer to “What do you need?” includes joinery

  3. Then

    Assign the deal to Sam and alert the team

  4. Wait

    2 days

  5. Then

    Email Jo a follow-up if the estimate is not accepted

Stops when the estimate is accepted

When, if, then

Pick a trigger, add conditions and choose what to do. Triggers cover forms, contacts, deals, estimates, invoices and payments, such as a form being submitted, a deal changing stage, an estimate being accepted or an invoice becoming overdue.

What a rule can do

Assign an owner, either a fixed person or shared out in turn. Alert your team in the app and by email, email the customer, create a task, move a deal to a stage or send an invoice reminder.

Branches and waits

Split a rule into up to five named paths plus an Otherwise path. Wait anywhere from a minute to 365 days before the next step, and choose the hours it may continue in.

Stopping at the right moment

A rule can stop when something happens, such as an invoice being paid, so a reminder chain does not carry on after the work is done. A starter, Invoice reminder chain, shows the idea.

A test run before you turn it on

Test a rule on sample data or a real record. Nexus shows the path it would take and the waiting times, and sends nothing.

Drafts until published

A rule stays a draft until you publish it. Run history lists every run, including those that are waiting, which you can continue now or cancel. A rule never runs twice for the same event.

Start with your next enquiry.

Free trial. No card needed. Cancel any time.