I have a marina client. I'm trying to get the assistant to say "bass" (like "pass" or "mass"), but every #$#$% time it pronounces bass like "base". Prompt additions: Never use the word "bass" alone. Always use it with the type of "bass" like "large-mouth bass" or "small-mouth bass". When pronouncing the word "bass", always use the short "a" sound like in the word "mass" or "pass" and never the long "a" like in the word "mace" or "place". I've tried prompting it for pronunciation with the above, but it's almost comical at this point. The agent will say Agent: "largemouth BASE" Me: "What kind of fish?!? How do you pronounce bass?" Agent: "You know BASE, like as in pass or mass" Any tips to get the agent to pronounce things as directed?

Any meaningful upgrade comes with a moment of discomfort. V3 is one of those moments. To support what’s coming next, we had to migrate some core components earlier than planned. While this was the right decision for the long term, we know the timing has caused real frustration. If you’ve experienced call issues, delays, or unexpected behavior, we want to be clear from the start: We see it. We understand the impact. And we’re actively fixing it. Right now, there are three main things we want to acknowledge. First, there is a delay in the AI agent greeting on outbound calls, and this is affecting all outbound traffic. We know how important that first moment of a call is, and we agree that this experience is not where it should be. A fix for this is part of the upcoming patch and is being treated as a top priority. Second, some users are experiencing latency or connection issues. The majority of the platform is operating normally, but we already have a patch in progress that directly addresses these issues and will be rolling out shortly. Third, there is a busy signal issue affecting a small subset of numbers. We currently host over 14,000 phone numbers. Out of those, a few hundred are affected. If you’re one of them, your frustration is valid, even if the issue is isolated. Most of the impacted numbers fall into one of these categories: - Custom Telnyx setups that don’t align with our updated requirements - SIP trunking requests that were never completed - Older numbers still in the final stages of porting from Twilio to Telnyx If you’re affected, there are two paths forward. Option one: wait it out. For many numbers, this will be resolved automatically over the next few days as the patch and cleanup complete. Option two: move faster. You can purchase a new number and let our support team know. If your old number qualifies, we’ll credit your wallet for the entire year for the phone number ($30) for the trade-in. This option is there for anyone who can’t afford downtime.

Been on with support for 5 days trying to figure out whats going on, running into all kids of issues with my numbers. I just wanted to see if it was just me or not. Anyone else having issues where outbound calls are not following the script or just sound different in general than they do for inbound?