Resourcesicon
Scale Customer References with Group Events and Forums
Collage of pictures of people on cpmputer screen illustrating one-to-many reference activities.

Scale Customer References with Group Events and Forums

Are you taking advantage of one-to-many reference activities? One-to-one reference calls are the standard approach for connecting a buyer and a customer reference. They are more labor-intensive to arrange but offer the most personalized sharing of information between two parties. The high-touch reference approach generally works pretty well until demand exceeds supply, such as at the end of a quarter or year. Some companies will connect only deals meeting a certain revenue threshold with reference customers. Buyers who don’t meet that threshold may not kindly take the “You’re too small to warrant a reference call” implication, which isn’t a great way to begin a relationship. Fortunately, a few options are available to meet high demand periods yet still retain a one-to-one call’s dynamic, interactive quality:

  1. Limited group events
  2. Reference Forums
Limited Group Events

The idea behind a limited group event is to have 2-4 prospects join a call with a single customer reference where all attendees take turns asking questions. This is the simplest form of one-to-many customer reference activities, and can be set up easily. A side benefit of these calls is that one prospect may pose a different set of questions than the other prospects. One could make the argument that it’s a more thorough due diligence opportunity. Of course, some questions may not be pertinent to other prospects, so that’s a potential downside. Nevertheless, during spikes in reference demand, group calls may offer the only feasible way to accommodate all prospects in the reference-check stage of the sales cycle.

Limited Group Events may have representation by the vendor, but more often than not are un-chaperoned.

It’s always important to track revenue influenced to any sales-related reference activities. In the case ofone-to-many activities the customer’s influence applies to each attending prospect opportunity. The reward for the customer may be higher given this additional influence, but generally is rewarded for a single activity. The same applies to Reference Forum customers.

Reference Forums

Reference Forums are reference calls at scale. In the early days of Point of Reference, we used to plan, facilitate, record, and host edited recordings of Reference Forums as our one-to-many reference activity. Some had as many as 70 prospects in attendance. That sounds unwieldy for Q&A, but typically only 10-20% of attendees asked questions. The rest were simply happy to listen. Reference Forums were more planning- and labor-intensive but worked quite well to satisfy the due diligence requirements of prospect companies.

Here are some key considerations in offering Forums:

  • Participating in a forum is a different ask of a customer reference, so your contact needs to be comfortable with being on-stage with a larger audience.
  • The customer needs to provide a brief bio, picture, and customer relationship backstory for promotional purposes.
  • Once a date and time are selected, promote the event to the sales team.
  • Give the sales team guidelines on what type of prospect is appropriate to invite. For instance, existing customers are not appropriate because they will likely ask different “how to” type questions
  • Providing a registration method is essential so that you know who is registering. – This is important if competitors of the customer company register. The customer must approve these attendees.
  • Have a list of “seed” questions to fill in if there is a lapse in attendee questions during the call. Share the seed and other likely questions with the customer, so they’re well-prepared with any facts and figures.
  • The event requires someone to manage the call and question queue and someone else to act as host or master of ceremonies– The call manager manages the question queue, and unmutes accordingly
    – The MC kicks off the call with a brief introduction, key customer facts, and asks a few starter questions.
    – The MC also asks the “seed” questions should audience questions trail off.
    – If any questions are inappropriate (e.g., pricing), the MC can jump in and table those.
  • It’s also a good idea to have a solution expert from your company on the call should any questions stump the customer, or should an incorrect answer be given related to the solution.
  • To maximize the value of these calls, record them. If a prospect couldn’t make a call, but can listen to the recording the day after, that works nearly as well.
  • To maximize the value of these calls, record them. If a prospect couldn’t make a call, but can listen to the recording the day after, that works nearly as well. It’s very important to disclose that the call is being recorded at the start of the session.
  • Part of the service we offered was listening to the full recording then parsing out questions related to a specific subject (e.g., reporting, customer service, results, etc.). Grouping these segments together so a future listener could go just to the areas of interest was a real convenience.
  • There is also value in having the recording transcribed. Maybe a prospect would prefer to read the interview vs. listen. Perhaps the call contained quotes from the customer that could be “gold” for other purposes.

Feedback from attendees of one-to-many reference events is typically quite positive. The brain trust of the attendees leads to questions from a host of different perspectives. Comments such as “I wouldn’t have thought to ask some of those questions” are not unusual.

While we view group events as another “tool” in a program’s “toolbox,” we have worked with at least one company that has made group events the primary option for reference conversations. They gained commitment from customers to do monthly or quarterly calls, the dates scheduled in advance throughout the year. The schedule is published for sales, so they always knew what type of customer was available and when. It took a very particular type of program manager/team to go all-in on this model. But it worked for them.

However you choose to leverage these one-to-many reference options, they ensure you never have to “turn off the tap” on reference activities when demand exceeds conventional one-to-one reference calls.

Check out some of our own customer success stories on the Our Advocates page!

It Started With a Legitimate Aspiration

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.

What's Next?

Now that the user has three advocates, what should happen?

  • Should they email the customer directly?
  • Should they contact the Customer Success Manager first?
  • The account executive for one of the accounts was about to make a request. Was that considered?
  • Has anyone noticed that this customer has already participated in three activities in the last 60 days?
  • Are they currently navigating a difficult support issue?
  • Did they recently decline another invitation?
  • Would someone else actually be a better choice?

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.

Haven't We Seen This Movie Before?

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:

  • A spreadsheet might tell you that Sarah from ABC Company has spoken at a conference. It couldn't tell you that she'd spoken three times already this quarter.
  • Custom CRM fields could tell you a customer was referenceable. They alone couldn't coordinate approvals, notify relationship owners, recognize participation, measure outcomes, or attribute revenue.

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.

When Search Replaces Process

Let's imagine two different worlds.

In the first, AI recommends an advocate for a sales call.

  1. A request is automatically created.
  2. The Customer Success Manager approves participation.
  3. The customer receives preparation materials.
  4. The call takes place.
  5. The activity is recorded.
  6. Recognition is issued.
  7. The opportunity is linked to the advocacy activity.
  8. If the deal closes, revenue attribution updates automatically.
  9. Executive dashboards reflect the contribution.

Months later, AI knows this customer recently participated and may deserve a break before being asked again.

Now imagine the second world.

  1. AI recommends the same advocate.
  2. The salesperson sends an email.
  3. The customer agrees.
  4. The meeting happens.
  5. Everyone moves on.

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.

Invisible Work Stays Invisible

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.

  • It loses context, attribution, and recognition.
  • It loses another piece of history that could have helped improve the next decision.

The most valuable advocacy data isn't simply who your customers are.

It's everything they've done.

  • Every request, acceptance/decline, event presentation, analyst interview, product beta, reference call, press interview, reward, closed-won opportunity revenue influenced by their participation.

That's the story AI actually wants to read.

AI Needs Memory, Not Just Data

It's often said that AI needs good data.

That's true.

But operational history is far more valuable than static customer information.

  • Advocate profiles answer questions about who someone is.
  • Operational history answers questions about what consistently works.
  • That's where AI begins uncovering insights that no spreadsheet could ever reveal.
  • Perhaps healthcare advocates participate twice as often as financial services advocates.
  • Perhaps customers who join advisory boards are twice as likely to become conference speakers.
  • Maybe advocates who receive recognition within a week participate significantly more often than those who don't.

Those aren't search results.Those are patterns.

  • Patterns emerge from history.
  • History emerges from process.
  • Process emerges from systems.

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.

Don't Stop at "Who?"

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.

  • Every request becomes institutional memory.
  • Every activity measured.
  • Every contribution attributable.
  • Every outcome becomes another lesson AI can learn from.

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.

  • "Where are we running short of advocates?"
  • "When is the most effective time to use advocates?"
  • "What types of advocacy generate the greatest business impact?"
  • "What patterns have we been missing?"

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.