When a lead books a meeting and is initially round-robined to an SDR, there is no way to automatically reassign that meeting if a CRM field is updated after booking. For teams that run AI scoring or enrichment processes asynchronously, the score isn't available at routing time, so initial assignment happens without it. If the score later indicates the lead should go to an AE instead, the meeting remains on the SDR's calendar with no automated path to reassign it.

Admins should be able to configure a rule that monitors a specified CRM field after booking, and automatically reassigns the meeting to a different rep or queue if that field meets a defined condition.

This decouples routing quality from data availability at form submission time, and removes the need for manual intervention or Slack-based workarounds when high-priority leads are initially misassigned.