Day 4: Test, Revise, and Help the User

Daily Learning Contract

• Topic: Customer Service
• Objective: Students will identify communication and problem-solving skills that transfer among careers by testing a help desk sequence, revising it from feedback, and responding to a frustrated user.
• TEKS: d(4)(B)
• Demonstration of Learning: Students document one partner-test finding and one revision, then complete a customer-service response that follows four support rules and names another career that uses the same skill.

Lesson Overview

Before Students Arrive

Keep the Day 3 teams and pair each team with one neighboring test team. Per team, set out one saved project or paper trace and one Program Evidence sheet. Print one Role-Play Script per pair, one Customer Service Check per student, one monitoring roster for the teacher, and place the optional bilingual script at the same table. Post a visible timer and the four customer-service rules.

Bellringer — Technical Problem or Communication Problem? (5 min)

Prompt: A technician knows the correct fix but gives five fast directions full of jargon. Did the technician solve the user's problem? Explain.

Bridge: technical accuracy matters, but a user must be able to follow the explanation.

Activity 1 — Reopen and Finish the Core (15 min)

Teams confirm:

• three Button A steps;
• return to Step 1 after Step 3;
• Button B displays FIXED; and
• the evidence sheet explains the first-step reason.

Core behavior comes before sound, animation, or extra steps.

Cap file recovery at three minutes. If a project does not reopen, use the named backup or paper trace instead of rebuilding.

Activity 2 — Partner Test and Revision (10 min)

Partner teams run or trace the sequence without an explanation. They record:

1. one part that was clear;
2. one point of confusion; and
3. one specific suggested change.

Think-Pair-Share: silent notice, Team A evidence, Team B evidence, then a shared revision decision. Sentence stems:

• “The order made sense because ___.”
• “I got stuck at Step ___ because the words ___.”
• “Change ___ to ___ so the user can ___.”

Each team makes and documents one revision.

Activity 3 — Customer-Service Role-Play (15 min)

Teach the four rules before practice:

1. acknowledge the problem;
2. use plain language;
3. give one step at a time; and
4. stay calm and explain what happens next.

Pairs complete one short round and switch roles for a second round if time allows. A written chat transcript or annotated script is an equal route.

Active monitoring: record one observed example for each student. If several students skip acknowledgment, pause and model one opening line. Do not grade acting confidence, accent, or humor.

Activity 4 — Customer Service Check (10 min)

Students select the best first response, identify two rules it follows, rewrite one rejected response, and name another career that uses the same communication skill.

Begin this check by minute 40. Use the final two minutes to collect checks, scripts, and team evidence and return any hardware.

Answer key: C. It acknowledges the urgency, uses calm language, and asks one diagnostic question. A corrects emotion instead of helping; B skips acknowledgment and assumes a cause; D abandons the user.

Supports

• Let students rehearse privately before a partner round.
• Use bilingual phrases and a visible word bank: acknowledge/reconocer, step/paso, explain/explicar, escalate/pasar al especialista.
• Allow speech-to-text, written chat, or teacher-partner practice.
• Use the stem: “A ___ also needs this skill because ___.”

If the Project or Student Is Missing

Paper teams swap and trace the same sequence. If a saved project is missing, use the backup instead of spending the period rebuilding. An absent student completes a written support exchange and reviews a supplied test result before recording a revision.