Begin with a narrow responsibility
Define a specific job before automating an entire sales conversation. For example, the agent might ask for missing dimensions, summarize a brief, or prepare a revision for review. Give it access to the information required for that job and describe what it should do when the answer is missing.
Connect responses to approved information
Product suggestions should refer to the catalog used by the sales team. Price and delivery answers need an identified source. When those sources disagree or are out of date, the workflow should flag the issue instead of manufacturing certainty. Write down which promises the agent is allowed to make.
Make revision requests explicit
A customer asking for “something cheaper” has not necessarily approved a new product. Ask which constraints can change: finish, model, quantity, or delivery timing. Have the agent summarize the proposed change and its effect on the quote before the revised version becomes the basis for an order.
Evaluate the workflow with realistic examples
Test incomplete briefs, contradictory requests, unavailable items, and discount exceptions. Review whether the agent asks useful questions, preserves the customer’s requirements, and hands off at the right point. Track corrections and unresolved cases, not just the number of messages sent. Expand its role only when the narrower workflow behaves as intended.