Manual enrolment
Add Contacts by Hand to Automations
Some customers should be asked because a person decided so: the client who just praised you on a call, the account that renewed early. From Pro, an automation can start when you add people by hand, so the judgement stays human and the chasing does not.
- Who on the team may enrol whom
- A short reason recorded with each one
- The flow handles the ask and the reminders
The problem, solved
When the right person to ask is spotted by a person
They praised us on a call, then nothing
The account manager means to send a request after the call. A week later the moment is gone.
With StoryProof: From Pro, an automation can start when you add people by hand, so enrolling the contact straight after the call is the whole task.
I can enrol them, but not chase them
Hand-picking is quick. Remembering to remind each person twice is what never happens.
With StoryProof: The flow can send the request, then the reminder and last email, stopping as soon as they leave a testimonial.
Two of us added the same customer
Several people talk to the same account, and each assumes they are the one asking.
With StoryProof: The review request action skips anyone who already reviewed or was asked recently, so a duplicate enrolment does not mean a duplicate ask.
Nobody remembers why someone was asked
When the testimonial arrives, the marketer has no idea what prompted it or which conversation to reference.
With StoryProof: Have the flow add a tag at enrolment, and use the logs to see who was enrolled and every step that ran.
Not everyone should be enrolling customers
An enthusiastic new hire can enrol a customer who is mid-dispute.
With StoryProof: Roles and permissions keep the workspace parts each teammate can use to what their job needs.
Flip the switch to see how StoryProof handles each one.
Team checklist
Agree who gets hand-picked, and by whom
Settle this with everyone who will enrol contacts. The criteria are short on purpose so people actually use them in the moment.
Ticks stay in your browser. Nothing is saved or sent.
In StoryProof
Build the hand-picked flow
- You will need
- A StoryProof workspace on Pro or above
- Contacts in StoryProof
- A collection form the request links to
- 1
Start from the manual trigger
In the automation builder, choose the trigger for people added by hand. The draft saves itself and nothing runs before you publish.
- 2
Tag on entry
First action: add a tag such as hand-picked, so these contacts can be told apart from list or scheduled requests.
- 3
Send and follow up
Add the review request, the reminder and the last email, inside working hours and with a cap on how often one person hears from you.
- 4
Enrol yourself first
Before anyone enrols a customer, add your own contact and watch the emails arrive. It runs for real, which is the point.
What happens next: Every month, look at who was hand-picked and how many replied. It tells you whose instincts to trust.
Before you start
What manual enrolment leaves to the team
Judgement is the input
The flow asks whoever you add. It does not check whether now is a good time; the hold-off criteria do.
Where to click is not described here
This page does not give the exact screen for adding someone to an automation. Look for it in the automation itself.
One contact at a time is assumed
For dozens of customers at once, a list-triggered flow or a campaign fits better than hand enrolment.
Plan gated
Manual enrolment is an automation trigger, available from Pro.
Logs do not last forever
Run history is kept for 30 days, so record the reason for each enrolment somewhere longer-lived.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is this different from sending one request by hand?
Yes. Enrolling someone in the flow also sends the reminders, honours your sending hours and skips them if they were asked recently.
Can I remove someone after enrolling them?
This page does not cover stopping a run by hand. The sequence stops on its own when they leave a testimonial; check the automation for any other option.
Who should be allowed to enrol customers?
The people who talk to them: account managers, founders, senior support. Agree it, then set roles to match.
Can the same flow also start from a list?
Keep them separate. A hand-picked flow with its own tag makes it easy to see what personal judgement produced.
Still have a question? Ask the StoryProof team or book a demo.
Pick the person, let StoryProof ask
Enrol customers by hand when the moment is right, and let an automation send the request and reminders.
Last updated 2026-11-18.