Read conversation context
Allow an agent to inspect its current conversation context through a defined local tool.
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
Purpose
Purpose. The Conversation details tool provides context for the current account/conversation so the agent can reason about the existing customer and assignment rather than inventing identifiers.
- 02
Scope
Scope. This is a local read operation for the active conversation. It is not a global customer-search API or permission to inspect another workspace.
- 03
Usage
Usage. Explain when the agent needs the context and combine it with explicit field-update or handoff skills for actions. Reading information does not itself modify the contact, state or assignee.
- 04
Private context
Private context. Team notes can inform the agent through the configured context path, but they remain private notes. The agent must not copy internal discussions or tool credentials into a customer reply.
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.