Order enquiries often combine two different needs: a current fact from the order system and an explanation of what that fact means. Chatropic can bring those together when the order lookup, identity checks, and supporting policy content have been configured. This article uses a fictional order to explain a read-only enquiry. Address changes, cancellations, and refunds are separate operations and need their own permissions and tests.

​
Prepare the order lookup

Identify the system that holds the current order record and the endpoint the agent may use. Confirm who owns the integration, how credentials are managed, and which fields the customer is allowed to see. Decide how the customer’s relationship to the order is established. Your engineering and policy owners should test that one customer cannot retrieve another customer’s information.

​
Add the policy that explains the result

The API can return a status such as “Awaiting dispatch.” Your knowledge content should explain what that means and the approved next step. Keep changing facts in the connected system. Do not store a delivery estimate in a general policy article and treat it as the current estimate for every order. A date should come from an approved source for that request.

​
Follow a customer conversation

A fictional customer asks, “Where is order CH-2048?” The agent follows the configured verification process and calls the permitted lookup. The returned record says “Awaiting dispatch.” The agent explains that status using the approved delivery policy. If the record contains a supported next update or estimate, it can explain it. Otherwise, it should avoid inventing a tracking number or arrival promise. If the customer disputes the result, the workflow should follow your escalation policy rather than repeat the status as if it settled the issue.

​
Test missing records and failures

Include a valid order, an incorrect reference, an unauthorized request, a delayed order, and an unavailable service. Check both the returned data and the wording the customer receives. A failed lookup should lead to clarification or handoff. It should never be described as a successful check. Make sure your support team can inspect what was attempted when it receives the case.

​
Decide when to add actions

A read-only enquiry can establish whether the connection and conversation work well. Add changes to orders only after defining eligibility rules, confirmation requirements, and failure behavior for each operation. Use the integration guide to prepare the system details for your technical owner or a tailored demo.