PX Product Ideas
PX Product Ideas
- 663 Posts
- 1,452 Replies
Hi ALL, If we export an Xliff file from Engagement translations, then the <target> tag also need to be included which will help for the user that to know where the target text need to be added or changed. Regards, R Satheesh
In PX Engagements, In the "Audience" screen of an engagement - sometimes we define rules and we want to be able to turn them on / off for testing purposes. It would be nice to have an "enable/disable" button for each rule. Adding the rules and deleting them again would be more time taking. Instead we can simply have Enable/disable button for each rule. Thanks, Shireesha.
It would be really great, if there was a way to add the User ID in product mapper section and display the activity report in the same tab somewhere to view the results rather than creating and event and in product mapper section and navigate to the audience explorer tab to look for the user ID by accessing full profile to view the results of the event in the recent activity.
Allow Metropolis or Helvetica Font in PXWorkaround Available
posting on behalf of customer, In PX, We knew there are different font families and styles we can use in customisation. Can we add Metropolis or Helvetica as an additional fonts in PX. These will be helpful for customer to customise their Engagements more effectively. Thanks, Shireesha
Can we have consistent selection criteria across filters and engagement audiences? An example is on Accounts Explorer, the “Create Date” field is populated by PX. When you go into the engagement audience, the “Create Field” is not available for selection. It’s cumbersome to have to tell developers to pass in a custom attribute on the identify call when it’s already available. Thank you!
Provide the ability to filter the default full Adoption Report emails so they can be more usefulNo Status
Posting on behalf of a customer… The default full Adoption report delivered via email includes nice statistics and breakout categories for ALL users. However, since it include ALL users/accounts and cannot be filtered to exclude/include only certain users/accounts, and it is not very useful. Also, this multi report email format cannot be recreated as a custom Adoption Report or User/Audience Report, so it is not currently possible to get the same summarized insights for a particular set of users/accounts. Requests: Add the ability to filter the default Adoption report to exclude users/accounts (e.g. internal users) so this default report is more useful Provide the ability to recreate the Adoption report email contents through custom Adoption Report or User/Audience Report.
Additional Throttling OptionsAcknowledged
Hi folks, The throttling concept is great in the Settings → Engagments part of PX, but it could be a lot more functional. What I would *like* to do is set up the following rules for the 3 types of engagements we currently have: Welcome Guides - no restrictions, fire when applicable Notifications - no restrictions, fire when applicable. Surveys - Restrict to 120 days between surveys. Restrict to 3 days between other engagements. We will have 10+ surveys constantly trickling data in. This gives me the ability to limit surveys once a quarter per user and never more than 4 in a year, to give them a little breathing room (but not too much) between surveys and other engagements, and not restrict anything mission critical. We can’t do that today, so I’m stuck with: Welcome Guides - no restrictions, fire when applicable. Notifications - no restrictions, fire when applicable. Surveys - Restrict to 14 days between any engagement so we don’t overwhelm a user with surveys. Whenever a global
Use case: When we have multiple engagements added in KC bot, I would like to target few engagements visible to particular accounts or users. With the current design, we don't have this ability, all the engagements added to KC bot will be visible to all the users. This feature can be handy. Thanks
Rules for Knowledge Center BotImplemented
Use case: We have several different roles that have different permissions in our systems and our clients are requesting that content displayed in the knowledge center bot be filtered out based on the role a user has so a lower level admin who doesn't have reporting permissions doesn't see any of our guides about making reports. I realize that you can put rules about role permissions in the individual guides themselves but that doesn't stop every admin on our system from seeing the guides listed in the knowledge bot. It merely prevents them from actually making use of the guides. Being able to apply rules to the knowledge bot is something that would be very useful to us and in truth we really need it if we're going to make use of other features like the feedback tab.
There seem to be a lot of functionality issues with the Feature Guide (Knowledge Bot)Partially Fixed
Hi everyone, Wondering if anyone has tried to use the feature guide (knowledge bot) yet? I've run into some pretty major issues, as well as just some inefficient and confusing pain points. Hoping that someone has some insights, as these are really show stoppers for us being able to use this feature. This is for the product formerly known as Aptrinsic. Major issues: [list=1] [*]Setting the engagement visibility for the items in a feature guide doesn't impact the visibility of the feature guide. I found that out when I launched the feature guide, ostensibly for testing, to myself, and everyone saw it :(. [*]There's no way to set feature guide visibility. Would have expected underlying engagement visibility to dictate the feature guide visibility, but that is not the case. Therefore, there is no way to test the feature guide. [*]There are some pages on our platform such as code editor tools where the feature guide button displays over the top of the primary action b
Ability to Enable/Disable or modify KC BOT functions.Partially Fixed
Use Cases: Ability to Enable/Disable the Tabs (On boarding, Feedback) of the Knowledge centre bot. If the user don’t need to go through the on- boarding articles, then it would be better if we have the leverage to turn off the tab. Ability to display the KC Bot to only specific customers cohorts, For whom it is needed. With the current design, if we launch the KC Bot it will pop-up for every customer. So we don’t have the ability to customise the knowledge centre Bot. Ability to change the style/location of the bot with custom CSS/Code. Now, with the current design there is no option to update or edit the CSS code. We can just change the shape of the Bot. Unlike it can we make it possible to change the location of the BOT.
Hello team and @harshibanka , It would be better to track the stats of the articles that which are being viewed. It would be nice if we can also track which article is being opened quite often and maximum times and which article is being opened minimum. Presently we only track the stats of the engagements in the KC bot but not the articles in the KC bot. thanks, Avinash.
In PX, Currently We have a option to submit the feedback from Knowledge centre Bot. We can submit different feedbacks like, Issue, Feature request, General Feedback, Other. When we submit the feedback the admin will receive the feedback with the Subject line of Product Feedback. If the user links the KC bot with Zendesk, It will also create a ticket with the subject as Product feedback. And in the description field issue type will be displayed. So If we can link this Type of Issue to Subject line, And instead of Product feedback, If we can display the type of the issue directly, It will be really helpful to understand Feedbacks Easily. And this will also help to sort Feedbacks Effectively. Example Subject line would be like this, “General_Feedback: Test” Thanks, Shireesha.
As we all know that, with one of our latest releases, We now have the option for KC bot analytics. We can see how many users/accounts viewed the particular Article or Engagement of the KC bot. But the only thing we don’t have is the option to drill down to Account or User level, to see who are all viewed the particular Article/Engagement. It would be really awesome if we can have the option to Drill down to User/Account level in the Knowledge centre Bot Analytics. Thanks, Shireesha.
Y’all changed a vital chart, and actually removed important information and did not replace it. This is a monthly chart. You used to show how this chart looked vs. the previous equal timeframe. That is now gone. I’m not sure I care about these new values, and they’re organized oddly. Aside from missing data, I have to think far more than I should every time I look at this thing. Sunday is down 88% since last Monday? Well no kidding. Show me change vs. equal day of week. Show me change vs. previous 7 days. GIve me something like this.
It would be really great If User had a ability to automate the Audience explorer report and schedule to share it on daily or weekly basis. Eg: User created a bookmark and wants to share it via email on daily basis from Audience explorer automatically .
With the current design of PX, If we configure the Dialogue Engagement as Bar, in Bottom like the below Image, The Dialogue bar will cover the content of the Page in End Application, And it will prevent accessing the content or footers in the page until and unless We close the Dialogue bar. Like this, It would be really helpful if we can Display the bar in the Bottom without covering the main content. Thanks, Shireesha.
Additional logic for NPS surveys in engagements (with/without comments)Under Consideration
At the end of January we ran an in-tool NPS survey which returned over 9,000 responses and provided us invaluable insight into the NPS for each of our accounts. This allowed us to take important actions for those accounts with lower NPS, touch base with admins that were passive/detractors and generally get a great feel for satisfaction with our product globally. We have set this survey to run every four months, with the next survey due to show in the tool at the end of May. We would like to act smarter and more systematically the next time this survey starts to receive responses, especially for detractors and passives, in the form of an email engagement. One thing that is lacking in the logic for NPS surveys in engagements is to be able to filter surveys by with/without comments. Depending on whether the user left comments or not in their response can massively change how you want to approach your engagement. I.e. With comments means you can contact user directly as they have alr
In the Recent Activity section on the PX User Profile, mouseover a Feature should show the full path to the Feature in the PX Product MapNo Status
In the “Recent Activity” section on the PX User Profile, mouseover a Feature should show the full path to the Feature in the PX Product Map. See example below: Sample mouseover Feature Map text that should be displayed: We already do this for Page Views, Identify Calls, Custom Events, etc., so this would be a very helpful improvement.
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.