Email deliverability for manufacturers and engineering suppliers.
When a buyer misses a quotation or your estimating team cannot find an RFQ, another chase can hide the underlying problem. Neotiqa helps you investigate email across staff mailboxes and ERP systems, establish what happened to the affected message and give your IT and software providers a clear next step.
- What does a manufacturing email-deliverability assessment cover?
- It establishes the sending route and available evidence for the business messages in scope, from staff correspondence to ERP-generated quotations and order confirmations. Neotiqa provides a read-only assessment with prioritised findings and a technical handover. Configuration changes, workflow implementation and ongoing monitoring are agreed separately.
First establish which part of the enquiry-to-order process failed
Separate four questions: was the right document generated, was an email sent through the expected route, did the receiving system accept it, and could the intended person access the document? A missing email, a missing attachment and a drawing link that will not open need different checks.
A request for quotation, or RFQ, arriving from a customer is an incoming message. Your quotation back to that customer is an outgoing message. Record the direction and the responsible system before asking either administrator to investigate. If a deadline is close, use an established contact route while the technical work continues.
RFQs, quotations and order confirmations need different evidence
| What your team sees | The useful next question | Who can provide evidence |
|---|---|---|
| A customer says they sent an RFQ, but estimating cannot find it. | Which address received it, and did the receiving system accept, filter or route it elsewhere? | Your mail administrator, with the customer’s sending details and the agreed enquiry owner. |
| A quotation exists in the ERP, but the buyer has no email. | Was the document generated for the correct contact, and was an email actually queued or sent? | The sales or estimating team and ERP provider, followed by the mail administrator for the identified route. |
| The buyer receives a quotation without the expected drawing or revision. | Which document version, attachment or link was included in that exact outgoing message? | The authorised document owner and application owner, using the quotation reference and revision. |
| The email arrives, but the drawing link cannot be opened. | Does the intended recipient have the required access through the approved sharing method? | Your IT or document-system provider, using the recipient identity and actual access result. |
| The ERP records an order, but its confirmation is missing. | Did the confirmation workflow generate a document and submit an email to the correct contact? | The order-processing team and ERP provider, with sending and receiving evidence where available. |
Why an Outlook reply can arrive when an ERP quotation does not
The ERP message may use a different account, connector, template or sending service from the staff email. A successful Outlook reply is useful comparison evidence, but it does not verify the quotation’s route. Start with one affected message and identify the account, recipient, time and application event.
For example, Microsoft’s Business Central email documentation (opens in a new tab) distinguishes its Microsoft 365 shared-mailbox connector, Current User connector and SMTP connector. Email scenarios can assign different accounts to different document categories. Your ERP provider should confirm the connector and scenario used by the affected document, rather than assume that every message follows the same path.
Business Central can email sales quotes as PDFs and resend revised quotes (opens in a new tab). Keep the quote reference and revision alongside the message evidence. The document record and the email outcome answer different questions.
IFS Cloud 25R2 provides another documented example. Its quotation email (opens in a new tab) and order-confirmation email (opens in a new tab) workflows depend on document generation, PDF events, routing and customer contact settings. Ask the IFS provider to check the installed version and applicable workflow before treating a missing confirmation as recipient spam filtering.
These are product-specific examples of why the route matters. Neotiqa scopes the email investigation with your existing providers. For the message evidence to request, use our guide to reading email headers and identifying the sending service.
A delivered email does not prove the right drawing was available
Check the actual outgoing message and the authorised document revision. A file stored against an ERP record is not proof that it accompanied the email. Microsoft’s Business Central attachment guidance (opens in a new tab) explains that users select document attachments when emailing, and that this action does not select files attached to document lines.
A sharing link adds a separate access question. Microsoft’s external-sharing guidance (opens in a new tab) distinguishes links for specific recipients from links that others can forward. Have the system owner check the intended recipient and approved permissions rather than making the file public to get a test through.
Your engineering or document owner remains responsible for drawing correctness and revision approval. ERP remediation, file-format compatibility and sharing-policy changes belong with the relevant provider unless separately scoped. Keep confidential drawings and customer records out of the initial enquiry.
Keep these outcomes separate
- The quotation or confirmation was generated
- An email was submitted to a sending service
- The receiving system accepted the message
- The intended person could access the right document
- The customer accepted the commercial offer
Illustrative example: the sales reply arrives, but the quote does not
In this fictional example, an engineer receives an Outlook reply from the supplier, but cannot find the revised quotation sent from its ERP. That difference is a starting point, not proof that the ERP or Microsoft caused the failure.
The estimating team confirms the quotation reference, revision and intended buyer. The ERP provider checks the document event, selected sending account and queue outcome. The mail administrator then looks for the matching submission and, if it was accepted, works with the receiving administrator to locate that message.
If the message is found but its drawing link fails, the next action moves to authorised document access. If no message was generated, changing DNS or asking the buyer to allowlist the domain would not address the observed failure. The handover names the confirmed stage, the remaining unknown and the owner of the next check.
Useful evidence to agree
- Message type, direction and business impact
- Document reference and approved revision
- Sending system, actual recipient and time zone
- Recorded error, queue event or recipient finding
- A comparable successful message from the same route
Get a focused assessment alongside your existing providers
Work directly with Peter Black to define the email question, the available evidence and the people who can act on the findings.
Agree the affected route
Define the messages, systems, access, evidence-sharing method and outputs. Your sales or estimating team explains the business impact, while IT and the ERP provider identify the systems they own.
Investigate without changing production
Compare the agreed application events, authentication, sending evidence and supplied message examples. Keep observations separate from assumptions, with recipient-side checks requested where needed.
Receive findings and next actions
Get prioritised findings, evidence gaps and a technical handover with responsibilities and verification steps. Implementation or ongoing support is separate agreed work.
Match the support to the problem
Start with an email deliverability assessment when messages go missing, reach junk or take an unclear sending route. If messages arrive but enquiries need better CRM routing or follow-up ownership, GTM engineering may be a separate scoped project, subject to supported integrations and feasibility.
You work directly with Peter Black, with remote support for UK manufacturers and engineering suppliers. Your team retains the customer relationship, technical document approval and production decisions.
Practical guides for the systems behind the message
Plan a deliverability assessment
Agree the evidence, access and outputs before starting an investigation.
Read the assessment checklistMicrosoft 365 emails going to spam
Separate sending-side checks, recipient filtering and messages from connected applications.
Read the Microsoft 365 guideGoogle Workspace email checks
Identify the sender, authentication and recipient-side evidence for Workspace messages.
Read the Google Workspace guideMissing invoices and reminders
Follow the billing route when the problem affects invoices rather than quotations or order confirmations.
Read the invoice email guideQuestions from manufacturing and engineering teams
Why do quotation emails go to spam when ordinary emails arrive?
The quotation may use a different account, sending service, template, attachment or link. First confirm whether it was sent, rejected, filtered or received without the expected document. Compare evidence from the affected route before changing authentication or recipient settings.
Can you investigate missing RFQs as well as outgoing quotations?
Yes, within an agreed scope. A customer RFQ is an incoming message, while your quotation is outgoing. Each may need evidence from different administrators. We agree which route and evidence are available before the assessment starts.
Do you work with our existing IT and ERP providers?
Yes. They retain control of their systems and product-specific changes. Neotiqa investigates the agreed email-delivery question and supplies findings and next actions. General ERP implementation and engineering-document validation are outside the assessment.
Does a sent order confirmation prove the customer received it?
No. A document status, an email submission, receiving-system acceptance and the person reading the message are separate observations. Keep the order reference and message evidence together, and use your normal commercial process to confirm acceptance.
Can you help when an email arrives but its drawing link does not work?
We first separate successful email delivery from document access. Your IT or document-system provider may need to check the intended recipient, sharing settings or file compatibility. That is a different question from inbox placement, and any further work is scoped accordingly.
Will you need confidential drawings or customer specifications?
Not for the initial conversation. Describe the message type, systems and observed problem. Before work begins, we agree the minimum evidence and an appropriate sharing method with you, rather than asking for confidential drawings, credentials or unredacted customer messages through the public form.
Do we need to replace our ERP or email provider?
The assessment starts with your existing setup. Any system change needs evidence and a separate agreed scope. We do not guarantee inbox placement or assume a replacement is necessary.
Last reviewed 7 November 2026. Service descriptions are general. Every engagement has a written scope.
Which quotation or order email keeps needing a second chase?
Tell us which messages are affected, which email and ERP systems you use, and what the sender or recipient has observed. We will discuss a focused assessment with the people who manage those systems.