← All issues

Allow conditional chat routing based on page-specific visitor intent

Submitted
Posted by Ethan Hales1 voteFeature

Hello tawk.to team,

I'm currently using tawk.to on websites where visitors arrive for very different reasons, and I've noticed a limitation when trying to route conversations based on the context of the page being viewed.

For example, some pages focus on informational content, while others provide interactive tools and calculators. In these cases, visitor intent can be very different even though they are using the same chat widget.

A practical example is https://calcolaascendente.it/, where users enter personal birth information and receive dynamically generated results. Visitors often have questions specifically about how the calculation works, which creates a different type of conversation compared to general support requests. Ideally, those chats could be routed to a dedicated queue or agent group.

At the moment, routing options seem more focused on general chat assignment rules, but it would be extremely useful to have conditional routing based on:

Current page URL
Page category
Custom page tags
JavaScript variables
Visitor interaction type

Example workflow:

Visitor lands on a support page → route to support team
Visitor lands on a billing page → route to billing team
Visitor lands on https://calcolaascendente.it/ or another specialized tool page → route to a subject-specific team

Benefits:

Faster response times
Better visitor experience
Improved agent specialization
More accurate reporting and analytics
Reduced manual chat transfers

I reviewed the available routing and automation options, but I haven't found a way to dynamically assign conversations based on page-level context alone.

Would other users find value in more advanced page-aware routing rules?

I'd be interested in hearing how others currently handle visitor segmentation when a single website contains multiple content types and user journeys.

Thank you.

Comments (0)

Sign in to post a comment.

No comments yet.