Partner uses a third-party survey system that receives data via URL parameters. When tickets originate from email, the PSA supplies variables like member/contact name through the link automatically. However, for live chats, the survey is triggered via a Flow, and the only currently supported variables are limited (e.g., {ticketemail}, {board}, {type}, {priority}). Variables like {Member First Name} are not supported in Flows, causing them to send as literal text and breaking the survey link. As a result, their team must manually review each survey rating to tag it to the correct team member. Expanding Flow variable support to include member and contact name fields would allow the survey link to be fully populated automatically, eliminating manual review overhead.