Why is tech support doing project work without extra pay?
Technical support staff are being pulled into project implementation and scope creep without a role change, pay bump, or clear departmental boundaries. Because incoming standard tickets and project requests get blurred, staff are forced to absorb extra workload without the necessary capacity or staffing.
Core Friction Pattern
Analysis of 2 peer accounts across online developer and community forums reveals that “Why is tech support doing project work without extra pay?” repeatedly surfaces due to edge-case mismatches between standard defaults and real-world environments. Standard troubleshooting frequently falls short, compelling practitioners to develop custom workarounds.
+5 alternative community-tested workarounds cataloged below.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
Why is tech support doing project work without extra pay?
- 1Querying management about why tickets are being transferred incorrectlyDid this help you?
- 2Documenting project work performed on support tickets to use as evidence for a raiseDid this help you?
- 3Pushing back on lack of capacity while dealing with regular support queuesDid this help you?
- 4Using a 'keep versus change' rule where maintenance is covered and environment additions are billed as projectsDid this help you?
- 5Applying a 'Rule of 5' threshold covering users, devices, or hoursDid this help you?
- 6Setting time limits such as anything over a specific number of hours or daysDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“I've always found it a little confusing for clients what defines a project. Obviously, in most cases, a project is work that we could anticipate under the managed service agreement. But even that's a little bit vague.”source ↗
“What's your definition of the project? I'm looking to develop our own definition.”source ↗
“Do you typically stop and quote them the estimated time or just send them a bill? That's the other issue is catching the request and informing the client it is going to be billable before the work is done.”source ↗
“Shouldn't this all be done under the Project's team, not having the Tech Support team do this?”source ↗
“Not even getting a pay bump for doing this work or a roll change 😂”source ↗
“I was never initially involved in anything to do with this project. I primarily deal with incoming calls standard tickets that get sent through email the usual often on again technical support.”source ↗
“The main issue for me is that the scope wasn't initially told to me that I would then be drafted in further to the project”source ↗
“even though I've pushed back and said I don't have the capacity to do this they say oh well we'll just reopen the ticket.”source ↗
Where this came up
People with this problem also raised
- 2How to balance workloads for different mock trial roles
- 14When your family treats household chores like an IT help desk
- 27How to handle too much work without project engineers or coordinators
- 2Why is my entire day eaten up by meetings and micromanagement?
- 2How to handle project management and coding at the same time
- 3How to handle client support when you're a solo freelancer on vacation