Great question—multi-threading is such an effective strategy for building stronger account coverage, and it's great you’re thinking about how to implement it thoughtfully. Here are a few ideas and best practices that might help:
1. Parent vs. Linked Cadences
Creating separate "linked" cadences for multi-threading is a smart approach! It keeps the steps targeted to the additional contacts while leaving the parent cadence intact for the primary point of contact.
For example, the parent cadence could focus on decision-makers, while the linked cadences target influencers or champions. You might also consider cadences by title or persona:
- A simple naming convention (like iAccount Name] - Parent and aAccount Name] - Multi-thread) can make it easy to stay organized.
2. Managing Steps
If you don’t want the team skipping steps in the parent cadence, keeping multi-threaded cadences separate is a good call. This also allows you to tailor steps to the role or persona of the contact. Consider adding tags and/or using “Account” to view Cadences by “Company”, to ensure quick access to all account-related activities.
3. Tracking and Reporting
Use tags to track multi-threading efforts and capture key insights about each contact. This keeps everything centralized for easy reporting.
In Salesloft Analytics, you can set up reports to track performance on these linked cadences (e.g., engagement rates, booked meetings). It’s a great way to see what’s working across all threads in an account. (To do this, add a filter → Name → type or select Cadences to be included.)
4. Collaboration and Coaching
Multi-threading is most effective when the whole team is aligned, so building it into your account planning discussions can help identify the right personas and messaging.
Consider reviewing some of the team’s outreach within multi-threaded cadences to ensure messaging is consistent across contacts—it’s a great coaching opportunity, too!
What’s worked for you with multi-threading? Share your tips or strategies below!
Sheena
Thanks @SheenaJohnson! This is great feedback and insight. I had not thought about tags, but I will implement it immediately. We are just getting started with formalizing multi-threading so we can bring the team together. While I’m researching best practices, we are working to move forward with a plan and will refine it as we go forward.
Nice - do keep us posted if you encounter any unexpected hurdles or wins. We loved receiving your question and look forward to the next!