Skip to content

Make an Agent available to customers

A customer action connects Sherpa to a published EosHQ Agent. Each reached Skill must support the customer authorization contract.

Prepare the Agent

Build and publish the Agent in the existing Agent editor. Check its Skills, integrations and approval rules. An Agent being available to staff does not make it suitable for customers.

Bind the action

  1. Open Configuration > Support AI > Agent actions.
  2. Choose Add an action and select a compatible published Agent.
  3. Enter the customer-facing name and description.
  4. Define the input fields to match the Agent's input contract. Use clear labels and required fields.
  5. Choose the permitted result fields. Return only information safe for that caller.
  6. Set the verified-customer requirement and any allowed anonymous use.
  7. Set customer confirmation and staff approval requirements. Enter the allowed staff approval roles.
  8. Enable the action and save the binding to that Agent version.

Writes always require customer confirmation. An unchecked confirmation option cannot weaken that rule. A binding cannot remove an approval or verification requirement imposed by its Agent or Skills.

Test the result

Test with an allowed customer and a customer who should not have access. Check the proposed arguments, confirmation, approval state and final record scope. Do not use a live business-changing action as a casual test.

Publishing a changed Agent requires reviewing its binding again. Read uncertain outcomes before retrying a failed-looking business action.