Most first-week problems are technical
When a first activity goes badly, the cause is rarely the activity. It's a microphone that isn't permitted, a browser that isn't cooperating, or a student sitting in a shared space who doesn't want to speak out loud. All of that is preventable with one email sent before the first deadline.
Lemon says: Everything in this guide is written to be copied. Take it, change the details, send it.
A syllabus paragraph
Putting this in the syllabus sets expectations on the record and heads off the "nobody told me" conversation later in term.
Copy this into your syllabus
This course uses ChitterChatter for spoken practice outside class. You'll have regular short speaking activities where you hold a conversation with an AI partner in the target language and receive feedback afterwards. Each activity takes about [X] minutes. You may practice the same activity as many times as you like, and where an activity requires a submission you choose which attempt to submit. You'll need a working microphone, a reasonably quiet space, and a current browser. These activities are assessed on [participation / the rubric provided with each activity]. If you have a documented accommodation that affects spoken work, contact me in the first two weeks so we can arrange an alternative.
The accommodation line matters. Raising it proactively is far better than a student having to ask.
Lemon says: Fill in the brackets and you're done. Two minutes now saves a lot of email later.
A first email to students
Send this before the first activity becomes available, not on the day it's due. It covers setup and, just as importantly, sets the tone.
Copy this into an email
Before our first speaking activity this week, please take five minutes to get set up. What you need: • A microphone — a headset or earbuds with a mic works better than a laptop's built-in mic • A quiet-ish space where you're comfortable speaking out loud • Chrome or another current browser When you first start an activity your browser will ask permission to use your microphone. You have to allow this or the conversation can't begin. There's a mic test on the preparation screen before you start — please use it. A few things worth knowing: • You can practice the same activity as many times as you want. The first attempt is not the one that counts. • If you get stuck, it's fine to say you don't understand. Your conversation partner will rephrase. • Nobody expects this to be perfect. Keep talking — that's the whole point. Come and find me if anything doesn't work.
The "first attempt doesn't count" line reduces anxiety more than anything else you can say.
Lemon says: Students who know they can retry speak more on the first attempt. It's a real effect and it costs you nothing.
Microphone and browser troubleshooting
The same handful of problems account for nearly all first-week support requests. Having the answers ready saves everyone time.
- No sound picked up — open the browser's site information or permissions control and allow microphone access for ChitterChatter
- Permission was denied earlier — it must be re-enabled in browser site settings; the prompt won't reappear on its own
- Another app is holding the mic — video call software commonly blocks it; close it and reload
- Wrong input device — check the operating system's sound settings, especially with headphones connected
- Nothing works — try a different browser before anything else; Chrome is the most reliable
Lemon says: "Try Chrome and reload" resolves more of these than any other single step.
What to say in the first class
Five minutes of framing changes how students approach the whole term. The points below address the anxieties that actually stop students speaking.
- It's practice, not a test — nobody is listening live and judging
- You can retry as often as you want
- It's normal to be slow and to make mistakes; that's what practice is
- If you freeze, say so in the target language — your partner will help
- Your instructor can see the transcript of any attempt you submit, so treat it like homework you're handing in
Lemon says: That last one matters. Students should know their submitted transcripts are visible — it's both fair and a useful nudge.
Explain the in-conversation controls
Students who know the controls use them. Students who don't tend to freeze and quit. It takes thirty seconds to demonstrate.
- Details — the goals, the scenario description and your notes, and the transcript so far, available mid-conversation
- AI Text — shows the AI's response as text, which rescues a student who missed a word
- Pause and Resume — a break without ending the session, unless the activity limits or turns off pauses
- End — finishes the session; ending before the minimum time means no feedback
Lemon says: AI Text is the one to point out. It turns "I didn't catch that and now I'm lost" into a two-second recovery.
Setting expectations about feedback
Students who understand what the feedback is — and isn't — take it better. A short, honest framing prevents both over-trust and dismissal.
- It's generated from a transcript of what you said
- It's good at patterns across a conversation and less reliable about any single moment
- Speech recognition isn't perfect, particularly with accents — if something looks wrong, it may be
- Bring anything that looks off to your instructor
Lemon says: Telling students the transcript can misread them is honest, and it stops them internalising an error that wasn't theirs.