Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    hemanth_kalidindiGainsight Employee ⭐️

    Allow the field to field comparision in JO Evaluate & Conditional Wait StepsNew Idea

    Hi Team, Currently, our JO both Old and New programs don’t allow the Field to Field comparison in the Evaluate and Conditional Wait steps either for Audience or Calculated fields; like how we allow it in the Report builder (see the 2nd Screenshot) Use Case: There are accounts that regularly have a change of data in fields, let’s take CSM field as an example; on Day 1, I sent an email with CSM Name as “ABC” later if the CSM gets changed for that account to “XYZ”, then in that case I wish to send my subsequent emails to receive a different contextual email template altogether, but I can only send a different Template if I can evaluate if the CSM of that particular account is changed by comparing it with the initially loaded participant CSM value. Had I known that account CSM i can simply pass it as value in Evaluate step, but since each account have a different CSM then I can manually choose to create multiple branches.Had I have the option to compare the current CSM field (taken from Calculated field) and check with the Participant CSM field in Evaluate by comparing on field to field basis i would be able to achieve my use caseNote: Although I can use calculated fields, but I can’t dynamically evaluate the value coming from Calculated field with Participant field Existing Evaluate or Conditional Step functionality only allows to pass static values: Field to Field comparison in Report builderfyi @vmallya 

    alizee
    alizeeVIP ⭐️⭐️⭐️⭐️⭐️

    Allow to change outline color on Survey Secondary Button StyleNew Idea

    Here’s a nice, basic web design standard one. In Surveys, we are offered three types of buttons:Primary CTA (colored fill) Secondary CTA (colored outline, transparent fill) Normal Link (colored text When you select the Primary CTA, you can change:Fill color Font colorWhen you select the Secondary CTA, you can change:Fill color Font colorYou cannot change the outline color and if you want something else than Gainsight blue, WHY offer a secondary button style for which you can’t change the outline color, only the fill color?--Support (Tier I) has been telling me that this is expected and suggested I change the fill so my button matches the primary button 🙄😶 (Yeah, sure. I want a secondary style button that looks exactly the same as the primary style), and claims that they (support, engineering, product) do not remember a time where we could change the outline color on the secondary button style. I do remember that time, but maybe I fabricated a memory of the only logical and possible approach to this. According to Support (Tier i), in their AI response, it’s not a bug and I’m mixing things up with email templates features.Fact is, I can’t see the point of even offering this style if there was never the option to change the outline color, but would be happy to be proven wrong and demonstrated the value of the feature as it stands by the pm in charge (not by Tier II). If you agree that we should be able to change the outline of the secondary button style (and not the fill), please upvote the hell out of this post ! PS: https://designcourse.com/blog/post/primary-vs-secondary-cta-buttons-in-ui-design, because at the end of the day, a survey is delivered via a web page. PS2: customer brand guidelines may require outline style buttons regardless of primary or secondary. 

    alb
    albContributor ⭐️⭐️⭐️⭐️

    Additional Throttling OptionsOpen

    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 notification goes out, we flat out stop conducting surveys for 2 weeks.  That’s valuable data not being collected.  It also means we could (in theory) overwhelm users every couple of weeks with a survey (even though we’re using % audience rules to attempt to limit this).     Anyway, would love to be able to apply these throttling rules to groups of engagements instead of globally.  Groups could be defined as the type of engagement, or as an actual organized group of engagements (if a folder hierarchy is every applied to engagements page, this could be used here).   Appreciate the read...