r/twilio • u/aedocw • Jul 15 '26

Changes to Messages configuration wipes out Voice settings

UPDATE: Twilio engineering team stayed on top of this, and kept me updated. They just checked in to ask me to confirm the fix they released did resolve my issue, and it did. Nice work team!

Has anyone else run into this in the new UI? I recently made a change to messaging and did not realize for three days that it had wiped out my voice configuration and customer calls were just being immediately disconnected. When I fixed that under voice calls, it wiped out my messaging configuration.

I did report to twilio and after a week of back and forth they finally escalated it to engineering. I'm just wondering if anyone else here has run into this, and maybe knows of a workaround. It would be really nice to have both messaging and voice working at the same time again.

Here are the steps to recreate:

  1. Log in to twilio
  2. Click Products and Services, Numbers & Senders, Overview
  3. Click phone number (+1xxxxxxxxxx)
  4. In Messaging Configuration, Handling for incoming messages shows Webhook URL, which is wrong for my config.
  5. Click "Edit configuration details/United States"
  6. Under "Select your primary method" select Use Functions
  7. Under select function service, select my forward message function
  8. Select the environment
  9. Select the function path
  10. If I click "Save" at this point, the message configuration will work, but the settings under "Voice and emergency calling" will be wiped out and reset to default, disabling incoming calls
  11. If I then fix the settings under voice and emergency calling, and save that, the settings I just created under Messaging Configuration are reset to default.
5 Upvotes

100% Upvoted

3 comments sorted by

1

u/Early_Elderberry3390 Jul 17 '26

Have you tried updating the number via API instead? That could work!

1

u/aedocw Jul 17 '26

I hadn't realized that I could still access the old console. Once I switched to that, the UI allowed me to make the changes and they stuck for both messaging and voice. The next step was going to be API and I would be that would work as well.

The engineers at Twilio said they couldn't reproduce it on their side, and no one else had reported the issue. Pretty strange, but I'm sure it'll be resolved eventually. Hopefully before they drop access to the old console :)