Guided Selling - Summer 2025 Release (v11)

Guided Selling just got easier and smarter. Version 11 delivers on‑the‑fly flexibility, lighter data footprints, and faster, more focused workflows — helping your team move faster, stay organized, and focus on what matters most.

What this means for you:

• Adapt in real time – Insert or remove steps in live sequences without disrupting reps.
• Act in the moment – Reps can create Quick Actions—one‑off Calls or Tasks—for any lead or contact, whether they’re in a sequence or not.
• See only what matters – Just‑in‑Time Action Creation eliminates clutter and accelerates load times.
• Trust your data – Activities automatically tie back to the opportunity or campaign that triggered them, giving you cleaner attribution.

Feature Highlights

1. Just-in-Time Action Creation – Boosts performance and reliability by removing unnecessary records.
2. More Precise Due Dates – Manual actions appear in Engage in near real time (on page refresh).
3. Email AI Assistant (Revenue AI) – Drafts and refines personalized emails in seconds—powered by Revenue AI. Admin‑controlled enablement lets you decide when to activate AI for your team.
4. Quick Actions – These ad hoc actions show up in Engage and help reps follow up in the moment, without needing to add a task or reminder outside of Guided Selling.
5. Expanded Merge Fields – Personalize emails with data from Opportunities, Accounts, and any object related to your participants through standard or custom relationships.
6. Improved Activity Association to Opportunities and Campaigns – Engagement that is easier to trace back to revenue.
7. Mid-Sequence Edits – Adjust live sequences by inserting or removing steps to keep reps on track and adapt sequences to new strategies and updates.

Implementation Steps

Steps by Package Version

Follow the steps below to upgrade to the Guided Selling Summer 2025 Release based on your installed version. Not sure what version you are using? Ask your Admin to check the version of the installed packages within Salesforce's setup admin.

Before Upgrading:
To avoid potential post-install migration jobs from failing, navigate to Salesforce Setup > Custom Settings > GS_User Settings to ensure Enable Papertrail is unchecked. This setting should remain disabled indefinitely.

• For customers installing Guided Selling for the first time, you can take a look at our getting started guides to make sure that your admins are installing and configuring the package for use by your team.

• Revenue Intelligence Package Dependency: To install the latest version of the Guided Selling version you will need to have installed version 1.116 of the Revenue Intelligence package or later. This install must be made before installing the latest Guided Selling version.

  • Revenue Intelligence Package 1.116: Sandbox Install/Production Install

  After upgrading the Revenue Intelligence package, navigate to Guided Selling Sequence Settings > System Update to begin the self-service upgrade.
  
  For more detail, see: Self Service Upgrades for Guided Selling

  After Upgrading:

  1. Click the “Set Batch Owner ” button on the Sequence Settings > Batches page. This will initiate new Apex Jobs and ensure they are owned by a System Administrator user.   
  2. Navigate to the Users section on Sequence Settings and click the “Grant All Permissions” button to ensure any new fields added to the package are added to your Guided Selling Standard Object Permissions set. 

• Some organizations have reported that actions disappear from Engage immediately after upgrading. If you encounter this and do not see the "PopulateSeqAssociationLookupBatch" running in your Apex Jobs list, follow the steps provided in the article linked here to manually start the batch:
  Manually Run Sequence Associations Backfill Batch
  
  Processing time for this batch depends on the volume of records in your Salesforce instance. We recommend running installs after business hours to avoid impact to your end users.

  After Upgrading:

  1. Click the “Set Batch Owner ” button on the Sequence Settings>Batches page. This will initiate new Apex Jobs and ensure they are owned by a System Administrator user
  2. Navigate to the Users section on Sequence Settings and click the “Grant All Permissions” button to ensure any new fields added to the package are added to your Guided Selling Standard Object Permissions set. 

  Disable Campaign and Campaign Member Triggers (Optional)

  When upgrading from some older versions of Guided Selling, we've observed instances where triggers are incorrectly enabled or disabled compared to your previous settings. Some organizations choose to disable certain triggers to reduce the number of concurrent batch jobs and triggers running in the background. As a best practice, we recommend enabling triggers for objects you have Sequences created for.

  If your organization contains many Campaign and Campaign Member records and Campaign sequences are not being used, we strongly recommend disabling the Campaign and Campaign triggers for performance purposes. 

  1. Navigate to the Guided Selling App | Settings | Triggers

  2. Validate your list of enabled triggers. For instance, if you are not running any Campaign Sequences, consider disabling Campaign and Campaign Member.

• Disable Campaign and Campaign Member Triggers (Optional)

  When upgrading from some older versions of Guided Selling, we've observed instances where triggers are incorrectly enabled or disabled compared to your previous settings. Some organizations choose to disable certain triggers to reduce the number of concurrent batch jobs and triggers running in the background. As a best practice, we recommend enabling triggers for objects you have Sequences created for.

  If your organization contains many Campaign and Campaign Member records and Campaign sequences are not being used, we strongly recommend disabling the Campaign and Campaign triggers for performance purposes.

  1. Navigate to the Guided Selling App | Settings | Triggers

  2. Validate your list of enabled triggers. For instance, if you are not running any Campaign Sequences, consider disabling Campaign and Campaign Member.

  Assigning Batch Owners:

  1. Click the “Set Batch Owner ” button on the Sequence Settings>Batches page. This will initiate new Apex Jobs and ensure they are owned by your user.   
  2. Navigate to the Users section on Sequence Settings and click “Grant All Permissions ” to ensure the Guided Selling Standard Object Permissions is current based on your Sequences Entrance and Exit criteria.

  Delete rdnacadence__Unique_Id__c from Participant Sequence History object.

  This is a legacy field that is deprecated, though if left in an org it will cause issues in future upgrades.

  Replace the legacy Template Edited field on the Participant Action object. 

  1. Update the page layout for the Participant Action to include the unused "Template Edited" field and remove the legacy one currently on the page layout.  
  2. Delete the legacy Template Edited field from the Participant Action (must be done on Salesforce Classic)

  Disable legacy Process Builders:

  1. Rollup Field on Participants(Email Replied)
  2. Rollup Field on Participants(Email Sent)
  3. Rollup Field on Participants(Email opened)
  4. Rollup Field on Participants(Is Deferred)
  5. Rollup Field on Participants(Is Performed)

New Features and Functionality

Just-in-Time Action Creation for Improved Guided Selling Performance

What's New?

Sequence actions are now generated dynamically, as they’re needed, not all at once. 

Why Was This Built?

This update ensures a more responsive application and a more reliable user experience by reducing system strain, improving data accuracy, and simplifying sequence management.

How Does It Work?

• Participant Actions are created only as needed, reducing unnecessary data.
  • The first action is created at the time it is added to the sequence.
  • For Slow Drip Sequences, the first action is created when the Sequence Association Status is updated from Queued to Active.
  • Each subsequent action is created when the previous action is performed.
• Sequence progress is still tracked in the Participant Action Overview module; future steps are visible but records are generated on demand.

Real‑Time Action Visibility & Precise Due Dates

What’s New?

Sequence actions and Quick Actions now surface in Engage the moment they become due–evaluated continuously against due dates and action criteria instead of relying on scheduled batch jobs.

Why Was This Built?

The shift to a just‑in‑time action‑creation engine opened the door to rethink how due dates are evaluated. By eliminating the hidden 30‑minute batch jobs that once decided when actions appeared, we removed a major source of latency and failure. Real‑time evaluation means a precise due date actually matches when a rep sees the task, simplifying the workflow, boosting performance, and restoring confidence that Engage always shows the right actions at the right moment. Admins will spend less time chasing “missing” actions and more time optimizing sequences.

How Does It Work?

• Engage continuously evaluates due dates and action criteria; as soon as a sequence action or Quick Action is due, it appears on Engage.
• Reps see exactly what they need to do, right when it matters.
• A page refresh, which happens automatically or can be done manually, is required to trigger evaluation of upcoming actions.

AI Email Assistant – Powered by Revenue AI

What's New?

Email AI Assistant is now included with your Revenue AI license and can be enabled by Administrators when your team is ready.

Why Was This Built?

Email remains the #1 channel for revenue teams, yet drafting high‑quality, personalized messages takes precious time. By adding generative email to the Revenue AI suite, we expand the value of your existing license, giving reps the same trusted AI that powers coaching feedback and opportunity insights, now applied to outbound communication. The result: faster outreach, higher response rates, and even more ROI from the license you already own.

How Does it Work?

Once an admin enables the assistant, reps will see Draft with AI as well as inline Refine with AI controls—options like Expand, Trim, Translate, or Adjust Tone—directly within their sequence email actions and templates, letting them generate or polish content in a single click.

• The OpenAI remote site setting has been removed from the package; enabling the assistant is handled via Revenue’s licensing model.
• Admins must assign appropriate Revenue AI licenses and explicitly turn on the feature to enable external LLM Connections.

Mid‑Sequence Edits Without Disruption

What’s New?

Admins can now insert or remove actions in the middle of live sequences. Reps stay on track without losing progress, and the next step automatically reflects the updated structure.

Why Was This Built?

Previously, all sequence actions for a participant were created in advance, preventing mid-sequence adjustments. This made sequences harder to maintain and less adaptable to real-world changes and adjustments in strategy.

How Does It Work?

• Insert new actions anywhere in the sequence; participants will automatically follow the updated flow.
• Remove an action; existing participant actions remain unchanged, and the system adjusts Next Action pointers to maintain sequence integrity.
• Skip Criteria can be applied to force participants to bypass a removed step.
• Reordering actions is not supported when participants are active. Instead, insert a copy at the new position and remove the old one.

Create Quick Actions to Stay on Top of Your Outreach

What’s New? 

Create one‑off Calls or Tasks for any participant—or even for leads/contacts not in a sequence—and have them appear at the top of a rep’s Engage view.

Why Was This Built? 

Reps often need to follow up outside a predefined sequence. Quick Actions provide a lightweight, in‑context way to stay organized and act immediately.

How Does It Work?

• Create Quick Actions in convenient locations—on the Participants tab in Guided Selling or the Participant Overview module.
• Task and Call actions can be created by simply choosing a due date and a name.
• In v11, actions appear in near real‑time, enabling Quick Actions to surface at the top of Engage exactly when you need them, prioritized above sequence actions.

Pro Tip:

• The Name field is limited to 80 characters. Add context to the Name to recall the reason for it; it is visible when expanding the action on Engage. Here are some examples that are well below the character limit:
  • • “Follow-up on Q2 pricing email”
    • “Confirm demo date with Julia L.”
    • “Gauge interest in pilot expansion”
    • “Send revised contract for signature” 

Expanded Merge Field Options for Emails

What's New?

Admins can now reference fields on related parent objects—such as Opportunity, Account, User, or any custom object—by entering dot‑notation paths that follow Salesforce’s standard or custom relationships.

Why Was This Built?

This enhancement allows admins to personalize emails with richer context from related records—solving a key limitation that blocked many users from including essential business information in templates.

How Does It Work?

• Manually-typed merge field paths are supported, including references like Participant.Account.Name or Opportunity.SyncedQuote.Account.Id.

• Supports up to four relationship levels (e.g., Participant.Account.Owner.Email).

• Works only for sequence‑related email actions.

Improved Activity Association to Opportunities & Campaigns

What’s New?

Activities from Campaign and Opportunity Sequences now link directly to the source campaign or opp — giving you cleaner reporting and better visibility into what’s working.

Why Was This Built?

Accurate engagement tracking is critical for forecasting, coaching, and proving ROI. By writing sequence Calls, Emails, and Tasks back to the originating Opportunity or Campaign—admins and managers can review the full history in one place, understand what propelled the deal forward, and surface playbooks that work.

How Does It Work?

• On by default – no extra configuration required.
• Each completed sequence action for Contacts will get an Activity record that's automatically associated with the source Opportunity or Campaign.
• Limitation - Salesforce locks the WhatId on Lead Tasks to preserve campaign attribution in case the Lead converts to an Opportunity, so the Campaign Id cannot be written to these.
• Existing reports, dashboards, and automations that join Activities to Opportunities/Campaigns will immediately surface richer engagement data; review any custom logic that filters on WhatId to ensure it still aligns.

Technical Improvements

1. Simplifying Slow Drip Sequences – Removes dependency on the Queue Entry object; Queued vs. Active participants are visible directly on Sequence Association records.
2. Combined Sequence History & Association – Sequence Associations will act as a reference of active and historical sequence participation, using a status value of ‘Active’ or ‘Completed.’  This eliminates the need to create new Participant Sequence History, and makes reporting easier, improves performance, and gives your team a clearer view of each participant’s journey.

3. Bulk Managing Active Participants – Bulk actions now extend to the Participants tab for faster workload management.

Known Issues

There may some rare cases when a participant exits a sequence, and the next action is created in error.  This could cause an errant action to be on Engage.  Admins can check for any Participant Actions with a 'Ready' Action Status where the related Sequence Association has a 'Completed' Association Status.  These are safe to delete, but in some cases the Custom Setting Enable Deletion Validation will need to be temporarily disabled to delete these actions successfully.

Package Changes for Admins

🆕 New Public Custom Setting: Area Code

We introduced a new Public List Custom Setting to manage area codes and time zones, used to present the local time for Call Actions on Engage.

⚠️ Although custom settings technically share limits with custom objects, this setting does not count toward org limits because it is part of a certified managed package.

Object Label: Area Code
API Name: RDNACadence__Area_Code__c

Fields:

• Label: Area Code
  API Name: RDNACadence__Area_Code__c
  
  • Type: Text (255), Required, External ID, Unique
    
    
• Label: Time Zone
  API Name: RDNACadence__Time_Zone__c
  
  • Type: Text (255)
    
    
• Label: Last Sync Date
  API Name: RDNACadence__Last_Sync_Date__c
  • Type: DateTime

🔧 Admin Responsibilities
✅ No action required. Area Code records are inserted automatically by the system. This object is hidden from end users and is not intended for manual entry or customization.

🆕 New Fields on Sequence Action 

Object Label: Cadence Action
API Name: RDNACadence__CadenceAction__c

These are fields used by the system to support linked sequence actions and enhancements to sequence management.

Fields:

• Label: Deleted
  API Name: RDNACadence__IsDeleted__c
  
  • Type: Checkbox, Default: false
    
    
• Label: Next Sequence Action
  API Name: RDNACadence__Next_Sequence_Action__c
  
  • Type: Lookup to Cadence Action

🔧 Admin Responsibilities
  ✅ No action required.
⚠️ These fields should not be modified.

🆕 New Fields on Participant Action 

Object Label: Sequence Action
API Name: RDNACadence__Sequence_Action__c

Fields:

Action Status is used by the system for tracking actions as they are performed.

• Label: Action Status
  API Name: RDNACadence__Action_Status__c
  
  • Type: Text (50), External ID

Configuration holds details provided by a user for Quicks Tasks.

• Label: Configuration
  API Name: RDNACadence__Configuration__c
  
  • Type: Long Text Area (32,768)

This new Action Type field holds the type for Quick Actions. Sequence actions will have a blank value for this field, and Quick actions will have a blank value for RDNACadence__Cadence_Action_Type__c.

• Label: Supplemental Action Type
  API Name: RDNACadence__Type__c
  
  • Type: Picklist
  • Values:
    
    • Call
    • Task

🔧 Admin Responsibilities
✅ No immediate changes required.  For reporting on Quick Actions, include a filter for Supplemental Action Type.

🗑️ Removed Fields from Participant Action

These deprecated summary fields have been removed:

• Label: (Deprecated) Email Links Clicked
• API Name: RDNACadence__Email_Links_Clicked__c
• Label: (Deprecated) Email Opens
  API Name: RDNACadence__Email_Opens__c
• Label: (Deprecated) Email Replies
  API Name: RDNACadence__Email_Replies__c

🔧 Admin Responsibilities
⚠️ Review existing reports and dashboards that used these fields. Replace with updated engagement tracking logic (likely based on related event objects).
✅ Remove these from page layouts if still present.

🆕 New Fields on Sequence Association 

Object Label: Sequence Association
API Name: RDNACadence__Sequence_Association__c

Many field additions are related to the consolidation of Participant Sequence History Records, so that the Sequence Association can provide all of the same functionality while storing data in one place. Other changes include system fields, and relationship fields that power enhancements for email merge fields and better engagement tracking for Opportunity and Campaign Sequences.

Fields:

• Label: Association Status
  API Name: RDNACadence__Association_Status__c
  
  • Type: Text (50)
    
    
• Label: Campaign
  API Name: RDNACadence__Campaign__c
  
  • Type: Lookup to Campaign
    
    
• Label: Campaign Member Id
  API Name: RDNACadence__CampaignMemberId__c
  
  • Type: Text (18)
    
    
• Label: Lead Conversion Date
  API Name: RDNACadence__Lead_Conversion_Date__c
  
  • Type: DateTime
    
    
• Label: Last Completed Sequence Action
  API Name: RDNACadence__Last_Completed_Sequence_Action__c
  
  • Type: Lookup to Sequence Action
    
    
• Label: Opportunity
  API Name: RDNACadence__Opportunity__c
  
  • Type: Lookup to Opportunity
    
    
• Label: Opportunity Contact Role ID
  API Name: RDNACadence__Opportunity_Contact_Role_ID__c
  
  • Type: Text (18)
    
    
• Label: Participant Iteration
  API Name: RDNACadence__Participant_Iteration__c
  
  • Type: Number
    
    
• Label: Sequence Entry Date
  API Name: RDNACadence__Sequence_Entry_Date__c
  
  • Type: DateTime
    
    
• Label: Sequence Exit Date
  API Name: RDNACadence__Sequence_Exit_Date__c
  
  • Type: DateTime
    
    
• Label: Sequence Exit Criterion Met
  API Name: RDNACadence__Sequence_Exit_Criterions_Met__c
  
  • Type: Long Text Area
    
    
• Label: Sequence Exit Type
  API Name: RDNACadence__Sequence_Exit_Type__c
  
  • Type: Picklist
  • Values:
    
    • Manual
    • Automatic
      
      
• Label: Sequence Participant Snapshot
  API Name: RDNACadence__Sequence_Participant_Snapshot__c
  
  • Type: Long Text Area
    
    
• Label: Sequence Attribution Threshold
  API Name: RDNACadence__Sequence_Attribution_Threshold__c
  
  • Type: DateTime
    
    
• Label: Sequence Conversion Attributed
  API Name: RDNACadence__Sequence_Conversion_Attributed__c
  
  • Type: Formula (Checkbox)
    
    
• Label: Unique Id
  API Name: RDNACadence__Unique_Id__c
  
  • Type: Text (100), Unique

🔧 Admin Responsibilities
✅ Recommended actions:

• Add key fields to page layouts as needed:
  
  • Sequence Entry Date
  • Sequence Exit Date
  • Sequence Exit Type
  • Lead Conversion Date
• Review any custom Flows that may have been based on creation of Participant Sequence History records and move them to updates to the Association Status. When a participant exits a sequence for any reason, the Association Status is updated to ‘Completed.’

🆕 Compact Layout Change for Sequence Association

Compact Layout: GS_Sequence_Association_Compact_Layout
Object: RDNACadence__Sequence_Association__c

Fields Displayed:

• Name
• RDNACadence__Association_Status__c
• RDNACadence__Sequence__c
• RDNACadence__Sequence_Entry_Date__c
• RDNACadence__Last_Completed_Sequence_Action__c

🔧 Admin Responsibilities
✅ No action required unless your org has overridden compact layout assignments. This layout improves record visibility in Lightning pages.

🆕 New Lookup on Sequence Attribution 

Object Label: Sequence Attribution
API Name: RDNACadence__Sequence_Attribution__c

Field:

Enables relationship between attribution records and sequence participants.

• Label: Sequence Association
  API Name: RDNACadence__Sequence_Association__c
  
  • Type: Lookup to Sequence_Association__c

🔧 Admin Responsibilities
⚠️ Optional: This field enables deeper attribution reporting. Consider surfacing it on page layouts if using custom reports or integrations tied to attribution logic.