Current limitation
- There is no trigger for conversation lifecycle events such as conversation assigned to a team or a Fin/conversation attribute changed to a specific value.
- The only near-fit trigger, "customer sends any message," misses these cases, because the state change (attribute set + handoff) happens within the same step and no further customer message follows.
What we'd like (general, not one narrow trigger)
- Event-based triggers for conversation outcomes: assignment to a team/teammate, state changes, and attribute changes.
- Clean composability: an action defined once should run whenever a conversation reaches a given outcome — regardless of whether a Procedure, a Workflow, an escalation rule, or a manual action produced it.