Messaging routes on what Zendesk itself knows: the channel, the group, the conversation's fields, a skill, the customer's tags. What it can't see is what your other systems know. A customer on a large contract, one with an order stuck in the warehouse, or one halfway through a renewal looks exactly like a first-time visitor unless that fact reaches Zendesk before the chat starts.
Two pieces fix that. First, sign logged-in visitors in to the widget with a JWT from your own server, so the conversation belongs to a known user and their history follows them. Second, keep the facts that matter, such as tier and account owner, current on the Zendesk user or organization, or pass them in as conversation fields as the widget opens. Then a plain messaging trigger or omnichannel routing rule can send that customer to a senior agent.
n-frames has built both halves for support teams: a lookup that runs when a logged-in customer opens the widget so top accounts skip the general queue with their order history attached, and a step that tags and prioritizes the ticket from the chat's keywords and that account data, so agents stop sorting chats by hand. The fuller list of what Zendesk connects to sits on our Zendesk integrations page, and the developer side is on the Zendesk API reference.