What happens between an emailed quote request and a sent Business Central quote — one queue, identity, line matching, supplier choice and review — and where Sales Order Agent stops.
Microsoft ships an agent inside Business Central that reads an emailed request and creates a sales quote. This is the whole eight-step process underneath it, what Microsoft documents as going wrong, and why explaining a match is not the same as ranking which line to check.
Ordered by chapter. Each post stands alone but builds on the one before it.
A distributor with four inbound channels has four queues and no answer to "what have we not replied to yet". The fix is not a faster reader — it is one queue where every request shows how long it has been waiting.
A price list, a contract price and a quantity break all hang off the customer record. Until a request resolves to a customer, a line can only be quoted at list — and Business Central's own agent matches identity on one field.
A deadline, a job reference, a question and a signature block all name products and quantities. Send them to a catalogue and you get order lines nobody asked for — and a delivery date that vanishes without trace.
The message that changes something is almost always the second one. A correction names a product and a quantity, so every product test fires on it — and applying it as an order line is how a customer's change disappears while the quote still looks right.
The honest answer is a line that says it matched nothing. Microsoft documents its own agent returning a washing machine for washing powder — the failure is not the miss, it is the confident near-miss that reaches the quote.
Two lines can both look certain while one was a coin toss between catalogue entries differing only in supplier. What separates them is how the match was found, how far ahead of second place it finished, and which attribute made it the right item.
The right item at the wrong quantity is worse than no match at all, because the item is visibly correct and nobody checks. Microsoft documents its own agent returning 2,000 grams for 2 kilograms and a price of zero that means "not calculated".
The saving is not that a machine read the request. It is that a person reviews three lines instead of forty — which only happens if something tells them which three, and per-line uncertainty is that mechanism.
The supply decision sets the cost the margin sits on, so it belongs inside the quote. Business Central's agent checks inventory and promises dates — across four pages it never compares who to buy from, at what cost, at what margin.
Three writes are worth having: the quote, the customer's own names for your products, and a new customer record. Stock quantities, financial postings and records it did not create are the line — and volunteering that line is what makes the access conversation short.
Microsoft publishes the boundary of its own quoting agent in unusual detail — the channel, the line cap, variants, records it will not create, and pricing it will not discuss. Every limit here is quoted from Microsoft's own documentation.
Not a contest — a sorting exercise. Business Central's agent handles the clean Exchange request from a registered contact under fifteen lines. This is how to tell which of your requests that describes, and what the rest need.
Five situations where this is the wrong investment, the cheaper fixes to try first, and an honest account of what nobody in this category can yet prove about win rates.