Business workflows
Make the next step a rule you can inspect.
Repeated work needs a clear trigger, a defined action and a way to stop. POST’s workflow builder lets you configure supported business automations, inspect their steps and review execution history.
A reminder without conditions becomes another interruption.
“Follow up with every lead” is incomplete. A customer may already have replied, a teammate may have taken over, or an order may be complete. A useful rule starts with an observable event or absence and accounts for what changed afterward.
POST supports event triggers such as lead-stage changes, order placement and payment events, plus scanning triggers for unanswered or inactive records. Message-based reply rules run on the incoming conversation. Choose the trigger and action the interface supports for your case.
- Readable trigger and condition
- Review the trigger, conditions and action before saving. New rules are active when saved; inspect the resulting canvas and pause the rule if needed.
- Supported actions
- The current builder offers a queued WhatsApp message or an owner flag. Inspect the actions and any stored branches on the canvas to understand what an existing rule does.
- States and execution history
- Review whether a workflow is active or paused, inspect previous runs and investigate failures. Pause a rule when its assumptions or business policy change.
- Outbound controls
- Workflow outbound actions enter the sending process with the applicable mode, rate limits, cooldown and business-hour checks. Approval requirements depend on the action and workspace configuration.
Inside the product
Workflows & automation
Open a step in a sample bulk-enquiry workflow with two branches.
An existing sample rule. No workflow is created or triggered in this recording.
A practical workflow
A service team notices an unanswered enquiry.
Demonstration example: a team wants the owner to review a conversation that has had no reply for 24 hours. The example starts with an internal notification.
- Choose the supported no-reply scanning trigger and review what records it matches. A periodic scan is not an exact appointment timer.
- Add the available conditions for the intended audience, then choose the owner-notification action.
- Start with synthetic records and inspect the run result. Check an answered conversation as well as an unanswered one.
- If adding outbound messaging later, review consent, current conversation state, sending mode and the channel’s requirements before activation.
Set the controls first.
Start with one narrow rule and an internal action. Review its first runs before expanding who it can reach or what it can send.
Test when a customer replies, a teammate takes over or the record changes stage. Check that available conditions and sending controls support your stop rules; do not assume that every desired exclusion is automatic.
Check the fit.
- Saving a new rule activates it. Start with a bounded internal action and review the configuration before saving; the current builder does not have a separate draft state.
- The builder supports a defined trigger and action vocabulary. Saved rules can be paused or deleted; changing their steps currently requires rebuilding the rule.
- Scanning and event processing depend on worker execution and integration events. An active rule is not proof of successful provider delivery.
- A Business Brain procedure is conversational guidance, separate from an executable workflow. Learning a procedure does not activate an automation.
Follow the work.
Design follow-ups with stop rules and human review →Start with a 14-day free trial. Review the plans, watch the product and tell us what your business needs during onboarding.