Create, publish, schedule, and send a client brief

Open Briefs and choose New brief, or choose Prepare the update for the client on a verified record, or ask the assistant for the client update and choose Review beside this chat (in a client’s conversation) or Open to review on its answer. Select the client, who it is for, and the period. The first time, add your name, title, practice name and the address clients can reply to; Your practice name goes on the letterhead, so it is yours, not the client's. AgentHub assembles the current workflow register, recorded changes and incidents.

There are two ways in. From Briefs, from a record, and on a schedule without your notes, the draft is made from recorded work only. In a client’s conversation, you can also tick items from your private notes, such as progress, figures or next steps, before you choose Prepare the draft (see Ask the assistant about your work). The client sees those items as your report, never as checked work, and your notes stay private.

Dates and the period use your workspace's time zone, so work you verify in the evening counts on that day. It is set from your browser the first time you sign in as the owner; an owner or admin can change it under Settings, Workspace name, Time zone.

Open items are included even when they began before the selected reporting period. Canceled and declined requests remain out. Completed verified changes are available for you to review before publishing. The draft remains private.

The draft opens on What should the client know? Under What goes in, leave completed verified changes ticked only when they belong in the client update. Uncheck internal tests, duplicate records, or work that should stay private. Excluding a record from the brief does not delete it from AgentHub.

New drafts include recorded approval details beside each completed change. Approved by uses the name supplied through the client approval link. Approval recorded by names the team member who logged an outside approval, who may not be the approver. Check the name and date before sharing. Approval emails and private response notes are not copied into the brief.

The workflow register shows a record date. This may come from a recorded sync, recorded version, or manual record update. It does not prove the workflow is connected or running.

Read the draft as the client would. The summary is a letter written from the record in the client's words: what they asked, what changed, and how it was checked when you wrote that down on the record. Edit it so it sounds like you. When nothing is recorded for the dates, the summary says only that the update includes no completed and verified changes; it never tells the client that nothing is outstanding, and Before you publish reminds you to add progress or open items from your notes. Anything you add goes right after it as part of the same message, signed with your name. Empty sections do not appear, and a field you have not filled in is never shown to the client. A change that differs from what was asked stays visible. Only links you marked for client briefs are included.

Under each change, the client sees What we changed, which is what you wrote when you moved it to Verify, then What was agreed, the scope. A line with a link, or a word such as password, token or key, is left out. The note also shows under What goes in: untick the change if the client should not read it. Setup reminders, such as a workflow with no named owner, are not in the update: Before you publish lists them for you only.

Choose Save and preview. AgentHub shows the saved update exactly as the client will see it. Edit the update goes back to writing, and Publish returns only after you save and preview again. Editing the narrative or visibility choices does not change the underlying records.

Items you kept from your notes show under From your notes after you preview, with whose notes they came from and who changed them. Choose Edit or Remove on any. Only the person whose notes they are sees where each came from. When a note an item came from changes before you publish, the item says why, for example A newer note corrected this. or Newer notes came in after this draft, so check it is still right., and Publish waits until someone chooses for it: Remove, Keep as my own statement, or, for your own notes after you check them, Still correct. A newer note that AgentHub has read and that has nothing to do with the item no longer flags it, when the item rests only on facts AgentHub remembers from your notes. While a newer note is still being read, the item says so; the page checks again by itself for a few minutes, or choose Check again.

Beside a client’s conversation, the draft opens on the letter itself, with Ready to publish? above it: who it is for, the dates it covers, what it holds, and what is left to check. If the letter reads right, choose Looks right: it saves the letter exactly as shown, the same as Save and preview with nothing changed. To change the summary, add something, or untick something the client should not see, choose Edit the update; Back to the letter leaves without saving. Items from your notes that need a choice are marked in the letter, with 1 of 2 to move between them; Looks right never clears them. Every item shows whose notes it came from and, for your own notes, Where this came from (only you see this); any other item has Edit or remove. An edit you started stays open, with your text, if the item is flagged meanwhile. Opening another update beside the conversation starts it fresh. When AgentHub updated the summary’s wording, a sentence still has a part in brackets, the summary needs checking against the work you selected, or a Slack summary needs a look, the letter goes through Edit the update instead. Publish appears once the letter is saved, and stays waiting until every marked item is chosen. Open as a full page shows the same update on its own page, where More options keeps the email history, discarding a draft and revoking a link.

An update prepared in Slack has a summary AgentHub wrote from the changes it included. If you then change what goes in, the update says Review the summary: the included changes changed. Read the summary, then choose The summary is still right or edit it. Publishing waits until you do.

Under Ready to share it with the client, or at the bottom of Ready to publish? beside the conversation, choose Publish and create link. Publishing freezes that version and creates the private client link. Anyone with the link can open it. It does not email anyone.

Only records selected for the client brief are copied into the frozen published version. Excluded records stay private in AgentHub.

Choose See what they see once before sharing it. If the record changes later, create a new brief instead of altering the published version.

Choose Copy the link to send it through your normal client channel. To email from AgentHub, check the recipient under Email it and choose Send by email. AgentHub records the delivery receipt, and a failed send shows its reason on the page.

An emailed brief carries its own reply-to address. If the client replies, the reply lands on their record as a request draft and you get their message by email. Nothing in a reply is treated as approval.

Open Briefs → Schedule briefs. Select the client, recipient, weekly or monthly cadence, and next draft date. The schedule prepares a private draft for your review. The client does not need a workflow. You can also start a schedule from a client update you prepared in a client’s thread.

Dates follow your workspace’s time zone. A weekly draft covers the seven days before its date; a monthly one covers the month up to the day before.

To include your notes, tick Add items from my notes each week (or month) and save. On the date, AgentHub opens a private conversation for you, such as Weekly update, October 18 to 24, and lists the items it found in your notes for that period, ticked as in any update you ask for. Open it from Briefs with Choose your notes. Change the ticks if you want, then choose Prepare the draft; the draft opens beside the conversation. Nothing from your notes is added unless you keep it. Only your own notes are read, and only while you are an owner, admin or operator. It uses AI actions, usually one each time. If a teammate saves the schedule without ticking it, your notes are turned off.

A scheduled draft is never automatically published or sent. You still review, publish, and decide whether to email it.