A follow-up sequence can look organized while prospects still wait days for a reply. Salesforce Sales Engagement gives reps a structured outreach queue, but useful results depend on licensing, ownership, and reporting choices.
For a small SaaS team, the goal is reliable follow-up without duplicate outreach or unnecessary administration. Start by confirming access, then build one focused cadence and measure whether it produces qualified conversations.
Check Salesforce Sales Engagement prerequisites
Confirm your edition and licenses
Salesforce documents Sales Engagement as included with Sales in Performance, Einstein 1, and Unlimited Editions. Professional and Enterprise Editions require an extra-cost add-on. Salesforce also documents add-on availability for Service and Lightning Platform.
These distinctions don’t establish what your organization has purchased. Confirm your contract, user licenses, and required permission set licenses before assigning access. Don’t assume every Sales Cloud user can execute cadences or use performance analytics.
In Setup, search for Sales Engagement and review its setup page. Enable the feature where available, then check email and calling dependencies for the steps you intend to use. Automated email requires more preparation than a sequence of manual tasks.
Separate administrator, creator, and rep access
Salesforce lists Customize Application, Modify All Data, Assign Permission Sets, and Manage Users as setup permissions. Those are implementation requirements, not a reason to give reps administrator access.
Cadence creation requires the Sales Engagement Cadence Creator or Sales Engagement Cadence Creator Included permission set. Follow Salesforce’s permission assignment guidance for the appropriate user access.
As an operational recommendation, group reusable permissions by responsibility. Keep cadence creation separate from routine execution where practical.
Also check record sharing and field-level security. Permission sets don’t automatically grant access to every Lead or Contact. Test with a representative non-admin user, because an administrator can conceal access problems.
Plan one cadence around one sales motion
A demo request needs a different follow-up process than a research-stage contact. Trial milestones, outbound prospecting, and renewal conversations also have different timing and ownership requirements.
Salesforce provides cadence examples for customer outreach. Use them as starting points, then adapt the sequence to your team’s capacity and customer expectations.
Before building, document the entry condition, responsible rep, desired outcome, and reasons to stop outreach. For demo requests, the outcome might be a qualified meeting. For early research contacts, it might be a reply that confirms interest.
Use account fit and buying intent to prioritize enrollment, but remember that cadence targets are individual records. Salesforce supports leads, contacts, and person accounts, not business accounts as targets.
Recommendation: Begin with one motion and a short sequence. Include enough time for reps to handle replies before the next outreach attempt.
Also decide how to handle existing opportunities, duplicate records, and people who opt out. These are operating rules your team must implement, not protections you should assume every cadence provides automatically.
Create and activate a cadence in Builder 2.0
Build the main sequence
Salesforce recommends Cadence Builder 2.0 for new cadences. Classic is the original builder, with retirement planned for a future release. Salesforce hasn’t specified a retirement date in the documentation referenced here.
To create a cadence:
- Open the Sales Engagement app, select Cadences, then choose New Cadence.
- Select Open Cadence Builder 2.0 and enter a clear name and description.
- Add steps to the Main track in the order reps should perform them.
- Configure each step’s timing and available settings, including email content where applicable.
- Save the cadence, then review its tracks and rules before activation.
Use the description to record the audience and intended outcome. A name alone rarely explains when enrollment is appropriate.
Choose step types that match your process, such as email, calls, or other supported actions. Builder 2.0 also supports screen flows as cadence steps, which can guide reps through structured work.
Configure tracks, exits, and activation
Builder 2.0 has three tracks: Main, Positive, and Negative. Track entry rules can move targets between tracks. Main-track exit rules apply across tracks.
Configure rules around supported signals and your documented outcomes. Don’t assume a booked meeting or CRM status change automatically stops outreach without an appropriate rule or removal process.
For call-based branching, review call-result mapping before testing. Inconsistent dispositions can send targets down the wrong path.
Finally, save and activate the cadence. Activation makes it available for enrollment; it doesn’t prove that sending, branching, or permissions work correctly.
Enroll targets and assign execution responsibility
Add eligible records and choose an assignee
Once the cadence is active, open an eligible Lead, Contact, or Person Account record and use Add to Cadence. Select the cadence and target assignee. Salesforce also supports adding targets from list views and reports.
Before bulk enrollment, filter for the intended audience. Check qualification, ownership, contact details, and existing outreach. A broad list can create a large backlog immediately.
Treat target assignment and CRM record ownership as separate decisions. The cadence assignee should be the person responsible for completing outreach, even when your broader account-coverage model involves other teammates.
If the action is missing, inspect activation, user permissions, and page configuration before changing broader access. Also confirm that the user can open the target record.
Execute work and preserve handoff context
Reps perform cadence work through the Work Queue. They should complete supported actions and log outcomes consistently so progression and reporting reflect actual activity.
Make execution rules explicit. For example, define which call disposition indicates a connection and who removes a target after an outcome requiring human review. Don’t let each rep invent their own interpretation.
When coverage changes, review active targets and pending work rather than changing record ownership alone.
The cadence history related list helps users inspect previous cadence participation and the last completed step. That context reduces repetitive outreach during handoffs.
Choose the reporting layer your team needs
Start with reports that answer operational questions
Salesforce provides standard reports, custom report types, and dashboards for cadence activity and performance. Its Sales Engagement reporting documentation describes options for evaluating qualification and step effectiveness.
Documented custom report types include Cadences & Steps, Cadences & Steps with Monthly Metrics, Cadences & Trackers, and Cadences and Trackers (Inner join).
Use step-oriented reports to examine sequence structure and step metrics. Tracker-oriented reports help examine target participation and progress. Monthly metrics support period comparisons, but monthly totals alone don’t establish an enrollment cohort.
Check report filters and row detail before interpreting totals. A report containing multiple step rows per target can overcount people if you treat every row as a distinct prospect.
Enable performance analytics separately
The Sales Engagement Performance Analytics Application requires activation in Sales Engagement Setup. Treat this as a separate configuration task, not an automatic consequence of enabling cadences.
Review applicable analytics access and licensing before promising dashboards to every user. Report and dashboard folder sharing also needs deliberate configuration.
Call-result mapping is another dependency in Salesforce’s analytics setup guidance. Without consistent mappings, call-performance comparisons can be misleading.
For a small team, begin with reports that answer immediate questions: who has pending work, where targets stall, and which sequences generate useful responses. Add more analytics only when someone owns the review process and resulting decisions.
Measure outcomes without confusing activity with success
Salesforce Sales Engagement reporting becomes useful when activity connects to a business outcome. The measures below are recommended definitions, not a claim that every dashboard calculates them automatically.
Use a consistent reporting window and distinct target counts.
| Measure | Suggested calculation | What it helps diagnose |
|---|---|---|
| Enrollment volume | Distinct targets added during the period | Work entering the sequence |
| Step completion rate | Completed steps divided by steps due | Execution capacity and backlog |
| Reply rate | Distinct replying targets divided by contacted targets | Audience and message response |
| Qualified meeting rate | Targets producing qualified meetings divided by enrolled targets | Conversation quality |
| Opportunity creation rate | Targets linked to new opportunities divided by enrolled targets | Downstream pipeline contribution |
The strongest comparison uses similar audiences and enough time for outcomes to occur.
A cadence launched last week shouldn’t compete on opportunity creation with one whose targets have had months to progress.
Segment results by sales motion, lead source, market segment, and enrollment period. Otherwise, high-intent demo requests can make an average sequence look stronger than outbound prospecting.
Low completion with many pending steps suggests a workload or execution problem. Strong completion but weak replies points toward audience selection, timing, or messaging.
Replies without qualified meetings require a closer look at qualification and handoffs. Also separate positive responses from refusals or opt-outs.
For meeting and opportunity attribution, define how outcomes connect to targets. You may need additional CRM fields or reporting relationships. Cadence participation alone doesn’t prove that the sequence caused revenue.
Pilot the workflow and govern changes
Before broad rollout, test a small set of appropriate records through the complete workflow. Use a sandbox when your release process supports it, then follow your normal deployment controls.
Test as a rep and as a cadence creator. Verify allowed actions and denied actions, including access to sensitive fields and reports. Confirm that email content, timing, call outcomes, and target assignment behave as intended.
Then inspect the reporting output. Reconcile enrolled targets against report counts and check whether completed steps appear where expected. A functioning Work Queue doesn’t guarantee a trustworthy dashboard.
Assign an owner for cadence changes, access reviews, and performance definitions. Document temporary coverage access with a reason and expiration date, then remove it when coverage ends.
Recommendation: Change one meaningful variable at a time during performance reviews. Altering the audience, timing, and message together makes it difficult to identify which change helped.
Build a Cadence You Can Operate and Measure
A useful cadence gives every target a clear next action and an accountable rep. Reliable reporting depends on the same discipline: consistent outcomes, defined denominators, and comparable cohorts.
Start with one sales motion, test the full workflow with real user permissions, and verify the resulting reports. Expand Salesforce Sales Engagement only after the team can explain both its pending work and its qualified outcomes.
