Skip to main content

The inbox is where your team already is

Email Teammates When Testimonials Arrive

Plenty of people who care about new testimonials never log into StoryProof: the founder, the sales lead, the person whose name keeps appearing in the reviews. Forwarding each one by hand lasts about a week. From Pro, an automation can email up to ten teammates when a testimonial arrives, and conditions decide who gets which. The helper below checks whether email is the right route for your team or whether another one fits better.

  • Email, in-app alert, webhook or a manual digest
  • Chosen from your plan, team size and tools
  • Filters so each person gets only what matters

The problem, solved

Why forwarding testimonials by hand breaks down

  • I forward them, when I remember

    Manual forwarding depends on one busy person, and it stops the first week they are away.

  • Sales does not need every review

    Send everyone everything and they stop reading. Each person wants the reviews that matter to them.

  • Only tell people about approved ones

    Some teams only want to share testimonials that are cleared for use.

  • We are not on a plan with automations

    Email alerts are an automation step, so they need the plan that includes automations.

  • The team lives in another tool

    If nobody reads email at work, an email alert is the wrong route.

Flip the switch to see how StoryProof handles each one.

Route helper

Is team email the right route?

Answer four questions about your team. The helper suggests a route and the next best one.

Is your workspace on a plan with automations?
Who needs to hear?
Where does your team pay attention?
How quickly do they need to know?

Your answers stay in your browser. Nothing is saved or sent.

In StoryProof

Set up the team email

  • You will need
  • A StoryProof workspace on Pro or above
  • Up to ten teammates per email
  • An idea of who wants which testimonials
  1. 1

    Pick the moment

    In the automation builder, start when a testimonial is received, or when it is approved if only cleared ones should be shared.

  2. 2

    Split by audience

    Add a condition with a named branch per group. Tags you already use can help decide who hears about which testimonial.

  3. 3

    Add a team email on each branch

    Choose the teammates for each branch, up to ten per email.

  4. 4

    Test with your own testimonial

    A test runs every step for real. Submit one through your own link and check the right people got it.

What happens next: After a month, ask the recipients if the emails are useful. If not, tighten the branches.

Before you start

Limits of team email

  • Ten teammates per email

    For a wider group, forward the email yourself or send reviews to a shared tool through a webhook instead.

  • Email or dashboard only

    Team alerts are emails or in-dashboard notifications. There is no native Slack or Teams alert.

  • Too many emails get ignored

    Every testimonial to everyone is noise. Use branches.

  • Needs automations

    Team emails are an automation step, from Pro.

FAQ

Questions people ask

Short answers to what usually comes up next.

How many people can get the email?

Up to ten teammates per team email step. Different branches can email different people.

Can sales get only 5-star reviews?

Conditions can route testimonials to different branches. Check in the builder which rules are available, then give sales its own branch.

Can the alert go to Slack instead?

Not natively. Use a webhook and a middleware to reach a chat tool.

Should we alert on arrival or approval?

On arrival if someone needs to act fast; on approval if the email is about sharing testimonials that are cleared for use.

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

Stop forwarding testimonials by hand

Let StoryProof email the right teammates the moment each testimonial arrives.

Last updated 2026-11-18.