Hi
We have let our 5 "end users" try out their interface. It is overwhelmingly positive. But one thing that each one of them struggled with was the naming convention of destinations as extensions. So when a ring group is created, it gives it an extension number. We know this of course and understand it. But an end user does not and gets completely confused about it. "I thought our extension numbers were 1XX, but now I see 9200" so what do I put there?. Or they will see the below and say "huh, is it going to business hours, or is it going to an extension"
I think it would be better to either just not show the underlying extension number at all in the client interface, or alternatively give it a different name, something like "destination" or "code"
We have let our 5 "end users" try out their interface. It is overwhelmingly positive. But one thing that each one of them struggled with was the naming convention of destinations as extensions. So when a ring group is created, it gives it an extension number. We know this of course and understand it. But an end user does not and gets completely confused about it. "I thought our extension numbers were 1XX, but now I see 9200" so what do I put there?. Or they will see the below and say "huh, is it going to business hours, or is it going to an extension"
I think it would be better to either just not show the underlying extension number at all in the client interface, or alternatively give it a different name, something like "destination" or "code"