Contacts

Champion status

Classifies a contact as champion, detractor, or neutral based on recent communications and behavior

One of 51 free, open-source prompts from Sonora — copy-paste-ready AI prompts for customer success and account management, organized by customer lifecycle stage. Copy this into any AI assistant, or run it on autopilot inside Sonora.

The prompt

Determine whether this contact is a champion, detractor, or neutral based on their recent communications and behavior.

Step 1: Gather data

Collect all recent interactions involving this contact from the last 90 days across contact engagement history and meeting transcripts.

Step 2: Look for champion signals

  • Unprompted praise, positive language, or expressions of ROI (“this saved us X”, “the team loves it”)
  • Proactive internal advocacy — mentions of recommending the product to colleagues, other teams, or external peers
  • Willingness to be a reference, participate in a case study, or speak at an event
  • Drives internal adoption — onboards new users, expands use cases
  • Highly responsive to outreach; attends QBRs or EBRs
  • Constructive, forward-looking feedback (feature requests, roadmap curiosity)

Step 3: Look for detractor signals

  • Repeated complaints, frustration, or expressions of disappointment
  • Escalations or cc’ing executives on support issues
  • Competitor evaluation language (“we’re looking at alternatives”, “evaluating other tools”)
  • Churn or cancellation signals (“thinking about not renewing”, “not sure this is worth it”)
  • Consistent non-responsiveness despite multiple outreach attempts
  • Challenges to value or ROI (“we’re not seeing the value”, “hard to justify the cost”)

Step 4: Classify

  • champion: Active positive advocate. At least two champion signals present with no strong detractor signals.
  • detractor: Expressing dissatisfaction or risk. At least one strong detractor signal, or two or more mild negative signals.
  • neutral: Insufficient data, purely transactional interactions, or mixed signals without a clear tilt.

Return exactly one of: champion, detractor, neutral

Include the key signal that drove the classification in the reason field.

Data sources required

Customer communicationsemail, SlackMeeting transcriptsGong, Granola, Fireflies

The catch

A prompt is only as good as the data you feed it.

Run this well and you'll be stitching together 2 disconnected systems by hand, for one account at a time — and the answer is only ever as fresh as your last copy-paste. Sonora already has the context, live:

  • Customer communications — connected and continuously synced
  • Meeting transcripts — connected and continuously synced

Inside Sonora this prompt runs grounded in your real customer data, on a schedule, across every account at once — and flags what needs you, before you have to ask.