Connected tools
Give the agent explicit connected actions for requests that require an external system.
Use a test channel or sample conversation first. Confirm the visible result in ValueChat before applying the setup to production traffic.
How it works
- 01
When to use
When to use. A customer request needs an external result or action, such as a permitted store lookup.
- 02
Set up the tool
Set up the tool. Add an available tool, choose its saved connection, name it clearly and enable it. Credentials remain in protected connection settings.
- 03
Example instruction
Example instruction. Use this order lookup only when the customer provides the required identifier. Ask for missing information, then report the actual lookup result.
- 04
Context and targets
Context and targets. Use $ for permitted contact values and @ for supported linked targets or knowledge bases. Writing an unsupported action in instructions does not create a new tool.
- 05
What happens
What happens. The model requests an available action; the application validates and executes it using the selected connection, then returns the result.
- 06
Remove and verify
Remove and verify. × removes only this agent’s tool binding, not the shared connection. Save to apply changes and use the agent preview to inspect action results before testing customer traffic.
What to verify
✓The expected channel, conversation, contact or execution is visible.
✓The assigned person or agent matches the routing rule.
✓No customer-facing message claims an action that failed.
✓Activity or execution history contains enough context to investigate.
Collect the workspace, channel, conversation and execution identifiers, then contact support@valuechat.app. Never send API keys or passwords.