PX Product Ideas
PX Product Ideas
- 38 Posts
- 1,452 Replies
It would be nice to have a back button on a multi-question survey, along with a submit button. For example, I am creating the following question in a multi-question survey: [img]https://d1qy7qyune0vt1.cloudfront.net/gainsight-en/attachment/backbutton-1c4ae324-7470-497c-ad74-f99864a361c2-556018068.png[/img] And it would be nice if a customer could go back to confirm what the previous question was, or it would be nice to just go back in general to review answers earlier in the survey.
We export the texts of our engagements to be localized via API, based on the translation state ‘Ready for translation’. For Knowledge Center Bots it is not possible to set a translation state, this option is missing. Please add the possibility to set translation states also for KC Bots.
Hi, we would like to create Knowledge Center Bot in Finnish in PX (we don’t want to use xliff translation files, because we have all content ready in Finnish). Otherwise creating bot in Finnish is done well, but we can't edit two sections in the Feedback section without a xliff file: 1. Guiding texts in the text area 2. CTA-button (Submit).Could these be customizable?
Hi Everyone, Currently the "magnifying glass" icon on the search bar of KC Bot is by default set to green colour, it would be helpful to customers if it was possible to change colour to that of their product brand colours. Thanks, Srinivas
I'm running an engagement to draw attention to a new menu item in our product.I want to show a hotspot (linked to a tooltip) each time the user sees the new menu item, and only stop when they complete the engagement.This would seem a common use case - but PX doesn’t support it.
Hi, Can PX filter the audience or account [i]relative[/i] to a certain date? For example, can I filter "where trialEndDate less than $TODAY"? (unexpired trials) or "where trialEndDate equals $TODAY+5" (i.e. trial expires in the next 5 days)? -Matt
Folders for uploaded imagesPlanned
Hi All,We upload so many different images to our Engagements on PX, it can be quite overwhelming to find the right image if we wanted to reuse something (and uploading it again just shows us duplicates which again adds to the scrolling torture!). Would it be possible to bring in folders which we can add images to? that way we can categorise our images into things such as ‘Email Hero Images’ , ‘Product A GIFs’ or ‘Company Logos’ It would be a massive time saver for us!
Hey Folks, We have implemented the creation of Zendesk tickets via PX via: Admin > Engagement > Feedback > Created Category with Zendesk Request enabled. This successfully allows end users to create tickets to the Support team; however, I feel that this could be greatly improved with literally the changing of words. When a ticket is submitted, the wording ‘Thank you for your feedback’ is shown to the end user; I get that the feature was initially introduced to provide feedback, however it is now also an integrated route for creating Zendesk tickets, and in this scenario it’s not a great UX to see ‘feedback’ when actually you’re wanting help. An improvement would be to allow for the wording to be changeable by the PX admin, or changed to something generic that would make sense for scenarios of both providing feedback or a support ticket. If there’s a known solution either to change this wording, or another solution available to allow ZD tickets to be created using KC bot/engage
It would be ideal to have the option to customize the question we send to our customers at the end of a survey depending on the score they provide us. For example, if it is a Promoter the question could be different from the one we ask to a Passive or Detractor. So far this option is not available in PX and could be quite useful in order to have more insights from our customers and users.
Search by engagement IDPlanned
Hi, We would really appreciate if we could search by engagement ID. The files we export via the localization export/import API contain the engagement ID in their file name.But there is no way to find these IDs in PX. Use case: After importing the translated texts via API, we always check whether everything is fine. If, for instance, we find an error in a translated file and want to correct it in PX, we cannot see which engagement the localized file corresponds to. Clicking through all the engagements with all their localizations is not an option.Thank you very much.Best regards,Katharina
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.