Your team may manage projects, requests, documents and deliverables in monday.com while most conversations with clients happen somewhere else. A client replies to an email about a project. Feedback on a deliverable arrives in another thread. A file is attached to a separate message. A general account question lands in someone's inbox. The work itself remains organized in monday.com, but the communication around that work gradually becomes disconnected from it.

A client portal can bring those conversations closer to the workflow they relate to. With Client Portal Builder for monday.com, clients can communicate with your team through their portal while your team continues working in monday.com. Project specific feedback can stay attached to the relevant monday.com item, while general conversations can live in a separate client inbox. Email can still play an important role, but mainly as a way to tell clients that something new is waiting for them.

Context

Different client conversations belong in different places

Not every client message has the same context. A question about a specific deliverable should ideally stay connected to that deliverable. A general account question should not have to be attached to an unrelated project item. And an email notification does not necessarily need to become another place where the actual conversation continues. A useful way to separate these interactions is:

• Item comments
  For communication about a specific monday.com item.
• Client Inbox
  For general communication with the client that is not tied to one particular item.
• Email notifications
  For letting clients know that something new requires their attention.

This keeps each conversation close to the information it belongs to while giving clients a consistent place to interact with your team.

Item comments

Keep project specific feedback attached to the right item

Many client conversations are really conversations about a specific piece of work, for example:

• feedback on a design
• a question about a project task
• clarification on a request
• comments on a report
• a file related to a particular deliverable
• discussion about an item awaiting approval

If that conversation happens entirely through email, your team eventually needs to connect it back to the relevant work manually. Item comments provide a more direct relationship. Imagine a monday.com item called: Homepage concept

The item contains the current status, due date and design file. When the client opens the corresponding item through the portal, they can also leave a comment such as: Could we use the alternative hero image from the first concept?

The comment stays associated with the Homepage concept rather than becoming a separate conversation that someone needs to match back to the project. Your team can reply from monday.com, and the client sees the response in the portal. The result is a simple relationship: monday.com item → client sees item in portal → client comments on that item → team replies from monday.com → conversation remains connected to the work

General messages

Use a client inbox for conversations without an item

Not every client message belongs to a project item, a client might want to ask:

• Who should I contact about billing?
• Can we schedule a meeting next week?
• Where can I find our agreement?
• Can you add another person to our portal?
• We have a general question about our account.

Creating a monday.com project item simply to hold one of these conversations would add unnecessary structure. Client Portal Builder therefore also includes a Client Inbox for general private communication.

The inbox belongs to the client relationship rather than to one particular project, request or deliverable. Clients can open it from their portal and exchange messages with your team without having to decide which board item the conversation belongs to. Your team can manage these messages from the client's record in monday.com. This creates a useful separation:

• “Can you change the image in this deliverable?” → Item comment on that deliverable
• “Can we move our monthly meeting?” → Client Inbox

Notifications

Use email to bring clients back to the conversation

A monday.com client portal does not mean clients will keep it open all day. When your team sends a new message or replies to a comment, the client still needs a way to know something happened. This is where email remains useful. Instead of using email as the place where the entire conversation happens, an email can simply notify the client that a new message or update is available, for example:

Team replies to an item comment in monday.com → client receives an email notification → client opens the portal → client sees the message in the context of the relevant item → client replies there

The same pattern can be used for general Client Inbox messages. This keeps email useful for attention and delivery while the actual conversation remains connected to the portal and monday.com workflow.

Files

Keep files and feedback in the same context

Client communication often includes more than text, a client may need to attach:

• a reference image
• a revised document
• additional project material
• screenshots
• supporting information

When those files arrive through separate email threads, someone on the team often has to download them, identify which project they belong to and upload them to the right place. If the file is part of feedback on a specific item, it can instead be exchanged together with the item comments, for example:

Annual report draft → client reviews file in portal → client leaves feedback on the item → client attaches a corrected spreadsheet → team receives the comment and file in the context of the same monday.com item

Workflow

Let communication follow the client workflow

Communication usually happens throughout a client process rather than at one isolated stage. Consider a project moving through:

In progress → Waiting for client → Client review → Approved → Completed

Different conversations can happen at each stage. While the project is in progress, your team might use the Client Inbox for a general scheduling question.

When more information is required, the client might comment directly on the corresponding request item. During client review, feedback can remain attached to the deliverable. If the client requests changes, the discussion stays with the same item while your team prepares the revision. Once the work is approved, the item still contains the history of the conversation that led to that result. Communication therefore becomes part of the surrounding workflow instead of an independent channel beside it.

This also works naturally with the other ways clients can interact through the portal:

• Create new work → submit a request through a form
• Update existing work → edit selected information on an existing item
• Discuss existing work → use item comments
• Make a decision → approve or request changes

The underlying projects and items remain in monday.com while the portal provides the client facing interactions around them.

Example

Manage project feedback and general client messages

Imagine an agency managing a website project for a client in monday.com. The Projects board contains a deliverable called: Homepage design

The agency finishes the first version and makes it available for client review. The client opens the portal, previews the design and leaves an item comment: We like the direction. Could you replace the hero image and make the main CTA more prominent?

The project manager sees that feedback in monday.com and replies directly on the same item. The client receives an email telling them that there is a new response and returns to the portal to continue the conversation. Later that day, the client has a completely different question: Could we move our project call from Tuesday to Thursday?

That message is not really about the Homepage design or any other deliverable. Instead, the client sends it through the Client Inbox. The agency now has two conversations:

• Homepage feedback
  Attached to the Homepage design item.
• Meeting question
  Attached to the overall client relationship.

From the client's perspective, both happen through the same portal. From the agency's perspective, each conversation remains in the context where it makes sense.

Client approvals

Combine feedback with client approval workflows

Communication becomes particularly useful when clients need to review and approve work. An approval rarely consists only of clicking a button. A client might review a deliverable and decide that changes are needed. In that case, the decision and the explanation behind it both matter. A workflow could look like:

Deliverable becomes ready for review → client previews it in the portal → client selects Request changes → client adds feedback to the item → team revises the deliverable → client reviews the new version → client selects Approve

The predefined action controls the workflow state while item comments hold the conversation around that decision.

Portal or monday.com

When should clients communicate directly in monday.com?

A client portal is not always necessary. If an external collaborator already works closely with your team inside monday.com and should participate directly in the board, inviting them as a guest may be the simpler approach. That is particularly relevant when the external person needs broad collaboration access rather than a separate client facing experience.

A portal becomes more useful when you want to control the relationship differently. Your team can continue working with complete boards and internal information in monday.com, while clients see only the projects, items and communication intended for them.

Summary

Give every client conversation the right context

Client communication does not need to become a separate system beside the work you already manage in monday.com. The key is giving each conversation the right place.

• Use item comments when the message belongs to a particular project, request or deliverable.
• Use the Client Inbox when the conversation concerns the client relationship more generally.
• Use email notifications to tell clients when something new is waiting for them.

That creates a simple communication model:

• Project specific conversation → Item comments
• General client conversation → Client Inbox
• Attention and notification → Email

Your team keeps working in monday.com while clients get one dedicated place to view their work and communicate about it.