Problem:

Magic Agent listening mode is currently tied to matching a specific status on each board (set via the status mapping page). When a Flow moves a ticket from one board to another — e.g., from a dispatch/triage board to a destination board like MIT-Remote — the flow sets the ticket to that destination board's default status, not necessarily its listening-mode status. If the two don't match, the agent disengages immediately, even though the ticket hasn't actually been picked up or worked by a tech yet.

Today the only workaround is to manually configure every board a ticket could traverse to share the identical listening-mode status — which is fragile, requires ongoing manual upkeep, and breaks silently whenever a board's default status changes.

Requested behavior:

Give Flows an explicit way to control Magic Agent listening state as part of a board-move action (e.g., "keep listening" / "disengage") rather than relying on incidental status-name matching across boards. This would let the agent correctly stay engaged until a ticket is genuinely assigned to and being worked by a tech, regardless of what default status a destination board applies.

Priority driver: Currently the only reliable path to correct behavior is manually synchronizing listening-mode status across every board in the routing path — not scalable for MSPs with more complex board/flow topologies.