What is Stage Follow-up Automation in Mr. AI?
This feature watches the customer's published Conversation Builder stage. If the customer stays in the selected stage without replying for the configured time, the system runs a defined outcome: create a team task, schedule an AI follow-up, or try an AI follow-up and then create a human task when needed. The current release is specifically based on customer inactivity inside a stage; it is not a general-purpose rules engine for arbitrary conditions.
- The current trigger is customer inactivity inside a published stage.
- New rules never create work from historical stage events that happened before the rule was published.
- Opening the page does not invoke AI or create work; execution reacts to persisted server-side stage events in the background.
How to use it
- 1
Open Customer Operations, then Stage Follow-up Automation.
- 2
Choose an active stage from the published Conversation Builder and set the customer inactivity duration.
- 3
Choose the outcome: team task, AI follow-up, or AI follow-up followed by a human task.
- 4
For a team task, configure work type, priority, assignment, due time, escalation, or expiry as needed.
- 5
Save a draft, then publish the rule. Monitor generated work in Operations Inbox.
Frequently asked questions
How is this different from normal Follow-up Automation?
Normal Follow-up Automation configures general conversation follow-up messages. Stage Follow-up Automation ties execution to a specific published Conversation Builder stage and can create human work or use AI follow-up.
What happens if Conversation Builder changes?
The rule is tied to the published Builder version. After the Builder changes, the rule may become stale and should be reviewed and republished before relying on it.
Can Testing Chat create real tasks?
No. Testing Chat stage events are excluded from live rule execution.