Support teams are often expected to be helpful in all situations. Customers reach out with a wide range of requests, and the instinct is to accommodate as much as possible.
Over time, this creates a pattern where support takes on work that does not belong to it. Requests that should be handled by product, sales, or customer success end up in the support queue. Agents spend time on tasks that are outside their core responsibilities.
This has two effects. First, it increases workload in ways that are not always visible. Second, it makes it harder to prioritize effectively, because the queue contains a mix of issues that require different types of attention.
Saying no in this context is not about being unhelpful. It is about maintaining clarity. When a request falls outside of support scope, it should be redirected appropriately. That may involve connecting the customer with another team or setting expectations about what can be handled.
Clear boundaries make it easier for agents to focus on what matters. They also create a more predictable experience for customers.
Without boundaries, support becomes a catch-all function. That might feel helpful in the moment, but it becomes difficult to sustain as the organization grows.