Why Is Half My Customer Success Team's Time Going to Internal Requests?

Internal requests accumulate because the CSM is the only person in the company who holds the whole picture of an account, which makes them the cheapest place for every other team to get an answer. Sales needs a reference. Product needs a customer to interview. Finance needs an overdue invoice chased. Support needs to know whether this customer is fragile before replying. Each request takes four minutes to send and forty to serve, and none of them lands in a queue anyone manages.

We read 33,600 Reddit posts from r/CustomerSuccess, r/SaaS, r/sales and r/startups covering May 2024 to September 2026. Inside the 7,100 posts in r/CustomerSuccess, 443 mention internal work, 471 mention meetings, 166 mention admin and 39 mention firefighting. The threads that describe the problem in detail keep landing on the same shape: the customer work is fine and the work around the customer is what breaks the week.

Two design faults sit underneath. Internal requests have no queue, so they arrive by direct message and are served in arrival order, which means the loudest colleague outranks the largest account. And the requests are invisible to planning: the account list is modelled in a spreadsheet and the second list is modelled nowhere, so every capacity conversation starts from a number that was wrong before it was written.

Seven categories of internal request cover almost everything that lands on a CSM in a B2B SaaS company. Sort last week's asks into these seven before you decide anything, because the answer for a reference request is different from the answer for a report, and arguing about them as one lump is how the conversation stalls.

Notice how many rows are routing. A CSM forwarding a ticket, chasing an invoice or answering what a customer meant is being used as a search function for another team, at the salary of somebody who is supposed to be preventing churn. That is the cheapest load to remove, because removing it needs a shared record and a routing rule, not a hire.

Tally two weeks by hand, in 15 minute blocks, against the seven categories. No benchmark we can verify exists for how a CSM's week splits between customer-facing work and internal work: the B2B SaaS publishers that disclose a sample and a method, among them SaaS Capital, Benchmarkit, High Alpha and ChartMogul, publish headcount ratios and retention rates, and none of them asks how the hours are spent. Your own two weeks beat all of them, and the tally takes each CSM about four minutes a day.

1. 1

   Agree the categories before anyone logs a minute

   Use the seven above, or your own seven, but write a one-line definition for each. A tally where two CSMs classify the same hour differently produces an argument, not a number.

2. 2

   Log in 15 minute blocks, twice a day

   Once before lunch, once at the end of the day. Retrospective logging at the week's end is guesswork, and the guess always favours customer work because that is the part people remember.

3. 3

   Tag every block with the requester, not only the category

   Team name is enough. The requester column is what turns the result from a grievance into a routing decision, because it names who has to change.

4. 4

   Run it for two full weeks, including one with a renewal in it

   A single quiet week understates the load and a single chaotic week overstates it. Two weeks spanning a renewal is close enough for a budget conversation.

5. 5

   Total by category, by requester and by CSM

   The by-CSM column matters: internal load is rarely spread evenly, and the person absorbing the most is usually the most helpful one on the team.

6. 6

   Publish the result to the requesting teams, not only upwards

   Most of the asking is done without any idea of the cost. Sales does not know a reference request takes three hours. Showing the number to the requester removes a share of the requests with no policy at all.

Refuse the request that is somebody else's job with a customer attached to it, and redirect it in the same sentence you decline it. A flat no from Customer Success reads as unhelpful and gets escalated. A no that names the owner, the channel and the time it will take there reads as competence, and it survives the escalation because the requester now has somewhere else to go.

The last row is worth defending hard. Daily activity reporting is the internal request that produces the most resentment for the least information, and it tends to be introduced as a proxy for trust in remote teams. The answer is an agreed set of outcomes and one weekly exception report, which is also the only version leadership will still be reading in three months.

Give internal requests two fixed windows a day and one channel to arrive in, and defend the rest of the calendar as customer time. Fragmentation is the real cost, not the minutes: a 10 minute interruption in the middle of renewal preparation costs the preparation, and a CSM who is interrupted eleven times before lunch has no deep work left to give the accounts that decide the quarter.

Batching works only if the customer blocks are real. A calendar with protected time that anyone senior can override is a calendar with no protected time, and the team learns that within a fortnight. How to move to proactive customer success with a reactive team covers holding those blocks when the inbound queue is the pressure, and who should own the knowledge base covers the documentation habit that removes a share of the questions permanently.

Show the internal load as headcount, because hours are arguable and full-time equivalents are budget. A VP who hears that the team is busy gets sympathy. A VP who sees that internal requests consume 1.6 of their 8 CSMs, with the requesting team named on each hour, has a resourcing decision in front of them and a number to take to Finance.

Put the result beside the coverage model. High Alpha's 2025 SaaS benchmarks, based on 800 or more self-selected private SaaS respondents, put customer success and support at an average of 18% to 20% of all employees for companies above 1m ARR, which is the headcount your internal load is quietly spending. If the coverage model says 60 accounts per CSM and 39% of the week is committed elsewhere, the real figure is closer to 37, and how many accounts per CSM is too many is the page that turns that into a tiering decision before the next renewal cycle.

GainTrace connects billing, CRM, support and product usage into one account record that Sales, Support and Finance can read without asking a CSM. The account history, the renewal date, the open risks and the usage trend are fetched instead of retold, which removes most of the escalation relay and most of the data pulls. Playbooks run the recurring work on a schedule so the weekly report is generated instead of assembled, and customer success leaders shows the coverage and risk picture that leadership was asking each CSM for by hand.