Function: Customer marketing

AI Workflow for Customer Advocate Identification

Deployment Brief

Start with an advocate candidate list that includes signal, proof, ask type, owner, permission status, and next action.

Related Field Report

AI customer health scoring workflow: A field report on customer risk, retention signals, owner review, and measurable follow-up.

Quick Answer

An AI workflow for customer advocate identification finds customers with advocacy signals such as positive feedback, strong outcomes, referrals, reviews, renewal, or support praise. It separates possible referral, testimonial, case study, review, reference, and private-feedback asks. The account owner reviews permission, timing, ask type, incentive, and relationship-sensitive cases.

TL;DR

Advocacy should start with fit and permission. A happy customer is not automatically a public reference.

What is customer advocate identification?

Customer advocate identification is the process of finding customers who may be appropriate for referrals, testimonials, case studies, reviews, references, or private feedback.

Who is this workflow for?

Service businesses, SaaS firms, agencies, consultants, and professional firms that need proof and referrals without over-asking customers.
Marketing and account teams that want to turn happy moments into the right type of ask.
Owners who need advocacy without damaging customer trust.

What breaks in the manual process?

The manual process fails when positive feedback is forgotten or mishandled. Teams either never ask, or they ask for the wrong thing at the wrong time.

How does the AI-enabled process work?

The workflow reviews feedback, outcomes, renewals, support history, referrals, reviews, and permission status. It suggests the appropriate advocacy ask and routes it to the account owner.

What does this look like in practice?

Example scenario: A client praises a completed project and renews for another quarter. The workflow flags them as a possible case study candidate, checks for unresolved issues, and asks the account owner whether a private referral ask or public testimonial is more appropriate.

What decision rules should govern this workflow?

Do not treat private praise as public permission.
Match the ask type to the customer's relationship and proof level.
Hold back when unresolved issues exist.
Route sensitive or high-value accounts to the owner.
Record permission for public use before publishing anything.

What are the implementation steps?

1. Trigger: A customer gives positive feedback, renews, achieves a clear result, submits a referral, leaves a good review, or becomes a strong reference candidate. 2. Inputs collected: positive feedback, customer outcome evidence, renewal or expansion status, support or service history, referral activity, public review or testimonial history, permission status, account owner review rules. 3. AI/system action: The system checks source evidence, prepares the referral output, and flags attribution, timing, eligibility, reward, permission, or relationship review requirements. 4. Human review point: The account owner approves advocate status, ask type, timing, incentive, public-use permission, sensitive relationship context, and customer-facing language. 5. Output delivered: advocate candidate list, advocacy signal summary, recommended ask type, permission and sensitivity flag, owner task, measurement event for advocacy participation. 6. Measurement logged: Track candidates identified, asks approved, participation, permissions granted, references used, referrals generated, testimonials collected, and ask deferrals.

Required inputs

positive feedback
customer outcome evidence
renewal or expansion status
support or service history
referral activity
public review or testimonial history
permission status
account owner review rules

Expected outputs

advocate candidate list
advocacy signal summary
recommended ask type
permission and sensitivity flag
owner task
measurement event for advocacy participation

Human review point

The account owner approves advocate status, ask type, timing, incentive, public-use permission, sensitive relationship context, and customer-facing language.

Risks and stop rules

customer asked for public advocacy too soon
private praise treated as public permission
wrong ask type for the relationship
advocacy request made while issues remain unresolved

Stop the workflow when attribution is disputed, consent is unclear, the ask is poorly timed, the customer has unresolved issues, a reward or commission is involved, or public advocacy permission has not been approved.

Best first version

Create an advocate candidate list with signal, proof, ask type, owner, permission status, and next action.

Advanced version

The advanced version maps advocates by industry, use case, persona, proof type, public-use permission, reference availability, and referral quality.

Related workflows

Measurement plan

Track candidates identified, asks approved, participation, permissions granted, references used, referrals generated, testimonials collected, and ask deferrals.

What not to automate

Do not automate public testimonial requests, case study asks, reference requests, or permission assumptions without account owner review.

FAQ

What is customer advocate identification?

It is the process of finding customers who may be appropriate for referrals, testimonials, case studies, reviews, references, or private feedback.

What can AI detect?

AI can detect positive feedback, outcomes, renewals, referrals, reviews, support praise, and permission status.

What should stay under human review?

Ask type, timing, permission, incentive, public use, sensitive accounts, and customer-facing language should stay under account owner review.

What is the simplest first version?

Create an advocate candidate list with signal, proof, ask type, owner, permission status, and next action.

How should this workflow be measured?

Measure candidates, approved asks, participation, permissions, references, referrals, testimonials, and deferrals.