A customer advocacy manager is not simply the person who chases a testimonial before the quarter closes. At their best, they help a company recognize the customers with a real story to tell, make a thoughtful invitation, and use that contribution in a way that helps both the customer and the next person deciding what to do.
That makes this a relationship role as much as a marketing role. A strong manager sees the difference between a customer who had a good experience and one who is ready to put their reputation behind a recommendation. They know when a reference request is a good fit, when a customer story needs more context, and when the most respectful answer is not yet.
The job description below gives teams a practical starting point for hiring or defining the role. It is designed for an organization that wants customer proof to feel useful and credible, not extracted.
What the role is there to accomplish
The core job is to create a dependable path from a meaningful customer outcome to a contribution that can help someone else. That might be a peer reference for an active buyer, an honest review, a customer story, a speaker for an event, feedback for a product team, or a conversation in a community. The form changes. The standard does not: the customer needs to understand the request, have room to decline, and see why their time matters.
A useful role description begins with customer value, not an inventory of content assets. The manager should build an advocacy experience that recognizes expertise, creates appropriate opportunities, and closes the loop when a customer helps. That is what makes voluntary participation sustainable.
The role can support growth, but it should never treat growth as a license to exhaust the same generous customers. A well-run program earns better proof because people feel respected enough to keep saying yes when the right opportunity comes along.
Customer advocacy manager responsibilities
The daily work should connect relationship care with practical coordination. Current roles in the field commonly combine customer relationships, reference operations, story development, and cross-functional planning. The exact mix depends on the business, but a clear job description usually includes these responsibilities:
- Identify customers who have achieved a real outcome and may be open to sharing their perspective.
- Maintain a clear record of customer interests, permissions, past participation, and boundaries.
- Match customers to appropriate opportunities, including references, stories, reviews, events, peer conversations, and product feedback.
- Coordinate requests with sales, customer success, marketing, product, and event teams so customers do not receive duplicate or conflicting asks.
- Interview customers with enough curiosity to find the detail that makes a story useful rather than generic.
- Prepare customers for participation, communicate what will happen next, and make follow-through visible.
- Review participation health and business impact, then improve the program without sacrificing customer trust.
The manager does not need to personally write every case study, host every event, or own every account relationship. They do need to be the person who can make those efforts cohere. Without that ownership, an advocate can easily become a name passed around in a spreadsheet while no one is accountable for the experience.
The scope is broad by design, but it should be grounded in real customer participation rather than an abstract idea of engagement. For example, a current customer advocacy role from Blackbaudbrings together community, champion programs, customer stories, peer connections, and product input. That is a useful reminder that the manager’s work can create a coherent experience across many formats, rather than treating each one as a separate campaign.
Build a customer story pipeline, not a request queue
A weak program starts with a backlog of internal requests. A sales team needs a reference. Marketing needs a quote. Events need a speaker. Each request may be reasonable on its own, but the customer experiences them as one company. The manager’s job is to see the full relationship before another invitation goes out.
A better system begins with customer context. What outcome did this person achieve? What part of the story are they comfortable discussing? Who knows the relationship best? Have they helped recently? What would make the opportunity worthwhile to them? These details make it possible to match a specific advocate to a specific need instead of sending a broad plea to whoever seems enthusiastic.
This is why the role needs judgment, not just organization. A customer who would make an excellent private reference may not want a public case study. A customer who enjoys speaking may not have the right experience for a technical buyer conversation. The customer reference program guideexplains how careful matching protects both the buyer and the advocate.
Skills to look for when hiring
The strongest candidate is usually part relationship builder, part storyteller, and part operator. They should be able to have a real conversation with a customer, translate the useful parts of that conversation for internal teams, and keep a promise once the customer agrees to participate.
Look for listening before persuasion. Advocacy managers need to hear when a customer is proud, when they are cautious, and when the language in a request feels too polished to be true. Good interviewing and writing matter because a customer story is only useful if it preserves the customer’s actual experience. Project management matters because the role often coordinates many small commitments across several teams.
Cross-functional credibility is equally important. The manager should be comfortable telling a sales leader that a customer is not available, helping product marketing understand what proof a buyer needs, and partnering with customer success without taking over the relationship. A candidate who can do this with tact will protect more future value than one who merely promises a higher volume of advocacy activity.
Where the role should work with other teams
Customer advocacy lives between teams, so no single department can make it work alone. Customer success can recognize when an outcome is real. Sales can explain the question a buyer needs answered. Marketing can turn a useful experience into a story without sanding off its texture. Product can learn from recurring friction and from the outcomes people genuinely value.
The advocacy manager should give these teams a shared way to request, prioritize, and learn. That might be a simple weekly review for a small program or a clearer intake and permission process for a larger one. The important part is that every request has a purpose, an owner, and a relationship check before it reaches a customer.
This coordination is a reason the role often belongs in customer marketing, marketing, or customer success. The reporting line matters less than access and authority. If the manager has no view of customer context, or cannot pause an inappropriate request, the title will not solve the underlying problem.
What not to load into the role
Customer advocacy is often placed in a job description alongside every customer-facing marketing responsibility: lifecycle campaigns, a full community calendar, social channels, field events, partner marketing, content production, customer education, and executive programs. That can make the role sound ambitious. It also makes it very easy for the relationship work to lose to the next deadline.
Keep the first version focused. If the business needs stronger sales references, start there. If it needs a repeatable customer-story practice, make that the first program. If it needs a community, give community its own clear charter. A manager can connect these paths over time, but asking one person to launch all of them at once usually produces a lot of outreach and very little trust.
There is also a line between inviting participation and pressuring it. A customer advocacy manager should never be evaluated on positive reviews alone or asked to make an incentive contingent on praise. TheFederal Trade Commission’s guidance on reviews and testimonialsis clear that incentives cannot be conditioned on a particular sentiment. More importantly, a program built on pressure is poor proof even when it technically produces a higher number.
Measures that keep the role honest
Count activity, but do not confuse it with value. It is useful to know how many reference requests were fulfilled, how many customer stories were completed, how often advocates participate, and how long requests take to resolve. Those numbers help the manager run the work.
The more important measures ask whether the work helped. Did a buyer get a more relevant answer? Did a story clarify the value of the business? Did a referral introduce someone who was truly a fit? Did the customer feel respected and remain willing to help again? The brand advocacy measurement guideoffers a wider scorecard for tying these signals to real behavior.
Participation health deserves a place beside pipeline or content measures. Watch for the same names being asked repeatedly, a rising number of declined invitations, or advocates who disappear after a single request. Those are not merely operational annoyances. They are signs that a relationship may be carrying more than its fair share.
A job description teams can adapt
A practical description can be short: “Own and grow a customer advocacy program that helps customers share their experience through relevant references, stories, reviews, events, and feedback. Build trusted relationships, maintain clear permissions and participation history, coordinate requests across teams, and measure customer and business value without compromising the experience.”
Add the context that makes the role real in your organization. Name the primary advocacy formats, the teams it will partner with, the customer groups it will serve, and the first meaningful outcomes. Do not make the job description a wish list for every customer-marketing, community, content, event, and operations function. Focus gives the person a chance to build trust before the program asks them to scale it.
A practical first 90 days
In the first month, the manager should listen. Meet the people closest to customers, review recent reference and story requests, and find out where requests become messy. Build a small picture of the customer moments already creating belief. This is not the month to launch a large advocate campaign.
In the second month, choose one operating improvement. It might be a cleaner reference intake, a simple permission record, a better customer interview brief, or a way for account teams to flag a meaningful outcome. Test it with a small group and listen closely to how both customers and internal teams experience the process.
In the third month, share what the early work revealed. Name the types of contribution customers actually welcome, the parts of the journey that make an ask feel timely, and the requests that need clearer rules. Then set a modest next goal. A durable program grows from evidence of respect, not from a launch deck promising that every customer will become a spokesperson.
How Chris helps make advocacy worth sharing
A customer advocacy manager can coordinate the opportunity, but the underlying story still has to be worth carrying. Chris helps teams find that clarity through brand consulting, hands-on workshops, and creative work that gives people something distinct to talk about. The goal is not to script customers. It is to give them a real experience and a sharper way to explain why it mattered.
Frequently asked questions
What does a customer advocacy manager do?
A customer advocacy manager builds trusted relationships with customers and creates useful ways for them to share their experience. The role often coordinates references, reviews, customer stories, speaking opportunities, advisory groups, and feedback, while protecting customers from poorly timed or repetitive requests.
Where should a customer advocacy manager sit in an organization?
The role commonly sits in customer marketing, marketing, or customer success, but it needs active partnerships across those teams as well as sales and product. The right home is the one that gives the manager access to customer context and enough authority to protect the experience when a request is not appropriate.
What should a customer advocacy manager measure?
Measure whether advocates are being treated well and whether their contribution helps. Useful measures include fulfilled reference requests, story quality, qualified referrals, participation health, repeat willingness, and the influence of advocacy on a meaningful buyer or customer outcome. A large activity count alone is not enough.
Does a small company need a customer advocacy manager?
Not always. A small company may begin with a shared owner who has strong customer judgment and a simple process. A dedicated role becomes more valuable when references, stories, reviews, and requests are growing, or when several teams need a dependable way to coordinate customer participation.
