Skip to content
All help guides

Requests and changes

Capture and review a client change request

This guide shows you how to turn a secure client-link submission, email, call, ticket, or selected Slack message into a formal change request without losing the original context.

5 minConsultants and delivery operatorsReviewed August 14, 2026

Before you start

  • The client's request or a source reference to it.
  • The client and workflow names if either record is not already in AgentHub.

Give a client one secure request link

Open the client workspace and find Client request link. Choose Create request link, copy the full URL while it is visible, and share it through the email, Slack, or WhatsApp conversation you already use with that client.

The client enters their name, an optional email, and the requested change. Their submission appears in Request inbox as a draft. Choose the affected workflow, edit the title and request when needed, then confirm or dismiss it.

Important: AgentHub sends nothing automatically. Submitting the form does not approve scope, start work, or create a formal change until your team confirms the draft.
Open client workspaces

Use manual capture for email, calls, and tickets

Choose Create → Client change and start with the requested outcome. Select the client and workflow if they exist, or add the missing records without leaving the form. The title is derived automatically unless you add one.

Capture the decision-relevant request. A link to the source is usually better than pasting a long conversation.

Record a manual request

Review Slack drafts when Slack intake is connected

AgentHub watches only the client channels selected during Slack setup. A likely workflow request appears in Request inbox as a draft. Nothing is filed automatically.

Open the source message when needed, choose the affected workflow, edit the title and request text, confirm the requester and priority, then choose Create change request. Choose Dismiss if the message is not a real request.

Open request inbox

Review the formal record before work begins

Open the new change record and confirm the client, workflow, requested outcome, source, and requester. Assign the owner and due date when the next decision depends on them.

Do not treat a Slack message as approval. The approval decision is a separate lifecycle step.

Verify it worked

  • The request appears under Changes with status Requested.
  • The change record points to the correct client and workflow.
  • A client-link submission first appears in Request inbox and becomes a formal change only after a person confirms it.
  • A confirmed Slack draft disappears from the Request inbox and becomes a formal change request.

Common issues

No workflow can be selected

Choose Add a new workflow in the same form, enter its name and platform, then continue with the request.

I lost the full client request link

Open the client workspace and choose Replace request link. The old link stops working immediately, and AgentHub shows the new full URL once so you can copy it.

A client should no longer use the request link

Open the client workspace and choose Revoke request link. Future visits and submissions through that link stop immediately.

A client-link draft has no workflow to select

Add an active workflow for that client, then return to Request inbox and confirm the draft. The submission remains a draft until a workflow is selected.

No Slack drafts appear

Confirm the AgentHub Slack app is in the selected channel and that the channel is mapped to the correct client. Only likely requests from selected channels appear.

Ordinary Slack conversation was captured

Dismiss it. Human review is the filing boundary, and dismissal creates no change request.

The original request changed after it was filed

Keep the original request intact and record the new decision in the change lifecycle. If the scope is materially different, create a new request.

Related guides