Skip to main content

One customer, one ask

Stop Team Members Double Asking Customers

Your account manager asked on Monday. Support asked on Wednesday after closing a ticket. Marketing put the same customer in Friday’s campaign. Each request was reasonable on its own, and together they look disorganised. Use the checklist below so everyone on the team can see who already asked a customer before they ask again.

  • A lookup habit before anyone sends
  • One owner per customer account
  • A shared record of every open ask
Use the free toolStart your shared workspace (opens in a new tab)
No double asks
2 of 12 done17%
  • Every customer account has one named owner who decides whether a request goes out.
  • The team agrees a quiet window after any request, during which nobody else asks.
  • All customers anyone may ask are contacts in one shared workspace, not private lists.
  • Tag names for an open request are agreed and written down, including who asked and the month.
  • Support knows it must check the shared record before asking after a closed ticket.
Free tool, no sign-upTry it below

The problem, solved

How a customer ends up asked three times in one week

  • Nobody checks before hitting send

    Each teammate keeps their own list in a spreadsheet or an inbox, so a colleague’s request from yesterday is invisible.

  • We cannot see who has an open request

    Even a shared list does not show that a request is already waiting for a reply.

  • Reminders keep going after they replied

    A manual reminder from one person lands after the customer already answered someone else.

  • Three departments each run their own tool

    Support asks from the help desk, sales from a CRM sequence, marketing from a newsletter tool. Nothing joins up.

  • Requests go out through too many channels

    A chat message, an email and a printed card all ask the same question.

Flip the switch to see how StoryProof handles each one.

Team checklist

Before anyone asks a customer

Agree these once as a team, then run the last group every time someone is about to send a request.

Agree the ground rules
Join up the departments
Every time, before sending

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

When two teammates both want to ask

Settle the common collisions in advance so nobody argues over a customer in the moment.

SituationWho asksThe other person
Support closed a happy ticket, account owner planned to ask next monthAccount owner decidesPasses on the moment and the ticket details
Customer is in a marketing campaign and has an open request tagNobody newCampaign skips them
Customer praised the product to sales on a callAccount owner, citing what they saidSales logs the remark on the contact
Customer already left a testimonial this quarterNobodyUse the one you have
Customer has no owner yetWhoever assigns an owner firstWaits for the owner to decide

In StoryProof

Set up a shared record in StoryProof

  • You will need
  • A list of everyone who currently asks customers for testimonials
  • An agreed quiet window, such as 60 days
  1. 1

    Invite everyone who asks

    Give support, sales and marketing staff a seat in the same space so they work from one record.

  2. 2

    Bring customers in as contacts

    Add the customers you might ask as contacts, then build a smart list of those nobody is allowed to ask right now.

  3. 3

    Tag every request when it goes

    Use the agreed tag names so a filter shows open and recent requests at a glance.

  4. 4

    Let reminders stop by themselves

    On Pro or above, turn on the follow-ups automation so reminders end when the customer replies.

  5. 5

    Review the queue together

    Submissions wait for approval, so a weekly look at the queue shows who answered and lets you close their tags.

What happens next: Once a month, filter for open request tags older than the quiet window and close them. Stale tags make the record lie.

Before you start

What the shared record cannot do for you

  • It only sees what goes through it

    A request sent from a personal inbox or a chat app leaves no trace. The habit matters more than the tool.

  • Tags are typed by people

    StoryProof does not tag a contact for you when someone asks. Misspelled or skipped tags break the lookup.

  • No lock on a contact

    Nothing in StoryProof stops a second teammate from sending. The lookup step is a team rule, not a software block.

  • Seats are counted per space

    Large teams may run out of seats on a smaller plan. Check pricing before you invite every department.

FAQ

Questions people ask

Short answers to what usually comes up next.

Who should own a customer for testimonial requests?

Usually the person with the closest working relationship, often the account manager or success manager. What matters is that there is exactly one owner and everyone knows who it is.

How long should the quiet window be?

Long enough that a second request would feel like a new conversation. Many teams pick a few weeks after an unanswered ask and longer after a testimonial was given.

What if the customer was asked twice already?

Have the account owner send one short note apologising for the duplicate and saying no further reminders will follow. Then make sure that is true.

Does this replace a CRM?

No. It keeps testimonial requests in one place. If your team already logs activity in a CRM, add the request there too so sales sees it.

Can we still ask at events or in person?

Yes. Ask whoever collected in person to tag those customers afterwards so the next email request does not repeat the question.

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

One record for every request

Put contacts, tags and requests in one shared workspace so the next ask is never a repeat.

Start your shared workspace (opens in a new tab)

Last updated 2026-11-07.