Complete your first client automation change

A new workspace opens on Home. Choose Paste a client’s message, then paste the client's email, Slack message, or ticket as they wrote it. AgentHub reads the title, who asked, and the request text from it, and asks you for the client (their company name). What they call the workflow is optional; if you name it, choose where it runs. If something needed is still empty when you continue, one line says which, and the first one is focused. Edit the message reopens the paste.

Choose Save and prepare draft. That one action creates the client, the workflow if you named one, and the request, then opens the request in the client assistant and prepares a draft scope, checks and questions for you to review; it counts toward your AI actions. Save only creates the same records and opens the request without a draft. If the paste contains something that looks like a credential, AgentHub stops and tells you which line, and saves nothing until you remove it.

Once your workspace has a client, open Create → Request, or choose New request on Work, for the next one. Select the client, or add it from the same form. The workflow is optional: choose it, add it, or leave it as Not known yet and set it on the record before the work starts. Use a real client; sample clients do not count toward setup progress or proof totals.

AgentHub opens the new change record in Requested state. It derives a short title from the first meaningful line of the request and leaves the original request intact.

With Save only, the record opens on No scope written yet. and shows the request as recorded, labeled as the client's request, not a scope. Choose Prepare a draft scope, or Write the scope yourself and then Save scope. Once a scope is saved, the record shows Ready to agree the scope?; the request stays as it was under Original request as recorded, and earlier scopes stay in the history. If the record says Workflow: Not known yet., choose Set the workflow when you know it; starting the change needs it. A misspelled client name is fixed with Rename the client, under More options.

Open the client or workflow later to add contact email, purpose, business impact, source URL, repository, deployment, or different owners. Those details do not block the first request.

If client approval is needed, choose Get client approval. AgentHub shows the saved scope in full; choose Create client approval link, copy the link, and share it through the client channel you already use. Unsaved scope edits must be saved or discarded first, because approval uses the saved scope. If the request is already authorized, open Already authorized? and choose Start the change.

The client sees Does this match what you need? with the frozen scope, and chooses Approve scope or Request changes without an AgentHub account. The page says who sent it. While you wait, the record shows when the link expires and when it was first opened, and while it is open on your screen it checks for their decision every minute; Check for the client's decision looks right away. Approval stops at Approved; you still choose when to start the change. A change request returns the record to editable review.

Make the change in your own tools. Then answer What did you change? in plain words, the way you would tell the client, and choose Ready to verify. The note is required. Under Evidence, Add evidence attaches a pull request, commit, test run, or deployment; it stays Workspace only unless you mark it for client briefs.

The record asks What did you find? Open Write down what you will check if you want the checks on the record before you run them. Do the checks in the source platform, then write what you did and what you saw under What did you see? It is optional, but it goes into the client update; leave it empty and the record says No checks written down.

Under Did it work?, choose Passed, Failed or Not enough evidence. Nothing is chosen for you. For Passed, answer Does it do what they asked, and nothing more? Choose Yes when it stayed inside what was asked, then Mark verified. Choose It differs from what was asked when it went beyond or away from it, then say the client approved the difference elsewhere and where, or close with the difference noted. AgentHub records your judgment but does not make it.

Failed needs a note on what failed, and Record the failure and go back to the change returns it to implementation. Go back and wait for evidence parks it without a passed or failed result. AgentHub keeps uncertainty visible instead of treating missing evidence as success.

From the verified record, choose Prepare the update for that client, or open Briefs and choose New brief. Choose 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. Choose Generate draft.

The draft opens on What should the client know? Under What goes in, untick anything that should stay private. The Summary follows the selected records until you edit it. Your edits are kept if you change the selection; check them against the selected work or replace them with a fresh record-based summary. Choose Save and preview to see the saved update exactly as the client will.

If it reads right, choose Publish and create link; Edit the update goes back to writing. Publishing freezes the update but sends nothing. Choose Copy the link, or under Email it, check the recipient and choose Send by email.