Client feedback
How do I keep client feedback out of scattered emails and texts?
Short answer
Give each project one link where the client sends feedback, and ask them to use it from the first day: requested changes, questions and notes on files. Reply there too, so the habit sticks. PaloWorks gives every project a client portal like that, with no account to create, so the history sits on the project instead of across your inbox and phone.
Free for 1 client, 3 active projects. No card to start. Updated by PaloWorks.
What to look for
One link per project
Clients use whatever is closest to hand; make the right place the closest.
In PaloWorks
The client portal holds the brief, scope, delivery, invoices and changes on one link. Clients who prefer can sign in with an emailed code to see every project.
Change requests that count as rounds
Feedback that is not counted becomes free work.
In PaloWorks
The client asks for changes from the scope link; notes sent while a round is open join that round instead of starting a new one.
Messages both ways
Questions need answers in the same thread as the work.
In PaloWorks
The client can message you from the portal, and your replies sit on the project.
Notes on the files themselves
"The second one" means nothing three weeks later.
In PaloWorks
On a delivery, the client comments per file or per page, and you reply under it.
Texts that point back to the link
Some clients only read texts.
In PaloWorks
A client who opts in gets project updates by text, each pointing to the link. Replies by text are not read into the project.
How it works in PaloWorks
Step 1
Send the portal link
With the first email, say that changes and questions go through it.
Step 2
Move stray feedback in
When notes arrive by email, log the round or reply on the project so the record stays whole.
Step 3
Answer on the link
Reply in the portal; the client learns where the conversation lives.
Step 4
Close each round there
Mark the round as sent back to the client; later notes start the next round, so the count and the history match.
When PaloWorks is the wrong pick
- Email replies to project mail reach your own inbox, not the project; only replies to inquiries land in PaloWorks.
- There is no markup on images or video frames; detailed visual review stays in a proofing or review tool.
Comparing tools? Read PaloWorks compared, including what the others are better at.
Questions people ask
- Can a client reply by email and have it saved to the project?
- No. Project email is sent with your address as the reply-to, so replies reach your inbox. Replies to an inquiry thread do land in PaloWorks.
- Does the client need an account?
- No. The portal is a link. A client can sign in with a code emailed to them to see every project, if they want to.
- Can clients comment on the agreement?
- Yes. They can ask for changes section by section before they sign. Agreements are on Pro and Studio.
- How do I get clients to stop texting feedback?
- Set it out at the start, reply on the link with a short note, and log what they sent so they see it counted there.