Routing and scheduling assume a connected Salesforce or HubSpot instance as the source of record data and rep ownership. Teams that run their pipeline somewhere else, in Notion, in a spreadsheet, or in a system with no Chili Piper integration, can't use the routing logic at all, even when the logic itself is what they want. The blocker isn't a missing feature inside routing, it's the CRM prerequisite in front of it.

Requested behavior: let routing and scheduling run against a non-CRM source of record data. Two shapes came up as acceptable, a connected spreadsheet that supplies rep, territory, and ownership data, or manual entry of that data directly in Chili Piper. Either way, routing rules, distributions, and booking would work off that source instead of requiring a supported CRM connection.