Clippter
Back to Help

Deliver

Project chat and Communications hub

Use Clippter chat for work talk that belongs on a project or a workspace channel — not for company-wide random chatter. Captured CC email lives next to chat under Communications.

Where to open chat

PlaceWhat you get
Chat bubble (bottom right)Home (full Communications, email, Chat with Clippter Support, bug) · Messages (direct messages with teammates, project chats, client chats, spaces; short thread in the bubble) · Help (live search)

Chat with Clippter Support (Home in the bubble) opens a support thread with the Clippter team. Those messages land in the Clippter Demo workspace support inbox (configured via SUPPORT_INBOX_ACCOUNT_ID). Sign in as that workspace to see Clippter Support inbox under Home and reply. When Support replies, you get a badge on the bubble (and on Home / the Support button); opening the bubble brings that same Support chat back.

In Messages (and the full Communications hub) you can start DMs, open project/client threads, create spaces and add people, send emoji, attach images/PDFs, see send/read ticks, and unread badges. Type @ to mention a teammate — they get a notification in the bell until they open the chat. Portal Ask the team supports attachments.

| Hub → Chats | All active project channels, client threads (team side), and custom channels (#marketing, …) |

| Hub → Email | Account-wide CC inbox (Needs link / Linked) |

| Project → Communications → Chat | Only this project: Internal team thread and Client light thread |

| Project → Communications → Email | Emails linked to this project (and related deal mail) |

| Portal → Ask the team | Client asks the agency about that project (not the internal team channel) |

There is no Communications item in the top navigation. Use the bubble for workspace-wide chat and email.

Project channels

Chats are opt-in active, not auto-open for every project:

  1. Team / direct — 1:1 with a teammate (e.g. Joost).
  2. Project — internal team thread on one project.
  3. Client — light project thread that portal clients can read and reply on (not a private 1:1 with one contact). In the portal this is Ask the team. Open from the bubble or when a client messages.
  4. Spaces — invite-only team rooms (e.g. #marketing). On create, pick people (like Google Chat). Later: People in the space header to add or remove. Only members see the space.
  5. Close (× on a row) hides from the active list; history stays. A new client message brings the client thread back.

Use Open Communications in the bubble for the full-screen hub (Chats + Email).

Frame-accurate review notes stay on deliverables under Review. Do not use project chat as a replacement for review comments.

Project chat people

Internal Project threads include people working on that job by default (project manager, creative lead, planning bookings, task assignees). Use People in the chat header to see who is in, and to invite extra teammates. Project-role people stay linked to the project (no Remove); invited extras can be removed. Opening a project chat from the project also adds you if you were not already in.

Spaces (custom channels)

Create a named space (for example marketing or ops) from Messages → Spaces. Add teammates when you create it, or later with People in the space. Only those people see it — not the whole workspace, and not clients.

Tips

  • Prefer the project thread when the topic is about one job.
  • Use a custom channel for ongoing team topics that are not a single project.
  • Keep client chat light; put detailed picture/time feedback in Review.
  • For CC email capture, see Capture client emails with CC.
  • Portal access and what clients see: Client portal.
Still stuck? Contact support