The onRouted event fires when Concierge routes a submission (before booking), but its payload doesn't describe how the visitor was routed. Clients can't tell a calendar-assigned outcome from a catch-all one, so they can't branch behavior. Today only a routingId is available (via onEnrichData); there's no rule, queue, or outcome type.

Requested behavior — include routing-outcome metadata in the onRouted payload:

Why it matters: teams building custom post-routing behavior (redirects, messaging, analytics) need to react to the outcome, which today they can only infer.