Spelling Recognition Failure When Capturing Email ...
# support
s
Hi @Vapi team The assistant fails to correctly capture the first part of an email address, even when each letter is being carefully spelled out by the user. This issue significantly impacts the assistant’s ability to collect accurate user information. Call ID: b6d44f31-5e73-4bae-848b-49901bc34e15 Timestamp: Starting around 01:25 During this call, the user attempts to spell out the first part of an email address (sai.yagneswarreddy) clearly and slowly, one letter at a time. Despite this, the assistant consistently misinterprets the letters and in some cases repeats characters incorrectly (e.g., repeating a letter 3–4 times instead of recognizing it twice or once). This makes the final captured email completely unusable and inaccurate.
v
Thanks for flagging this! I couldn't find enough info in the docs to help with the spelling recognition issue you described, so I'm escalating this to a human on the team to take a closer look. They'll be able to dig into the details and get back to you soon. If you want to check out general info on how transcription works in Vapi, you can find it [here](https://docs.vapi.ai/quickstart) and [here](https://docs.vapi.ai/how-vapi-works), but for your specific case, a human will follow up. 👍
c
Hey Sahil, it is to be expected because transcribers aren't trained on capturing email but rather things which have meaning assosicated with it.
s
hi Sahil tell me some way so that I can make the assistant take proper emails. Please try to understand Its very crucial for me. If you could provide some standard piece of prompt instructions or some examples that would be really helpful for me 🥹 🙏
c
Hey Sahil, the email transcription depends upon on the transcriber As sahil-vapi already mentioned. If you're okay with some rework, I can try to reduce the error rate by suggesting changes with in your prompt. Let me know what you think.
s
Hi Shubham that would be really helpful I am sharing my current prompt. It would be great if you could suggest some changes in this to make it better https://cdn.discordapp.com/attachments/1381544297857290331/1382576169035235419/message.txt?ex=684ba7e5&is=684a5665&hm=260088068e2cacdf5b7b7a4459af20c51bcc517466ed6fba603f03bbb492d6f8&
c
Hey Sahil, this is a communication message to let you know that I tried tweaking out of ROM with few different things, but it didn't work out. I'll take a look at it again later.
s
Hey Sahil, as Sahil from VAPI mentioned, it's primarily a transcription issue. However, you can still give this prompt a try. Final Instructions for Accurate Email Address Spelling in TTS
Copy code
To ensure accurate capture and confirmation of email usernames when users spell them out during voice interactions.

### 1. Ask for the Email Username

- If using a company domain:  
  *“Please spell out the first part of your email address, the part that comes before the @ symbol.”*
- If using a custom email:  
  *“Please spell out the complete email address.”*


### 2. Guide the User to Spell Slowly

- Encourage the user to say each character one at a time, or in small groups (3-5 characters).
- Example:  
  *“Please spell your email username slowly, one character at a time.”*

### 3. Confirm Each Segment Using the Phonetic Alphabet

- Break longer usernames into smaller segments (e.g., 3-5 characters at a time).
- For each segment, repeat back using the phonetic alphabet:
  - Example:  
    *“You said: s-a-i-dot-y. Let me confirm: s as in Sierra, a as in Apple, i as in Ice, dot, y as in Yankee. Is that correct?”*
- If any segment is incorrect, ask the user to repeat only that segment.


### 4. Repeat for All Segments

- Continue until the entire username is confirmed.
- For numbers or special characters, clarify as needed:
  - Example:  
    *“You said: 1-2-3. Let me confirm: 1, 2, 3. Is that correct?”*

### 5. Final Confirmation

- Once all segments are confirmed, repeat the full username and ask for final approval.
- Example:  
  *“Just to confirm, your email username is sai.yagneswarreddy. Is that correct?”*


## Example Workflow

User: “I need to reset my password.”  
Assistant: “Please spell out the first part of your email address, the part before the @ symbol.”  
User: “s-a-i-dot-y-a-g-n-e-s-w-a-r-r-e-d-d-y”  
Assistant: “Let me confirm the first part: s as in Sierra, a as in Apple, i as in Ice, dot, y as in Yankee. Is that correct?”  
User: “Yes.”  
Assistant: “Next: a as in Apple, g as in Golf, n as in November, e as in Echo, s as in Sierra, w as in Whiskey, a as in Apple, r as in Romeo, r as in Romeo, e as in Echo, d as in Dog, d as in Dog, y as in Yankee. Is that correct?”  
User: “Yes.”  
Assistant: “Just to confirm, your email username is sai.yagneswarreddy. Is that correct?”  
User: “Yes.”  
Assistant: “Thank you. I have your email address. Proceeding with your request.”

## Key Tips

- Always confirm each segment using the phonetic alphabet.
- Never skip confirmation steps.
- If the user says “that’s not right,” restart confirmation for that segment.
- Speak slowly and clearly during confirmations.
s
and which model will you recommend me to use with this prompt instructions that would give the best results ?
i tried but still doesn't seem to work correctly i tried long to spell and at last it got totally confused and started repeating something invalid callId : bd0d9e22-cd0d-4d80-aa96-bcbd1b7785b1 FYI I was trying to spell sahil.dutta and the desired email was sahil.dutta@accelnomics.com
c
Hey Sahil, this is expected because models are trained on words with associated meanings, not specifically on emails.
3 Views