Keep every conversation with the work

Start the conversation where the client already is

An embeddable chat widget can let a visitor message the studio from its own website. The inquiry arrives inside StudioLedger rather than disappearing into another shared inbox, giving the studio a direct path from the first question to the contact, lead, and project workflow that may follow.

The widget should collect a useful conversation without becoming an anonymous support maze. The studio controls the public placement, and the message can move into a real relationship when the visitor becomes a client or active opportunity.

Put chat on the page the client is viewing

An estimate or invoice can include client chat when the studio turns on Enable Client Chat in the document builder. After the document leaves draft, the client can ask a question from the public estimate or invoice instead of opening a separate email and describing which document, total, or term they mean. The resulting conversation remains identified with that document for the studio.

A published gallery can offer the same direct path when its Chat setting is enabled. The client can start a gallery-wide conversation while reviewing the work, and the studio can return to that thread from the gallery rather than reconstructing the context from a general inbox. Gallery access controls still apply, and licensing-store galleries keep chat disabled so purchasing and review modes retain clear boundaries.

Client messages need project context

A question about an estimate, call time, gallery, or delivery means more when the relevant project is nearby. Contact messaging keeps the client thread inside the relationship, reducing the need to search an inbox before understanding what the person is referring to.

The client-facing conversation remains separate from internal team discussion. A producer can coordinate with teammates, record a decision, and keep the private production context private while still answering the client from the correct project history.

Email should remember what happened

Branded templates and smart fields reduce repetitive writing, but the sender still previews the resolved names, dates, totals, and links before delivery. Messages can be sent now or scheduled, and the Email Center keeps the delivery state visible after the composer closes.

The useful outcome is not one enormous chat stream. It is a set of communication tools that preserve the right boundary and keep the message close to the client, Job, document, or teammate that gives it context.