For the complete documentation index, see llms.txt. This page is also available as Markdown.

Routing Logs

Use Routing Logs to understand what happened to a particular prospect. They bring together the recorded routing decision, assignment, booking, and related activity. Workspace admins can inspect logs for their workspace.

Find an attempt

Open Form routing → Routing Logs, Click routing → Routing Logs, or Outbound routing → Routing Logs. Search for the prospect and narrow the results with the filters available on that page.

You can also follow a routing-log link from a router, booking, or insight report. Open the row to review its details.

Routing type
One row represents

Form routing

A recorded form submission and its routing context.

Click routing

A recorded routed visit and its result.

Outbound routing

A sales handoff, which can contain several routing or booking attempts.

Follow the recorded result

For Form and Click Routers, review the submitted values, rule evaluation, assignment, and meeting details. CRM activity and workflow results appear separately. A successful routing decision can still be followed by a failed CRM update or workflow action.

Routing timeline with an expanded rule match, assigned owner, and completed meeting outcome
Expand a routing decision to see the rule and recorded values behind the match.

A Booked result means a booking exists. Open the meeting details to check whether it was later cancelled or marked as a no-show. The current booking owner can differ from the original assignment; use the recorded history to understand the change.

A recorded redirect destination does not prove that the visitor opened it. Missing details or timestamps mean that evidence was not recorded.

For an outbound handoff, review the ordered trace of answer changes, routing, availability, link sharing, booking attempts, and delivery. A handoff may have several attempts. A link being created or opened is not a confirmed booking, and a confirmed booking can still have a delivery problem.

Decide what to change

Use Explain where available to ask Copilot about the recorded context. An explanation does not change the router.

Correct configuration in the relevant router, rule, form, or integration, then test and publish the intended version. The log itself does not rerun the prospect's journey. Historical attempts can retain earlier configuration even after the current router changes.

Use Reporting to compare trends across prospects, Availability preview to investigate missing times, and CRM activity for personal or group booking-link delivery.