I have a Samsung Galaxy S25 Ultra on AT&T. Before a recent One UI update, I had conditional call forwarding configured so that unanswered, busy, or unreachable calls to my AT&T number would automatically go to my Google Voice voicemail.
Everything was working perfectly until the update.
The Problem:
After the One UI update, unanswered calls stopped reaching Google Voice voicemail.
I didn't initially realize this was happening until someone informed me that they had tried calling multiple times.
They reported:
"It rang several times and then a recording stated that the wireless customer was not available and to try again, no option to leave VM."
This is a serious issue because callers cannot leave voicemail, and I have no way of knowing that someone tried to reach me unless they contact me another way.
Possible Cause:
It appears that the One UI update may have reset or affected AT&T's conditional call-forwarding settings.
Potential Solution:
Open the Samsung Phone app.
Go to Settings → Supplementary services → Call forwarding → Voice calls.
Check the following settings:
- Forward when busy
- Forward when unanswered
- Forward when unreachable
Make sure all three are configured to forward to your Google Voice number.
Keep "Always forward" disabled.
Alternatively, Google Voice documents AT&T conditional forwarding dial codes:
- Unanswered: "61GoogleVoiceNumber#"
- Unreachable: "62GoogleVoiceNumber#"
- Busy: "67GoogleVoiceNumber#"
Replace "GoogleVoiceNumber" with your actual 10-digit Google Voice number. Dial each code separately and wait for confirmation.
After configuring, test by calling your AT&T number from another phone and letting it ring unanswered.
If the settings fail or forwarding still doesn't work, AT&T may need to check conditional call forwarding on the line.
I have updated the below to fix my issue.
- Forward when busy
- Forward when unanswered
- Forward when unreachable
Question for the community:
Has anyone else experienced conditional call forwarding to Google Voice breaking after a Samsung One UI update, particularly on AT&T?
Did reconfiguring the forwarding settings fix it, or did you have to contact AT&T to get it working again?
Hope this helps.