Nine contacts, four failures and a refrigerator repaired eight days late: the MT221 service encounter analysis for Unit 2 places each failure inside a designed step. Searches like "mt 221 unit 2 assignment example", "mt221 unit 2 sample" and "mt221 unit 2 example" land here.
What a finished MT221 Unit 2 service encounter analysis looks like
About four pages anchored by a nine-row timeline, one row per contact, from a six-minute Monday booking call to the second technician visit eight days later. Columns record the time, whom the customer dealt with, what that person was permitted to decide, what the customer experienced and whether the contact succeeded. Four rows are marked as failures: a booking that never asked for the model number, an arrival forty minutes past the window with no call, a part order given no delivery date, and a Friday status call answered only with in transit. A short costing section under the table prices the episode for the household: an $89 diagnostic fee, a $236 repair, roughly $140 of spoiled food and two mornings away from work. The closing pages trace each failure upstream to the process behind it.
How a MT221 Unit 2 example is structured
Chronology organizes the analysis, because an encounter is lived in order and a failure early in the sequence often explains several later ones. Each contact is treated as a moment of truth in Carlzon's sense, a point where the customer forms a judgment, and each is described in facts before any is judged. The critical incident technique supplies the sorting rule: a contact counts as a failure only when a specific event, not a general impression, made the experience worse. Failures are then followed upstream. The missing model number is placed in the booking script, which never asks for it, and the paper shows how that one omission kept the part off the first visit's truck. The unannounced late arrival is placed on the dispatch board, which carries no rule for calling ahead. Its final paragraph stays with the process, not the people.
Monday 8:10 to the following Tuesday
Nine contacts are listed with times: the booking call, a confirmation text, a Wednesday call chasing the technician, the late arrival, diagnosis, payment, a Friday status call, a scheduling call and the second visit that finished the job.
Who could decide what
One column records each person's authority. The scheduler could not name a technician or an hour inside the window, and the parts clerk could not quote a date, so two of the customer's questions had nobody able to answer them.
The question the booking never asked
No model number was taken on Monday, so the technician arrived without the evaporator fan motor that had failed. The paper shows this single missing field producing the second visit, a second fee conversation and most of the eight days.
Late, and silent about it
The technician reached the house at 12:40 against a window that closed at noon. Lateness is treated as a scheduling problem and the silence separately, because no rule told anyone to call before the window closed.
What the household paid
Fees, the repair, spoiled groceries and two mornings off work are totaled, since the cost to the customer rather than to the firm sets the size of the recovery that later units in the course go on to design.
Where marks go in MT221 Unit 2
Narrated frustration drains more credit from an encounter analysis than anything else, because events have not been isolated. A paragraph describing how annoying the week was cannot be graded against the criteria, while a row showing a 12:40 arrival against a noon window can. Missing the upstream cause is the second common loss: blaming the technician for arriving without a part, when the booking step never collected the information that would have put it on the truck, locates the failure in the wrong place. Many sections expect a named concept, moments of truth, critical incidents or the service encounter triad, applied rather than defined. Skipping the contacts that went well costs balance. Ending on an apology or a feeling, rather than on the process that failed, leaves the unit's central question unanswered.
Get a MT221 Unit 2 example written to your instructions
An encounter you lived through works best, especially one whose times can be rebuilt from texts, emails or receipts. Pass it on with the Unit 2 instructions and rubric. Within 24-48h the first custom sample arrives free, contacts in order and each failure traced to its step, with the business and its staff left unnamed.
MT221 Unit 2 questions, answered
Can the encounter be one I had as a customer?
Many Unit 2 prompts expect exactly that. A first-hand encounter gives the paper times and details no secondhand account can, and receipts, texts and call logs recover the ones memory has lost. If you work in service and would rather analyze an encounter from behind the counter, check the prompt first; some sections allow it and others want the customer's view.
What is a moment of truth?
The phrase comes from Jan Carlzon, who ran Scandinavian Airlines in the 1980s and argued that each brief contact between a customer and an employee decides how the whole company is judged. In an encounter analysis it justifies treating every contact on its own, small ones like a confirmation text included, because customers form judgments at each point, not just when the job closes.
How many steps should the analysis cover?
Enough to reach the cause. An encounter that went wrong at a counter may need only four or five steps, while one stretched across a week, like the repair in this example, needs every contact to show how an early omission produced later failures. Cutting steps to save space often removes the one that explains the rest, so trim prose instead of rows.