Redirect later notifications to the current responsible user after a transfer
Once a conversation has been transferred, every notification that fires afterward — a new message, a due follow-up, a reactivation — goes to the current responsible user, never to whoever held it before.
When this happens: A conversation-scoped notification event fires for a conversation that has been transferred.
How it works
- After Radu transfers Ana Popescu's conversation to Elena, Ana sends a new message.
- Resolves the conversation's current responsible user (Elena) at the moment the
ConversationNewMessageevent fires — not a value cached from before the transfer. - EasyCRM creates and pushes the notification for Elena; Radu receives nothing for this conversation.
Other paths
Follow-up scheduled before the transfer falls due after it
A follow-up Radu scheduled before transferring the conversation falls due after Elena has taken over. FollowUpDue resolves the responsible operator at due time and notifies Elena, not Radu.
Good to know
- Recipient resolution reads the conversation's current responsible user at the moment the event fires.