Identify what actually happened
An examination can stop at several different stages: check-in may fail, the application may disconnect, a proctor may end the session, or the programme may later communicate a result decision. These situations should not be described as the same problem. Before preparing a complaint, identify the stage and the message you received.
A useful first record is a short chronology: appointment reference, programme, local time and time zone, whether questions had begun, the last non-confidential message displayed, and what support instructions you followed. Record observations separately from assumptions about the cause. This makes the case easier for support to investigate.
Use the authorised support route
Pearson directs candidates with persistent delivery problems to the customer-service route for their examination programme. Programme-specific support matters because the examination owner and delivery provider may have different responsibilities. Ask which team owns your case, whether an incident reference exists and what information is still needed.
If the session is still active, use the permitted communication mechanism and follow the instructions you receive. Do not open unrelated applications, invite someone into the room or use your phone unless authorised. A reasonable attempt to get help can itself conflict with examination rules when taken through the wrong channel.
Make a review request clear and factual
Use a concise message describing the event and the outcome you are requesting: clarification, investigation, confirmation of appointment status or information about the applicable review process. Include the relevant reference numbers. Avoid repeatedly creating new cases for the same event unless support instructs you to do so.
Preserve appointment confirmations, support correspondence and ordinary error messages. Do not record, reconstruct or send examination questions as evidence. If a rule-related decision is involved, ask for the applicable policy and the correct review procedure rather than assuming a general technical-support complaint is an appeal.
Do not assume the financial outcome
A disrupted session does not by itself establish that a refund, replacement voucher or free retake is available. The programme and delivery provider determine the outcome under their applicable terms. Keep the investigation separate from a new purchase so that an additional booking does not obscure the unresolved case.
If a voucher came through another seller, notify that seller with the support reference and ask what assistance its written terms provide. The seller cannot normally override an issuer’s examination-security decision. CertMatrix preparation support should not be represented as a guarantee that a stopped session will be reinstated.
Use the event to choose the right request
If check-in never completed, describe an access or admission problem: which verification step stopped and what the greeter told you. If the application disconnected after questions began, describe a delivery interruption and ask whether an incident was logged. If a proctor expressly ended the assessment for conduct, request the applicable incident and review process. These branches should not be combined into an unsupported statement that the result was “unfairly failed”.
For a Microsoft appointment, start with the testing provider’s programme support for delivery issues; an issuer security or credential decision may require Microsoft Credentials support. Ask support to confirm responsibility rather than forwarding the same message indiscriminately. Keep the existing case number in every follow-up so that facts and responses remain together.
An incident note you can adapt
An illustrative note is: “Programme: Microsoft. Appointment reference: [reference]. Time: 10:12 IST on [date]. The secure browser disconnected after the assessment started. I had not received a final score. I followed the displayed relaunch instruction and then contacted support; case [number]. Please confirm the appointment’s recorded status, the incident-review route and any further evidence needed.” Replace the example details with your actual observations; omit examination content.
For a rule-related termination, state the explanation you were given and your factual response without guessing what a recording will show. Ask which decision is currently final, whether a review deadline applies and how the outcome will be communicated. This is a case-organisation method, not a promise that an appeal will succeed. Retain the acknowledgement and check the original case before creating another request.
Decide what to change before another attempt
After the case is resolved, review the factor you can control: device compatibility, a private room, programme-specific break rules, identification or account details. Fix the confirmed issue, then repeat the relevant official checks. Avoid changing many unrelated settings on the assumption that one will prevent every future interruption.
Keep the final support decision with your examination records. If the cause remains uncertain, compare another approved delivery option, such as a test centre, before paying again. A calmer, evidence-based next step is more useful than a promise that the same problem can never recur.
Official references
Certification requirements and programme terms can change. Use the issuer’s current page and your account to confirm details before applying or paying.