Skip to main content
Intempt

Ask for advocacy at the moment a customer is actually happiest

A generic 'leave us a review' ask misses the specific moment a customer is genuinely pleased - first value achieved, a renewal just closed, a milestone hit. This detects that moment and matches the ask to it.

Marketjourney-builderB2BSaaSAdvanced6 steps6 outputs
1
2
3
4
+2 more
Attribute Segment Content Asset Recommendation Journey Dashboard
Run this recipe

What it does

Detects natural advocacy moments via an AI attribute - first value achieved, expansion completed, renewal closed, a high-engagement streak, a customer milestone - and fires a contextual advocacy ask matched to the moment: review, referral, case study, or speaker opportunity.

You get

an advocacy ask timed to the customer's actual happiest moment

How it works

1

Build Advocacy-Moment AI Attribute

create_ai_attribute

Create an AI-derived attribute 'active_advocacy_moment' on the User/Account object. Detects natural advocacy windows (when goodwill is highest). Inputs: (a) first-value-achieved events (key activation milestone), (b) expansion-completed events (account just upgraded), (c) renewal-closed events (just renewed for another term), (d) high-engagement-streak (consecutive weeks of strong activity), (e) customer-success-milestone (reached usage benchmark, completed initial use case), (f) explicit positive support sentiment, (g) NOT during friction or churn-risk. Output: object with moment_type, moment_strength (high/medium), recommended_ask (review / referral / case-study / speaker-opportunity / roadmap-feedback), and ask_recipient_role (champion / economic-buyer / power-user).

Produces:Attribute
2

Identify Advocacy-Ready Users

Create Segment

Build a segment 'Advocacy-ready' capturing users where active_advocacy_moment is high-strength in the last 7 days AND the user hasn't been asked for an advocacy action in the last 90 days (avoid donor fatigue) AND there's no active friction/churn signal (the timing is genuinely good, not just numerically positive). Partitioned by recommended_ask so the journey routes accordingly.

Produces:Segment
3

Build Per-Ask Content Variants

Generate Content

Generate advocacy-ask email variants per recommended_ask. Review ask: 'You just [hit milestone] — would you share your experience publicly? Takes 3 minutes.' Includes one-click links to G2, Capterra, or the relevant review site, pre-filled where the platform allows. Referral ask: 'You're [in top X% of users / just expanded / just renewed] — know anyone who'd benefit from [Product]? Here's your referral code for [reward].' Case-study ask: 'Your team's [specific achievement] is a great story — would you be willing to share it as a customer case study? Our marketing team will do all the writing.' Speaker-opportunity ask: 'We have a [conference / webinar] coming up — would you be interested in speaking?' Roadmap-feedback ask: 'You're using [Product] in such interesting ways — can we get 20 minutes for product roadmap feedback?' Tone: peer-respectful, never transactional. Send-from: named CSM or success lead, never marketing@.

Produces:Content Asset
4

Build Advocacy Recommendation Surface

create_recommendation

Configure a recommendation surface 'Advocacy opportunities' that activates for advocacy-ready users in the in-app dashboard. Shows the user 2-3 advocacy actions they could take, each with a clear effort estimate ('3 min', '15 min', '1 hour') and what the user gets in return (recognition, referral reward, speaking visibility). Soft-surface — discoverable not interruptive. Lets the user volunteer rather than only being asked.

Produces:Recommendation
5

Build Advocacy Journey

Create Journey

Build a journey wired to advocacy-ready segment. Touch 1 (Day 1 after moment detected): advocacy-ask email matched to recommended_ask. Touch 2 (Day 0 of touch 1): activate recommendation surface in-app. Touch 3 (Day 7, ONLY if user engaged with touch 1 OR rec-surface): light follow-up with concrete next step ('You said you'd love to refer someone — here's the link to send them'). Branch: if user submits an advocacy action (review left / referral submitted / case-study agreed / etc), tag the user as 'active advocate' for cross-team awareness AND ensure they're prioritized for future advocacy opportunities. Exit on: action completed (success — log advocacy_event), explicit decline (respect), or 14-day timeout. No badgering.

Produces:Journey
6

Build Advocacy Program Dashboard

Build Dashboard

Compose an advocacy program dashboard: advocacy-moment detection volume per week, ask-to-action conversion rate by ask type (which advocacy asks actually convert — referrals usually beat reviews in volume but reviews beat referrals in long-term value), top advocates (users who have completed 3+ advocacy actions — this is the inner-circle list to nurture specially), and downstream attribution (reviews influencing G2 score, referrals creating new pipeline, case studies appearing in sales decks). Reframes CS work from 'retention cost-center' to 'pipeline contributor'.

Produces:Dashboard

Ready to run this recipe?

Tell Blu what you need. It builds the segment, content, journey, and dashboard in minutes.

Sign up free

Hire the team that reclaims what your GTM stack is leaking.

You set the strategy. Agents run the plays. Seven AI agents across design, marketing, sales, and analytics. One customer context, tracked from first pixel to final dollar.

Start for free
Milestone-Driven Advocacy Asks | Intempt