Skip to main content

Non-responders

Move Quiet Contacts to New Lists

A customer who ignored three emails will ignore a fourth that looks the same. From Pro, an automation can notice who went quiet and move them to a Smart List of their own, where the team decides on a different angle instead of repeating the first one.

  • Define quiet before you automate it
  • Move, tag and stop: three contact actions
  • A separate list with its own, gentler plan

The problem, solved

What happens to the people who never answer

  • Silent contacts just sit in the old list

    Without a next step, they get swept into the next campaign and receive the same email that did not work.

  • Quiet means different things to different teams

    Ten days of silence after a support call is not the same as ten days after a busy launch week.

  • Our reminders already ran their course

    The standard sequence sends a reminder and a last email, then stops. After that the contact needs a decision, not another nudge.

  • We cannot see who was moved and why

    A contact who appears in a new list with no explanation confuses the next person who picks up the account.

  • I do not want to pester anyone

    Repeated asks to someone who chose not to answer damage the relationship more than the missing testimonial costs.

Flip the switch to see how StoryProof handles each one.

Team checklist

Decide what quiet means and where it leads

Agree each item with the people who own the relationships. Moving contacts is easy to automate; deciding what they get next is the real work.

Define quiet
Move them
Decide the next approach

Ticks stay in your browser. Nothing is saved or sent.

In StoryProof

Build the quiet-contact flow

  • You will need
  • A StoryProof workspace on Pro or above
  • A request sequence already running
  • A new Smart List for non-responders
  1. 1

    Pick the quiet trigger

    In the automation builder, start from a contact going quiet, or from a request getting no response after your chosen number of days.

  2. 2

    Add the contact actions

    Add to the non-responder list, remove from the ready list, and tag with the reason.

  3. 3

    Publish and review the first moves

    After the first contacts are moved, read their runs in the logs and confirm none were still mid-sequence.

  4. 4

    Meet on the list monthly

    Look at who is on it and agree, account by account, whether a different approach is worth trying.

What happens next: If the list grows fast, the original request is the thing to fix, not the people on the list.

Before you start

What moving contacts does not solve

  • Quiet is not defined here

    This page does not say what the product counts as a contact going quiet. If that matters, use the no-response trigger, where you choose the days.

  • Moving is not asking

    The flow sorts people. Whatever they receive next is a separate decision and, if automated, a separate automation.

  • Unsubscribes are different

    A contact who unsubscribed should not be on any request list. The follow-up sequence already skips them.

  • Requires automations

    Triggers and contact actions start on Pro. Lists and contacts are on every plan.

  • Test only on yourself

    A test run performs every action for real, so it moves and tags a real contact. Use your own.

FAQ

Questions people ask

Short answers to what usually comes up next.

Should the quiet list get another automatic email?

Usually not straight away. A different person or a different kind of ask works better than a fourth email from the same sequence.

Can a contact move back if they reply later?

A separate automation that starts when they complete a request could remove them from the quiet list. Check the logs to make sure it fires.

Which trigger should I start with?

If you want to choose the number of days, start from the no-response trigger. It is the one whose timing you control.

Is this the same as unsubscribing them?

No. They stay contactable; they are just set aside. Unsubscribing is a separate contact action and should follow the contact’s own wishes.

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

Give silence its own plan

Run testimonial requests in StoryProof and let non-responders move to a list your team can treat differently.

Last updated 2026-11-18.