No. A sent message alone does not establish acceptance. On November 13, Maersk reported delayed intake of some customer emails into its case system and advised using established phone or chat channels for urgent requests. That does not establish an outage today, but it illustrates why cutoff-sensitive work needs confirmation.
Check the agreed submission route. A portal receipt might mean upload, case creation or final acceptance. These are different outcomes. A file in a queue can still be rejected for missing information.
Near a cutoff, use an official contact and provide the reference, original send time, request and deadline. Refer to one final version. Do not let several colleagues submit competing copies or send sensitive documents to an unfamiliar address. Link the new case to the prior message and resolve what should happen to the duplicate.
If a buyer requests a consignee correction in the final hour, report that it has been sent but is not yet accepted. Find out whether missing the cutoff would affect the sailing, require an amendment or allow a later action. Do not promise the original schedule from an email timestamp.
The buyer needs the deadline and the current outcome, not a detailed diagnosis of the email platform. If a case exists but acceptance is pending, agree when to decide whether to defer or rebook. Refer to the exact shipment so a similar customer name does not lead to the wrong case.
Keep sent, received and accepted as separate milestones. Record the time and next owner so a shift handover does not convert a pending request into a completed action.