Skip to main content

Decide who is happy before anyone is asked

Build Smart Lists of Happy Customers

Every team says it only asks happy customers. Few have written down what happy means, who decides, or what takes someone off the list again. Contacts and smart lists are on every plan. This page is the team process that keeps one list honest: agreed signals, a tag that marks them, clear exclusions and a weekly look before anyone is asked.

  • Signals the whole team agrees on
  • A tag that feeds the list
  • Exclusions that take people off again

The problem, solved

Why happy lists drift, and how to hold them

  • Everyone in the CRM gets asked

    Without a list of its own, the request goes to churned accounts and unhappy ones alike.

  • Nobody agrees who counts as happy

    Sales thinks one thing, support another, and the list reflects whoever added the last name.

  • Someone complained after they joined

    A customer was happy in March and furious in May, and the list never noticed.

  • The same people are asked again

    Your happiest customers are exactly the ones most likely to be over asked.

  • Anyone can edit the list

    A new hire adds a whole import by mistake.

Flip the switch to see how StoryProof handles each one.

Happy list rules

Write the rules for your happy customer list

Work through it in one team meeting. Copy the summary into your team notes so the rules outlive the meeting.

Signals that put someone on
Exclusions that take someone off
How it is marked
Weekly review

Ticks stay in this browser tab. Nothing is saved or sent.

In StoryProof

Setting up the list with your team

  • You will need
  • A contact list in StoryProof
  • Access to your support and billing tools
  • Half an hour with the people who talk to customers
  1. 1

    Agree the signals and exclusions

    Use the checklist with support, sales and success in the room, and write the result down.

  2. 2

    Create the tag and the smart list

    Add one contact tag for happy customers and a smart list built on it.

  3. 3

    Restrict who can edit it

    Give list editing to the list owner and the few people who add customers.

  4. 4

    Automate the removals you can

    From Pro, have a low rating remove the tag and the list, and let request emails skip anyone recently asked.

  5. 5

    Connect the request

    When the list is trustworthy, joining it can start a request automation.

What happens next: Revisit the signals each quarter. If customers who joined the list rarely respond, the definition of happy is too loose.

Before you start

What a smart list cannot know

  • Filter fields are not listed here

    This page does not claim which contact details a smart list can filter on. Check in the app; a tag is the safe common ground.

  • Your other tools stay separate

    Support tickets and refunds live in other systems. Someone has to bring those signals in, by hand or with your own integration.

  • Happy today is not happy forever

    A list is a snapshot of your judgement. The weekly review is what keeps it true.

  • Automation is plan dependent

    Tag and list actions, low rating alerts and skip rules need Pro or above.

FAQ

Questions people ask

Short answers to what usually comes up next.

Is asking only happy customers a problem?

Choosing who to ask is normal. What matters is that you do not hide or filter out the honest answers you get back.

Should a survey score be the only signal?

It works well alongside one behaviour signal, such as a renewal. A single score can be given on a good day and mean little.

Who should own the list?

Whoever is closest to customer health, often customer success. One owner, so removals are not left to chance.

How is this different from the list trigger?

The trigger decides what happens when someone joins a list. This page decides who should be on the list in the first place.

Still have a question? Ask the StoryProof team or book a demo.

Ask the customers your team can vouch for

Contacts and smart lists on every plan, with automations to keep the list current.

Sources

  1. Automations: contact triggers and actions, StoryProof. Checked 2026-11-19.

Last updated 2026-11-19.