Sales orders
Orders written straight into the body of the email.
SalesEnact turns the order emails your customers already send into NetSuite sales orders ready for review. Your team checks each draft and posts it, so nothing reaches NetSuite without your approval.
Five stages, the same every time, with your team at the end.
The customer's order arrives by email.
Threats and hidden instructions are caught before the agent reads the email.
The customer, products, quantities, pricing and order details are identified.
The order is drafted in NetSuite.
Your team checks the order and decides whether to post it.
Your customers keep emailing orders the way they do today: in the body of a message, as a PDF, or a mix of both. Nothing changes for them.
Customers don't need to change how they order.
Hi, please can you send the attached for the Leeds site. Same valves as last time, and we need it by Thursday.
PO 4471.pdf · 142 KBSpoofing, phishing and hidden instructions are caught and held before the agent reads anything. Only clean email reaches the next stage.
SalesEnact reads the thread and its attachments and works out what the customer means before anything is drafted: the account, the products, the quantities, the delivery and the price level.
"…send the attached for the Leeds site. Same valves as last time, need it by Thursday."
SalesEnact builds the NetSuite sales order with the right customer, items, quantities, pricing and address. If something is unclear, it flags it for your team instead of guessing.
The agent drafts. Your team posts.
| Item | Qty | Rate | Amount |
|---|---|---|---|
| 15mm isolating valve | 20 | £3.10 | £62.00 |
| 22mm copper tube 3m | 10 | £14.80 | £148.00 |
| 150L unvented cylinder needs attention | 1 | — | — |
Every draft lands in a review queue. A person checks the customer, products, quantities, pricing and delivery, resolves anything flagged, then approves. Posting to NetSuite is their decision.
SalesEnact handles the repetitive work. Your team makes the final decision.
One order, all the way through. Nothing is posted until your team approves it.
A customer emails their order.
Checked for anything malicious.
Customer, lines and pricing identified.
A NetSuite sales order is populated.
Your team checks and approves.
The order is posted to NetSuite.
Because not every customer sends an order the same way.
Orders written straight into the body of the email.
Purchase orders contained in an attached document.
Requests read and drafted as a NetSuite quote.
Scans, spreadsheets and supporting documents.
Each customer's own layout, shorthand and codes.
When something doesn't look right, SalesEnact doesn't guess. It drafts what it can, flags the rest and holds it for a person, with the reason shown.
Line 3: product code not recognised. Held for a person to confirm, rather than drafted wrong.
SalesEnact slots in front of NetSuite. Your customers, your NetSuite and your fulfilment process stay exactly as they are. The manual retyping in the middle is what goes.
The repetitive work is handled; the decisions stay with your team.
Malicious and suspicious email is held before the agent reads it.
A person approves and posts every order. Nothing reaches NetSuite unattended.
Anything unclear is flagged with the reason, never guessed.
A scoped bundle you install and can revoke; the agent only drafts.
Every draft, approval and post is recorded against the original email.
More for IT and finance on the security page.
Book a demo and we'll show you what SalesEnact would do with the kinds of order emails your team handles, next to what your team posts today.
We use one necessary cookie to remember this choice. With your consent we also use Google Analytics, and load Google Maps on our contact page. See our privacy notice.