Last updated: Wednesday 30th September 2026

AI customer service agents: measure trust, not tickets closed, and the revenue follows

The AI customer service agent that earns trust earns the revenue. The one that only closes tickets fast does not. That is the argument of IDC's September 2026 post on agentic customer service, sponsored by Meta. It ends with a one-question audit: when a conversation escalated, did the customer have to repeat themselves? This page sets out IDC's numbers in plain terms, what they mean for a clinic, showroom or hotel on WhatsApp, and how Learnmind builds agents that pass that audit.

A clinic receptionist holding a tablet talks with a smiling patient across the front desk
Trust is built when the person you reach already knows why you are there.

The short answer

Accuracy beats speed. IDC found the accuracy of autonomous resolutions is the single highest-rated driver of satisfaction with agentic AI, at 66%. Speed is not.

Context is four things, not one. Verified facts, behavioural signals, real-time intent and decision history. An agent missing any one, in IDC's words, "knows the customer accurately but understands them poorly".

The handoff is where trust is won or lost. 64% of organisations are satisfied with their AI handoffs, yet only 49% can fully keep the customer's context when a conversation crosses channels.

A solved problem is a natural moment to sell. Only if service and sales share what they know, so the customer gets one voice instead of two contradictory ones.

The whole audit is one question. Did the customer have to repeat themselves?

66%accuracy of autonomous resolutions, the highest-rated driver of satisfaction with agentic AI
64%are satisfied with how their AI agents handle escalation handoffs
49%can fully preserve customer context when a conversation crosses channels
15%have a unified view that carries context across the whole customer experience
43%are investing in AI-written conversation summaries at the handoff
5%treat trust as a C-suite priority, though 21% score every interaction for it

IDC's 2026 numbers on AI customer service, in one table

The IDC post was written by Roger Beharry Lall, published on 17 September 2026 and sponsored by Meta. It draws on seven IDC reports. Every figure below is as the post gives it, with the report it cites. The right-hand column is our reading for a business with one location and a handful of staff, not IDC's.

FindingFigureIDC source citedWhat it means for a smaller business
Organisations building agentic AI into service that rank better customer outcomes ahead of financial metrics54%Customer-Centric Organizations Are Doubling Down on CX with Agentic AI, April 2025The question is whether the customer was helped, not how cheaply
Organisations with fully centralised customer data32%Customer Experience Market Overview and Outlook, 2025-2026, September 2025Most businesses keep what they know about a customer in several places
Organisations with a unified view that carries context across the whole experience15%Same reportVery few can hand a customer from one channel to another without loss
Accuracy of autonomous resolutions as the top-rated satisfaction driver66%State of Contact Center and Customer Service Technology, August 2026A fast wrong answer is worse than a slower right one
Satisfied with how AI agents handle escalation handoffs64%Same surveyMost teams think their handoff is fine
Can fully preserve customer context across channels49%Same surveySome satisfied teams are losing context they cannot see
Apply a trust score to every customer interaction21%Customer Experience Market Overview and Outlook, 2025-2026Few score every conversation
Treat trust as a C-suite priority5%Same reportFewer still act on what they measure
Investing in AI intent detection and routing44%State of Contact Center and Customer Service Technology, August 2026Reading what the customer wants, and sending it to the right person
Investing in AI conversation summaries at the handoff43%Same surveyThe person who takes over gets a briefing, not a blank screen
Chief sales officers naming customer lifetime value a top-priority metric17% in 2024, 29% in 2025The Chief Sales Officer Agenda, March 2026Sales now cares about the repeat customer that service creates
Agentic buying's forecast contribution by 203030% of revenue, 20% of profit growthFutureScape: Worldwide Agentic Experience Orchestration 2026 Predictions, October 2025A forecast, not a result, and only if the business is ready
G2000 organisations forecast to have agentic operations ready by 203017%Same reportReadiness is the scarce part, and trust is one of the top three barriers

The contact-centre figures (66%, 64%, 49%, 44% and 43%) come from an IDC survey of 256 decision-makers at companies with more than 200 employees, in North America and the UK. None of it is Gulf data. A clinic in Jumeirah or a showroom on Sheikh Zayed Road has no C-suite to persuade. Its customers have the same expectations, and there are fewer people to meet them. That makes the findings more urgent for a small business, not less.

Context is four things, and an agent needs all of them

IDC defines context as "verified facts, behavioral signals, real-time intent, and decision history working together". Each has a plain example in the post. We have added what the same thing looks like in a WhatsApp conversation with a Dubai aesthetics clinic.

IngredientIDC's exampleOn WhatsApp, at a clinicWhere it has to live
Verified factsA contract renewal dateThe last treatment date and the package the patient boughtThe customer record
Behavioural signalsA shift in support-ticket frequencyThree messages about the same appointment in two daysThe conversation history
Real-time intentA frustrated tone in a chat transcript"This is the second time I have asked" at 11pm, in ArabicThe message itself, read as it arrives
Decision historyA prior retention offer on fileA goodwill discount given last month after a late startNotes on the contact, visible to whoever replies next

IDC's warning is precise. "Miss one, and the AI customer service agent knows the customer accurately but understands them poorly." An agent with the facts but not the decision history offers a second discount. One with the history but not the intent sends a cheerful reminder to someone who is already angry.

Where context hides in a small business

IDC found only 32% of organisations have fully centralised customer data. In a business with ten staff the scatter is more personal than a set of databases. It usually looks like this:

Most of these hold one of IDC's four ingredients. None holds all four. An AI agent connected to only one of them will be fluent and partly blind.

The fix is not a bigger model. It is one business number, one inbox and one record per customer that every reply, human or AI, reads first. The context layer is the part of an agent a business cannot buy off the shelf, and this is why.

Accuracy beats speed, so stop celebrating response time on its own

IDC's strongest finding is the plainest. "The accuracy of autonomous resolutions, not speed, is the single highest-rated driver of satisfaction with agentic AI performance, at 66%." Leading organisations, the post says, are dropping ticket-closure speed as their primary metric altogether. "A resolution can take as long as it needs."

Speed still matters at the very first message. A new enquiry on WhatsApp is deciding whether anyone is there at all, and an answer in seconds keeps it. After that first reply, being right matters more than being fast.

A confidently wrong answer is the most expensive thing an agent can say. Quote last season's price in four seconds and the business inherits a dispute, a refund conversation and a customer who now checks everything twice. The customer believed the agent. That is exactly the trust the business spent.

Three wrong answers that cost more than a slow one.

A price the business stopped charging. Availability that disappeared an hour ago. A policy exception that only the manager can grant.

Each comes from the same cause: the agent answering from something other than a maintained, approved source.

This is why a Learnmind agent works from a playbook the business approves: what it may quote, promise and recommend. A question outside that playbook goes to a person, not a guess. For clinics we add hard no-go rules on anything clinical. A business that wants to start cautiously can run in approval mode, where a person signs off every reply until they trust it.

The handoff is where AI customer service wins or loses trust

This is the finding that should worry most businesses. Some 64% of organisations are satisfied with how their AI agents handle escalation handoffs. Only 49% can fully preserve the customer's context once a conversation crosses channels. IDC's verdict on that gap: it is "where agentic customer service actually breaks down".

Other research points the same way. In J.D. Power's 2023 study of US customer service, people had to give the same information more than once in about 40% of phone contacts. In a Gartner survey from early 2026, 87% of customers said it is essential that a company using generative AI for service offers a way to reach a human agent.

A woman takes a phone call and writes notes while a colleague beside her looks on
When a person takes over, the notes should already be on the desk.

IDC calls the customer's experience of that moment binary. The next person, human or AI, either carries the conversation on or starts it again. There is no partial credit. A customer who has to restate the problem to a person, after explaining it to an agent, has learned that the business was not listening.

The momentA restartA carry-over
The person's first message"Hi, how can I help you today?""I can see Thursday's 6pm doesn't work. I have Saturday at 4pm, would that suit?"
LanguageSwitches to English because the staff member doesStays in the language the customer chose
HistoryAsks for the booking reference againAlready has the booking, the earlier messages and last month's visit
PromisesUnaware of what the agent said would happenHonours "someone will confirm before 8pm" because it is in the note
What the customer concludesThis business is several people who don't talkThis business remembers me

What a handoff note should contain

IDC reports that 43% of organisations are investing in AI-generated conversation summaries at the point of handoff, and 44% in AI intent detection and routing. Both aim to make sure the next person knows what the customer already said. A good summary is short, and it answers seven questions. Here is one, for an illustrative patient at a Dubai clinic.

An example handoff note, read by the person taking over

Who: returning patient, second visit, writes in Arabic.

Wants: to move Thursday's 6pm laser appointment to the weekend.

Already tried: Saturday 11am and 2pm offered. Neither works.

Mood: frustrated. Second time asking this week.

On file: 10% goodwill discount given in August after a late start.

Told so far: a person will confirm today before 8pm.

Do not: offer another discount without the manager.

Illustrative example. The format is ours, not IDC's.

Four of IDC's ingredients are in it. "Who" and "On file" are verified facts and decision history. "Mood" carries both real-time intent and the behavioural signal: second time asking this week. The other lines, what the customer wants, what has been tried and what they have been told, are our additions.

The person who picks this up answers in one message, in Arabic, before 8pm, without a second discount.

When to hand over in the first place is its own subject, with its own rules. We cover it in how to build an AI agent customers trust. This page is about what travels with the customer when the handoff happens.

WhatsApp's own rules point the same way. Its Business Messaging Policy says a business "may use automation when responding during the 24-hour window, but must also have available prompt, clear, and direct escalation paths". An in-chat transfer to a human agent is one of the paths it lists. The others are a phone number, email, web support, a store visit or a support form. Only the in-chat transfer keeps the customer inside the conversation they started.

On Messenger and Instagram, Meta's conversation routing passes a thread between an app and a human inbox. For independently built WhatsApp agents we found no general equivalent in Meta's developer documentation. The handoff happens inside the system that runs the agent. That makes where the conversation lives, and who can see it, a design decision rather than a detail.

Trust is measured more often than it is acted on

Only 21% of organisations apply a trust score to every customer interaction, and only 5% treat trust as a C-suite priority. IDC's summary is blunt: "Organizations are measuring trust faster than leadership is acting on it." In a small business the owner is the leadership, so the owner can close the gap by acting on what the numbers show.

A trust score does not need a data team. It needs someone to read a sample of conversations every week and count six things. This is our method, not IDC's.

SignalHow to count itWhat it tells you
RepeatsThe customer restates something already said in the threadContext is being lost inside one conversation
Corrections"No, I said Saturday." The customer fixes the agentThe agent is not reading carefully, or the facts are wrong
Restarted handoffsThe person's first message asks for something the customer already gaveThe handoff note is missing or unread
Unkept promises"Someone will call you" with no call loggedThe agent promised on behalf of a team that never saw it
Tone at the endIs the last customer message warmer or colder than the first?Whether the conversation built trust or spent it
ReturnsCustomers who write again within 30 days, for something newThe only trust signal that pays directly

In our experience, twenty conversations a week is enough to see a pattern. The first four signals should fall over time. The last two should rise. If they do not, the fix is usually upstream, in the facts the agent reads or the note it passes on, not in the wording of its replies.

The upsell window opens after the problem is solved

The share of chief sales officers naming customer lifetime value a top-priority metric rose from 17% in 2024 to 29% in 2025. IDC's point is that customer service already produces what sales needs to act on that: a signal, a moment and a reason to get in touch.

A shop assistant shows a product box to a smiling older customer beside wooden shelves
A suggestion lands after the problem is solved, not before.

The timing matters. "A customer whose issue just got resolved and whose sentiment just shifted to positive is in a different life-cycle stage than they were 48 hours before," the post says. Paired with what the agent has just learned, that timing makes the next conversation feel earned rather than opportunistic. In IDC's words: "Trust, not timing alone, is what makes the offer land."

The failure IDC describes can happen in any business where more than one person sends messages. A customer at risk of leaving gets a discount from customer service. Marketing does not know. The same customer gets a contradictory upsell email that same week. The business has spoken with two voices, and the customer notices.

Six rules for an AI agent that suggests the next purchase

  1. Only after the customer confirms the problem is fixed"That works, thank you" is the signal. Silence is not.
  2. Never in the same message as an apologyAn apology with an offer attached reads as a sales tactic.
  3. Only something the conversation made relevantAftercare after a facial. A service plan after a car's first service. A late checkout after a room move.
  4. Never while anything is openA pending refund, an unresolved complaint or a promised callback closes the window.
  5. Read the decision history firstIf a discount went out this month, a full-price promotion this week is the contradiction IDC describes.
  6. OnceIf the customer says no, or does not reply, the agent does not repeat the suggestion tomorrow.

On WhatsApp, anything promotional sent outside a live conversation also needs the customer's opt-in and an approved marketing template. We explain the UAE side of that in WhatsApp marketing consent in the UAE.

IDC's broader frame is an "agentic mesh": agents across service, marketing and sales that pass context between them so the business can "act as one brand". A small business can get most of the way with less. One timeline per customer that every message, human or AI, reads before it is sent. IDC's point on cost is the same: the real savings arrive "when a problem doesn't have to be solved twice".

What to measure instead of tickets closed per hour

"Tickets closed per hour stops being the metric that matters," IDC concludes. What replaces it, the post says, is whether the customer felt understood and whether the exchange built enough trust to survive the next one. Here is how we turn that into numbers a business can actually track on WhatsApp.

Common metricWhy it misleadsTrack this instead
Tickets closed per hourRewards closing, not solvingProblems still solved seven days later
Average handling timePunishes the long conversation that kept the customerAccuracy, checked weekly on a sample of answers
Deflection rateCounts customers who gave up as successesCustomers who had to repeat themselves, the lower the better
Average response timeA fast wrong answer scores wellFirst response time for new enquiries, then accuracy for everything after
Cost per contactIgnores what the contact was worthBookings and repeat purchases traced to the conversation that produced them

Every Learnmind WhatsApp build ships with a dashboard that keeps first response time per conversation, not a monthly average that hides the 3am ones. It ties each booking to the chat that produced it and shows customer lifetime value alongside where every lead came from.

What is ready for an AI agent now, and what still needs a person

IDC separates what is production-ready today from what still needs to mature. Ready: proactive issue detection and context preservation across touchpoints. Still maturing: "fully autonomous AI agents handling complex judgment calls without a human representative in the loop". IDC's advice is to build the data architecture before adding agents. The split below is ours, not IDC's.

Give it to the agent todayKeep a person in the loop
Prices, availability, location and policy questions, answered from approved factsRefunds, and any exception to a written policy
Booking, rescheduling and remindersComplaints involving money, health or safety
Reading intent and routing the conversationClinical, legal or financial advice
Writing the handoff noteYour most valuable relationships, when they ask for you
Follow-ups the customer agreed to receiveAnything the playbook does not cover

IDC notes that trust and governance concerns rank among the top three barriers when deployments stall. Its reading of the 2030 forecast follows from that. The organisations that capture agentic revenue first are "more likely the ones that solved trust before they scaled". Starting narrow, with a person in the loop on the right questions, is how a business earns the right to widen.

Transparent by default: tell customers what the agent is and what it knows

IDC's picture of winning includes being transparent "by default about how customer context gets accessed and used". For a business on WhatsApp in 2026, that has three practical parts.

In the EU, the law now requires it. Article 50(1) of the AI Act has applied since 2 August 2026. It requires AI systems that interact directly with people to be designed so those people are informed they are talking to an AI, unless that is obvious from the circumstances.

The UAE's Federal Decree-Law No. 45 of 2021 has no specific rule on disclosing AI. It does require personal data processing to be "fair, transparent and lawful". Its Article 13 lets customers ask about the purposes of processing and decisions made by automated processing.

Two exclusions matter here. Health data that has its own legislation is outside the law, which affects clinics. Businesses in the DIFC and ADGM free zones fall under those zones' own data protection laws instead.

On a Learnmind build, the WhatsApp number, the conversations and the chat history belong to the business. If we part ways, the business keeps all of it, and we hand over cleanly and delete what we hold. We explain the UAE rules in more depth in WhatsApp and UAE data protection.

The one-question audit, run on your own WhatsApp this week

IDC closes with a test anyone can run. "The next time a support conversation escalates, ask whether the customer had to repeat themselves. That single question is the whole audit." Here is how to run it in under an hour.

  1. Pull the last 20 conversations that reached a personFrom the shared inbox if you have one, from staff phones if you do not.
  2. Read only the person's first message after the handoffThat one message shows whether the context arrived.
  3. Mark every question the customer had already answeredName, booking, problem, preferred language, what they were promised.
  4. Mark every place the customer restated the problemEven politely. "As I said earlier" counts.
  5. Count the marksEach conversation with a mark is a restart. Write the number down.
  6. Find the cause of each restartNo summary, no history, a different inbox, or a staff member who did not read it.
  7. Run it again in four weeksThe number should fall. If it does not, the fix went to the wrong place.

The audit works whether or not you use AI at all. It also catches restarts between two people, such as the owner and a receptionist, which no AI project will fix on its own.

What this looks like for a UAE clinic, showroom and hotel

WhatsApp is how many customers in the Gulf reach a business, so for UAE businesses the handoff often happens inside WhatsApp itself. The context that matters, the moment to hand over and the right follow-up differ by sector.

Aesthetics or dental clinicCar showroom or rentalHotel or holiday rental
Context that matters mostTreatment history, the practitioner, the package boughtThe car asked about, trade-in, finance status, documents receivedDates, the room, arrival time, what went wrong on the last stay
Hand to a person whenAnything clinical, any complication, any refundA price negotiation, a test drive, a damage disputeA complaint during the stay, a VIP guest, a group booking
The handoff note must carryLanguage, the treatment, what was promisedThe car, the budget, the deposit statusRoom number, the issue, what was offered
The right next suggestionAftercare, or the next session in a courseA service plan, or insurance at handoverA late checkout, or a return-stay rate
Never whileA complication is being handledA deposit dispute is openA complaint is unresolved

Language is part of context in the UAE in a way it is not in many markets. A customer who wrote in Arabic and is answered in English by the person who takes over has been restarted, even if every fact survived. Learnmind agents reply in the language the customer writes in, with English and Arabic standard for our Gulf clients. The person who takes over sees the whole conversation.

How Learnmind helps businesses win on trust, and then on revenue

Learnmind builds WhatsApp AI agents for businesses where the experience is the product. Customers hear an agent that sounds like the business, not like a bot, and one that remembers them. Remembering is what IDC calls context, and IDC's research ties context to trust and to the next sale. This is how a Learnmind build answers what IDC found.

What IDC foundWhat it looks like on WhatsAppWhat Learnmind builds
Accuracy over speed (66%)Confident answers from stale pricesA playbook you approve; outside it, a person, not a guess; optional approval mode
Scattered customer data (32%, 15%)Owner's phone, receptionist's phone, booking systemOne business number and one inbox; every conversation, contact and booking in the operator dashboard each build ships with, or in your own CRM or the Learnmind AI CRM
Context lost at handoff (49%)"Can you send your booking reference again?"Handover with the whole conversation, the client profile and exactly where things stand
Summaries at handoff (43%)A person picks up coldYour team alerted with the full conversation context; for one client, a detailed email briefing and the whole transcript when a qualified lead books
Trust measured, not acted on (21%, 5%)Nobody reads the conversationsA human team that reviews real conversations and closes the gaps it finds
Contradictory offersA discount from one person, a promotion from anotherEvery conversation in one inbox, with each client's history and what they have ordered, so whoever writes next can see what was offered
Lifetime value (17% to 29%)No idea which conversations produced revenueA dashboard that traces bookings to the chat and shows customer lifetime value

One example from our own work. Alcaz Media, a UAE performance marketing agency, runs a Learnmind agent on its WhatsApp.

When a qualified prospect books a strategy session, the founder receives a detailed email summary with the full conversation transcript. By the time the call starts, the founder already knows who the prospect is, what they need, their budget and what they care about most. When the agency's pitch, case studies or pricing change, the agent is updated the same day. The full case study is on our results page.

Most Learnmind agents are live within 14 days. See how a Learnmind agent goes live, or what the WhatsApp agent does from first message to confirmed booking.

Want an agent your customers never have to repeat themselves to?

We build WhatsApp AI agents that sound like your team, work from facts you approve, and hand over to your team with the whole conversation attached.

Terms worth being precise about

Agentic AI
AI that takes actions, such as booking or routing, rather than only answering questions.
Context
In IDC's definition, verified facts, behavioural signals, real-time intent and decision history, working together.
Escalation handoff
The moment a conversation passes from an AI agent to a person, or to another agent.
Handoff note
A short written summary the agent passes on, so the next person does not ask the customer again.
Intent detection
Reading what a customer wants, and how they feel, from what they write.
Trust score
Our working definition: a measure, per interaction, of whether the exchange built or spent the customer's trust.
Customer lifetime value
The total a customer is worth to a business across every purchase, not just the first.
Agentic mesh
IDC's term for connected agents across service, marketing and sales that pass context between them.

Frequently asked questions

What matters most in AI customer service, according to IDC?
Accuracy. IDC found the accuracy of autonomous resolutions is the single highest-rated driver of satisfaction with agentic AI, at 66%. Speed is not the top driver.

How does an AI agent hand over to a human without the customer repeating themselves?
It passes the whole conversation, a short summary, the customer's history and what the customer has been promised. The person's first message then continues the conversation instead of starting it again.

What is a trust score in customer service?
A measure of whether each interaction built or spent the customer's trust. IDC found only 21% of organisations apply one to every interaction. A small business can approximate it by counting repeats, corrections and restarted handoffs in a weekly sample.

Should an AI customer service agent try to upsell?
Only after the customer confirms the problem is solved, only with something the conversation made relevant, and never while a complaint or refund is open. One suggestion, once.

What should replace tickets closed per hour as a metric?
Problems still solved a week later, answer accuracy, customers who had to repeat themselves, and revenue traced to the conversations that produced it.

Can a small business do this without a data team?
Yes. One WhatsApp business number, one inbox, one record per customer that every reply reads first, and a weekly read of twenty conversations.

Does a WhatsApp AI agent have to offer a human?
Not necessarily inside the chat. WhatsApp's Business Messaging Policy requires a business that automates replies in the 24-hour window to have "prompt, clear, and direct escalation paths". An in-chat transfer to a human agent is one option; a phone number, email, web support, a store visit or a support form are the others. Only the in-chat transfer keeps the customer's context in one place.

Do customers have to be told they are talking to an AI?
In the EU, yes, unless it is obvious: Article 50(1) of the AI Act has required it since 2 August 2026. The UAE's federal data protection law has no specific AI disclosure rule, but requires processing to be fair and transparent. Either way, if a customer asks whether they are talking to a person, the answer should be true.

Are AI customer service agents allowed on WhatsApp?
On our reading, yes, for a business's own customer service. Since 15 January 2026, Meta's terms have barred AI providers from offering general-purpose assistants on the WhatsApp Business Platform, unless legally required. An agent that answers a business's own customers about its own services is incidental to that business: that is how we read the terms, and how Learnmind agents are built.

How we checked this, and what we could not settle

Checked: every IDC figure and quotation on this page comes from IDC's blog post "AI Customer Service Agents: Earn Revenue by Earning Trust". The one exception is the survey's sample, taken from IDC's own summary of that report.

The post was written by Roger Beharry Lall and published on 17 September 2026. We read it in full, and each figure is attributed to the IDC report the post itself cites. The post is published on Meta's WhatsApp Business site, marked "Sponsored by Meta", and was last modified on 28 September 2026. We confirmed that all seven IDC reports it cites exist on IDC's site, with the titles and dates given.

The WhatsApp policy and Meta's platform terms were read on 30 September 2026, both last updated on 23 September 2026. The EU AI Act wording and dates come from the European Commission's AI Act Service Desk and its quick facts on transparency rules. The UAE law is quoted from the official English text on uaelegislation.gov.ae. The J.D. Power and Gartner figures come from their own press releases.

Not settled: the seven IDC reports behind the post are paid research, and we have not read them. The post itself gives no sample sizes, regions or question wording. IDC's own report summaries fill part of that gap: the contact-centre survey covers North America and the UK only. For the other reports, we cannot say whether UAE organisations were included.

The post is sponsored by Meta, which runs WhatsApp, Messenger and Instagram and has an interest in business messaging. The 2030 figures are forecasts.

The J.D. Power figure is for US phone contacts in 2023, not chat. We found no WhatsApp handoff mechanism for independent agents in Meta's documentation, but we cannot rule out one we did not find. The UAE data protection law gives businesses six months to comply once its Executive Regulations are issued. Every official page we could read shows them still unissued, but we could not confirm the position on the day of writing.

Several parts of this page are our own work, not IDC's findings. They are the handoff note, the restart and carry-over table, the six trust signals and the six upsell rules. So are the metrics table, the split between agent and person, the seven-step audit and the sector table.

Sources

Written by Edmund Gay, Learnmind.ai, Dubai. Figures and quotations are as published in the IDC post (last modified 28 September 2026); forecasts are IDC's own; the interpretation, checklists and examples are ours.