Skip to main content
New Idea

Associate CTA with Success Plan

Related products:CS Success Plans & Customer Goals
  • September 30, 2024
  • 3 replies
  • 189 views

Now that Success Plans can be configured to include CTA Types beyond only “Objective” it would be great if a CSM could associate an existing (independent) CTA with an existing Success Plan or (added bonus!) create a Success Plan from an existing CTA. 

We have several CTAs that are automatically created when certain customer criteria is met, think low or drops in product usage, and we have a “Get Well” Risk Mitigation/Red Account process that uses the Success Plan feature -- it would be nice to enable CSMs to associate a system generated Risk CTA to an existing Red Account Success plan or use that CTA to spin up an associated Red Account Success Plan if one doesn’t already exist. 

Similarly, the same process could be applied for more standard automated lifecycle/adoption CTAs to be applied to adoption/growth focused Success Plans.

3 replies

bradley
Forum|alt.badge.img+8
  • Expert ⭐️
  • March 6, 2025

Good one ​@avertuca ! This should have been part of the release or at least a fast follow. Thought I had made my own post on this but I think I just grumbled about the release itself.


  • Contributor ⭐️⭐️
  • March 26, 2025

We are also looking to be able to associate existing CTAs with Success Plans


shense
Forum|alt.badge.img+2
  • Contributor ⭐️⭐️
  • September 24, 2025

Our Use Case:
Our team runs Success Plans quarterly to keep CTAs organized. Often, a CTA created in one quarter still needs to be tracked/migrated in the next quarter’s plan. Currently, CTAs tied to an existing Success Plan cannot be reassociated or moved to a new plan, which creates gaps in continuity and manual overhead.

Impacted Roles:

  • Customer Success Managers/Accout Mangers (CSMs): Responsible for managing Success Plans and CTAs, requiring efficiency and historical accuracy.

  • Operations/Admins: Supporting teams need to maintain clean reporting and ensure data integrity across plans.

A few note - for these particular Success Plans:

  • Our CTAs are unique and manually created per plan (not generated by Rules Engine), so they cannot be moved using a RE.

  • Current workaround is to close the CTA and manually recreate it in the new plan, but this loses the original creation date, details, and action history.

Workaround/Current Solution from our CSSC.

  • Adding a “Created Date” field so the original creation date can be manually re-entered.

  • Manually copying details and actions into the new CTA.
    These solutions are inefficient and prone to error.