Hello everyone,
we have an issue with forwarded calls in 3CX:
When an incoming call is forwarded multiple times in sequence (e.g. Extension A → B → C) and ultimately nobody answers it, all involved users see the call as a missed call and often call the original caller back because they cannot see for whom the call was originally intended. This often leads to confusion for the original caller, because they only tried to reach Person A and do not understand why Persons B, C, and D are suddenly calling them back saying that he/she had called them.
For external calls, we found a partial workaround by naming the DIDs. We currently use DID names like: "Call for Firstname Lastname - Extension". This way, forwarded calls show the original target in 3CX v20 Windows App.
However, we still have two problems:
Thanks for any ideas.
we have an issue with forwarded calls in 3CX:
When an incoming call is forwarded multiple times in sequence (e.g. Extension A → B → C) and ultimately nobody answers it, all involved users see the call as a missed call and often call the original caller back because they cannot see for whom the call was originally intended. This often leads to confusion for the original caller, because they only tried to reach Person A and do not understand why Persons B, C, and D are suddenly calling them back saying that he/she had called them.
For external calls, we found a partial workaround by naming the DIDs. We currently use DID names like: "Call for Firstname Lastname - Extension". This way, forwarded calls show the original target in 3CX v20 Windows App.
However, we still have two problems:
- Managing DID names manually is a lot of work. Is there a way to automatically generate DID names using variables, e.g.: "Call for <Extension Name> - <Extension Number>" ?
- We found no similar solution for internal calls that are forwarded (Extension → Extension → Extension). Is there any workaround so users can see the original target of the call?
Thanks for any ideas.
Last edited:
