Best for
- B2B teams that need more G2 reviews or testimonials
- Customer marketing teams building an advocacy engine
- CS teams with happy customers but no structured ask process
Identify happy customers, route them into the right advocacy ask, and generate review, testimonial, reference, and case study outreach.
Create an advocacy nurture system that turns customer satisfaction signals into reviews, testimonials, and reference opportunities.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
6 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Review and advocacy programs fail when every customer gets the same ask at the wrong time. A good system matches the ask to the customer’s relationship, recent success, and comfort level. This workflow creates a safe nurture path from satisfaction signal to review, testimonial, reference, or story.
Expected results
Advocacy paths created
5-8 ask types
The ladder supports different customer comfort levels instead of forcing every customer into a case study or review request.
Review campaign setup
2-3 hours
Segments, templates, approvals, and tracking can be set up quickly using existing customer data.
Relationship safety
CS-approved outreach
Approval gates reduce the risk of asking unhappy or sensitive customers for public advocacy.
Proof captured
Reviews, testimonials, references
The workflow turns customer satisfaction into multiple proof formats, not only G2 reviews.
Step-by-step workflow
The first 3 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
45 min
45 min
Create a simple ladder of advocacy asks: private feedback, G2 review, testimonial, quote approval, reference call, webinar, case study, or advisory board invite. Work in airtable and hubspot and capture the concrete operating details: campaign name, audience, channel, offer, message angle, asset URL, performance baseline, owner, and approval status. Keep the work narrow: complete step 1, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the output is specific enough for the next person to use without guessing what happened; the expected handoff is An advocacy ladder with qualification rules for each ask type.
An advocacy ladder with qualification rules for each ask type.
Do not ask for a case study when a review is the better first step. Advocacy should escalate gradually.
45-60 min
45-60 min
Use HubSpot to create customer segments based on health score, lifecycle stage, renewal status, product usage if available, CS notes, NPS, and recent support sentiment. Work in hubspot and airtable and capture the concrete operating details: campaign name, audience, channel, offer, message angle, asset URL, performance baseline, owner, and approval status. Keep the work narrow: complete step 2, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the output is specific enough for the next person to use without guessing what happened; the expected handoff is A qualified happy-customer segment with exclusion rules.
A qualified happy-customer segment with exclusion rules.
Exclusion rules matter more than inclusion rules. Asking the wrong customer for advocacy can damage the relationship.
45 min
45 min
Use Claude to classify customers into the right advocacy path based on relationship strength and evidence. Work in claude, airtable, and hubspot and capture the concrete operating details: campaign name, audience, channel, offer, message angle, asset URL, performance baseline, owner, and approval status. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the output is specific enough for the next person to use without guessing what happened; the expected handoff is A customer advocacy routing table with recommended asks and senders.
A customer advocacy routing table with recommended asks and senders.
The sender matters. Some asks should come from the CSM, not marketing.
Pro workflow preview
Previewing 3 of 7 steps
Get the remaining 4 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Classify customers into advocacy ask paths.
Customer list:
{{customer_list_with_signals}}
Advocacy ladder:
{{advocacy_ladder}}
Exclusion rules:
{{exclusion_rules}}
For each customer, output:
1. Recommended ask type
2. Why this ask fits
3. Recommended sender
4. Timing
5. Personalization angle
6. Risk notes
7. Approval needed
8. Backup ask if customer declines
Be conservative. Do not recommend public asks for risky accounts.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
Create a customer story pipeline with proof snippets, story angles, and approval status.
Create a customer-ready QBR deck with value recap, adoption risks, success plan, and expansion narrative.
Create an expansion signal engine with account briefs, play recommendations, and approved outreach assets.