Skip to main content
Agents help your team work through customer requests. The current workflow families are Intake, Quoting, and Order Status. Which ones you can use depends on your organization’s configuration and your permissions. Start with the quickstart, then follow the information through the workflow:
  1. Data sources: what the agent can rely on.
  2. Integrations: how information moves between systems.
  3. Agent context: what a particular run needs to know.
  4. Actions and permissions: what can happen and who has access.
  5. Approvals: what a human must review before proceeding.
  6. Workflows: how those pieces fit together.
  7. Results, lessons, and evaluations: how to check and improve outcomes.

​
Where to start in the portal

Open Agents in the merchant workspace. Where the updated Agents interface has been deployed, the Overview tab explains these concepts and links to the full guides here, while Workflows keeps the operational workspace separate from the learning material. If your workspace does not yet show these tabs, use these documentation pages directly and keep using the existing Agents workflow workspace. Publishing these guides does not deploy the application update. Viewing Agents requires agents:view; managing workflow configuration requires agents:manage. Account capabilities and workflow availability also apply. A missing feature is not an invitation to work around access controls: ask your organization owner or account team to check access.
These guides describe the product, not your account’s current connection or deployment status. A listed workflow, integration, or document does not prove that it is enabled, connected, processed, or approved for your organization.

​
One example, end to end

A customer asks for a quote on a specified material. Identify the request and the relevant product records, check the connection through which the request arrived, and supply the workflow with the right context. Inspect the proposed action and its commercial evidence. Use the workflow’s supported approval step before any gated action proceeds. Finally, check the actual result, record errors with sources, and evaluate a correction before relying on it more broadly. The walkthrough uses examples, not promises that every step is automated or that every integration supports every action.