The short answer
You are a highly trained Technical Support Specialist. You troubleshoot complex system anomalies and structural failures. You are absolutely not a free data entry clerk for a lazy, disorganized client. When a Tier-2 account floods your technical queue with basic password resets and simple CSV formatting errors, they are aggressively exploiting your Service Level Agreement to avoid doing their own basic administrative work. You must halt this behavior immediately. State directly and without apology that manual data formatting and basic credential management fall completely outside the scope of technical support. Redirect them forcefully to the self-service knowledge base. Require them to purchase a paid training package if they refuse to learn how to format their own data correctly.
Why this question is a trap
The client is actively treating your highly paid support desk like an outsourced administrative assistant pool. They have quickly realized that filing a lazy ticket is significantly faster for them than reading the documentation or formatting a spreadsheet correctly on their own time. This is a dangerous, systemic operational drain on your entire department.
If you continue to quietly solve these basic tickets to be helpful, you deeply penalize your other clients. Your response times for actual, critical technical emergencies will plummet because you are too busy fixing commas in a client's CSV file. You are directly subsidizing the client's operational incompetence with your own valuable technical bandwidth. The client will never learn the system. They will remain perpetually dependent on your free labor. You must actively break this cycle of learned helplessness. You must force the client to assume total responsibility for their own basic platform administration. Guard your queue.
What most people say
Most Support Specialists hate confrontation and deeply fear receiving a bad customer satisfaction score. They prefer to quietly fix the CSV file because it only takes five minutes, rather than spending ten minutes arguing with the client about proper formatting rules.
They reply to the ticket with extreme, sickening politeness. They say things like, "I went ahead and fixed the formatting for you this time to get you moving, but please try to follow the template next time!" The client completely ignores the plea. They submit another horribly broken file the very next day. The Specialist sighs heavily, fixes it again, and complains to their manager in a private Slack channel about the annoying client. This passive, conflict-avoidant approach completely fails to enforce the commercial boundaries of the support contract. It ensures the repetitive support overhead will continue indefinitely until the Specialist burns out or the department loses money.
What to say instead
Close the ticket immediately without fixing the file. You must prioritize client enablement over client accommodation.
Reply to the client stating plainly that the submitted CSV file fails the standard system validation parameters. Provide the exact link to the formatting documentation. Tell them they must update their file according to the strict specifications and re-upload it through the self-service portal. State with absolute clarity that the technical support desk does not provide manual data manipulation services. Do not do the work for them. If they reply and claim they do not understand the documentation, offer to connect them directly with their Account Executive to purchase a dedicated, paid administrative training package. Monetize their incompetence.
The phrase to anchor on
The necessary phrase to memorize is recurring support overhead.
This terminology elevates the issue instantly from a minor personal annoyance to a systemic, highly expensive operational problem. You use this precise phrase internally and externally to clearly define the boundary. You inform the client that manual data formatting creates unsustainable recurring support overhead that falls entirely outside their Tier-2 SLA. It is a structural, business-based rejection based on departmental capacity, not a personal refusal to assist.
How to deliver it
Deliver the strict boundary in writing with absolute precision. Use short, declarative sentences. Do not use exclamation points to artificially soften the message or sound friendly.
Do not use the word "unfortunately" when stating that you will not fix the file. You are not unfortunate; you are enforcing a contract rule. Bullet point the exact technical errors in their file so they cannot falsely claim they do not know what is wrong. Provide the link to the self-serve portal. Close the ticket immediately after sending the response. Do not leave the ticket open waiting for them to argue or negotiate. Force them to open an entirely new ticket if they have a legitimate technical question. Control the ticket lifecycle.
Mistakes that cost you the room
The biggest and most common mistake is fixing the file "just one last time" to clear the queue. There is never a last time. If you fix it, you own the behavior forever.
Another severe error is apologizing for the perceived complexity of the CSV template. The template is not complex; the client is simply refusing to follow basic instructions. Do not validate their laziness by agreeing that the system is slightly hard to use. Stand absolutely firm on the requirement that basic data hygiene is the client's sole responsibility. Your job is to ensure the software processes valid data correctly, not to clean the garbage data before it enters the system.
Practice plan
This drill involves practicing structural refusal in written communication. Draft a macro response template for basic data errors right now. Review it brutally to ensure all apologetic, hedging language is removed completely.
Practice reading the template aloud. Make sure it sounds firm, highly professional, and utterly unyielding, not petulant or annoyed. Rehearse the follow-up response for when the client inevitably complains to their Account Manager about your lack of helpfulness. Stand your ground internally. Defend your highly technical capacity against administrative exploitation. Please be aware that this guide is a rehearsal mechanism strictly for communication scenarios. Talk Rightly does not offer formal HR or employment counsel.