Skip to main content

Ownership

Who Should Ask Customers for Testimonials

When everyone could ask, nobody does. Sales assumes success will, success assumes marketing will, and the happiest customers are never asked at all. Answer five questions about how your customers reach you to find who should hold the ask.

  • Names the role that should send the request
  • Shows a second role when two fit
  • A hand-off table so nobody asks twice

The problem, solved

When the ask has no owner, and how StoryProof gives it one

  • Everyone thinks another team is asking

    Sales, success and support each meet happy customers. Without one owner, each quietly assumes the request is someone else’s job.

  • A customer gets asked three times

    Two teams send their own request in the same week, and the customer’s goodwill is spent on being annoyed.

  • The person they trust is not the sender

    A customer replies warmly to their account manager and ignores a request from a marketing address they have never seen.

  • The owner is too busy to chase

    Account managers ask once, then the follow-up slips behind renewals and calls.

  • There are too many customers to ask personally

    With hundreds of orders a week, no individual can own the ask without it becoming their whole job.

Flip the switch to see how StoryProof handles each one.

Decision helper

Which role should own the ask?

Answer for the customers you most want testimonials from. If two roles score close, both are shown.

After the sale, who does the customer talk to most?
Who sees the customer’s first clear win?
How many new customers a month?
How big is the team that talks to customers?
What will the testimonials mostly be used for?

Answers stay in your browser.

Hand-offs once the owner is named

The owner sends the request. Everyone else has a smaller, defined part.

TeamTheir partWhat they never do
OwnerDecides when each customer is asked and sends the requestSend to someone another team flagged as “not now”
SalesFlags customers who praised you during the dealAsk in the middle of a negotiation
SupportFlags tickets that ended with a thank-youAsk after a complaint that is still open
MarketingWrites the request and keeps the shared listSend a request the owner has not seen

In StoryProof

Set up one owner in StoryProof

  • You will need
  • A decision on who owns the ask
  • Agreement from the other teams on how they flag candidates
  1. 1

    Give the owner a seat

    Seats come per brand space, so the owner works under their own access alongside the rest of the team.

  2. 2

    Keep one shared contact list

    Other teams add or flag candidates as contacts; the owner sends from the smart list.

  3. 3

    Keep “asked” and “not now” as smart lists

    Smart lists come with every plan. One look tells any team whether a customer has been asked or should be left alone for now.

  4. 4

    Let the owner use their own voice when it helps

    For key accounts, the owner can paste the collection link into a personal email instead of sending the standard request.

What happens next: Revisit the owner when the team changes shape, for example when you hire your first success manager.

Before you start

What this decision cannot settle

  • A role is not a person

    Write a name next to the role. “Customer success” owning the ask still means nobody until someone is named.

  • Incentives can skew the ask

    If a team is rewarded per testimonial, it may ask customers who are not ready. Reward the process, not the count.

  • Large accounts may need two people

    An executive sponsor may expect to hear from your leadership even if success owns the day-to-day ask.

  • Automation still needs an owner

    Someone has to choose the rule and read what comes back, even when emails send themselves.

FAQ

Questions people ask

Short answers to what usually comes up next.

Should sales or customer success ask for testimonials?

Usually whoever holds the relationship when the customer sees a result. In most subscription businesses that is success; where the salesperson stays the main contact, it is sales.

Can marketing own testimonials if it never talks to customers?

Marketing can own the program, the template and the list, while the request itself comes from the person the customer knows. Or marketing sends an automated request where there is no personal relationship.

What stops two teams asking the same customer?

One shared list and a visible “asked” marker. If every request goes through the owner, duplicates stop.

Should the owner change for different customer segments?

It can. Enterprise accounts might be owned by success while self-serve customers get an automated ask owned by marketing. Write both down so nobody falls between them.

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

Name the owner, share the list

Give every team one contact list and let the owner send the request.

Last updated 2026-11-05.