Canonical triggers
React to governed events instead of page-specific UI state.
Automated follow-ups
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.
Timing is lost when every seller must remember each sent, viewed or unanswered quote.
Start from a canonical event such as quote sent or customer question.
Combine waits, conditions, messages and seller tasks.
Inspect timing, channels and stop conditions before activation.
See completed, waiting, stopped and failed steps with safe retry controls.
The workspace exposes trigger, steps, safeguards, publication and run state.
Prerequisite: Requires Automation access and configured communication channels for customer messages.
Sign-in and the correct plan are required. This link is not a public demo.
React to governed events instead of page-specific UI state.
Stop messages when the customer has replied, accepted or otherwise completed the goal.
Apply quiet hours, timezone and contact frequency limits.
Trace every step, suppression, failure and guarded replay.
OfferAgent states what the capability does and what still requires configuration, permission or a human decision.
Supported canonical events such as quote delivery, view, reply or another configured business event.
It does when acceptance is included as a stop condition in the published sequence.
Yes. Preview exposes the ordered steps, delays and safeguards before publication.
No. AI-assisted copy remains a reviewed input to a separately governed sequence.