Skip to content
BTS 2026Met us at the summit?Claim your summit offer
Rules written in plain English

Write the Rule as a Sentence. Read Back the Steps.

Say what should happen when an agreement is sent, signed or coming up for renewal. FlowVerify turns the sentence into a trigger, conditions and up to 8 actions, and reads the rule back to you before anything is saved. Each rule runs as its owner, with that person’s permissions.

  • Nothing is saved until you save it
  • Try it on a real document first
  • Every run is logged, step by step

From sentence to rule

Four Steps, and You Read Every One

A model drafts the rule. FlowVerify checks the draft against your workspace, asks about anything it could not resolve, and writes the readback itself.

  1. When a vendor agreement is signed, post it in the procurement channel.

    Or start from a recipe

    • Declined → tell Slack
    • Completed → move the CRM deal
    • Ending soon → notify

    Write What Should Happen

    One sentence in the composer, or a recipe to start from, such as telling Slack when a document is declined.

  2. Which channel is “procurement”?

    Two channels in your Slack match.

    • #procurement
    • #procurement-vendors

    Answer What Is Unclear

    If a channel, a folder or a template could mean two things, it asks, and offers the choices from your own workspace.

  3. When
    A document is completed
    Only if
    The document is a vendor agreement
    Then
    Post to Slack #procurement

    Not saved yet. You choose: save and turn on, save turned off, or edit the steps.

    Read the Rule Back

    When, only if, then. The readback is written from the rule FlowVerify validated, never from the model’s wording.

  4. Vendor NDA — Nandi Freight · FV-2611-102

    This rule would run

    1. 1Would post “Vendor NDA — Nandi Freight was signed” to #procurement

    A dry run. Nothing was posted.

    Test It on a Document

    Pick a recent document and see whether the rule would run and what each step would do, without anything happening.

What a rule can use

What Starts a Rule, and What It Can Do

A rule has one trigger, up to 10 conditions that must all hold, and up to 8 actions. Every run is recorded with the outcome of each step.

It Starts When

  • A document movesSent, viewed, completed, declined, voided or expired
  • A recipient actsSigns, declines, views, or their email bounces
  • An approver decidesApproves, rejects or asks for changes
  • A sign form is submittedFrom its public link or QR code
  • A key date is coming upThe end, renewal or notice date of a signed agreement

Then It Can

  • Post to Slack
  • Call a webhook
  • Update Zoho CRM
  • Update HubSpot
  • Send an email
  • Notify a person
  • Add a tag
  • Move to a folder
  • Remind signers
  • Send from a template
  • Up to 8 actions in a rule, run in order
  • A rule runs as its owner, with that person’s permissions
  • A retry skips the steps that already finished
  • An hourly cap limits how often rules can run
  • A rule that keeps failing is switched off, and its owner is told
  • Test-mode documents never start a rule

Follow-up agent

A Follow-Up Agent That Chases for You

Switch it on for one document or for the whole workspace. It plans the reminders for each signer and stops when they sign, when they decline or when the deadline passes.

WhatsApp follows SMS for signers who opted in.

A Plan for Each Signer

Reminders go at the hour that signer usually opens, or at 10 am when there is no history yet. Email comes first. SMS and WhatsApp follow for signers who can be reached there.

Limits It Keeps

Never more than the cap you set, never in quiet hours, never after the deadline, and never to someone who has signed or declined. By default the cap is 5 reminders and quiet hours run from 9 pm to 8 am.

The Reason It Stalled

The Today page says why each document is stuck, such as not opened, stuck on the OTP or not delivered, with the next step to take. Each sender gets a digest in the morning.

Agent-to-agent negotiation

Agents Propose. People Decide.

Before a draft goes out, your agent and the counterparty’s agent can exchange wording on the clauses you opened for negotiation. Every agent turn waits for a person on that side to release it.

  • Agents can propose and counter. They cannot approve, release or send
  • The mandate names the clauses that are open and the number of turns
  • Terms are agreed only when a person on each side approves the same wording. They bind once the agreement is signed
  • A counterparty without a workspace answers on a secure page that opens this negotiation and nothing else
  • Agreed wording arrives in the draft as suggested edits, and the transcript goes into the evidence pack

Without the dashboard

Start a Document From Email or Slack

Forward the document to your personal send address, or type /flowverify send in Slack. FlowVerify reads the recipients, their roles, the message and the due date from your own words, places the fields, and sends you a link to review.

  • You confirm on the Review step before anything goes out
  • The usual checks before sending still apply
  • Text below your own message in a forwarded email is ignored
  • Mail from an unknown or unverified sender is dropped

If you link a mandate that allows sending to your address, a forwarded document can go out without the confirmation, inside that mandate’s limits.

FAQ

Questions About Automations

Something else on your mind? Book a demo and ask us.

It starts from an event, such as a document being completed or declined, a recipient signing, or an agreement’s renewal date coming up. It can then post to Slack, call a webhook, update Zoho CRM or HubSpot, send an email, notify a person, add a tag, move the document to a folder, remind signers, or send a new document from a template. A rule holds up to 8 actions and runs them in order.

You confirm a readback that FlowVerify writes from the validated rule, and nothing is saved until you save it. You can test the rule on a real document first, without anything being sent. Once it is on, it runs with its owner’s permissions, an hourly cap limits how often rules run, a retry never repeats a finished step, and a rule that keeps failing is switched off.

No. To draft a rule, the model sees your sentence and a short list of names from your workspace: templates, folders, Slack channels, connected CRMs and tags in use. It does not see documents, recipients or secrets, and like every AI feature it stays off until a workspace admin accepts the AI terms.

Its owner’s. Every action runs as the person who created the rule, with that person’s permissions, and the audit trail records the automation as the source. If the owner leaves or loses the permission, the rule stops running. Each run is logged step by step in the run log.

No. Agents can propose wording and counter it, inside the clauses and the number of turns their mandate allows. A person on that side releases every turn before the other side sees it, and terms are agreed only when a person on each side approves the same wording. They bind once the agreement is signed, and nothing in a negotiation sends or signs the document.

No. It never sends during quiet hours, which by default run from 9 pm to 8 am. It also stops at the cap you set, at the deadline, and as soon as the signer signs or declines. SMS and WhatsApp go only to signers who can be reached on those channels, and opt-outs are respected.

Book a demo

See It on Your
Own Agreements

Bring one thing your team does by hand after every signature. We write it as a rule with you, test it on a document and switch it on.

What you get

  • A live walkthrough on one of your own agreements
  • A workspace set up for your team
  • Answers from the people who build it