Buyers shouldn’t spend their days chasing orders and vendors
Envoy reads the mailbox, matches what arrives to the order it belongs to, and writes the result into SAP.
70+%of admin time returned to buyers
Envoy gives buyers their week back: the judgement calls, the negotiations and the ideas.
Workflow builder in action
Handle order confirmations in the channel the supplier already uses
Confirmations land in the mailbox and the agent matches every field back to the PO: price, quantity, dates. It only surfaces the ones that moved.
When a confirmation contradicts the PO, push back with the contract term attached
When an invoice or confirmation breaks the PO, the agent finds the governing contract term and pushes back with the clause attached.
Chase every late order and write the new dates back into the ERP
Late orders get chased across suppliers, new dates are written back to the ERP, and only the ones that stay silent reach a buyer.
Match every invoice line against the PO and the goods receipt before it posts
Three-way matching runs line by line. Clean lines post themselves, small deviations clear on tolerance, real gaps go to the buyer with the numbers already worked out.
You approve once. The ERP is updated line by line, and every write is logged.
The agent works the supplier’s reply in your mailbox, matches it to the purchase order line it belongs to, and writes the new date into SAP. Nothing reaches the system of record before you release it, and every field it touches is recorded against your name.
Spot the next job worth automating, and build it yourself
How a new automation gets built
Describe the job in a sentence: what triggers it, what it should check, who decides. Envoy drafts it as a flow on the canvas — a trigger, the agent steps with their instructions, the approvals and the write-back.
You adjust it by talking to it or by moving the nodes, run it against real traffic once, and publish it into the library. Every operational workflow you deploy runs here: triggered, tracked, and escalated to a named person when it needs one. Every run is logged, and anything that needs a decision goes to a named person rather than into a queue.
What an agent can touch, and what it can’t
An agent is a name, a set of instructions in plain language, and a list of tools it may use. It can do nothing outside that list. You grant each tool with a toggle, so an agent that reads spend and drafts replies cannot post to the ERP unless you say so.
The tools are procurement-native rather than generic: write back to SAP or Coupa, look up a price index, pull a contract down to the clause that governs it, mail a supplier and read the reply, route an approval by threshold, read three years of spend history. Most teams leave one off on purpose: sending mail from the agent's own address. Every outbound message still passes a person first.