At 7:15 on a Tuesday the inside sales coordinator at a sixty-person machine shop opens the sales inbox. Thirty-eight emails came in overnight. She reads each one. Eleven are requests for quote, most of them two lines of text and a PDF drawing. Nine are customers asking where an order is. Four are quality complaints or return requests. Six are supplier invoices and order confirmations that a buyer forwarded to the wrong address. Eight are newsletters and vendor marketing. For each real one she opens the attachment, looks the customer up in the ERP, decides whether the quote belongs to the estimator who does milling or the one who does fabrication, checks the schedule before answering a status question, forwards the complaint to the quality manager with the order number typed in by hand, and drags the invoices to accounts payable. Two of the RFQs sit in the wrong estimator's inbox until Thursday.
Every email in that inbox is three questions
The first is what this is: a quote request, a status question, a complaint, a bill, noise. That is classification, and it is the part software has become good at. The second is who should get it. That is a routing table: which estimator covers which process, which rep owns which account, who handles returns. It is the company's own rule and it changes when people change. The third is what the person who gets it needs in order to act: the customer's open orders, the last quote on this part number, whether the account is on credit hold, the due date buried in the drawing's title block. That is a lookup across the ERP and the quoting system, and it is what the coordinator does in her head in the ninety minutes between 7:15 and 8:45.
What Microsoft shipped, and what it leaves
Microsoft's roadmap lists email classification in Dynamics 365 Customer Service with the status "Launched", a "Rollout start" of August CY2026 and a release phase of "General Availability". Administrators define their own categories and subcategories, each with a name and a description, and set conditions for which emails are classified, such as specific mailboxes, sender domains or languages. The AI reads the subject and body of each inbound email and stores the category on the email record, where record-creation rules, Power Automate flows, the Case Management Agent and reporting can act on it. Microsoft's stated aim is to sort out thank-you notes, newsletters and spam and let its agent handle routine issues. Only Microsoft's own account of this feature was available; nothing here has been independently confirmed. It extends an earlier version: Microsoft announced a flat-list version as generally available on its Dynamics 365 blog on June 3, 2026, and a Microsoft message-center notice dated August 6, 2026 scheduled the category-and-subcategory version for general availability on August 21, 2026. The change is the hierarchy.
So question one is answered, for companies running Dynamics 365 Customer Service. The category is a stored value; where the email goes, and with what attached, is left to rules and flows that somebody builds. The description mentions the subject and body; it says nothing about attachments, and in a machine shop the drawing is the request. It says nothing about looking the sender up in an order system. And the categories, with descriptions good enough for software to apply, are the business's to write.
What would have to be built
Start with one page listing the shop's categories, the owner for each by customer and process, and what counts as urgent (a due date inside ten days, a top-twenty account). If that page cannot be written, nothing below it can be.
Then the reader. It takes each inbound email with its attachments, pulls the customer name, part numbers, quantities and dates from the body and from the PDF, and applies the categories on the one page.
Then the join, which is the part that is yours alone. With a customer and a part number in hand, look up the open orders, the last quote and its price, the account owner and the credit status in the ERP and the quoting system, and write a three-line brief: who they are, what they have open, what they are asking. The brief and the original email, attachment included, go to the named owner.
Then the exceptions queue, which is where the coordinator's job moves: emails that fit two categories, senders not in the ERP, RFQs with no part number, and anything the reader scored as uncertain. Nothing off the shelf that we found does this join against a small shop's own ERP and its own routing table; shared-inbox tools route on sender and keyword rules, and Microsoft's version lives inside a service application built for support teams.
The genuinely hard part
The attachment is the message, and extraction from a drawing's title block or a customer's homegrown PO format is unreliable in a way that body text is not; a wrong quantity in the brief is worse than no brief. And misrouting is silent. A wrongly classified RFQ does not raise an error; it sits in the fabrication estimator's inbox until the customer calls on Thursday. The build has to measure itself, which means someone has to count the misroutes each month.
Who will resist, and why they are right
The inside sales coordinator will, and she is right. She catches the line in the postscript that says the bracket is also needed by Friday. She knows the buyer at one account always undercounts and the one at another sends three unrelated requests in one email. She is the institutional memory the routing table pretends to encode. She will keep reading every email anyway, so you have added a step rather than removed one. The estimators will resist on the first wrong brief and go back to reading the raw inbox. The design that answers both is to make her the owner of the exceptions queue and the monthly misroute count, so the system is hers to correct, and to send the brief with the original attached so a wrong brief costs a glance, not a quote.
The honest no: below a few dozen inbound emails a day, one person reading the inbox for twenty minutes each morning is cheaper than anything described here, and she catches nuance a classifier misses. If the routing page cannot be written, there is nothing to build; write it first. And if the ERP does not hold customer part numbers consistently, the join has no key, and that discipline comes first.
If this is your Thursday afternoon, the ten agent roles are in the Library.