Client feedback software that asks the day the job is finished
FigsFlow sends a client feedback survey from the job itself, the moment the work is done. The client answers in the email or the client portal, and every ask is recorded on the client record, including the ones your team chose to skip.
The work is finished. Ask how it went
Either is fine, and either is recorded.
The problem
“They seemed happy enough.”
A client of eleven years sends a short email in March. They've moved to another practice. Nobody saw it coming. The last thing anyone heard from them was a thank-you when the accounts were filed.
Looking back, the signs were there: a delayed reply here, a fee question there. But nobody ever asked them how it was going, so nobody knew. Feedback in most practices depends on someone remembering to send a form, and in January nobody remembers.
Feedback asked for in this period: none
The moment
When does the client get asked?
When a job is marked finished, FigsFlow prompts the person who did the work to send the survey you've set for that job. They can add a personal message, or skip it.
Either choice is recorded against the client. So when a partner asks whether a client was ever asked how it went, the answer is on the record, not in someone's memory.
Every send and every skip is kept on the client record
From: your practice · Subject: How did we do on your annual accounts?
How did we do on your annual accounts?
Try it: click a rating
Answering
Do clients have to log in to answer?
No. You choose per survey. The first question can sit inside the email itself, so the client clicks a rating and they're done.
For a longer survey, the email links to the client portal instead, where the client answers the rest and the reply lands on the same record.
Who gets it
Can we choose which clients get which survey?
Yes. Narrow the audience by client segment, service, industry, account manager, region or date, and check the exact recipient list before anything is sent.
Add addresses by hand if you need to, then send now or schedule it. The invitation comes from your own email templates, with the client's and practice's names filled in.
Sample data
The results
What do we see once clients reply?
For each survey: how many responses came in, the response rate, the average score, and how the scores are spread across the scale.
Surveys use the same question types, conditional logic and branding as FigsFlow's request forms, so a follow-up question only appears when an earlier answer calls for it. The same tool runs staff surveys too, such as employee NPS and team pulse checks.
The difference
A form someone remembers to send, or a question the job asks for you
Most practices collect feedback with a survey link or an annual email. Both depend on someone finding the time.
| When… | A generic survey linkSent from an online form tool | An annual feedback emailOne round a year | FigsFlowAsked from the job |
|---|---|---|---|
| A job is finished | ✕Nothing happens unless someone remembers. | !The client waits months to be asked. | ✓The person who did the work is prompted that day. |
| A client answers | ✕The reply sits in a separate tool. | !Replies land in one person's inbox. | ✓Saved on the client record, next to the job. |
| You want to know who was asked | ✕No record. | !A mailing list, if anyone kept it. | ✓Every send and every skip recorded. |
| The client doesn't want to log in | !Another website to open. | !A reply they have to type. | ✓One click on a rating inside the email. |
| An account manager leaves | ✕The history leaves with them. | ✕So does the inbox. | ✓The next person reads it on the record. |
Related modules
Next in the platform
Feedback is only useful next to the work it's about. These are where that work lives.
Client portal
Where clients answer longer surveys, alongside their documents and messages.
See the portal moduleEvery client email on the same record, so feedback sits next to the conversation.
See the email moduleWorkflow templates
The jobs that finish, and the moment the feedback survey is asked.
See the templates moduleForms and requests
The same question types and logic your surveys are built with.
See the forms moduleQuestions