Workspace conversation
Bring questions and actions into a conversational workflow.
AMS · Connected business workflows
Use a conversational assistant to help with the AMS work you are authorized to access.
Signed-in teammates who want help finding or working with records they are permitted to access.
You remember the work you need but do not want to reconstruct where it sits in the workspace.
Fictional example: a teammate asks, “Find the Autumn launch project,” and sees an illustrative accessible result. This website example makes no live changes.
The user can start with a plain-language request and inspect the relevant workspace context.
Ask for help in the context of the workspace, with tools governed by existing permissions.
Bring questions and actions into a conversational workflow.
Registered product tools give the assistant structured ways to work.
Tool availability and execution follow the relevant resource permissions.
Supported tools can point back to the relevant part of AMS.
Use the AI provider configured for your workspace.
The assistant supports workspace work; brand agents handle configured customer-facing duties.
Some exposed tools can make changes. Available operations and any required confirmations follow the tool, your permissions and workspace configuration; a chat response alone is not proof that an action completed.
No. The response is an illustrative website sample. Real assistant use requires a configured AI provider and the relevant access; usage charges and quotas depend on the setup. Customer conversations use the separate brand-agent workflow.
AI needs a configured provider. Available tools vary with permissions and configuration. The visual is a website explanation, not a recorded assistant execution.
Read how each connection helps before choosing whether to open another page. Moving between tools does not itself configure an automatic handoff.
Continue in the project or task once you have identified the relevant work.
Give every task an owner, a deadline and the context to move forward.
Fictional example: Nour moves the Autumn launch creative brief from In progress to Review.
Available views and actions depend on your access. Time tracking and automations require an eligible paid plan.
Optional: explore the full Projects & tasks story ↗Understand the access that constrains available tools and records.
Control who can act, which project details they can change and what data they can see.
Fictional example: compare the displayed Project manager matrix with a Member view and assigned-record scope.
The displayed role matrix is an example, not the default of a named system profile. Access follows the configured project snapshot and applicable organization controls.
Optional: explore the full Permissions & scopes story ↗Choose a brand agent instead when the job is assisting customer conversations.
Give a brand agent the context to help with conversations and choose how it behaves on each channel.
Fictional example: the Autumn collection guide supports Instagram suggestions, while WhatsApp remains Off.
AI requires a configured provider; availability, quotas and provider charges depend on your workspace setup. AI responses can need correction. Auto mode is an explicit configuration, not the default behavior demonstrated here.
Optional: explore the full AI agents story ↗