Start with the account relationship
Match the customer using CRM and domain information before offering an appointment.
Use cases / Customer routing
Help customersreach their owner.
A customer wants a renewal discussion or an account check-in. Help them reach their account owner without asking around or entering the new-business queue.
The relationship exists.
Use it.
Customer-facing teams shouldn’t have to look up the right contact for every booking request. Use CRM ownership to connect a customer with the person responsible for their account.
Keep the conversation familiar
Route to the owner who handles the account, instead of distributing every request as a new lead.
One place to book.
Different account owners.
Give customer communications a consistent booking destination. A click-router link can use ownership rules to send different customers to their respective account owners.
Use the link in customer communications
Include it in account emails or a customer-facing website CTA.
Plan for requests without a match
Configure the distribution team that should handle customers who do not match an owner.
FAQ
Frequently asked
questions
Do we need a separate public link for each account owner?
A click router provides a shared entry point and evaluates ownership rules to choose the relevant rep. Individual booking links are another option when the owner is already known.
What if the customer does not match an owner?
Configure distribution rules for the team that should handle unmatched requests.
Does the owner need to be a Distro user?
The matched owner must be an eligible user in your Distro routing setup. Make sure CRM ownership and team configuration are aligned.
Make it easier
to reach the familiar face.
Show us how your customer team handles account meetings. We’ll help map the booking path to your ownership rules.