Keeping a client informed is invisible work that gets postponed until it becomes a problem. The expensive part is not writing the email, it is rebuilding the state of the project in your head first. TCB already holds that state.

Send update sits in the header of a project. One click and you get a draft written from what is actually happening: the delivery milestones, the tasks in the current cycle, the deliverables, the deadline and the progress.

The draft is a starting point. You can edit it directly, or use the Refine field to rewrite it with an instruction like "make it warmer" or "keep it to three lines". Then you either send it or copy it to your clipboard and send it yourself.

The email goes out with your name as the sender, and the reply-to is your real address. The body invites your client to just reply, so replying has to reach you, not a platform inbox.

At the bottom, TCB adds the link to the client portal, so an update is also an invitation to see the full picture. That footer is added by the system, never written by the AI.

No values, no prices, no invoices. Same rule as the client portal: what reaches your client talks about the work.

The update follows the language of the work, not the language of your interface. TCB resolves it from the project, then the client, then you. Changing your own interface language never changes what your client receives.

Writing the draft is part of the Base Intelligence layer, which belongs to the PRO plan. If your account does not have it, you still get an update built from exactly the same project data, written from a fixed template. The same happens if the AI is unavailable for a moment. You are never left without an update.

No. Nothing goes out on its own. Every update is a click you make, and only updates you actually sent are recorded, which is what anchors the "since your last update" in the next one.