Ask anyone who has worked a support rota for a few years how arrangements used to be settled, and a familiar picture appears. A client rings the duty phone. The engineer says, “We will keep an eye on it overnight.” Everyone feels reassured. By morning, nobody is quite sure whether “keep an eye on it” meant watching a dashboard, being ready to act, or merely reading the logs at breakfast. The trend in managed support today is a quiet move away from that picture, toward short written confirmations after almost every meaningful call. This piece follows one support lead through a year of that change.
A support lead’s first week of change
Marcus leads a small managed-services desk that looks after hosting and deployment pipelines for a handful of mid-sized clients. His team had grown the usual way, by being helpful. Helpfulness produced verbal promises: “we will restart it if it hangs”, “we can look at the backups too”, “call us any time”. After a particularly muddled weekend, in which a client believed the team had agreed to monitor a system that was never in the support scope, Marcus introduced one rule. After any call that changed what the team was doing, someone sends a two-line message to the client.
The message states what was agreed, who will act, by when, and what happens if the situation changes. Marcus expected grumbling. What he got was surprise at how well it landed.
What the shift looks like on the desk
Across managed support generally, three small shifts are visible, without needing any statistic to see them.
- Calls end with a promise to write. “I will send that over in writing” has become an ordinary closing sentence, much as “talk soon” once was.
- Tickets carry the agreement. Instead of living in someone’s notebook, the decision is posted to the ticket where everyone on both sides can read it.
- Clients ask for it. Buyers have been burned often enough that they now request a written summary themselves.
The common thread is that support is no longer judged only on speed of response. It is judged on whether the work done matched the work expected, and expectations can only be matched when they were captured.
Why the shift is happening now
Several pressures push the same way. Systems are more distributed, so more people depend on any single arrangement. Teams rotate faster, so the person who made a promise is often not the person who delivers it. Remote work has replaced hallway conversations with scheduled calls, which leave nothing behind unless someone writes. Each of these leaves memory shakier ground than it once was.
There is a cultural factor as well. The principles behind modern delivery, set out in our write-up on principles for steady software releases, emphasise transparency and shared understanding. A written confirmation is that attitude applied to a single conversation.
A small scene from the rota
Picture a Tuesday evening. A client’s developer phones the desk, worried about a slow deployment, and asks whether somebody can “just have a look” before morning. The engineer on shift, Leila, agrees. In the old days that would have been the end of it. Now she sends a short message straight afterwards: she will check the pipeline and the queue by ten that night, she will post findings in the ticket, and anything needing a change to the live system will wait for the developer’s go-ahead. The developer answers with a single word, “perfect”. Nobody has to guess in the morning what a look meant.
What changed for Marcus’s team
Within a quarter, the desk saw a pattern. The clients who replied “that is right” were the majority, and the replies that said “not quite” turned out to be the valuable ones. One client corrected a message about which environment was covered, revealing that they considered a test system part of the arrangement. Fixing that took five minutes. Left unfixed, it would have become a dispute at the next review.
Engineers felt the difference too. Junior staff, who used to dread phone calls where the client asked for “a little extra”, gained a sentence to lean on: “I will confirm what we can do in writing.” It took the pressure out of the moment, and it protected them from improvising promises they could not keep.
Where it can go wrong
The trend has its failure modes, and honest observers should name them.
- Over-long confirmations. Some teams respond to the idea by writing mini-contracts. Clients stop reading them, and the benefit disappears.
- Using the message as a weapon. A note that begins “as you agreed” and ends in blame damages the relationship it should protect.
- Never reading the replies. If corrections are ignored, the practice becomes theatre.
- Applying it unevenly. If only some engineers send confirmations, clients quickly learn that only some promises are firm.
Marcus’s answer to all four was to keep a template of five lines and to review a few threads together each month. Role clarity helps too: our guide to common DevOps role titles and what they involve shows how many hats a support engineer wears, which is exactly why the arrangement with each client needs to say which hat is on.
What clients can do from their side
The trend works best when both parties take part. As a client of a managed service, you can invite the habit by ending calls with, “Could you confirm that in an email?” You can also send your own summary first. If your provider replies with corrections, treat them as help. Both sides gain from a record that survives holidays, handovers and growth.
A look beyond technical support
Clients who run small businesses often have the same issue with other advisers. When it comes to accounts and company paperwork, some people look for a chartered accountant through a website that lets visitors filter chartered accountants by city, field of expertise and in-person or remote meetings. The habit transfers neatly: after the first conversation, send a brief message stating what you understood and what will happen next.
Where this probably goes next
Predictions are risky, but the direction seems clear. Written confirmation will probably become less of a conscious practice and more of an assumed courtesy, built into ticketing tools and call workflows. Some desks already generate a summary draft after each call for the engineer to edit and send. The tools will change; the principle will not. A shared record of what was agreed is easier to build at the moment of agreement than at the moment of dispute.
For Marcus, the best sign came a year in. A new client asked what the desk’s way of working was, and a junior engineer, unprompted, answered: “After every call, we write down what we agreed and send it to you.” The practice had stopped being a rule and become part of how the team describes itself.
Takeaway
Managed support is drifting from a culture of friendly verbal assurances to one of friendly written ones. The warmth is unchanged; the memory aid is new. Teams that adopt the habit early gain clients’ trust, protect their engineers from improvised promises, and catch misunderstandings while they are still small. If your own support arrangements still run on phone calls and good intentions, the move is simple: end the next call by saying you will send two lines, and then send them.
