Skip to main content
New Idea

Restrict CTA name update for System Administrator generated CTAs

Related products:CS Rules Engine
  • February 24, 2025
  • 1 reply
  • 35 views
  • lyne_therien
    lyne_therien
  • ltsponhour
    ltsponhour
  • yuniyal
    yuniyal
  • kppatel
  • navalsankneni

romihache
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 429 replies

I couldn’t find a setting to do this, hence the idea.

As the CTA Name can be used as identifier, is it possible to restrict the name to be updated if it was created by System Administrator?  I know we can play with the Create CTA once in xx setting but that will not work if we have the same name convention in different rules/actions, and I can think of  scenarios where the name can be used as a quick filter in a report.

Let me explain the context:
A CSM flagged a CTA that was created 3 times, 2 of them had the name we set up in the Action step (“XXX”). This is what I saw:


The first two CTAs were modified by the CSM and the stored date time is after the rule ran on the 20th, but as it only shows the last one we can't say with 100% certainty what was the name of the CTAs at the moment the rule executed on the 20th (and the modification could be anything, not only the name)

This is what happened: When the CSM updated the CTA name to “XYZ”, caused for the second one to be created on Feb 19th. Then the CSM also modified that second CTA from “XXX” to “XYZ”, causing a 3rd CTA to be created. She then left just one called “XYZ” and reverted the name of the second to “XXX” so when she reported the issue, with the limited audit log data we have on our end we could’ve easily mistaken the issue by a bug.  Behind this issue were a lot of “what ifs” to ask the end user additional questions to try to identify the root cause ourselves instead of submitting a ticket to support.

Long story short, a “CTA Rename” restriction might be useful, eg: 


Thanks,

1 reply

Molly.McQ
Forum|alt.badge.img+2
  • Helper ⭐️
  • 70 replies
  • February 24, 2025

Great idea, ​@romihache! Restricting CTA name edits- especially for system generated CTAs, would help improve data integrity, troubleshooting efforts, and reporting. 

Beyond overcoming some of the audit and reporting challenges that Romi mentioned, there are additional benefits to consider: 

  • Preventing automation disruptions - many teams design workflows based on CTA names (e.g., auto-assignment of tasks, triggering followups, , escalations, and follow ups. A renamed CTA could disrupt these workflows, causing missed actions, incorrect workflows misaligned team processes, and potentially, customer service issues. 
  • Maintaining data quality across integrations - if CTAs are referenced in external tools like Salesforce, Jira, or BI reports, renaming could create mismatches, leading to reporting inconsistencies and possibly, failed data syncs that disrupt the workflow and associated reporting.
  • Reliable trend analysis - teams often analyze CTA patterns over time to track engagement trends. If users frequently rename CTAs, trend analysis around customer behaviors, risk, or engagment patters could be skewed. As a result, historical data becomes less reliable, making it harder for teams to measure impact
  • Minimizing manual fixes and rework - when naming inconsistencies occur, teams can spend unnecessary time troubleshooting discrepancies, retracing steps, and validating reports instead of focusing on what really matters.

In terms of the business impact, a Rename CTA permissions setting would allow for governance while preserving flexibility for necessary updates. This would be especially valuable for larger scale Gainsight implementations where multiple teams rely on CTA-driven processes. Restricting renaming only for System-generated CTAs (vs. manually created ones) could be a configurable option to balance control and usability. A permission based approach helps ensure renaming is intentional, preventing accidental or undesired changes while keeping flexibility for those who truly need it. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings