Building on Erica Benton’s answer, I'd send this higher-quality welcome from the head of CS (or product). At that point, the customer mostly wants to know who's accountable for getting them live, and a senior CS or product voice signals exactly that. It also keeps the experience cohesive with the rest of the CS sequence. I'd save the CEO welcome for a high-touch advocacy program. A note from the CEO when a customer joins as an advocate tells them their voice matters at the top of the company. During onboarding, it's one more email in a busy first week. At advocacy enrollment, it's a moment they remember, and a strong start to that relationship.
Worth treating the interview space as a small capture system rather than a series of one-off chats, so decide up front which 2–3 anchor questions map to which later use (a keynote soundbite vs. a fuller customer story), so what you walk away with is reusable, not just "engaging in the moment." For senior leaders on a tight window, framing it as "reflection" rather than "testimonial" tends to lower the guard, and leaving room for one candid follow-up beyond your anchor questions is usually where the best material comes from. On getting people to stop by: an open invitation rarely works as well as pairing the space with something they can get out of it directly — a short highlight reel sent to them afterward, or positioning it somewhere they're already moving through (near registration or the speaker lounge) rather than a separate destination. On release forms — get consent and usage scope agreed before the event, not on the spot. Senior executives are the least likely group to want to pause and sign something live. Scope it broadly up front (internal use, social, sales enablement), so you're not circling back to re-ask for each new use later. Also, best to give them some time to check with their PR and comms department. You don't want them to be a blocker after the event, when all is set and done, wasting all your efforts!
I agree with having tiers as an internal rather than an external matter. Externally-facing ranks create pressure to escalate customers through levels just to keep them engaged. Which is fine if you are creating a kind of competitive community, but I prefer a more collaborative and celebratory one. Internally, tiers work better as a routing signal: "this account is CAB-ready, this one is G2-ready, this one is speaker-ready, etc, each with its own bar, rather than one ladder everyone climbs. If external recognition still matters to advocates, a named badge or public thank-you tied to a specific contribution should be enough.
Something to keep in mind in these cases is that a deck built around top advocates and quotes is easy for leadership to read as if it just happened. What tends to land better is a slide showing the operating model behind those moments, describing how accounts get identified, what makes one advocacy-ready, and how that connects into the pipeline or renewal. That's usually the real question behind 'beyond top advocacy activity': Is this a program, or a handful ad hoc things that just happen? Worth pairing the why/what/how with one slide that's explicitly capture, qualify, activate.
With a handful of early adopters serving multiple asks, the fatigue risk isn't really volume, it's the same customer getting stacked with every format because they said yes once. Two things that hold up well here: cap the number of active asks per customer at a time, and rank ask types by lift for the customer against the pool of collateral you actually need. A quote takes five minutes, a webinar is a real commitment, so match your best-fit customers to the highest-lift asks and spread the lighter ones wider. Also, in my experience, requiring customers to do something in exchange for getting early access or a discount is difficult to enforce. It is good to set expectations, though, so they know you will be asking them to do something and that the ask won't be out of the blue.
Worth splitting the survey into two questions people usually blend into one:
do reps know how and when to ask for a reference (a process question), and
do the references they've received actually help them close (a value question).
Ask only the value question and a mediocre score won't tell you whether the process is broken or the outcome is. The other thing that determines whether round two gets a response: close the loop. Share back what changed as a result of this round before you run it again. Something else that worked very well on a very large program I ran where I had to manage multiple reference managers reporting to me, was adding a satisfaction survey when you fulfilled a request. As part of the reference process, the last email would be a survey asking the sales rep about how it went. Then, at the end of every month, I would review all responses and, if any issues were flagged or a low score was noted, I would contact the salesperson and address them directly.
Hi Emily, so cool you got Gong approved and going, It's a FANTASTIC tool for any customer marketer. To make the most of it, the key is whether capture, validation, and activation are three connected steps or three disconnected owners. Gong will solve the capture. Someone still has to review what surfaced, decide whether the account is actually reference-ready, and route it to the right ask before the moment goes cold. So while you start playing with Gong's features, I would also define "reference-ready" as a short checklist by advocacy activity type, because a good G2 candidate and a good speaker candidate need different validation criteria and next steps. Also consider putting a shelf life on flagged accounts (two weeks or so) so stale signals don't just accumulate.
