Update 4 Beta: New Receptionist View & Status Scheduler

[Alphabetic]

Is it not possible to disable the use of 3CX Talk now?

This MCM stops groups calling ext in other groups?

Great for multi tenancy but how does the public address book visible work?

 

[kent3]

Not unless you enable MCM. I recommend using your second NFR to try this out.

Nice one mate! This will be fun

 

[tronic]

Quick question, If I install the BETA will this void any dummy extension call routing we already having in place on a system?

I'm pretty confident that the exceptions was missing with just beta install. Prior to enabling multi tenancy.

 

[kent3]

I'm pretty confident that the exceptions was missing with just beta install. Prior to enabling multi tenancy.

Thanks, think Ill wait for the dust to settle on this one for a week or so.

 

[Rhys Haskell]

@ENCOM-GEFFRAY So each and every of your users has their own extension level, time based exception rules, based on caller ID? In office hours or outside office hours? Really? It just seems very unlikely. A few might be using it yes... Please give me some use cases.....

The group level settings allow you to make rules per group of users, rather than per extension

We have multiple customers with IVR's where different options have different hours.

Will current exceptions configured be moved to the web client of the user?

Why is it not possible to have this on both, in the same way we do for the users mobile number and loads of other optipns?

It just seems like a pointless change with no real upsides.

 

[David Liddle]

@Nick Galea, could you provide a broader description of where these changes are heading? From the tidbits I've gleaned from reading your comments in this post, and from what I read of StartUP, it seems like there's a general migration of settings and functions from the management console to the web client—so that non-administrative users and groups can (also) have access to the elements that affect them the most. Since you report that at least one collection of settings will leave the management console for good, there will be some adjustment needed on the part of system administrators who have grown accustomed to making all changes there. If there are more such changes to come, it would be terribly helpful to read a brief, official description of the changes' rationale and the anticipated resultant interfaces.

It's like that old EDS commercial in which the airplane is being built in-flight. The difference is, we all boarded and took off in a well-functioning aircraft of one configuration, but we're going to be landing (eventually) in one of a different configuration. I'm not a real pilot, but I imagine that changes like that would make most pilots a little concerned.

P.S. Ubiquiti is going through a similar ... process ... with their UniFi Network Application. The lack of a clear explanation of their rationale and goals before and during the changes has resulted in a lot of ... discontentment ... among some of their customers. One has to don the virtual Kevlar before wading into the forums some days. I urge 3CX to stay on a different path.

 

[dallaskincaid]

@Nick Galea, could you provide a broader description of where these changes are heading? From the tidbits I've gleaned from reading your comments in this post, and from what I read of StartUP, it seems like there's a general migration of settings and functions from the management console to the web client—so that non-administrative users and groups can (also) have access to the elements that affect them the most. Since you report that at least one collection of settings will leave the management console for good, there will be some adjustment needed on the part of system administrators who have grown accustomed to making all changes there. If there are more such changes to come, it would be terribly helpful to read a brief, official description of the changes' rationale and the anticipated resultant interfaces.

It's like that old EDS commercial in which the airplane is being built in-flight. The difference is, we all boarded and took off in a well-functioning aircraft of one configuration, but we're going to be landing (eventually) in one of a different configuration. I'm not a real pilot, but I imagine that changes like that would make most pilots a little concerned.

P.S. Ubiquiti is going through a similar ... process ... with their UniFi Network Application. The lack of a clear explanation of their rationale and goals before and during the changes has resulted in a lot of ... discontentment ... among some of their customers. One has to don the virtual Kevlar before wading into the forums some days. I urge 3CX to stay on a different path.

VERY well stated. I hope Nick heeds this advice.

 

[N_G]

@David Liddle Well if you read more then a tidbid, you would have read that the Startup mode is not released yet and not available for general public and you would also have read that we have not provided any documentation yet and its only for those partners that want a sneak preview, knowing that there is no info available. I guess its what happens when you provide too much transparency.

Guys I am logging out of this thread....

 

[Hystiff]

@David Liddle Well if you read more then a tidbid, you would have read that the Startup mode is not released yet and not available for general public and you would also have read that we have not provided any documentation yet and its only for those partners that want a sneak preview, knowing that there is no info available. I guess its what happens when you provide too much transparency.

Guys I am logging out of this thread....

Bravo, you support the contradiction very well........

 

[tronic]

We have multiple customers with IVR's where different options have different hours.

Will current exceptions configured be moved to the web client of the user?

Why is it not possible to have this on both, in the same way we do for the users mobile number and loads of other optipns?

It just seems like a pointless change with no real upsides.

Basically how i understand it, the old exceptions in a user under admin is move to the client with receptionist group access.

Remembering, though, this is BETA, so things will and can change.

The old exceptions though it worked was a workaround because the system had one office hours and most don't know CFD to do it that way or find it more complicated.

So instead of old method you will need to create groups and add that resource into that group. If you create a user on the system and give yourself access to all resources, this seems like the easiest method at present.

Then login to the web client of your user and change from there the independent time profile.

 

[D Bedford]

@David Liddle Well if you read more then a tidbid, you would have read that the Startup mode is not released yet and not available for general public and you would also have read that we have not provided any documentation yet and its only for those partners that want a sneak preview, knowing that there is no info available. I guess its what happens when you provide too much transparency.

Guys I am logging out of this thread....

Genuine question here - do you have a partner-only forum that you could have had this discussion on, instead of the publicly visible forum? If it's only available to partners then that would have made more sense. Otherwise you are simply inviting everyone to participate, and then are left dealing with the aftermath of misunderstandings.

 

[dga]

Good morning everyone - I hope you will not move the exceptions only in the web client because the virtual extensions that are used to change the schedules compared to the standard must also be "managed" by the console. In addition, with the current settings the exceptions are no longer working as it is not possible to assign specific times. Thank you

 

[David Liddle]

@David Liddle Well if you read more then a tidbid, you would have read that the Startup mode is not released yet and not available for general public and you would also have read that we have not provided any documentation yet and its only for those partners that want a sneak preview, knowing that there is no info available. I guess its what happens when you provide too much transparency.

Guys I am logging out of this thread....

Everyone, I wish to express that it was not my intent to challenge @Nick Galea as he perceived. I do understand the nature of these early releases, and I have witnessed many times the delicate balance of generating introductions to and documentation for products that are in a state of flux. I should have been more careful and considerate with the words I wrote so as not to provoke him as I clearly did. Such a provocation is not right.

I am very interested in the changes that I see coming to the 3CX product. I am in favor of putting settings in reach of end users, supervisors, managers, and the like. I am in favor of making interfaces consistent and less complicated for developers, administrators, and end users alike. If these things are on 3CX's roadmap for its products, then I wish to encourage the staff in their efforts. May their work be infused with wisdom, and may their interactions with one another and with customers be infused with joy.

 

[timmbo]

Hi.

What is the great thing about the Receptionist view?
I don't see new things in the Receptionings-View.
Has someone a Screenshot?


Bye
Timm

 

[Evolute IT]

@David Liddle Well if you read more then a tidbid, you would have read that the Startup mode is not released yet and not available for general public and you would also have read that we have not provided any documentation yet and its only for those partners that want a sneak preview, knowing that there is no info available. I guess its what happens when you provide too much transparency.

Guys I am logging out of this thread....

One thing I wanna make clear tho because I think we misunderstood each other:

I see the group routing feature. But it's still just In/Out/Break. We need more than that most of the time to route exceptions in time. Thus why we use dummy extensions, so with this, we still need dummy exts to use exceptions.

Also, it'd be nice to have the ability to choose what the users can manage from the Office Settings. Like users and queues is fine, but I might not want them to see the trunks or the IVRs (for example.)

As for the operator extension, is it simply assigned to the "receptionist" of the group? So that when we do 0 from a VM, it goes to that person?

 

[tronic]

One thing I wanna make clear tho because I think we misunderstood each other:

I see the group routing feature. But it's still just In/Out/Break. We need more than that most of the time to route exceptions in time. Thus why we use dummy extensions, so with this, we still need dummy exts to use exceptions.

Also, it'd be nice to have the ability to choose what the users can manage from the Office Settings. Like users and queues is fine, but I might not want them to see the trunks or the IVRs (for example.)

As for the operator extension, is it simply assigned to the "receptionist" of the group? So that when we do 0 from a VM, it goes to that person?

@ConceptsWeb I disagree with group routing you mentioned. Dummy extension method is only because the system has one office time setting.
Multiple per inbound route yes, but for businesses with multiple divisions using one advertised.number this doesn't help.

How more established solutions do it such as Avaya is by creating a time profile with times and or dates. Then this time profile can refered to in multiple system places like queues/ring groups, incoming call routes, IVR is for greetings based on time of day and even user setting like twinning during business hours only etc.

@Nick Galea am I correct in saying that the multiple time settings are really designed to the startup market and not the existing 3CX customer base.
As I can create a user group. Add resources to it such as queues or IVR. This works great for multiple companies. Both companies get access to there own stuff.

For existing 3cx clients, it's common in Australia to have a warehouse team that start earlier say 730 and then finish at 330pm. Then office staff that start at 9am and end at 5pm.
On the IVR option 1 goes to office and option 2 to warehouse.
Obviously CFD does this but as you said direction is not to rely on that so much.
Currently easiest way to do it, though not by design is to send them to dummy extensions that have time exceptions that then route the call based on time of day/date to where you want call to go.

Using the new user group option I'm not sure how this could be achieved easily for this sort of common setup.
Say office times would be system time. Then the warehouse would be a seperate user group. That I then would need to login to the webclient on a user that had access to that resource and setup second time/date in there.
My logic would be it works the same as the sip trunks in startup.
I can create a sip trunk in admin and then using user groups add them to user groups. I can see this sip trunk in admin but also access it in the web client under a valid receptionist user. Changes you make reflect on both sides.
Would it be possible to just display the programming options that you see under receptionist, as displayed in the web client. In the relevant user group menu
Not doubling up just showing it in multiple places like sip trunks do. Not doubling up but displaying same in in the admin that you see in office settings in the web client.

Sorry for the long post. Hope this helps.

 

[Evolute IT]

Dummy extension method is only because the system has one office time setting.

Currently easiest way to do it, though not by design is to send them to dummy extensions that have time exceptions that then route the call based on time of day/date to where you want call to go.

That's what I said. I think you misread my opinion on this.

We use dummies all the time. Thus why I like the group thing but it's not enough.

 

[tronic]

That's what I said. I think you misread my opinion on this.

We use dummies all the time. Thus why I like the group thing but it's not enough.

Do you use it for CLI forwarding or just for time based routing?

 

[Evolute IT]

Do you use it for CLI forwarding or just for time based routing?

Both but mainly time based. CLI we do via CID Rules when we need it, which is rare.

Our CLI routing is usually CRM-based.

 

[tronic]

Also to those that update there system to beta and use the website live chat
Looks like the auto closing part is not in there yet or is it just me?