Skip to contentSkip to main content

Automated follow-ups

Follow up every opportunity at the right time

OfferAgent automation sequences react to defined customer or quote events and execute versioned steps such as waiting, checking a condition, sending through CommunicationHub or creating seller work. Stop rules, quiet hours, contact limits, idempotency and execution history keep follow-up controlled, while a published sequence remains unchanged for runs that already started.

Follow-up should not depend on memory

Timing is lost when every seller must remember each sent, viewed or unanswered quote.

How it works

  1. 01

    Choose a trigger

    Start from a canonical event such as quote sent or customer question.

  2. 02

    Build guarded steps

    Combine waits, conditions, messages and seller tasks.

  3. 03

    Preview and publish

    Inspect timing, channels and stop conditions before activation.

  4. 04

    Monitor every run

    See completed, waiting, stopped and failed steps with safe retry controls.

Product proof: versioned sequence execution

The workspace exposes trigger, steps, safeguards, publication and run state.

Prerequisite: Requires Automation access and configured communication channels for customer messages.

Automation sequence workspaceProduct flow
  1. 1Draft previewed
  2. 2Version published
  3. 3Run waiting safely
Open the signed-in product workspace

Sign-in and the correct plan are required. This link is not a public demo.

What this capability supports

Canonical triggers

React to governed events instead of page-specific UI state.

Stop conditions

Stop messages when the customer has replied, accepted or otherwise completed the goal.

Contact safeguards

Apply quiet hours, timezone and contact frequency limits.

Execution history

Trace every step, suppression, failure and guarded replay.

Prerequisites and clear boundaries

OfferAgent states what the capability does and what still requires configuration, permission or a human decision.

  • No sequence sends until it is published and its channel is configured.
  • A reminder can create seller work instead of contacting the customer.
  • Existing runs keep their published version when a new draft is created.

Frequently asked questions

What can start a sequence?

Supported canonical events such as quote delivery, view, reply or another configured business event.

Does it stop after acceptance?

It does when acceptance is included as a stop condition in the published sequence.

Can we test timing?

Yes. Preview exposes the ordered steps, delays and safeguards before publication.

Does AI send messages automatically?

No. AI-assisted copy remains a reviewed input to a separately governed sequence.