Skip to main content

Signature Survey - Option to use "custom CSAT/main CSAT" configurations

It is common to have custom CSAT for signature surveys, but the process of changing the HTML code to be able to use the custom csat is not user friendly, not intuitive and a lot of things can go wrong. It would be great to have a button to chose to use the custom CSAT on your signature survey, since it’s just the custom csat code that is added to 3 links within the html code.

2 comments

This request was merged into another request

Comments2

  • Red Turtle

    •

    May 5, 2025

    Current Process:

    1. Employees must extract their own HTML code from their profile page.

    2. Admins cannot centralize this because the code is individualized.

    3. The HTML then needs to be manually edited in three specific places to add “custom code” from the Custom CSAT.

    4. This process is time-consuming, error-prone, and requires technical know-how.


    Suggestions to Improve the Process

    Here are a few options you might explore to streamline or eliminate these manual steps:

    1. Automated Template Generator

    Develop a small internal tool or script that:

    • Accepts an employee ID or email.

    • Retrieves or reconstructs their profile HTML.

    • Injects the necessary Custom CSAT code in the correct three places automatically.

    • Outputs the final HTML for copy/paste or direct deployment.

    This would remove the need for each employee to manually get the code and reduce human error.

    2. Centralize via Admin Permissions

    If feasible within your system architecture:

    • Allow admins to impersonate or access all user profile HTMLs.

    • Provide an "Insert Custom CSAT" button that automates the injection of the code.

    @Kadu Azevedo

  • Tan Flashlight

    •

    May 5, 2025

    @User Hi Thais! 👋

    Thanks a lot for your feedback, that’s super valuable to us.

    To help us better understand your suggestion and evaluate how we could simplify this process, would you mind sharing a bit more detail about how you're currently solving this issue?

    If you have any examples on how you’re using or can point out exactly where things tend to go wrong, that would help us a lot.

    Looking forward to hearing more from you! 😊