Putting the right technology in place can make customer advocacy programs easier to manage and scale. Choosing and implementing that technology, however, can be surprisingly complicated.
For many teams, the first question is: “Where do we start?” There are many customer advocacy management platforms available, but they don’t all solve the same problems. Some focus on supporting reference requests from sales, while others offer capabilities for advocate recruitment, workflow management, communities, rewards, peer reviews, customer story development, or broader customer marketing activities. Most offer some level of reporting and analytics but the depth of those capabilities, as well as AI, can vary widely.
Some advocacy programs may need a dedicated platform, while others may be better served by connecting existing systems or improving their current processes.
Before looking at vendors, teams should assess how their program operates, including the needs of advocacy managers, key stakeholders, and the advocates themselves. Questions we typically work through with teams include:
Answers to these questions separate must-have capabilities from features that sound appealing in a demo but may not solve key problems. We also recommend mapping out a few everyday workflows to consider as you create your vendor shortlist and progress through evaluation.
Beyond individual capabilities, you’ll also want to consider integrations, security, data migration needs, reporting, and the effort to drive adoption.
Evaluate each vendor against the same realistic scenarios, not just standard sales demos. For example, ask:
Once you’ve done an assessment of your needs and requirements, the focus shifts to procurement and security reviews. Once a contract is signed, you’re then deep into implementation, coordinating with IT and other internal stakeholders, data migration, testing, roll out, and training.
Implementation is where many technology investments succeed or fail. A platform may offer strong functionality, but it will not create value if data is incomplete, the workflows don’t reflect how teams operate, or employees don’t understand how and when to use it.
The steps vary, but a few key things teams should prepare for:
Experience with customer advocacy programs can provide useful perspective throughout this process, helping teams evaluate technology in the context of real-world customer advocacy use cases and priorities.
AI deserves a specific evaluation, not just a mention on the feature checklist. Ask vendors to demonstrate current capabilities, explain where human involvement is needed, identify what customer and company data is used, and clarify whether that data trains AI models.
It is also important to distinguish between capabilities available today and those still on the roadmap, while involving security teams in the review.
Make sure to keep in mind that launch is the beginning; it is not the finish line. Once the platform is live, assess whether requests move faster, advocate engagement is better coordinated, and teams are using the platform as intended. Then, adjust workflows and training based on what the data and users tell you.
The goal is not simply to deploy a platform. It is to make advocacy easier to run, protect the customer experience, give internal teams dependable customer evidence, and build a program that can grow without adding unnecessary work.

© 2023 Big Sky Communications, Inc.
All Rights Reserved.