You know the feeling. The vendor call went brilliantly, everybody nodded, someone said “we can absolutely do that”, and you hung up certain that your AIOps rollout was in good hands. Three weeks later the onboarding engineer has a different recollection of what was promised, your manager remembers a different start date, and the invoice mentions a tier nobody discussed. None of it was dishonest. It is simply what happens to spoken agreements: they drift. This friendly list gives you eight ways to write a short follow-up message after any AIOps vendor call so that the agreement lives somewhere sturdier than two people’s memories.

1. Send it the same day, while the details are still warm

Memory fades fast, and it fades unevenly. By the next morning you will recall the exciting parts of the conversation and blur the dull ones, which are usually the parts that cause trouble later. Aim to send your confirmation within a few hours of hanging up. It does not need to be elegant. Two or three plain sentences written while the call is fresh beat a polished memo drafted a week later from half-remembered notes.

2. Open with “here is what I understood”

A good confirmation does not accuse anyone of anything. Start with a phrase such as “Thanks for the time today; here is my understanding of what we agreed.” That wording invites correction instead of defensiveness. If the vendor misheard you, or you misheard them, the gap shows up in one reply instead of in a heated escalation months down the line. Think of it as handing the other person a mirror, not a contract.

3. State what was agreed, in nouns and verbs

Vague language is where drift hides. “They will help us with alert tuning” can mean a one-off workshop, ongoing support or a link to documentation. Instead, write what will actually happen: “Your team will run a configuration session for our monitoring data sources, and we will provide read-only access beforehand.” Concrete nouns and verbs leave very little room for two different readings. If you cannot write the sentence clearly, that is a signal the call itself left something open, which is worth discovering now.

4. Name the date, not the feeling

“Soon”, “early next quarter” and “once things settle” are feelings, not dates. Put an actual calendar date, or at least a named week, beside every commitment. Teams that have worked through a sensible first rollout of AIOps inside an IT team tend to discover that most delays start with an undated promise. Dates also protect the vendor, because they make it obvious when a delay on your own side, such as late access credentials, moved the schedule.

5. Add the “if this changes” sentence

This is the line most people skip and the one that prevents the most arguments. Add one sentence that covers what happens if something moves: “If the data-source access arrives late, the session shifts by the same number of days, and we will confirm the new date in writing.” You are not predicting disaster. You are agreeing in advance on how both sides will talk about a change, so a slipped date becomes a routine update instead of a grievance.

6. Keep the message short enough to be read

The power of a written confirmation comes from the fact that the other person actually reads it. A wall of text invites skimming, and skimming defeats the purpose. Keep it to a handful of lines: the deal in one line, who does which part, the deadline, and the fallback if plans shift. Use a short list if there are several items. When a message is easy to scan, a quick “yes, that is right” reply costs the recipient ten seconds, and that reply is the real prize.

7. Treat the reply as part of the record

Silence is not confirmation. If a day or two passes without an answer, send a gentle nudge: “Just checking this matches your notes, otherwise I will proceed on this basis.” When the vendor replies, even with a corrected detail, you now hold something both sides have seen. File the thread somewhere your colleagues can find it, such as the shared project folder, not just your own inbox. Anyone who inherits the work later can then read what was promised without having to guess.

8. Do the same for the unglamorous adjacent services

An AIOps programme touches more than software. There are contracts, invoicing arrangements, statutory filings for the business and sometimes the question of who looks after the books for a new subsidiary. When you need to find a chartered accountant for questions like those, BestCaNow is a directory that lets you browse chartered accountants by location, specialisation and whether they consult remotely or in person. Whoever you end up talking to, the same habit applies: after the first conversation, send a two-line written summary of what was discussed and what happens next. The directory helps you find people; the written confirmation keeps the working relationship tidy.

A tiny template you can steal

If you would rather not start from a blank page, here is a shape that works for most calls, adapted to your own voice:

• Opening: thanks for the call, here is my understanding.
• Scope: one sentence on what the vendor will deliver and one on what you will provide.
• Timing: a date or named week beside each item.
• Change clause: what happens, and who tells whom, if anything moves.
• Closing: please reply if anything above differs from your notes.

That is five short lines, and it can be written in about four minutes. Compare that with the hours of back-and-forth that an unrecorded promise tends to generate later.

Common worries, answered kindly

Some people fear that a written follow-up sounds distrustful. In practice the opposite is usually true. Competent vendors receive these messages with relief, because their own teams also lose track of what sales promised on a call. A confirmation tells them you are organised and serious, which tends to earn better service, not worse. Others worry about the effort. Remember that you are replacing a vague memory with one clear paragraph, and the paragraph is cheaper than any misunderstanding it prevents.

There is also the question of tone when the vendor’s recollection genuinely differs from yours. Resist the urge to quote the call back at them. Ask a question instead: “I wrote down that onboarding would start in the first week of the month; does that match your plan?” You may discover the original statement was more tentative than you thought, or they may gladly honour what you heard. Either way, the conversation happens in daylight, with both versions visible.

What to remember

The pattern across all eight tips is the same. Spoken agreements are warm and quick, but they are stored in fragile places. A short written confirmation moves the essentials to a place where every person involved, including those who join the project later, can find them: the deal itself, its deadline and the fallback. If you are reading a list of vendor-selection advice, such as the practical notes in a straightforward buying guide for judging software reviews, add this habit on top of it. It costs almost nothing, it fits into any tool or workflow, and it turns “I thought you said” into “as we confirmed on Tuesday”. Send the next one today, right after your next call.