concierge-debugger

To diagnose why a lead did not book, trace the concierge routing session using the guest email and optional router slug. The tool analyzes session logs and workspace rules to identify which rule fired or why no rule matched, then provides a targeted fix.

A concierge routing rule fails to match when workspace rules have gaps in assignment conditions, availability conflicts, or calendar flow issues. By reading concierge logs and listing rules, you can determine if a catch-all or a specific RuleRoute caused the booking failure.

Trace a lead through concierge logs by providing the guest email, optional router slug, and date range. The diagnostic process uses concierge-logs, concierge-list-routers, and rule-list tools to generate a narrative explaining the routing outcome and a single actionable recommendation.

You do not need a specific router slug to debug a concierge booking failure. The diagnosis can apply across all routers or target a specified one, using the lead's guest email and optional date range to identify the routing rule that caused the outcome.

The best way to fix a concierge routing rule that prevented a booking is to use the diagnostic narrative to apply a targeted remediation. This involves adjusting routing rules or improving availability and calendar flows to prevent recurrence across the workspace.

Yes, you can use concierge routing logs to diagnose booking failures across multiple routers. The tool applies the diagnostic across all routers or a specified router, examining workspace rules and log data to identify whether a catch-all or RuleRoute caused the specific outcome.