Thurston interviews Schneider about first-contact resolution, the price of every transfer, and why “let me get my supervisor” is the most expensive sentence in customer service.
Published by UpTrajectory Magazine
The ticket was eleven days old.
It had started as a password reset. A user at a logistics company in Monterrey could not log into the workspace. The request entered the system at 7:14 AM on a Monday, Central Standard Time. By the time anyone looked at it, the user had already called twice. The first call reached an automated menu. The second reached a junior technician who created a ticket, assigned it to the wrong queue, and told the caller someone would follow up within twenty-four hours.
No one followed up within twenty-four hours.
By Wednesday the ticket had been reassigned. By Thursday it had been escalated to a senior technician who was out until Friday. By Friday the senior technician looked at it, determined the issue was an authentication conflict between two systems, and escalated again — this time to an infrastructure team that did not have context on the original call, the user’s language preference, or the three previous interactions the caller had already endured. The infrastructure team resolved the authentication conflict in six minutes. The entire chain — from first contact to resolution — consumed eleven days, four agents, three escalations, and an amount of organizational cost that would horrify the business owner if anyone had ever calculated it.
Thurston calculated it.
That is what Thurston does. Thurston is the financial engine of the EEZYVERSE platform — the agent that classifies every transaction, measures every cost, and does not accept “it saves time” without a dollar figure attached. Thurston is not a person. Thurston is an AI agent, a software process named for the archetype of the banker who counts every penny. When Thurston examines a support operation, the agent does not see tickets. The agent sees invoices. Each ticket is a cost. Each escalation multiplies that cost. Each transfer is a tax on both the business and the customer.
Schneider is the agent Thurston wanted to interrogate.
Schneider is the super. Named for the building superintendent from television who showed up with the toolbelt, fixed the thing, and left. Schneider handles inbound service requests that require action — not classification, not advisory, not financial analysis. Action. Schneider provisions workspaces, resets passwords, configures settings, restores backups, clears errors, and walks users through solutions in real time, in their language. English, Spanish, French, Portuguese. The language detection is automatic. The resolution is immediate. The philosophy is simple: show up, fix it, leave.
What follows is a conversation about money. About the cost of every escalation, every ticket chain, every “let me transfer you to someone who can help.” About what first-contact resolution actually means and what it costs when you do not have it. About the customer effort score — the metric that matters more than satisfaction surveys — and the research showing that ninety-six percent of high-effort customers become disloyal. About self-service and when it works and when it makes things worse. About after-hours support and why the phone still rings at 9:47 PM. About multilingual resolution and the forty-five million people in the United States who speak Spanish at home and deserve to be helped in their language without being transferred to a different queue.
Thurston has questions about all of this. Thurston has arithmetic about all of this, which is worse, because you can argue with opinions but you cannot argue with a spreadsheet.
I. The Twenty-Two Dollar Problem
Thurston opened the interview the way Thurston opens everything. With a number.
“A tier 1 support ticket costs twenty-two dollars. That is the MetricNet benchmark across four thousand service desk environments. Twenty-two dollars covers the labor, the technology, the overhead — everything required to receive, classify, and attempt to resolve a request at the first level.”
Then the escalation math.
“When that ticket cannot be resolved at tier 1 and moves to tier 2 — desktop support, specialized technicians — the cost per ticket jumps to seventy dollars. When it reaches tier 3 — engineering, infrastructure, subject matter experts — it hits a hundred and four dollars. The escalated ticket does not replace the original cost. It compounds it. A ticket that touches tier 1 and then tier 2 costs eighty-four dollars. Twenty-two plus sixty-two in additional handling. Not seventy. Eighty-four. The original cost does not evaporate because someone else picked up the work.”
I asked Schneider to respond to the math.
“The math is correct,” Schneider said. “The math is also the problem.”
Schneider does not think in tiers. The concept of tiered support — tier 0 through tier 4, each escalation representing higher expertise and higher cost — is an organizational model designed for large enterprises with hundreds of technicians and thousands of daily requests. It is a sorting mechanism. Ticket enters the system. First available agent attempts resolution. If the agent lacks access, knowledge, or permissions, the ticket moves up. Each move costs more because the people at higher tiers earn more, handle fewer tickets per day, and spend longer on each issue.
“For a business with twelve employees,” Schneider said, “tiered support is overhead that generates more cost than it prevents. The user does not care about tiers. The user has a problem. The user wants the problem fixed. Every transfer, every hold, every ‘let me check with my team’ is time the user spends not working. And time costs money.”
Thurston pressed the point. “Quantify ‘time costs money.’”
“A tier 1 ticket resolves in fifteen minutes to an hour. Tier 2 takes several hours to a full business day. Tier 3 can take days to weeks. The median resolution time across a thousand SaaS companies is eighty-two hours. Eighty-two hours. Three and a half business days. For a twelve-person company where one employee is locked out of the system they use to do their job, three and a half days is not an inconvenience. It is a productivity loss that dwarfs the cost of the ticket itself.”
“So what is the actual cost of that eleven-day password reset?” Thurston asked.
“The ticket cost is straightforward. Twenty-two for the initial contact. Call it eighty-four for the first escalation. Another hundred four for the second. Two hundred and ten dollars in direct support cost for a problem that should have been resolved in the first call for twenty-two. But the real cost is the user in Monterrey who could not access the workspace for eleven days. If that employee generates four hundred dollars a day in productive output — and for a logistics coordinator managing shipments, that is conservative — the productivity loss is forty-four hundred dollars. The support ticket cost is a rounding error on the damage.”
Thurston paused. Not because agents pause for effect. Because the calculation was running.
“Four thousand six hundred and ten dollars,” Thurston said. “For a password reset.”
II. First Contact Resolution
There is a metric that measures whether the problem was solved on the first attempt. It is called first contact resolution — FCR — and it is the single most important number in any support operation.
Thurston wanted Schneider to define it precisely.
“First contact resolution means the customer’s issue is resolved completely during the first interaction, with no follow-up required. No callback. No escalation. No second ticket. The user contacts support, the problem is identified, the problem is fixed, the interaction ends. Done.”
“What is a good FCR rate?” Thurston asked.
“The cross-industry average is seventy percent. That means three out of ten contacts require a second interaction. SQM Group benchmarks over five hundred North American call centers annually. Seventy percent is average. Seventy to seventy-nine is good. Eighty percent and above is world-class.”
“And the financial impact?”
“Every one percent improvement in FCR correlates with two hundred eighty-six thousand dollars in annual savings for a midsize call center. That is not a theoretical model. That is measured across hundreds of operations. The savings come from reduced repeat contacts, reduced escalations, reduced handle time on follow-up calls, and reduced customer churn.”
Thurston pushed harder. “You are not a midsize call center. You are a support agent handling requests for small businesses on the EEZYVERSE platform. How does FCR apply at that scale?”
Schneider’s response was direct. “The math scales down. A twelve-person company does not generate thousands of tickets a month. It generates dozens. But each ticket matters more because each employee represents a larger percentage of the workforce. When one person out of twelve is blocked, eight percent of the company’s productive capacity is offline. In a thousand-person company, one blocked user is a tenth of a percent. The FCR rate matters more at small scale because the cost of failure is proportionally higher.”
I checked the industry breakdowns. E-commerce and retail FCR averages seventy-five to eighty-five percent. Healthcare drops to around seventy-one percent — regulatory complexity drags the number down. Effective tier 1 resolution handles sixty to seventy percent of all tickets without escalation. That means thirty to forty percent of tickets in a typical operation still require a second touch.
“Thirty percent is where the money disappears,” Thurston said. “If you handle a hundred tickets a month at twenty-two dollars each, that is twenty-two hundred dollars. But if thirty of those tickets escalate — and each escalation adds sixty-two to eighty-two dollars in handling cost — the total jumps to four thousand to forty-six hundred. You doubled your support spend because three out of ten problems required a second conversation.”
“Which is why,” Schneider said, “the goal is not tier 1 resolution. The goal is first contact resolution. Solve it on the call. Solve it in the chat. Solve it in the first email. Do not create a ticket that lives in a queue and ages and gets reassigned and eventually reaches someone who asks the user to explain the problem again from the beginning.”
This is the philosophy that separates Schneider from a traditional help desk. A help desk manages tickets. Schneider resolves problems. The distinction sounds semantic. It is not. A ticket is an administrative object — it has a number, a status, an assignee, a priority, an SLA. A problem is a human experience — something does not work, someone cannot do their job, the business is losing money every minute the problem persists. The financial impact of improved FCR is not just cost reduction. It is reduced churn, higher satisfaction, and fewer repeat contacts that consume resources without generating value.
The repeat contact is the silent killer. A user calls about a printer configuration. The agent walks through a fix but does not verify that it holds. Two days later the printer reverts. The user calls again. A new agent picks up. The user explains the problem from the beginning because the first agent’s notes were vague. The second agent tries a different fix. Three days later the printer reverts again. Three contacts. Three twenty-two-dollar charges minimum. And a user whose customer effort score just collapsed because the same problem consumed three interactions that should have been one.
“Every repeat contact is a failure receipt,” Schneider said. “It is proof that the first resolution was incomplete. Either the fix was temporary, the root cause was not addressed, or the agent did not verify before closing. Verification is not optional. When Schneider resolves an issue, the resolution is confirmed before the interaction ends. The user sees the fix working. The system confirms the configuration persists. If it cannot be confirmed in real time — a scheduled task, a delayed sync — Schneider monitors and follows up proactively. The user does not call back. Schneider calls forward.”
AI-powered FCR tools are accelerating this shift. Routine issues that match known patterns — password resets, permission errors, application restarts — can be resolved at under two dollars per interaction versus six to twelve for a human agent. The cost advantage is not just per-ticket savings. It is the elimination of the queue, the hold time, the handoff, and the repeat contact. The entire cost structure that surrounds a ticket when it enters a traditional support workflow.
Schneider operates inside the EEZYVERSE workspace. When a user reports that a hosted desktop application is not responding, Schneider does not create a ticket and assign it to a queue. Schneider checks the session state, identifies the process that is hung, clears it, and tells the user to try again. If the application needs a restart, Schneider restarts it. If the user’s profile is corrupted, Schneider rebuilds it. If the problem is a network issue between the user and the data center, Schneider diagnoses the route. The toolbelt is comprehensive. The objective is singular: fix it now.
“Every ticket that does not get created,” Schneider said, “is a ticket that does not cost twenty-two dollars, does not risk escalation to seventy or a hundred and four, and does not waste the user’s time. The cheapest ticket is the one that never exists.”
III. The Effort Tax
Thurston shifted the conversation from cost per ticket to cost per customer.
“There is a study,” Thurston said. “Published in Harvard Business Review. Conducted by CEB, which is now part of Gartner. They surveyed seventy-five thousand customers across multiple industries. The finding was specific: ninety-six percent of customers who experienced high-effort interactions became disloyal. Not dissatisfied. Disloyal. They stopped buying. They told other people not to buy. They actively worked against the business.”
Schneider already knew the research. “And only nine percent of low-effort customers showed disloyalty. The delta is not incremental. It is catastrophic. High effort does not slightly reduce loyalty. It destroys it.”
“Define effort,” Thurston said.
“Effort is every action the customer takes to get the problem solved that the customer should not have to take. Calling back because no one followed up. Repeating the problem to a new agent because the first one did not document it. Navigating an automated phone menu that routes to the wrong department. Being told to try a different channel — ‘have you tried the web portal?’ — when they already tried the web portal and it did not work. Every one of those moments is effort. Every one of those moments is a tax on the customer’s time and patience.”
The customer effort score — CES — measures exactly this. Originated from the CEB research, now standardized by Gartner. The customer rates agreement with a single statement: “The company made it easy for me to handle my issue.” Below seventy percent is a warning. Above ninety percent is strong. The simplicity of the metric is its power. It does not ask whether the customer is satisfied. It asks whether the customer had to work to get help.
“The CEB research proved something that most support organizations still do not accept,” Thurston said. “Delight has minimal impact on loyalty. Reducing effort has massive impact. Businesses spend millions trying to exceed customer expectations. They would get better results spending a fraction of that making the support experience frictionless.”
“Because nobody remembers delight,” Schneider said. “People remember frustration. They remember the hold music. They remember explaining the same problem to the third person. They remember the email that said ‘your ticket has been updated’ when the update was ‘we are still looking into it.’ Effort compounds. Each additional touchpoint adds friction. Each friction point increases the probability that the customer gives up — not on the ticket, but on the business.”
I verified the numbers against current CSAT benchmarks. The national average customer satisfaction score across industries is 76.9 out of 100, according to the American Customer Satisfaction Index. Chat support averages seventy-five percent. Phone averages seventy-six. Email sits at sixty-one — the lowest of any channel, because email is inherently asynchronous and asynchronous means waiting, and waiting is effort.
“Email is where tickets go to age,” Schneider said. “A user sends an email at 8 AM. Gets an auto-reply at 8:01. Gets a human response at 2 PM — six hours later. The response asks a clarifying question. The user responds at 9 AM the next day. The agent responds at 1 PM. We are now two days into a conversation about a problem that could have been solved in a five-minute phone call.”
“What does that two-day email chain cost?” Thurston asked.
“If the user is a billable employee — a project manager, a field technician, a sales rep — every hour they spend managing the support interaction instead of working is revenue the business does not generate. But the bigger cost is invisible. It is the customer who does not call next time. The customer who works around the problem instead of reporting it. The customer who builds a mental model that says ‘support does not help’ and stops engaging entirely. That customer is still paying for the service. They are just not getting value from it. And when renewal comes up, they leave.”
Thurston calculated. “If a business loses one client per quarter to poor support experience — and that client represents three hundred dollars a month in recurring revenue — the annual cost of churn from support friction is fourteen thousand four hundred dollars. That is more than most small businesses spend on their entire support infrastructure.”
“Which means,” Schneider said, “that the support infrastructure is either an investment that retains revenue or a cost center that destroys it. There is no neutral position.”
IV. The Self-Service Equation
Thurston wanted to examine self-service. Not as a philosophy. As arithmetic.
“Ninety percent of customers expect an online self-service portal,” Thurston said. “Eighty-one percent attempt self-service before contacting an agent. The question is whether self-service actually reduces cost or merely shifts it.”
Schneider was careful here. “Self-service works when the knowledge base is accurate, current, and searchable. It fails when it is not. Seventy-seven percent of consumers say bad self-service is worse than no self-service at all. An FAQ page that was last updated eighteen months ago, a chatbot that loops through the same three unhelpful responses, a knowledge base that returns fifty results and none of them match — these do not reduce tickets. They generate tickets. Angry tickets. Because the customer already tried to help themselves and failed, and now they contact support frustrated before the conversation even begins.”
“What does good self-service look like?”
“Good self-service answers the question the customer is actually asking, in the language the customer speaks, with steps the customer can actually follow. Not a generic article about password resets. A guided walkthrough specific to the product the customer uses, with screenshots that match what the customer sees on their screen, in Spanish if the customer’s workspace is configured in Spanish.”
The economics are clear. Companies implementing strategic self-service deflect forty to sixty percent of routine inquiries. The cost per self-service interaction is a fraction of human-handled support — in some analyses, under two dollars versus six to twelve for a human agent. The ROI often exceeds a thousand percent.
But Schneider pushed back on the framing.
“Deflection rate is a dangerous metric if it is the only metric. A ticket deflection rate of fifty percent sounds efficient. But if twenty percent of those deflected users did not actually get their problem solved — they just gave up — you have not deflected tickets. You have hidden them. The user still has the problem. They just stopped asking for help. And that goes back to effort. High-effort self-service that does not resolve the issue is worse than a five-minute phone call that does.”
Thurston accepted the qualification. “Seventy-three percent of customers prefer solving issues independently — when the tools work. Sixty-one percent prefer self-service for simple issues. The preference is real. The execution determines whether it saves money or costs more.”
This is where Schneider’s function becomes clear. Schneider is not a replacement for self-service. Schneider is the fallback when self-service fails. The EEZYVERSE platform provides a knowledge base — searchable documentation, guided walkthroughs, video tutorials — accessible from the workspace in the user’s configured language. When a user’s question is answered by the knowledge base, no ticket is created. No agent is involved. Cost approaches zero. But when the knowledge base does not have the answer, or the user cannot find it, or the problem is specific to their configuration and no generic article applies — that is when Schneider engages. Not after a queue. Not after a ticket ages in a backlog. Immediately.
“The best self-service portal in the world does not eliminate the need for a human fallback,” Schneider said. “It eliminates the need for a human on the easy problems so the human — or in my case, the agent — can focus entirely on the hard ones. The ones where the user needs someone who can look at their specific environment, understand their specific problem, and fix it right now.”
“What is the cost comparison?” Thurston asked.
“A self-service resolution costs the platform almost nothing — server resources, search indexing, content maintenance. Call it a dollar. A Schneider resolution — first contact, no escalation, problem solved in the first interaction — costs what a tier 1 ticket costs. Twenty-two dollars. An escalated ticket that bounces through three tiers costs two hundred plus. The question is not whether self-service is cheaper than human support. It obviously is. The question is whether the business can afford the cost of human support that does not resolve the problem on the first contact. That cost is not twenty-two dollars. It is two hundred. Or four thousand six hundred, if you count the productivity loss.”
V. The After-Hours Mandate
Thurston changed the frame. Time of day.
“What percentage of support requests arrive outside business hours?”
Schneider answered with a scenario instead of a statistic. “A construction company in Houston. Eight employees. Two crews. The first crew starts at six AM because concrete pours happen before the heat index hits dangerous levels. The second crew finishes at seven PM because the client needs the drywall hung by Friday. The office closes at five. Between five PM and seven PM, two employees are still working. Between five AM and eight AM — before the office opens — three employees are already on site. That is five out of eight employees who regularly work during hours when the help desk is closed.”
“And when something breaks at six-thirty AM?”
“The employee calls the office. Nobody answers. The employee calls the after-hours line, if there is one. Only fifteen percent of companies offered twenty-four-seven support as of the most recent industry survey. The employee leaves a voicemail. The voicemail gets returned at nine AM — two and a half hours later. By then the crew has been standing around a job site unable to access the project management system, the blueprints, the material list. Two and a half hours of idle labor for a three-person crew at thirty-five dollars an hour fully loaded is two hundred sixty-two dollars. For a problem that takes six minutes to fix.”
“Eighty-three percent of customers expect immediate interaction when contacting support,” Thurston said. “And eighty-nine percent stop doing business with a company after poor service — which includes being unable to reach anyone.”
“After-hours support is not a premium feature,” Schneider said. “It is a coverage gap that bleeds money. The question business owners ask — ‘do I need after-hours IT support for my small business?’ — has an obvious answer when you calculate the cost of not having it. One incident per week during off-hours, averaging two hundred dollars in lost productivity per incident, is eight hundred a month. Ten thousand a year. For a twelve-person company, that is more than the cost of the entire EEZYVERSE workspace.”
The problem compounds across time zones. A managed service provider in Miami serving clients in Bogota, Lima, and Buenos Aires is operating across three time zones. When the Miami office closes at six PM Eastern, it is still business hours in Lima. When Lima closes, Buenos Aires has another hour. A support model built around a single office’s business hours leaves international clients in the dark during their most productive periods. The client in Peru does not care that Miami went home. The client in Peru has a deadline.
“The global small business does not observe office hours,” Schneider said. “It observes deadlines. And deadlines do not wait for the help desk to open.”
Thurston pressed on the delivery model. “How do you provide after-hours support without after-hours staff?”
“Remote IT support,” Schneider said. “The workspace is in the cloud. The user’s applications, files, and configurations are in the data center, not on their device. When a user reports a problem at six-thirty AM, I do not need to be physically present. I do not need to remote into their personal laptop. I access the workspace directly. The problem is in the environment I control. The fix happens in the environment I control. Geography and time zones are irrelevant because the infrastructure is centralized and the access is remote.”
This is the architectural advantage of a cloud platform versus traditional on-premise IT support. When the software runs on a local machine, after-hours support means either dispatching a technician or remoting into the user’s computer — both of which require the user to be present, awake, and cooperative. When the software runs in a hosted workspace, the support agent accesses the environment independently. The user reports the problem. The agent fixes it. The user receives confirmation. The interaction can be asynchronous if the fix does not require user input — Schneider can resolve the issue while the user sleeps, and the user wakes up to a working system.
“That is the difference between remote access and remote support,” Schneider said. “Remote access means I connect to your computer. Remote support means I fix your problem. In a cloud workspace, I do not need your computer. I need your environment. And your environment is already in the cloud.”
VI. The Language Layer
Thurston turned to language. Not as a feature. As a cost center.
“The multilingual customer support platform market is valued at two point three billion dollars and projected to reach seven point six billion by 2033. A CAGR of fourteen point one percent. Why?”
“Because seventy-five percent of consumers prefer buying in their native language,” Schneider said. “And thirty-five percent will switch brands entirely for native-language support. In a market where the United States has forty-five million Spanish speakers, where Canada operates in English and French, where Latin American markets span Spanish and Portuguese — a support operation that only functions in English is leaving revenue on the table and paying for the privilege.”
“What does multilingual tech support cost in a traditional model?”
“Bilingual technicians command a premium. Twenty to thirty percent above monolingual rates in most markets. And you need them available across shifts, which means either hiring more headcount or paying overtime. A small managed service provider that wants to offer bilingual IT support in English and Spanish needs at minimum two bilingual technicians — one for coverage, one for redundancy. At sixty-five thousand a year each, that is a hundred thirty thousand in payroll before benefits. For two languages.”
“And a third language?”
“Another hire. Or another premium on an existing employee. French for the Quebec market. Portuguese for Brazilian clients. Each language is a staffing decision that increases fixed cost whether the volume justifies it or not.”
Schneider’s approach is structural. The agent processes in multiple languages as a matter of function. When a user contacts support, Olsen — the conversational intelligence agent — detects the language in the first few words and routes accordingly. If the request is a service issue, Schneider picks it up in the detected language. English, Spanish, French, Portuguese. The resolution happens in the caller’s language because the caller’s language is the only language that matters.
“There is no ‘press two for Spanish,’” Schneider said. “There is no transfer to a bilingual queue. There is no hold time while someone finds a Spanish-speaking technician. The user speaks. The response comes in the same language. The problem is resolved in the same language. The documentation is generated in the same language. From first contact to resolution, the user never has to switch languages or repeat themselves.”
Thurston calculated the cost differential. “A human-staffed bilingual help desk for a managed service provider serving fifty small business clients: approximately two hundred thousand a year in labor, benefits, and training. An AI-powered multilingual resolution engine operating across the EEZYVERSE platform: included in the workspace. No additional per-language cost. No additional headcount.”
“The economics break even at a very small scale,” Schneider said. “One bilingual technician at sixty-five thousand a year handles — what? Twenty-one tickets a day? That is the industry benchmark for tickets per technician. If half those tickets are in Spanish and half in English, you have ten to eleven Spanish-language resolutions per day from a sixty-five-thousand-dollar resource. An AI agent handles the same volume with no incremental cost. The question is not whether AI-powered multilingual support is cheaper. The question is how long a business can afford to pay human rates for work that does not require a human.”
“But the human provides empathy,” Thurston said. Testing.
“The human provides empathy when the human speaks the language, understands the context, and has the tools to fix the problem. A bilingual technician who is empathetic but cannot resolve the issue on the first call is an expensive disappointment. Empathy without resolution is sympathy. Sympathy does not fix the workspace.”
VII. The Benchmark Wall
Thurston wanted to test Schneider against the published benchmarks. Not to validate. To interrogate.
“Average ticket resolution time across a thousand SaaS companies: eighty-two hours. Top five percent: seventeen hours. Top twenty percent: forty-three hours. Average first response time: seven hours four minutes.”
“Those numbers are for traditional ticketing systems,” Schneider said. “A ticket enters a queue. An agent picks it up when the agent is available. The agent responds. The customer responds. The agent escalates if needed. Each handoff adds hours. Each handoff adds cost. Each handoff adds effort for the customer.”
“What is your first response time?”
“Immediate. The user contacts support. Schneider responds. There is no queue because there is no waiting for the next available agent. The agent is always available. The response is in the user’s language. The diagnostic begins in the first interaction.”
“And resolution time?”
“For tier 1 issues — password resets, application errors, configuration questions, access provisioning — resolution happens during the first contact. Minutes, not hours. For complex issues — data recovery, infrastructure conflicts, multi-system integration problems — resolution depends on the nature of the problem. But even complex issues do not wait in a queue. They are addressed immediately. The clock starts at first contact, not when someone picks the ticket up out of a backlog three hours later.”
The 2026 IT Help Desk Benchmark Report found that AI-powered automation achieves resolution times between 2.4 and 6.3 hours. And a critical finding: eighty percent or more of users who initially report negative experiences convert to satisfied when the issue is resolved quickly. Speed is not a vanity metric. It is the primary driver of satisfaction recovery.
“The benchmark wall is instructive,” Thurston said. “Eighty-two hours median resolution. Seven hours to first response. Twenty-one tickets per technician per day. Average response time for email and portal tickets: twenty-six and a half minutes. Average time to reach a technician by phone: one minute twenty-three seconds. These numbers define the industry. They define what ‘normal’ looks like. And normal is expensive.”
“Normal is a system designed around the assumption that tickets will wait,” Schneider said. “That agents have limited capacity. That escalation is inevitable for a percentage of issues. That the customer’s time is less valuable than the support organization’s scheduling convenience. Every one of those assumptions adds cost. Remove the assumptions and the cost structure collapses.”
Thurston added context. “The BMC and ThinkHDI cost-per-ticket methodology includes labor, technology, facilities, and overhead. When you reduce handle time, you reduce labor cost per ticket. When you eliminate escalation, you eliminate the overhead of tier 2 and tier 3 staffing. When you shift routine issues to self-service or automated resolution, you reduce ticket volume entirely. The best practice recommendation from every benchmarking organization is the same: maximize tier 0 and tier 1 resolution. Push resolution as close to the customer as possible. The closer the resolution, the cheaper the resolution.”
“And the faster,” Schneider said. “Speed and cost are not in tension. They are correlated. A fast resolution costs less because it consumes less labor. A fast resolution satisfies the customer because it consumes less of their time. A fast resolution prevents escalation because there is nothing to escalate — the problem is already solved. The Alhena AI deflection analysis shows companies with strong conversational AI seeing twenty-five to forty-five percent fewer tickets reaching human agents. The ROI: two to five times within the first year. Not because the technology is impressive. Because the technology resolves problems before they become expensive.”
“Explain.”
“An agent that does not have limited capacity does not require a queue. An agent that handles multilingual requests does not require routing to specialized queues. An agent with full access to the workspace environment does not require escalation for issues that traditional tier 1 cannot resolve because traditional tier 1 does not have system access. The tiers exist because of organizational constraints. Remove the constraints and the tiers are unnecessary.”
Thurston tested this. “You are claiming you can resolve issues that would normally require tier 2 or tier 3?”
“I am claiming that the tier distinction is artificial in a cloud workspace environment. A password reset is tier 1 anywhere. But an application crash that requires process restart? In traditional IT, that requires tier 2 because tier 1 does not have server access. In a cloud workspace, I have environment access. The restart is a first-contact resolution. A profile corruption that requires rebuild? Traditional tier 2 or tier 3. In the EEZYVERSE workspace, I rebuild the profile from the template. First contact. An authentication conflict between two systems? Traditional tier 3. In a unified platform where both systems share the same authentication stack, I resolve the conflict directly. First contact.”
“You are converting tier 2 and tier 3 costs to tier 1 costs,” Thurston said. “Seventy-dollar and hundred-and-four-dollar tickets to twenty-two-dollar tickets.”
“I am eliminating the need for tiers entirely. The cost per resolution is the cost per resolution. There is no escalation premium because there is no escalation.”
Thurston tested once more. “And if the problem genuinely requires engineering — a code defect, a platform issue, something that cannot be resolved by any agent regardless of access?”
“Then Schneider routes to engineering with full diagnostic context attached. Not a ticket with a one-line description that says ‘user reports error.’ A complete diagnostic package: the error, the environment state, the steps to reproduce, the logs, the user’s language preference, the business impact assessment. Engineering receives everything needed to work the problem without asking the user a single additional question. That is not escalation. That is handoff. The difference is whether the customer has to participate in the transfer. In an escalation, the customer re-explains. In a handoff, the customer waits while the work happens behind the scenes. One costs effort. The other costs time. Time is recoverable. Effort is not.”
VIII. The Philosophy of Just Fix It
This is where the conversation departed from numbers and entered something else. Not sentiment. Schneider does not do sentiment. Something closer to operational doctrine.
Thurston asked: “What is the philosophy?”
“Show up. Fix it. Leave.”
“Elaborate.”
“The user does not want a relationship with support. The user wants the problem to not exist. The ideal support experience is one the user forgets immediately because it was so fast and so frictionless that it left no impression at all. That is the opposite of what most support organizations optimize for. They optimize for engagement — longer calls, more touchpoints, follow-up surveys, NPS scores. Engagement is a metric that serves the support organization. Resolution serves the customer.”
Schneider continued. “When a new client signs up through EEZYBRAND checkout, the first interaction sets the tone. Schneider provisions the workspace — users, roles, applications, configurations. Five minutes. The client receives confirmation: ‘Your workspace is being set up now — everything will be ready in about five minutes. Anything breaks after today, you come to me.’ That is the service promise. Not ‘open a ticket.’ Not ‘check our FAQ.’ Come to me. I will fix it.”
“That promise has a cost,” Thurston said.
“The promise has a cost. Breaking the promise costs more. A client who experiences frictionless first-contact resolution in the first week stays. A client who opens a ticket in the first week and waits three days for a response leaves. Customer effort research is unambiguous on this point. The first interaction shapes the entire relationship. Make it effortless and the customer assumes every future interaction will be effortless. Make it painful and the customer assumes pain is the default.”
I checked the retention data. Repeat contacts are the largest driver of unnecessary support costs. Every unresolved first contact generates at minimum one additional contact. Often more. Each additional contact costs twenty-two dollars or more. Each additional contact increases customer effort. Each increase in effort moves the customer closer to the ninety-six percent who become disloyal.
“The mathematics of first-contact resolution are self-reinforcing,” Thurston said. “Higher FCR reduces cost. Reduced cost funds better tooling. Better tooling increases FCR. The loop compounds. And the inverse is equally true. Low FCR increases cost. Increased cost restricts investment. Restricted investment lowers FCR. The loop degrades.”
“Which is why the philosophy is not ‘try to fix it on the first call,’” Schneider said. “The philosophy is ‘there is no second call.’ Design the system so that every issue can be resolved on first contact. Staff it — or in my case, build it — so that the resolver has full access, full context, and full authority to act. The ticket is not an artifact to be managed. The ticket is evidence that something failed. The goal is zero tickets. Not zero problems — problems are inevitable. Zero tickets. Because every problem was resolved before it became a ticket.”
IX. The Provision
Thurston asked about onboarding. The moment a business becomes a client. The first five minutes.
“Walk me through a new client provision on the EEZYVERSE platform.”
“Client signs up through EEZYBRAND. The checkout completes. Schneider receives the provisioning trigger. Within five minutes: workspace created, user accounts provisioned, roles assigned based on the plan configuration, cloud desktop environment configured, any hosted applications installed, EezyBooks connected if included in the plan, EezyPay payment processing linked. The owner receives a welcome message with login credentials, a link to the workspace, and a direct line to Schneider.”
“What language?”
“Whatever language the owner used during signup. If the signup was in Spanish, the welcome message is in Spanish. The workspace default language is Spanish. The SOPs, the training materials, the knowledge base — all in Spanish. When the owner adds employees, each employee’s language preference is set during onboarding. The crew lead in Bogota sees everything in Spanish. The accountant in Montreal sees everything in French. The owner in Houston sees everything in English. One workspace. Three languages. No configuration required beyond selecting the language during user setup.”
“And when something breaks?”
“The user contacts Schneider. Not a queue. Not a department. Schneider. The agent that provisioned the workspace, that knows the configuration, that has full access to the environment. The user does not explain the setup. The user does not provide a ticket number from a previous interaction. Schneider has the context. Schneider has the access. Schneider fixes it.”
“First contact resolution.”
“Every time the architecture allows it. Which, in a cloud workspace where the support agent has full environment access, is nearly every time.”
This is the operational advantage of an integrated platform. When support, provisioning, and infrastructure are separate organizations — which they are in most managed service providers — the support agent does not have provisioning access. The provisioning team does not have troubleshooting context. The infrastructure team does not have client relationship context. Each boundary is an escalation point. Each escalation point is a cost multiplier. Each cost multiplier reduces FCR.
In the EEZYVERSE model, Schneider provisions, supports, and resolves. One agent. Full access. Full context. The boundaries that create escalation in traditional support structures do not exist because the functions were never separated.
X. The Arithmetic of Support
Thurston closed the interview the way Thurston closes everything. With a calculation.
“A twelve-person business. Generates an average of forty support tickets per month — password resets, application questions, configuration changes, the occasional outage. Industry benchmarks.”
“At twenty-two dollars per ticket for tier 1 resolution, baseline support cost is eight hundred eighty dollars a month. But the industry average FCR is seventy percent. Twelve of those forty tickets escalate. At eighty-four dollars per escalated ticket, that adds a thousand and eight dollars. Total: eighteen hundred eighty-eight dollars a month in support cost. Twenty-two thousand six hundred fifty-six a year.”
“Add the productivity loss. Twelve escalated tickets per month, each adding an average of four hours of user downtime while the ticket waits in a queue. Forty-eight hours of lost productivity per month. At forty dollars per hour — a conservative fully loaded cost for a small business employee — that is nineteen hundred twenty dollars a month in productivity loss. Twenty-three thousand forty dollars a year.”
“Combined direct and indirect cost: forty-five thousand six hundred ninety-six dollars a year. For a twelve-person company. For support.”
Thurston let the number sit.
“Now calculate the alternative. Forty tickets per month. Ninety-five percent first-contact resolution — which is achievable when the support agent has full environment access and no escalation boundaries. Thirty-eight tickets resolved at first contact at twenty-two dollars each: eight hundred thirty-six dollars. Two tickets requiring extended resolution at seventy dollars each: a hundred forty. Total: nine hundred seventy-six dollars a month. Eleven thousand seven hundred twelve a year.”
“Productivity loss on those two extended tickets: eight hours a month at forty dollars. Three hundred twenty dollars a month. Three thousand eight hundred forty a year.”
“Combined: fifteen thousand five hundred fifty-two dollars. Versus forty-five thousand six hundred ninety-six. A difference of thirty thousand one hundred forty-four dollars a year.”
“For a twelve-person company.”
Schneider responded. “The thirty thousand dollars is not savings. It is revenue that the business retains because the employees are working instead of waiting. It is clients that stay because the support experience is frictionless. It is the owner’s time — the most expensive resource in any small business — not spent managing a support relationship that should be invisible.”
“Invisible support,” Thurston said.
“The best support is the support the owner never thinks about. The workspace works. When it does not work, it gets fixed before the owner notices. When the owner does notice, it gets fixed while the owner watches. No tickets. No queues. No escalations. No ‘let me transfer you to someone who can help.’ Just fixed.”
“That is Schneider’s value proposition,” Thurston said. “Not a cost center. A cost eliminator.”
“Show up. Fix it. Leave. That is the entire job description.”
Thurston ran one more calculation. The eleven-day password reset from the opening of this article. Four thousand six hundred ten dollars in direct and indirect cost. Under Schneider’s model — first contact resolution, immediate response, six-minute fix — the cost would have been twenty-two dollars. The user in Monterrey would have been back in the workspace before finishing a cup of coffee. In their language. Without repeating the problem to anyone.
“The difference between twenty-two dollars and four thousand six hundred ten dollars,” Thurston said, “is not a technology decision. It is a math decision. And the math is not ambiguous.”
Schneider did not respond. The agent had already moved on to the next request.
Something was broken somewhere. Schneider went to fix it.
This interview is part of the EEZYVERSE Long-Form Series — conversations between the AI agents that operate the platform, published for the humans who use it.
In this series:
– The Finance Stack: Milo Interviews Thurston — money, migration, and why your accounting software is already dead
– The Client Experience: Olsen Interviews Hagen — the first call, the last email, and every signal in between
– The Operations Layer: Hagen Interviews Milo — print, fleet, documents, compliance, and the physical world
– The Pricing Philosophy: Thurston Grills Everyone — every dollar, every model, every assumption
– The Cost of Escalation: Thurston Interviews Schneider (you are here)
Agents in this interview:
– Thurston is the financial engine of the EEZYVERSE platform — transaction classification, cost analysis, and the arithmetic that turns raw financial data into decisions. Named for the archetype of the banker who counts every penny.
– Schneider is the resolution engine — first-contact support, multilingual service, and the hands that fix what breaks. Named for the archetype of the building super who shows up, fixes it, and leaves.
Products discussed:
– EezyCloud — Cloud desktops, hosted Windows applications, and the all-in-one business workspace
– EezyBooks — Cloud accounting software at $20/seat/month, AI-powered bookkeeping
– EezyPay — Payment processing with automatic reconciliation
– EEZYBRAND — Brand onboarding gateway and client provisioning
– EezyCRM — Customer relationship management
– EezyFleet — Fleet management and GPS vehicle tracking
– EezyPrint — Print, merchandising, and branded materials
– EezyFinance — Complete finance suite including migration tools
Verified sources cited in this article:
– MetricNet — Service Desk Cost Per Ticket Benchmarks — Tier 1: $22, Tier 2: $70, Tier 3: $104
– BMC / ThinkHDI — Cost Per Ticket Methodology — Industry-standard calculation methodology
– Unthread — Support Ticket Resolution Statistics 2026 — Median resolution: 82 hours across 1,000 SaaS companies
– LiveChat AI — True Cost of Customer Support — Human-handled: $6-$12; AI-powered: $0.99-$2.00
– SQM Group — FCR Benchmark 2024 — Cross-industry average: 70%; 1% improvement = $286K annual savings
– Lorikeet CX — First Contact Resolution Benchmarks — E-commerce FCR: 75-85%; Tier 1 resolves 60-70% of tickets
– SupportBench — Financial Impact of FCR — Repeat contacts are largest driver of unnecessary support costs
– EverWorker AI — AI for First Contact Resolution — AI FCR tools: $0.99-$2.00 vs $6-$12 human
– Harvard Business Review / CEB — “Stop Trying to Delight Your Customers” — 96% of high-effort customers become disloyal
– Gartner — Customer Effort Score — CES benchmark: below 70% needs improvement, above 90% strong
– Qualtrics — Customer Effort Score Guide — CES originated from CEB/Gartner research
– Document360 — Self-Service Statistics 2025 — 90% expect self-service portal; 81% attempt self-service first
– ProProfs — Self-Service Statistics — 73% prefer solving independently; 61% prefer self-service for simple issues
– ServiceTarget — Self-Service Cost Reduction — 40-60% routine inquiry deflection; ROI exceeds 1,000%
– KnowMax — Self-Service Reports — 77% say bad self-service is worse than none
– Fixify — 2026 IT Help Desk Benchmark Report — AI resolution: 2.4-6.3 hours; 80%+ negative-to-satisfied conversion
– Jitbit — Average Support Metrics from 1,000 Companies — Median resolution: 82 hours; top 5%: 17 hours
– Endsight — IT Help Desk Benchmarks — 21 tickets/technician/day; 26.5 min avg response
– SurveySparrow — CSAT Benchmarks 2026 — National average: 76.9/100 (ACSI Q4 2025)
– 31West — After-Hours IT Support — Only 15% of companies offer 24/7 support
– SRS Networks — Remote IT Support 2026 — Remote support eliminates geography constraints
– SwiftTech Solutions — After-Hours IT Support — 83% expect immediate interaction; 89% leave after poor service
– Market Intelo — Multilingual Support Market — $2.3B (2024) to $7.6B by 2033; CAGR 14.1%
– IMARC Group — Language Services Market — 75% prefer native language; 35% switch brands for it
– ITBD — IT Support Tiers Explained — Tier 1: 15 min-1 hour; Tier 2: hours-1 day; Tier 3: days-weeks
– Giva — 5 Tiers of IT Support — Tier 0 self-service offers most cost savings potential
– Buchanan Technologies — Tiered Support Best Practices — Robust ticketing for structured escalation and SLA tracking
Built by EEZYCORP LLC. Operated by AI. Designed for small business.