Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6164 Ideas

    bradley
    bradleyExpert ⭐️

    Associated Records: Allow Company and Relationship Cross AssociationNew Idea

    This is admittedly very similar to a couple of other requests that I found, but wanted to make a more generic request on the topic (similar ones below, worth reviewing/voting). User Story: As a CSM, I want the ability to create a Timeline Record at the Company entity level, and associate it at the Relationship entity level for one or more of that Companies relationships (and vice versa), so that I can more effectively manage my documentation across entity levels. Example Use Case: At Company Inc., we use relationships to track projects for our customers. As a CSM for Company Inc., I want to have the ability to log an event that is applicable to my Project Success Plan Objective for the Relationship AND for my Company level Renewal Success Plan Objective without creating it twice. Also, as a CSM, I have no real need to understand the technical entity distinction between Company and Relationship, just how to use them. The fact that it is possible to do this same workflow between Company Success Plan Objectives, or between Relationship Success Plan objectives makes this an even more confusing process and point of friction between myself, the tool and my platform team. While, as an admin, I appreciate the distinction, I am unable to make the platform work better for my users and have to constantly fight the “why does it work like this here but not here?” questions, which is a problem I myself wonder about all the time just from a configuration standpoint on the back end. This type of friction leads to our users complaining to mangers/leaders, not following workflows, and ultimately becomes one in a series of questions execs will ask about why they are using this as a tool.   Related posts  

    dayn.johnson
    dayn.johnsonVIP ⭐️⭐️⭐️⭐️⭐️

    Mobile Settings for Images are a thing! Can we get Mobile Settings for Content Blocks too?New Idea

    Just discovered something awesome hiding in the style menu for email images today: the mobile settings menu, and the new “Image Responsive” toggle! 😀It definitely forces a visible difference when viewed on a computer and mobile device. Idea 1: would it be possible to get a “mobile settings” responsive option added to the content blocks as well?The settings are already there for an entire email template, but sometimes we have certain blocks that we’d like to display vertically if on mobile, without forcing other blocks to do the same (particularly the 1:2 or 2:1 containers). I’ve used other template building tools that allowed that per-container mobile responsiveness toggle before (Stripo), and it was a fantastic option -- especially since it didn’t require any coding.Idea 2:Another mobile setting that would AWESOME to include would be the option to show or hide selected containers on mobile (with the default being to show on all). Certain template layouts don’t read well on mobile, and it’d be awesome to be able to hide those blocks and design something that DID in case someone opened the email on their phone, to avoid those embarrassing or awkward situations.I’d much rather someone not see something, even if we have to add a mobile-only text block that says “please view on your computer for the full message” or something similar.Thanks so much!  

    Mário
    MárioContributor ⭐️

    Functionality "Me too" and "Topic status tracking"New Idea

    I hope this message finds you well. I am writing to propose two ideas that could significantly enhance our platform's functionality and improve user experience. These suggestions are aimed at better tracking and managing issues raised by our community users, thereby increasing engagement and efficiency. Issue Status Tracking: Implementing a feature to track the status of issues created by community users can greatly improve transparency and communication. Each issue could display its current status within the topic, using labels such as "Created," "Response," and "Solution." This would allow users to easily see the progress of their concerns and know when they have been addressed. For example: This clear status indication will help manage user expectations and reduce repetitive inquiries about the same issue. Example:   Created: Indicates that the issue has been submitted and is awaiting review. Response: Shows that a team member has responded and is working on the issue. Solution: Signifies that the issue has been resolved and a solution has been provided. "Me too" Option: Introducing a "Me too" option where users can indicate if they are experiencing the same issue as described in a topic would be incredibly beneficial. This feature would enable users to click a "Me too" button, which not only counts the number of users facing the same problem but also lists who has selected this option. This collective data would help us prioritize common issues and track recurring problems more effectively. For instance: A user creates a topic about a connectivity issue. Other users experiencing the same issue can click "Me too." We can then see how many users are affected and address the most pressing concerns promptly. Example:While we understand that Vodafone's forum may have a different provider, we believe these functionalities would be highly useful and improve our community interaction significantly.Thank you for considering these suggestions. I am confident that these enhancements will greatly benefit both our team and our users. Please let me know if you need any further details or if we can discuss this further.Best regards,