Start with the missing supplier reply

Imagine a buyer starting a shift with delivery confirmations still missing. The purchase orders are in the ERP, supplier replies are in email, and the planner has a separate shortage list. Give the first agent one job: gather the latest evidence for an order line, flag a missing or conflicting confirmation, and prepare a follow-up. Leave changes to the production schedule with the people who make that decision.

Decide where that job ends. An email draft saves little work if the buyer still has to find the supplier, locate the order and correct the quantity. Aim for a follow-up the buyer accepts, linked to the right order line, or an unresolved question assigned to someone. Look through recent cases with the people doing the job. Keep the examples they disagree about: those show where an agent will need help.

Write three lists: information the agent may read, drafts it may prepare, and changes that need approval. For this first pilot, reading an open order and drafting a reminder are useful limits. Leave changes to delivery dates, quantities or supplier commitments out until you have designed their approval and recovery steps. Machine commands and decisions to release a quality hold stay outside the example in this guide.

UiPath describes processes that wait for approval and resume afterward. Relevance AI lists approval rules for individual tools and rules that apply under specified conditions.^1,2,3

Have the supplier show those rules at work. Add a forbidden change to an otherwise valid request. You should receive a useful draft or a case passed to a person, while the forbidden change stays untouched. Then open the receiving system and check the record. A chat message saying the agent stopped is only part of the evidence; the purchasing record must agree with it.^1,2,3

Give the pilot cases where a near match is not good enough: a revised purchase order, two lines for the same part, a split shipment and a reply without an order number. Note which system owns each value and how to recognize the latest revision. When even the buyer cannot tell which value is authoritative, the agent should leave a visible question instead of quietly choosing one.

Workato documents connections to ERP systems and databases, plus an on-premises gateway. Google documents a federated BigQuery connector.^4,5,6

For every connection, ask to see a sample record, the available actions, the account used and how current the information is. Querying a warehouse may answer a question without providing a way to update the ERP. Reaching a system through a gateway does not establish where model requests or logs go. Write both answers down, so everyone knows what the supplier means by an integration.^5,6

Nexus says it builds the first procedure with the customer and continues improving it. Relevance AI describes an embedded team followed by training. Microsoft provides tools for building agents and approving releases.^7,8,9,10,11

Match the offer to the people available. A plant with no spare builders can compare services that help with implementation. A Microsoft team may prefer its own existing release process. Either way, someone in operations must decide whether the supplier reply is acceptable. Name the people responsible for supplier master data, connection changes and unanswered cases before comparing launch dates. Otherwise, that work can remain unassigned even after the software is bought.^7,9,10,11

Here is a proposed brief to adapt. Start when an open order lacks an agreed confirmation. Read the current order line and authorized supplier correspondence. Produce a follow-up draft with its sources, or assign the unanswered question. Allow the agent to save the draft. Prohibit changes to quantities, quality holds and promised production dates. Name the buyer as approver and keep the manual expediting list as the fallback. Add your actual systems, evidence owners and examples of acceptable work.

Proceed when the team can identify the records it trusts, show the allowed steps and give every exception an owner. Keep the pilot to reading and drafting if permission to write is still unresolved. If nobody owns the data or can agree what a correct result looks like, repair that process first. The buying decision should leave fewer unanswered operating questions, not hand those questions to an agent.