PX Product Ideas
PX Product Ideas
- 656 Posts
- 1,438 Replies
It would be great if, when searching for an engagement by name, you could hit enter and get a list of matches. Currently, you just get the dropdown that truncates the engagement names and hovering doesn’t display the full name. It’s then hit-or-miss by clicking on one to see if it’s what you wanted. THEN, if you search that keyword again, the dropdown results are not shown in the same order! So it’s an even more complex game of hit-and-miss.If the search finds 6 engagements with the keyword I enter, it would be great to see just those 6 appear in the regular engagement list view. Similar to how the engagement list changes if you click on a filter or a label.Also, I don’t know if this needs to be a separate idea, but it would be great to be able to export a list of engagements: full list, filtered list, labeled list, search results list, etc.
Screen readers use HTML Section Heading elements (e.g. h1, h3, etc.) to specifically announce content as headings. PX is using div elements (e.g. .px-tooltip-title-wrapper) as containers for titles, so the screen reader does not read them as headings. This reduces accessibility. Consider the Guide tool tip, for example. The distinction between the title and the body text is pretty critical. The workaround is to disable the title and manually code a heading element into the body of the engagement. This works in theory, but in practice this would need to be done for every localization version of every engagement, making it relatively impractical.
Have option for "Completed" Engagement StatusAcknowledged
I recently had a scheduled engagement so users could register for a live webinar. I only wanted the engagement to appear for a couple weeks, then stop. I’ve noticed with other scheduled engagements the Status will change to “Completed” after the date range used. With this recent engagement, I also had it displayed in the bot, so users could find it there as well. The scheduled was set to expire at 9:00am today, then I removed it from the bot. The Status is still showing as “Active.” My suggestion is that we have an option to change an engagement status to Completed. That would make it easier for filtering and reporting. I know that I can change the status to “Paused” but that is not an accurate designation. Plus, then in the “Paused” category when filtering, some of them are paused (for editing, etc.) and some of them are Completed.
In an organization in which not every user has access to PX or to share with a customer who may not have a PX license, it would be helpful to enable PX users/admins to seamlessly export Dashboards and their associated report/widget data externally (PDF, PPT, excel, etc.). Currently, this requires the PX user to manually capture images of the dashboard/widgets and export the csv data, then merge this in a single sheet/presentation. As these are images, it is not possible to drill into the data. Use Case: PX usage data is needed by a member of the organization who does not have PX access or this information needs to be shared with a customer. The dashboard and associated reporting is created in PX then shared externally for data transparency.
Find and replace CSS selectorsNo Status
Scenario: A PX admin builds a full Product Map and Engagements based on v1 of their application. V2 comes out, and the engineering team informs the PX admin that they updated several HTML elements. Now, the PX admin needs to manually comb through the Product Map and Engagements in order to find and update the CSS selectors that have were affected by the UI change. Problem: Locating all instances of a specific CSS selector can be tedious and challenging, especially if the PX subscription has a large Product Map, multiple products, or many Engagements). Proposed solution: Allow PX admins to bulk edit CSS selectors across both the Product Map and Engagements. Perhaps we could expand on the feature cloning functionality to work for existing features as well? Value proposition: Save time otherwise spent manually updating CSS selectors; reduce user error by ensuring that the PX admin does not accidentally miss a feature or Engagement that contains an outdated selector.
I am trying to integrate our Salesforce data to PX, but am unable to because there is a case mismatch. There should be a step where I can transform the data to get it to lookup properly. Getting the information to be the same between our CRM and products is operationally expensive, and is not guaranteed to last.
Ability to undelete an engagementNo Status
When you delete an engagement, it would be helpful if the engagement went to a “trash” or “archive” area instead of being completely deleted. Administrators could then go to that area and undelete engagements.Accidents can happen where someone accidentally deletes the wrong engagement. This feature would make it easy to reverse deletion.
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
Our cloud-hosted software makes use of modules hosted in a separate domain. These modules are written as plug-n-play so can be used over our suite of products. Each product makes the module available through an object tag in its HTML code.We are unable to get the PX Product Mapper to recognise any module-UI elements embedded in the object tag. We added our product PX tag to the module code as advised by support (with Srinivas Myakala) to no avail. Further testing with support have concluded that the object tag is not being treated the same as iframe tags by the Product Mapper.This is an important issue to our company as we would like user analysis to continue inside the new modules.
Posting on behalf of customer:Hi Team,Currently, we can get the webhook events generated for the events that are initiated from the application like new user signup/custom events/engagement.But for events that we can be generated via API like custom event/new user creation cannot trigger corresponding webhook events. It would be great if we can extend this feature to the events from API as well.Thanks,Srinivas.
Saved color palette in engagement editorAcknowledged
Currently the engagement editor has a palette of about 30 default colors that can be easily applied. It would be nice to enter hex codes that match the theme of our product and save these into this color palette to allow easily applying colors for text, headers, buttons, etc.
The “Title and Body” section of the article editor cannot be resized which makes it difficult to edit articles with a rich content like images. It would be nice to be able to resize this, or just have the content section a lot taller by default.
Hey Folks,Have you ever needed to make a minor update to an engagement but were locked out because it was active? And then you go to pause the engagement to make the quick edit, but again, blocked because the engagement is also housed in a K-Bot library. It would be really great if we could make an update on the fly without having to:Start on the engagement you notice has a spelling error Find the Right K-Bot where the engagement might be housed (there is no way to know without looking through each K-Bot) Find and remove the engagement Go back to the engagement launcher and pause it Go to the engagement editor and make the update to word or phrase Go back to the engagement launcher and launch it Go back to the K-Bot and find the engagement again (BTW it is no longer in the same order as it was when you removed it, so you will need to search through every engagement available to every K-Bot.) Add it back to the Bot. Re-order it in your K-Bot Menu and/or assign it to a Category. Save th
It would be very helpful to allow higher level of “view” access to user engagements and Knowledge Bots. View currently only allows system users to see the list of engagments, it would be nice to allow the user to “view” the editor page without ability to edit. This way, they can see what currently exists without permissions to edit. We have a lot of Marketing team members that would like to see what is available and determine if we need yet another message or if we can simply relaunch an older message.
Typically PX Engagements retain their original size as shown in the editor, which is then shown to end users.At times if a tooltip is left or right position biased , and being close to the viewport edge of an engagement creator’s screen, if an end user viewing it has a smaller screen in the end, things can go off the viewport like below. It is desired to have some configuration to control over the responsiveness aspect of engagements. Maybe if the screen is two small, go ahead and do word wrap to fit or remove an image within the engagement or remove certain text as things get smaller. etc.
Keep connection between template and engagementAcknowledged
Currently engagements seem to be copies of a specific template. Templates should however stay connected to the engagements.→ Engagements should stay connected to ‘their’ template.→ Templates should be editable.→ Modifications to a template should affect all engagements which are based on that template.→ It should be possible to apply a different template to an engagement.→ When creating and editing a template, users should be able to set single settings to ‘Don’t inherit’, so that these settings can still be defined for every single engagement.→ It should be possible to define template variants for languages, for example using a different font-family.→ The template of an engagement should also be listed in the overview in the engagement editor.→ It should be possible to apply a different template either in the overview or when an engagement has been opened for editing.
Trying to do iterative development on engagements is very painful and time consuming, especially when you enable triggering them from the KC Bot. Anyone with a rudimentary exposure to software development lifecycles knows that you should never work directly on what’s in production. Since there’s no real versioning or branching support, you end up cloning active engagements and the active KC Bot, changing the audience criteria and working on the new version.Working on the clones is also painful, as you need to constantly pause the Dev Bot or remove the engagement from it, then pause the engagement and then work on it. Actually, if you have the engagement open before you pause the bot, it will keep complaining it’s being used in an active bot, even if you have since paused it. The engagement doesn’t refresh the bot’s state after every attempt to pause the engagement. The opposite happens when you work on a bot, to add an engagement. It doesn’t refresh the engagement state, when you try t
Text badge supportAcknowledged
In addition to icon badge we have many use cases where a guide is launched from a text badge. Since text badge is not supported we tried to work around this limitation by creating a tooltip guide which hide all navigations and use a custom button to overlay on top of Next button in order to mimic text badge behavior. But we still can’t hide the triangle/caret from the tooltip step/engagement guide to match our design. Please consider to add text badge support.
[KC Bot] Allow KC Bot Added Engagements to Be Modified of their Engagement Level Configuration, Without Having to remove it from KC Bot.Acknowledged
Posting on Behalf of a Customer, but would say its a good idea also. Today when trying to edit the Engagement used in KC Bot you get below. Its a pretty bad experience where someone has to go back and forth to remove the Engagement from KC Bot, Pause the Engagement, Make Changes, Launch, then readd into KC Bot. Especially, If a simple change needs to be done, such as fixing a spelling error, or changing the title of a step. Somewhat related to this community thread:
I have a customer using Google Search knowledge base integration but they would like to be able to assign a specific URL to each bot, based on language. The use case here is that there are separate documentation sites for each language of documentation, which have unique URLs: https://help.company.com/espanol/vshttps://help.company.com/support.html
Ability to link a URL from a badgeNo Status
We would like to be able to add a badge to our cloud based app that launches context-sensitive help topics in our help centre. Whilst I appreciate that Developers can code this, we’d like to be able to make changes on the fly and react to any support tickets or issues that may arise. We don’t just want to launch engagements, we want to be able to call URLs.Is this something that others would find valuable?ThanksTracy
Gainsight supports css on guide and template levels. However there are multiple css selectors that are not accessible or can’t be customized, for example, 1) triangle (which points to the aligned element) from the engagement guide takes the background color and can’t be hidden using css (No. it doesn’t take transparent color as background); 2) a drop shadow on .apt-guide-popup level remains visible and can’t be customized even after turning off shadow in Settings. There are also css attributes that are cross templates (e.g., font-family, default text/link color) which need to be set/repeated in every template. Having capability to access/customize global css would help solving these limitations.
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.