Philippines staffing blog ·
Set a size limit policy for attachments that never arrive
A failed attachment is a chain of possible failures, so the desk needs a published limit, a tested alternative, and a record of what was received.

Direct answer
Operational guidance
Find where the attachment actually stops
An attachment that never arrives is not one failure but several possible ones. The file may exceed the mailbox limit, the portal may reject the type, the customer's own mail server may block it, or the desk's spam filter may hold it. Find the point of failure before changing the policy, because a size increase will not fix a blocked file type. Ask the customer for the exact error and the file size, and test with a file of the same shape.
Record the path the file took: sent, accepted by gateway, queued, scanned, delivered, or attached to the ticket. Each step has an owner and a different fix. A gateway log can show an accepted message that later failed a content rule. Without that sequence, the desk guesses and the customer resends the same file into the same wall. Keep that sequence in the ticket so the next agent does not repeat the diagnosis.
Publish the limit before the customer hits it
State the maximum attachment size and the accepted file types where the customer uploads or writes. A limit hidden in a help article that nobody reads is not a policy; it is a trap. Use the same number in the portal, the email footer, and the intake form. If the limit differs by channel, say so, because a customer who switches channels should know the rule changed.
Give the customer a way to check the size before sending. Most operating systems show it in the file properties, and a short instruction is enough. For large exports, suggest splitting the file into labelled parts or sending a link to an approved storage location. The aim is to keep the evidence while staying inside the channel's real constraints. A one-line tip on the upload page prevents most avoidable failures.
Offer an approved alternative path
Name one or two alternatives that the client has approved for files above the limit. A secure file-transfer link, a shared drive folder with restricted access, or a scheduled upload may fit. Check who can open the destination and how long the link lasts before publishing it. An alternative that exposes customer data to the wrong people is worse than a missing attachment.
Write the steps for the agent and the customer separately. The agent needs to know how to verify the file arrived and how to attach the evidence to the ticket. The customer needs a short instruction without internal jargon. Test the path with a colleague before a customer tries it during an urgent request in production. Two short guides are clearer than one page that tries to serve both readers.
Record what was received, not what was sent
Describe the attachment in the ticket even when the file is missing. Record the file name, the size the customer reported, the time it was sent, and the error message. A note that says customer will resend tells the next agent nothing about what was already tried. If the file did arrive later, record where it is stored and who confirmed it.
Do not claim the evidence is complete until someone has opened the file. A zero-byte file, a scanned image, or a password-protected archive can arrive successfully and still be unusable. Open the attachment and note whether the content matches the request. This step takes only seconds and prevents a wrong answer built on an unread file. An unopened attachment is a promise, not evidence.
Handle the ticket that cannot proceed
When the file is essential and cannot be delivered, tell the customer what will happen next instead of leaving the ticket open without a plan. Offer the approved alternative, give a deadline for the file, and explain what the desk can do if the deadline passes. If the request cannot be completed without the evidence, say so and record the reason. An honest stop is better than a ticket that ages for a week.
Set a review time for every ticket waiting on an attachment. At the review, check whether the customer replied, whether the file arrived through another channel, and whether the request can be closed or escalated. A waiting ticket with no review time becomes a hidden backlog. Put the review time in the queue view so a supervisor can see it.
Review limits after gateway changes
Mail gateways, portal releases, and endpoint filters change their limits without telling the support desk. Review the published numbers after any platform upgrade or mailbox migration. Send a test file just below and just above the limit, and record the result. The test is cheap and catches a mismatch before customers discover it during a busy week. Put the test on the calendar after every change, not only after a complaint.
Keep the limit table with the intake documentation and give it an owner. The owner checks the vendor documentation and the actual behavior, because the two can disagree. Update the customer-facing pages at the same time as the internal table. A limit that is correct internally but wrong on the website creates the same failed attachment. The table should show the date it was last verified against a live send.
Limits and a practical standard
No size policy can guarantee delivery across systems the desk does not control. A customer's mail server, a corporate filter, or a bad connection can still stop a file that meets every published rule. The desk can control the stated limit, the tested alternative, the evidence note, and the review time. Those controls make the failure visible and short instead of silent and long.
A practical standard is a published limit, a tested alternative, an attachment record, and a review time for every waiting ticket. Check the limit after each platform change and keep the test results with the policy. Train agents to ask for the error message rather than guessing at the cause. That habit turns a frustrating loop into a support conversation with a next step. Keep the test results with the intake guide so the next reviewer can verify the limit.
Authoritative sources
- Google Workspace: Send attachments with Gmail
- ISO 18295-1:2017 customer contact centres
- NIST SP 800-53 Rev. 5 security and privacy controls
- NIST Cybersecurity Framework 2.0