Assistant is saying "asterisk" when asked to spell out email. Weirdly, we haven't had this issue with any other Assistants, it seems to be just with this one. Call ID: f1222543-f963-4a8a-aba8-199908c9a260 At 00:38 assistant says Asterisk inbetween letters. This information is retrieved from KB which is in the following format (as per used in several other assistants with no issue) (bullet point) Email: info@companyname.com.Au

Thank you for sharing these details. I understand that the Assistant is unexpectedly saying "asterisk" when spelling out the email address, even though the KB entry format is consistent with what works for other Assistants. Your note about the specific call and timestamp is helpful for understanding the context. If you have any more details or examples, feel free to share them!

More recent calls with same issue when sharing information about a product: 00:22 ab8a6218-9d40-4b6f-acba-b4744589a11f 01:12 04911b0a-2c7e-4ac7-9f13-4faa687e023a

Instruct LLM to only return plain text, never markdown in system prompt

Try what @Pigeon recommended and let us know how that goes.

@Pigeon @Kyle Hi there, we've tried this and unfortunately did not resolve the issue. Here is our prompt: > Strictly NEVER say the word ‘asterisk’ and only return plain text, never markdown in the system prompt.

Well, LLMs dont

say

anything, so that part of promt doesn't do anything. Try variations of plain text, no markdown, this text will be turned to speech.

@Pigeon We've updated the system prompt below and this did not work: > Return plain text only. Never include markdown syntax like asterisks (*), underscores (_), brackets [ ], greater-than signs (>), or links. This content will be spoken aloud, so avoid any formatting characters that may be read out loud.

Which LLM do you use?

Having this same issue on our end as well. Been using jumping on openai, gemini, etc but all is the same. Ideally voice input can ignore text like as it gets included, if there is a way for ther input to be culled, would be great

Hey! To help track down this issue, could you share: - The call ID