Skip to content

Guide, read 10 Nov 2026

A reference call is worth having only if you ask about incidents, changes and exits, not about satisfaction

What should you do before an MDR reference call?

Ask the provider for three references: one of your size and sector, one with a real incident in the past year, and one that changed scope or left. A provider that cannot offer the third may have a reason. Write down what you need to learn, since a reference call lasts 30 minutes.

Providers publish customer statements on their sites. Arctic Wolf's MDR page quotes the Head of IT at BetterHome Group on not needing to re-tool, and Huntress's Managed ITDR page quotes a customer on disable account remediations. These are customer statements as published by the providers, read on 10 Nov 2026. They show how the provider presents itself and are not a substitute for your own call.

Questions on the first months

These test onboarding and are the ones references answer most freely.

  • How long did onboarding take, and what slipped?
  • Which sources were hardest to connect, and are all of them reporting now?
  • How noisy was month one, and how many exclusions did you add?
  • Who was your day-to-day contact, and has that person changed?
  • What did you have to do that the sales team did not mention?

Questions on authority and incidents

These test the contract in practice.

  • What actions does the provider take without calling you? Has it ever acted outside that list?
  • Describe your last real incident. How long until the first call, and what did the analyst know?
  • Was the escalation useful, or did you have to redo the investigation?
  • Did the provider help with counsel, insurers or regulators, and was that included in the price?
  • How did the provider handle an alert that turned out to be a false positive?

Questions on change and cost

These test the relationship over time.

  • Has the price changed at renewal, and by how much?
  • Which add-ons did you end up buying?
  • Did the provider change its platform, team or ownership while you were a customer?
  • How long does a detection change take after you ask?
  • If you left, how would you export your cases and detections?

Questions on scope and fit

These test whether the provider understands your environment.

  • Which of your tools does the provider cover well, and which did it ask you to replace?
  • Does the provider know your sector's usual attack routes, and did it show that in a case?
  • How does it treat cloud and identity alerts compared with endpoint alerts?
  • Did the provider reduce your after-hours calls, and by how much?
  • What would you change in the contract if you signed again?

How to read what you hear

References are chosen by the provider, so expect good news. Listen for specifics: dates, hours, names of tools, numbers. A reference who says it works great has told you little. One who says the second night's alert came 40 minutes after the host went quiet has told you much.

Keep notes in the same format for every call: question, answer, date, speaker's role. Share the notes with your team before you decide, and re-ask any answer that contradicts the contract. For scale, ENISA's Threat Landscape 2025 analyzes 4875 incidents between 1 Jul 2024 and 30 Jun 2025. Incident labels differ between reports and providers, so ask the reference what actually happened, in plain words, before accepting a category name.

Sources

  1. ENISA Threat Landscape 2025, read 10 Nov 2026
  2. Arctic Wolf, MDR page, read 10 Nov 2026
  3. Huntress, Managed ITDR page, read 10 Nov 2026

Last reviewed 10 Nov 2026.