You hear “Maya dot Lee”, type an address, and prepare to send. Before you do, a small uncertainty appears: was “dot” a punctuation mark, or part of the name? A useful repair is precise: “Do you mean the dot character, or the letters D O T?”
When an email address is dictated, separate letters, literal words and punctuation, then read back short chunks followed by the complete address. All addresses in this article are fictional teaching examples using reserved example domains. Do not send messages to them. The aim is accurate transcription, not proof that an address works or belongs to a particular person.
Choose a reading route: check the characters; see worked conversations; practise and compare answers.
Direct answer: ask what character belongs there
Start with the uncertain part rather than asking the speaker to repeat everything at the same speed. Say, “After Maya, is that a dot or an underscore?” Once the answer is clear, repeat the corrected chunk: “Maya, underscore, Lee.” Then check the part after the at sign separately. Finally, read the complete sequence and invite a correction before using it.
This gives both people a manageable checking job. The speaker listens for one possible mismatch; the listener changes one place instead of rebuilding the whole address from memory. A short explanation keeps the interruption courteous: “I want to get the characters right.” Neither person needs to apologise repeatedly for a routine clarification.
Why an address needs a different listening habit
In ordinary conversation, recognising the intended meaning often lets you continue. If someone says “the science group”, you can understand the group without checking every letter. An address requires the particular written sequence the speaker intends. A familiar name or plausible-looking ending can tempt you to supply something you did not actually hear.
For these exercises, treat the address as an exact copying task. Do not translate a name, replace an unusual spelling with a familiar one, insert punctuation because it looks tidy, or remove a mark because another service sometimes treats it differently. Preserve the supplied characters and ask about uncertainty. This article does not teach universal email-system rules.
A successful readback establishes that your copy matches what was supplied. It does not establish account ownership, permission to share material, message delivery or the safety of an attachment. Those are separate questions. Even a perfectly transcribed address can be the wrong destination for the task if the person supplying it selected the wrong contact.
Name punctuation without turning it into a word
The British Council’s email-address lesson explains that @ is spoken as “at”, . as “dot”, and _ as “underscore”. Cambridge identifies the hyphen as the mark -. These labels help listeners identify characters, but a spoken label may itself be intended as letters. Ask when the distinction is unclear rather than treating every occurrence as punctuation.
For example, the fictional address dot.team@example.com begins with the letters D O T, followed by a dot character. A careful speaker could say, “The word dot, D O T; then a dot; then team.” Likewise, at_home@example.org begins with the letters A T, then an underscore. Its later at sign separates the two main parts of the example address.
“Dash” can leave a listener wondering which mark to type. For an intended hyphen, name it explicitly and, if needed, show it in writing: -. Avoid substituting a longer typographic dash. If either person cannot confidently identify a symbol, an agreed written reference is more useful than repeating an uncertain label louder.
Use chunks, then check the join
Agree a pause after the part before @. For maya_lee@example.com, the first chunk is “Maya, underscore, Lee.” The next is “at example dot com”. If Maya’s spelling is unfamiliar, ask for the letters before confirming the chunk. Do not make someone spell every familiar word unless that extra check is useful.
After separate checks, read the complete address once. This catches a different kind of mistake: each chunk may be correct, but a separator can disappear or be added when the chunks are joined. Read from what you have actually written, not from what you remember hearing. The speaker should confirm the written sequence you reconstructed, not merely recognise the general sound.
Keep pauses in speech distinct from characters in the address. “Pause after Lee” is a speaking instruction, not an instruction to insert a space. If the speaker says “no spaces”, acknowledge that while retaining any punctuation they specified. A clean final readback should not include your notes, quotation marks or the sentence-ending punctuation around the example.
Fictional adult dialogue: dot or the word dot
Nina: “Please use dot team at example dot com.” Amir: “Does it begin with the word dot, or with a dot character?” Nina: “The word dot, D O T, then a dot character, then team.” Amir: “I have dot.team@example.com. The first three characters are D O T; there is one dot before team.” Nina: “Yes, that is the example I mean.”
The repair succeeds because Amir identifies the exact fork in interpretation. “Can you say it again?” might produce the same ambiguous sounds. He also checks the separator after the literal word rather than assuming that understanding the first word resolves the whole address. The fictional exchange concerns transcription only; no message is sent.
Fictional school dialogue: underscore or hyphen
Student: “The practice contact is art club at example dot org.” Teacher: “Is art club written together, or is there a character between the words?” Student: “An underscore: art underscore club.” Teacher: “So art_club@example.org, with the low line, not a hyphen?” Student: “Yes, underscore.” Teacher: “Thank you. I will keep that distinction in my practice copy.”
The teacher does not assume that a spoken pause represents a space. The student supplies the missing character, and the teacher contrasts two marks that can be confused. In a lesson, show both art_club@example.org and art-club@example.org and ask learners which matches the instruction. They should explain the differing character, not merely choose the more familiar-looking address.
Fictional team dialogue: a letter or a digit
Ravi: “Use plan zero two at example dot com.” Lin: “Are those digits zero and two, rather than the letters O and T?” Ravi: “Yes, the digits 0 and 2 after plan.” Lin: “I have plan02@example.com. Plan, digit zero, digit two, at example dot com.” Ravi: “That matches the practice address.”
Similar sounds create a different problem from missing punctuation. A helpful question names the possible character types. “Zero, the digit” is clearer than repeating “oh” when the listener is unsure. For letters that sound alike, use a mutually understood example word: “B as in book.” The example word clarifies the letter; it does not become part of the address.
Fictional family dialogue: stop guessing the ending
Aunt: “It ends with example dot org.” Nephew: “I wrote example dot com because I expected that ending. Let me change it.” Aunt: “Yes, O R G.” Nephew: “The complete practice address is family_notes@example.org: family, underscore, notes, at example dot O R G.” Aunt: “Correct.”
The nephew makes the mistaken assumption visible without blaming the speaker. Reading the domain ending as letters gives the aunt something specific to confirm. The lesson is not that one ending is more trustworthy than another. It is that a familiar ending must not replace the one actually supplied. Expectations are useful in conversation, but here they need checking against the characters.
A quick diagnostic before you ask again
Locate the uncertainty first. Is it a letter you did not hear, a digit that sounded like a letter, a punctuation mark, a literal word that sounds like a symbol name, or the boundary between chunks? Then ask a question that separates the plausible alternatives. “Is that underscore or hyphen?” is a better test than “Is that right?”
If there are several uncertain places, say so and restart slowly from a stable boundary: “I have the first name. Could we take the rest one chunk at a time?” Do not hide uncertainty to keep the conversation moving. A person who says “yes” after hearing only the familiar name has not necessarily checked the whole sequence.
Notice what kind of confirmation you received. “That is my usual name” confirms a name, not the punctuation or ending. “Yes, that complete address matches what I gave you” answers the broader check. If a written copy is available through an agreed channel, compare your transcription with that copy. Do not assume agreement merely because both versions look plausible.
Six practice situations
1. The punctuation word
Prompt: Your partner says, “dot club at example dot org”, intending dot.club@example.org. What question should you ask before completing the address? Write your question, then give a clear spoken readback of the intended sequence. Avoid solving the task by silently choosing the punctuation arrangement you prefer.
Answer: “Do you mean the letters D O T, then a dot character, then club?” A useful readback is “D O T, dot, club, at example dot O R G.” This distinguishes the literal word from the punctuation and checks where the separator goes. Simply repeating “dot club” leaves the original ambiguity in place.
2. The wrong separator
Prompt: The intended practice address is music_group@example.com. You wrote music-group@example.com. Give a repair that identifies the location and changes only the uncertain character. Then read the corrected address rather than the earlier version, even if the earlier one now feels familiar.
Answer: “Between music and group, you said underscore, not hyphen. I now have music_group@example.com.” This names the relevant position and the replacement. Saying “I fixed the line” is less useful because it does not identify which mark remains. The final readback checks that your correction reached the actual written copy.
3. A digit in the middle
Prompt: Your notes show teamO7@example.org. The speaker intended team07@example.org, with a zero after team. Ask a contrast question that does not assume the answer, and explain why the difference should not be dismissed as a minor visual detail.
Answer: “After team, is that the letter O or the digit zero?” Once confirmed, read “team, digit zero, digit seven, at example dot O R G”. The two characters are different transcriptions. You are checking the supplied sequence, not deciding that similar shapes or sounds must lead to the same destination.
4. At as letters and as a sign
Prompt: Dictate at_home@example.com to a partner who has not seen it. Your partner writes @home@example.com. How can you repair the beginning without making the explanation longer than necessary? Include the underscore and the later at sign in your correction.
Answer: “It starts with the letters A T, then underscore, then home. After home comes the at sign.” Read the full address after that correction. The explanation separates a literal word from a symbol name. It also prevents the listener from removing the genuine at sign while repairing the mistaken one at the start.
5. The guessed domain ending
Prompt: Your partner dictates reading.circle@example.org. You recognise “reading circle” and write reading.circle@example.com. Before any sending, you notice that you did not clearly hear the ending. What should you ask, and what should you avoid claiming after the answer?
Answer: “Could you spell the ending after the last dot? I wrote C O M, but I am not sure that is what you said.” After the partner confirms O R G, correct and read back the complete address. You may say the transcription matches the supplied example; you cannot infer delivery or ownership from that match.
6. An unresolved character
Prompt: A noisy connection makes the middle of study_notes@example.org unclear. The speaker repeats it twice, but you still cannot distinguish the separator. You are tempted to send to both possible versions. Give a better next step that keeps the uncertainty visible and avoids acting on guesses.
Answer: “I still cannot distinguish that character. Could you show me the address in writing through the channel we agreed to use?” If that is not possible yet, leave the action pending. Sending to multiple guesses does not resolve transcription. A clear pause preserves the difference between a confirmed address and an unfinished note.
Retrieval practice and transfer
Close the examples and recall the process in your own words: locate the uncertain character, ask a contrast question, confirm a chunk, and read the complete sequence. Then dictate one fictional address to a partner and swap roles. Record what caused the first mismatch: hearing, punctuation vocabulary, an assumed spelling, or failure to read from the written copy.
For a harder transfer task, have the speaker correct one character halfway through. The listener must update the copy and read the final version, not a mixture of old and new chunks. Use only fictional example-domain addresses during practice. You do not need real contacts, personal messages or a live email application to learn this skill.
The wider vocabulary guide supports learning words precisely. Here, useful vocabulary includes letter, digit, symbol, underscore, hyphen and readback. Knowing those terms matters most when you can use them in a short question that resolves a specific uncertainty. Memorising the labels without practising a conversation leaves the checking habit untested.
A four-week practice routine
Week 1: distinguish the characters
Use paper cards containing dots, underscores, hyphens, letters and digits. Take turns naming one character and pointing to it. Include contrasts such as zero and O, then discuss which explanation helped. Keep sessions short enough to maintain attention. The goal is reliable identification, not speed or a perfect performance on the first attempt.
Week 2: dictate and confirm chunks
Create three fictional example-domain addresses with different separators. One learner dictates the part before @, pauses for a readback, then gives the rest. Swap roles and compare the final copies character by character. Note whether the listener inserted anything during a pause. Correct the process gently before increasing the length of the examples.
Week 3: practise natural interruption
Add one ambiguity deliberately, such as the spoken word “dot” or an unclear digit. The listener must interrupt with a focused question rather than guess. Practise courteous openings: “Just checking the separator” or “Could you clarify that character?” Evaluate whether the question distinguishes alternatives, not whether it sounds elaborate. Clear, ordinary language is enough.
Week 4: transfer without sending
Role-play an adult enquiry, school activity, team discussion and family exchange. Use a fresh fictional address each time, and include one case that cannot be resolved immediately. Finish by saying whether the transcription is confirmed or still pending. Review one improvement and one remaining difficulty. Accurate stopping is part of the skill, alongside accurate copying.
Frequently asked questions
Should I spell every letter every time?
Not necessarily. Begin with the uncertain part and use chunked readback. Spell more when names, similar-sounding letters or an unreliable connection make that useful. The aim is a shared accurate copy, not the longest possible dictation.
Are dot, underscore and hyphen interchangeable?
Do not interchange them when copying an address. They are different characters. Preserve what was supplied rather than applying assumptions about how a particular email service might handle them.
Can I change capital letters automatically?
For this copying task, preserve the supplied form and clarify any uncertainty. Do not rely on a blanket claim that letter case never matters. This lesson does not establish the rules of any particular account or service.
Does a correct readback mean the email will arrive?
No. Readback checks your transcription against the supplied address. It does not verify delivery, account ownership, the intended recipient or permission to send particular material.
Why use example domains in practice?
They let learners discuss fictional addresses without inventing another person’s contact details. These examples are for reading and copying, not sending messages or testing delivery.
Language sources and teaching scope
The British Council lesson on saying email addresses supports the spoken labels at, dot and underscore. Cambridge’s entries for underscore and hyphen identify the corresponding marks. IANA’s explanation of example domains documents the illustrative purpose of example.com and example.org.
All dialogues, exercises, answers and practice routines here are original fictional teaching material. They illustrate conversation repair rather than email-system validation, delivery guarantees or security checks.