Client Replies and Comments
Client replies and comments let a client respond beneath a specific posted update. The reply becomes part of the project page, so anyone with the current private link can read it. The owner also gets a queued email notice with a link back to the relevant update.
How does a client reply to an update?
The client opens the current private project link and finds the update they want to answer. Every posted update has a separate reply form, so the client should use the form directly beneath the relevant update.
- Open the private client page.
- Find the update that needs a response.
- Enter a name in Your name.
- Enter the message in Reply to this update.
- Select Attach files if supporting documents are needed.
- Select Send reply.
The name is required and can contain up to 80 characters. The reply body is required and can contain up to 5,000 characters. Spaces at the beginning and end are removed when the reply is saved. After a successful submission, the button shows ✓ Sent, and the page says that the owner's first name will get it by email.
The page may remember the reply name for later replies in the same browser. The client should still check the name before sending, especially on a shared device.
Hypothetical example: A client reads an update asking them to approve a plan. They enter "Alex Morgan" and write, "Option B is approved. Please use the measurements in the attached PDF." They attach one PDF and select Send reply. The comment appears beneath that update rather than beneath a newer unrelated update.
Client replies and comments visibility
A submitted reply is visible on the client page under its update. It shows the entered author name, the reply text, its date, and links to any attachments. Everyone with the current private project link can read the reply and download those files.
Do not use a page reply for a private note that other approved project readers should not see. The page does not provide per-comment recipients or a private reply option. Use another agreed channel for confidential information.
Friday displays replies as escaped plain text with preserved line breaks. Markdown and HTML do not become formatting. Clients can make a long response easier to read by using short paragraphs, but they should not rely on Markdown headings, lists, or links.
What files can a client attach to a reply?
A client may attach up to three files to one reply. Allowed files are PNG, JPEG with a .jpg or .jpeg extension, and PDF. Each file can be no larger than 5 MiB. A reply does not accept plain text attachments, even though an owner update can accept one UTF-8 text file.
The service checks the file extension, reported file type, and file content. Renaming another format to .pdf or .jpg does not make it valid. Empty files and files that do not match the expected content are rejected.
If file validation fails, the page tells the client to select the files again. Browsers do not keep the previous file selection after an error. The entered name and reply text remain available on the error form, so the client can correct the attachment without rewriting the message.
For a full comparison between owner and client file rules, read attachments.
Who can see a client comment?
The signed-in owner sees comments beneath each update on the project page. Clients and any other person with the current private link see the same comments on the client page. A comment is therefore shared project content rather than a direct private message.
Replacing the project link with New link stops the old client page and old file links from working. The comments remain stored with their updates and appear through the new link. Link replacement does not delete comments.
Do not share the project link publicly. If it reaches someone who should not have it, the owner can use New link, then copy and send the replacement to approved readers. Read The Client Page and privacy and security before rotating the link.
How does the owner respond to a client reply?
The signed-in project page does not include an owner reply control. Friday does not provide a special threaded owner response workflow. The owner can read the comment under its update and choose an appropriate response channel.
Selecting View as client opens the public page and its reply forms. An owner can submit a reply there, but the result is an ordinary public comment with the entered name. It is visible to anyone with the link and is not labeled as an owner response.
The owner can instead reply to the email notice through their email application. The comment notice uses the client email as its reply address. An email response goes through email and does not appear under the update on the client page. Choose the page only when the answer should become part of the shared project history.
What happens if a reply email is delayed?
Saving the comment and delivering its notice are separate actions. A successful page submission saves the comment first and queues an email to the project owner. Queueing does not guarantee immediate arrival, and the owner's mail provider may delay or filter the message.
The owner should check the project page when a client says they replied but no notice arrived. If the comment appears under the update, it was saved even if the email is still queued or delivery failed. Follow email delivery and troubleshooting rather than asking the client to submit the same reply repeatedly.
The service also limits frequent replies. If too many are submitted in a short period, the page says how many seconds to wait and confirms that the reply was not sent. The client should wait for the stated time, then submit once. Repeated attempts during the wait do not help.
Keep replies clear and safe
Clients should answer under the exact update that raised the question. They should name the decision or file in the reply instead of writing a context-free "Approved." Owners should check the project page before acting when an email contains only part of the history.
Client replies and comments work best as a visible record tied to each update. Keep each response within the limits, attach only approved project files, and use another channel for information that should not be visible to everyone with the link.