Fallback destination phone number field isn't savi...
# support
d
Trying to set a fallback destination for inbound calls when the assistant or squad is not available (Phone number -> Inbound settings), however the fallback destination field isn't saving and gets cleared if I navigate to another page or refresh. Opening another ticket ticket for this issue that isn't solved. I don't want to share a loom here because it would contain info I don't want public.
v
message has been deleted
@doc I understand you're experiencing an issue with setting a fallback destination for inbound calls that isn't being saved. It's important to ensure that your settings are properly stored and effective. Since you prefer not to share sensitive information publicly, I would recommend reaching out to our support team directly for a more secure assistance channel. In the meantime, if you haven't already, please try clearing your browser cache or using a different browser to see if the issue persists. This can sometimes resolve interface-related problems. If you need to open another support ticket for this issue, I can assist you with that. Would you like me to proceed with opening a new support ticket for you?
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
s
can you send a request via api it will work
d
alright thanks, will try that and follow up
@Sahil I'm getting a 404 when setting the fallback destination phone via phone number Patch request in the API ref docs
s
asked my team member about it and they told me this should be fixed
d
Got a 200 from the API now. Just a heads up, still not seeing the number show up in the UI fallback destination number input field though. To confirm the expected behavior - if the assistant isn't available (say due to hitting my monthly usage limit) the user will be immediately transferred to the fallback number ?
3 Views