
User feedback is essential to continuous improvement. For marketers, it can be from community interactions, NPS surveys or other forms of customer satisfaction surveys, the customer success team and advisory boards. Turns out, the same channels apply for customer marketing managers seeking stakeholder feedback from sales, marketing, customer success, PR, digital, RFP & Proposals, social media and so on.
In this blog, we share what we’ve learned about leveraging surveys to gain insights that help inform your program decisions related to your advocate database and the output of that database: customer content. If you don’t have the right advocates you’re nothing more than a collector of happy customers. If you produce customer content (videos, case studies, etc.) that isn’t relevant then it just won’t get used and you’ll have wasted a good deal of your limited time and budget in the process.
How many and what questions to ask are, together, what will guarantee a good result. Remember, you’re asking people to spend their time on your survey, which they will do if they understand it will benefit them. You could probably ask 100 questions if you’re the curious type. But you only have so much of their attention span and time. So make your wish list of the things you want to know, then prioritize that list to 10-15 questions. More than that, and people tend to bail out. You’ll want to pretend you’ve been asked to take the survey and time it out. If you can promise a 10-minute experience in your survey promotion and invitation, completions will be much higher.
Every participant should be able to answer every question without getting stuck: “None of these answers quite fit my situation; now what do I do?” This can easily be avoided with an “Other” choice when it comes to multiple choice questions. For reporting, you want to minimize this, keeping the responses limited to specific answers; but not at the risk of the participant getting stuck.
When you include “on average” or “typically” or “annually” or “in the last quarter,” you provide important direction. Be as specific as possible so answering and making sense of the results is easy. We’ve seen program managers ask questions like, “What type of content do you find most valuable?” If the first reaction is “It depends,” you’ll gain limited value from asking it. Some people will answer as if you mean “to close the deal,” and some will think you mean “to open the door,” for example. Another potential can of worms is something like, “Did you find what you need in our advocate database?” If the answer is yes, then you can probably make some deductions based on the stakeholder’s role. If a seller is focused on Fortune 1,000 health insurance providers, then you know the database has ample Fortune 1,000 health insurance advocates.
What if the answer is no? Think about the possibilities.
The list could go on and on. So, choose your questions carefully to gain actionable feedback versus simply causing even more guesswork from the answers. Branching questions can help get to the important stuff, as can providing a text field for more detail. But in every case ask yourself if your design decisions will get useful information.
An anonymous survey may yield more honest answers, particularly if a stakeholder has some dissatisfaction to vent. Unfortunately, if they do, you won’t be able to gain additional detail or confirm you’ve solved their grievance after making changes. Our belief is that if you have a reasonably good relationship with your stakeholders, then they’ll know they can be frank, and you’ll take it the right way.
You want a statistically significant number of responses. If you send a survey out to 250 people and get eight responses, that’s not helpful. That small number of results may be highly skewed. If you race off to make changes and later learn that 200 other people felt differently about something than those eight, you’ll have squandered your time and still not made things better. What you’ll want to do in advance is get some management support, especially from those people who manage the participants on your list. It needs to be clearly communicated that these surveys are infrequent, but important; that the purpose is to make the program better, not to make busy work. There will be follow-up on what actions were taken as a result. Someone will be monitoring the uptake rate. Lastly, they will know when to expect the survey and when their submissions are due.
You know how frequently you’re asked for your thoughts, but then you have no idea where those thoughts went, if they were used, or if they resulted in changes? It sucks, right? The less you care about the thing you’re being asked to take a survey for, the less likely you are to even start that survey. Do I care to provide my feedback on a recent purchase of printer paper at Office Depot? Nope. But if my job performance hinges on leveraging customer advocates and someone is offering to make that part of my job easier, I care. The trick is to make it clear their feedback does matter, the program is adapting, and that future feedback requests will have the same positive effect on their work lives. So, formalize the outcome of the survey results. Share them in team meetings or a newsletter or whatever makes the most sense in your environment.
We would be remiss if we didn’t make the case for another awesome source of continuous feedback and that’s a stakeholder advisory board for your program. Every high performing customer marketing program has one.
Harnessing the power of well-constructed surveys can transform your customer advocacy and content strategies. By asking the right questions, prioritizing stakeholder insights, and ensuring a manageable survey experience, you can unlock valuable data that guides your decision-making. Remember, the goal is not just to collect feedback but to act on it effectively—making each advocate’s contribution meaningful and each piece of content impactful. As you refine your approach, keep the feedback loop active, transparent, and integrated into your ongoing strategy. Your advocates are more than just voices; they are pivotal partners in your journey towards more targeted and successful marketing endeavors.
It's only natural that many advocacy leaders have landed on the same objective: make the program easier to use by meeting users where they're already working.
Today, that increasingly means Microsoft Copilot, ChatGPT, Claude, Gemini or whatever generative AI assistant employees happen to have open.
Imagine a salesperson simply asking AI, "Find me three German healthcare customers using product Y, willing to speak with a prospect," instead of navigating to another interface, or waiting for someone from advocacy, or elsewhere, to respond. It's easy to see the appeal. Removing friction has always been one of the fastest ways to increase adoption.
It is exactly the right instinct.
The difficult parts, arguably the reason program managers exist, occur before and after AI says, "Here are your three best matches."
The value advocacy professionals bring is the ability to operationalize and scale customer advocacy for maximum impact. Quality advocate information doesn't just appear, it's the result of a system.
Now that the user has three advocates, what should happen?
Notice what happened. The search was completed.
The next steps are just as manual as ever if AI search is the be all, end all.
Reality Check
AI can tell you who could participate. It can't tell you who should participate unless someone (or something) has been keeping score.
This is where the story starts to feel strangely familiar.
Many companies still operate their program using spreadsheets, scattered CRM fields, shared drives, email folders, and the remarkable memories of a handful of program managers.
Eventually, organizations realize they aren't managing an advocacy program at all. They're managing lists that happen to contain advocates.
But the shortcomings are real:
Purpose-built advocacy platforms emerged because advocacy is much more than a search problem.
Ironically, AI has convinced some organizations to revisit the same shortcut they worked so hard to escape.
Let's imagine two different worlds.
In the first, AI recommends an advocate for a sales call.
Months later, AI knows this customer recently participated and may deserve a break before being asked again.
Now imagine the second world.
Three months later someone asks how many customer reference contributed to the revenue this quarter.
Silence. Nobody really knows.
The advocacy happened...hopefully. The program didn't. Collectively, the organization slowly stopped feeding the very system it depended on to understand its advocacy program.
Reality Check
If AI helps facilitate twenty closed-won opportunities this quarter, but none are recorded, your executive dashboard still says zero.
One of the easiest mistakes to make in an AI-first world is assuming that successful interactions somehow become organizational knowledge on their own.
They don't.
If a customer agrees to speak with a prospect and nobody records it, the organization loses far more than a single activity.
The most valuable advocacy data isn't simply who your customers are.
It's everything they've done.
That's the story AI actually wants to read.
It's often said that AI needs good data.
That's true.
But operational history is far more valuable than static customer information.
Those aren't search results.Those are patterns.
Remove any one of those pieces and AI becomes little more than an exceptionally fast search engine.
Reality Check
Every workflow skipped today is a pattern AI won't discover tomorrow.
The AI revolution has created tremendous excitement, and rightly so. Finding the right advocate is becoming dramatically easier than it was only a few years ago.
That's worth celebrating.
Just don't confuse a better search experience with a better advocacy program. Search is only one chapter in the story.
The organizations that see the greatest return from AI won't necessarily be the ones with the most sophisticated models.
They'll be the ones with the richest operational history.
Those organizations won't use AI merely to answer the question, "Who should we ask?"
They'll use AI to answer far more valuable questions.
That's when AI stops behaving like a better Google search.
That's when it starts behaving like a strategic partner.
Finding the right advocate has always been the opening scene.
If your AI can find advocates but your program can't learn from using them, you've built a remarkable search engine instead of a remarkable advocacy program.