TOEIC Link Self-Service Kiosk Installation and Support Service Vocabulary: The Deploy-Configure-Support Cluster for Part 3, Part 4, and Part 7
In TOEIC Link, a lobby check-in kiosk is never just "the machine by the door" — it is a unit surveyed and installed, a device configured and enrolled on the network, a workflow walked through with staff, a terminal monitored for uptime and paper jams, and a support call when it fails, and ETS can test every stage. A receptionist and a vendor technician discuss why the kiosk prints a blank visitor badge (Part 3). A recorded message tells employees that the new self check-in kiosks go live Monday and that anyone unable to scan their code should use the front desk (Part 4). An installation schedule sits beside an uptime report and a maintenance log, and a question asks why a kiosk was down, which site missed its go-live, or why a jam alert was not resolved (Part 7 triple passage). Because a kiosk deployment always runs the same loop — survey and install, configure and enroll, walk staff through it, monitor uptime and alerts, and dispatch maintenance — ETS can set what the kiosk reports against what the user actually experienced and leave exactly one answer standing. Miss a term like enroll, uptime, jam, or walkthrough and a linked pair can slip in one move.
This article organizes the cluster by the recurring deployment cycle — the site survey and installation, the configuration and enrollment, the user walkthrough, the uptime monitoring and jam alert, and the maintenance call — because that cycle is exactly how ETS threads the pieces together. Because a visitor kiosk does the same job the front desk used to do by hand, pair this first with the visitor check-in and facility badge access cluster — the same "who is this person and are they cleared to enter" logic governs both. And because a kiosk that prints an access credential depends on the door system behind it, contrast this with the access control and card reader installation cluster whenever a passage sets a badge issued against a door that still won't open.
Why self-service kiosk vocabulary is overweighted
Reason 1 — an uptime report plus a user complaint is a ready-made linked set. The uptime report says the kiosk was online; the user says it wouldn't print. A question asks why a visitor couldn't check in, and the two accounts force a single conclusion — precisely what a linked set needs. Only one reading reconciles "online" with "didn't work."
Reason 2 — a kiosk runs on a fixed deploy-then-support model. Because every unit is surveyed, installed, configured, and then monitored, ETS can ask "Which step was skipped?" or "Why did the go-live slip?" with exactly one correct answer. The reader has to trace the unit from install to live use.
Reason 3 — the terms are fixed service conventions. Enroll, configure, uptime, jam, and walkthrough mean the same thing across every kiosk program. That rigidity makes the cluster perfectly testable — and perfectly learnable. The collocation, not the isolated word, is the unit of memory.
The cluster, organized by the recurring deployment cycle
Stage 1 — the site survey and installation
Verbs and collocations: survey the site, install the unit, mount the kiosk, run the power and data, secure the enclosure.
Nouns: site survey, installation, mounting, enclosure, floor plan, cable run.
The recurring trap: a Part 3 conversation turns on the difference between a kiosk installed and a kiosk commissioned. A manager sees the unit bolted down and assumes it is ready; the technician explains it is installed but still needs a data line run before it can be configured. The question asks what the manager misunderstood, and the answer is the commissioning step, not the physical install. Installed ≠ ready to use.
Stage 2 — the configuration and enrollment
Verbs and collocations: configure the kiosk, enroll the device, connect to the network, load the workflow, set the permissions.
Nouns: configuration, enrollment, network, workflow, profile, firmware.
A Part 4 briefing often explains that the new kiosks must be enrolled on the company network before go-live — each unit registers, downloads its check-in workflow, and pulls the visitor directory. A question asks why a kiosk at one branch shows an error screen on launch day, and the answer is that it was installed but never enrolled. Installed ≠ enrolled.
Stage 3 — the user walkthrough
Verbs and collocations: walk staff through, demonstrate the workflow, train the receptionist, hand off the unit, post the instructions.
Nouns: walkthrough, demonstration, training, handoff, quick-start guide, prompt.
This is where adoption lives. Before a kiosk replaces a manual process, the vendor walks staff through the workflow so the front desk can help a stuck visitor. In Part 3, a receptionist who says "it's live, but no one showed us what to do when it jams" is describing the gap between a go-live and a handoff. ETS uses this because the unit being live and the staff being trained sit one step apart, and a distractor will treat the go-live date as proof that staff were prepared. Live ≠ staff trained.
Stage 4 — the uptime monitoring and jam alert
Verbs and collocations: monitor uptime, trigger a jam alert, flag the outage, report the error, clear the jam.
Nouns: uptime, downtime, jam alert, error code, outage, out-of-paper warning.
A kiosk program monitors uptime and fires an alert when a unit jams or runs out of badge stock. A Part 7 email may describe a jam alert raised at 9 a.m. and still open at noon, with visitors queuing at the desk. The trap sets "the kiosk is online" against "visitors can't check in": a unit can report healthy uptime and still be unusable because it is out of badge paper. The alert type, not the uptime number, is the answer. Online ≠ usable.
Stage 5 — the maintenance call
Verbs and collocations: log a service call, dispatch a technician, replace the part, resolve the ticket, schedule preventive maintenance.
Nouns: service call, dispatch, technician, replacement part, resolution, SLA.
When a fault outlasts a quick fix, the site logs a service call and a technician is dispatched under a service-level agreement. A Part 7 triple passage may set an alert timestamp against a resolution timestamp and ask whether the vendor met its response window. The trap treats a dispatched technician as a resolved fault: a call can be logged and a technician en route while the kiosk is still down. Dispatched ≠ resolved.
The paraphrase traps ETS builds on this cluster
Each stage can be restated, and the restatement is where the distractor lives.
- Installed vs. ready — "The kiosk is in place" is restated as "The kiosk is ready." The commissioning or enrollment step breaks the tie.
- Live vs. trained — "The kiosks went live Monday" is restated as "Staff can operate them." The walkthrough breaks the tie.
- Online vs. usable — "The unit shows healthy uptime" is restated as "It's working for visitors." The jam or out-of-paper alert breaks the tie.
- Dispatched vs. resolved — "A technician was sent" is restated as "The problem was fixed." The resolution timestamp breaks the tie.
In every case, the correct answer respects the boundary between a step started and a step completed; the distractor collapses the two.
How to drill this cluster for Part 3, Part 4, and Part 7
Read the cluster as one cycle, not twenty words. When a passage mentions a kiosk that isn't working, ask the cycle's diagnostic question: Was it installed, was it enrolled, were staff walked through it, is it reporting an alert, and has the service call been resolved? The answer to a TOEIC Link kiosk question is almost always the first stage that failed.
For Part 3 and Part 4, listen for the verb that marks a stage — installed, enrolled, walked through, jammed, dispatched. For Part 7, when an installation schedule sits beside an uptime report or a maintenance log, find the one line where the report and the user's account disagree; that line is the answer. Pair this cluster with the visitor check-in and facility badge access cluster and the access control and card reader installation cluster so that a kiosk, a badge, and a door all read as the same "issued vs. actually works" logic. Learn the collocations in their cycle and the linked set resolves itself.