3CX Multi-Tenant: Making Your SMB Customers Profitable Again

[João Vitor]

I recently been asked about the difference between Multi-Company and Multi-Tenant, would you please specify it if there is any?

 

[NicholasP_3CX]

I recently been asked about the difference between Multi-Company and Multi-Tenant, would you please specify it if there is any?

Multi-tenant defines that there is one tenant per instance. That tenant is a company, so it is essentially the same thing.

 

[João Vitor]

Multi-tenant defines that there is one tenant per instance. That tenant is a company, so it is essentially the same thing.

Thank you for the response Nicholas! So for example, my company has the MCM parameter active since it was released for testing purposes, and after migrating for v20 it behaves the same way as the multi-tenant. Essentially there is no difference between my company installation and a new one directly on multi-tenant?

 

[NicholasP_3CX]

Thank you for the response Nicholas! So for example, my company has the MCM parameter active since it was released for testing purposes, and after migrating for v20 it behaves the same way as the multi-tenant. Essentially there is no difference between my company installation and a new one directly on multi-tenant?

Pretty much yes! It is recommended to have it set up from the beginning as a multitenant to ensure everything is properly in place.

 

[arcrob]

Hi, great to see this rolling out. I am going to deploy this for a few clients in the new year. The phonebook I think will cause some issues as most of my clients use that. Do you have a target date for separated phone books for each tenant?

And thanks for going for 16SC, it makes easier for us to get in to.

Thanks

 

[N_G]

@acrob - thanks for the heads-up - Yes we are working on it we are making a reporting update and will do the company phonebook per department/tenant right after that. Its not trivial for various architectural reasons.

@João Vitor - Its better to deploy from new. You are using a beta and there were a lot of changes. Make a new deploy now so you start with the same version that we are testing.

 

[ict7]

Senza la directory di reparto, il multi-tenancy è inutile. Inseriamo 10 aziende che hanno contatti misti? Sono in fase di sviluppo da un anno ormai, è stata la prima cosa da fare sulla v20, ora i clienti ci stuzzicano su quando usciranno queste directory.

 

[NicholasP_3CX]

Senza la directory di reparto, il multi-tenancy è inutile. Inseriamo 10 aziende che hanno contatti misti? Sono in fase di sviluppo da un anno ormai, è stata la prima cosa da fare sulla v20, ora i clienti ci stuzzicano su quando usciranno queste directory.

As Nick mentioned above, it is not trivial due to architechtural reasons. There are a lot of checks and balances in place when something moves from a global to a departmental level.

As mentioned, we will be releasing the new reporting engine, which has had a LOT of work done at the core level.

Then the phonebook will be released after that.

 

[João Vitor]

@acrob - thanks for the heads-up - Yes we are working on it we are making a reporting update and will do the company phonebook per department/tenant right after that. Its not trivial for various architectural reasons.

@João Vitor - Its better to deploy from new. You are using a beta and there were a lot of changes. Make a new deploy now so you start with the same version that we are testing.

So I assume since it's a beta in some future version it will stop working correctly, and for that it is better to deploy a new one, right?


And are you guys planning on some sort of migration tool so we can put the small customers with 4SC in the multi-tenant? I question it because our clients wouldn't like to lose their current calls history and recordings.

 

[dbwx]

So I assume since it's a beta in some future version it will stop working correctly, and for that it is better to deploy a new one, right?


And are you guys planning on some sort of migration tool so we can put the small customers with 4SC in the multi-tenant? I question it because our clients wouldn't like to lose their current calls history and recordings.

The best migration feature would be able to activate the license on the existing instances and limit the sc individually, simple and fast right? Any support on this idea from 3CX?

 

[NicholasP_3CX]

There is no intention for this type of license. We license the back end of the system.

 

[bitn2]

This would be really good to habe the option to limit the sc by department.

 

[CentrexJ]

This would be really good to habe the option to limit the sc by department.

If you give them their own sip trunk you can put the limit in there.

 

[david.taylor]

Are there any limits on the number of tenants, or the number of users/ring groups/queues/IVRs per tenant?

Are the users of different tenants hidden in the web client? i.e. can a user only see other users on the same tenant?

Are calls blocked between tenants? What happens if a user dials the extension number of a user on another tenant?

 

[N_G]

No limits. You decide on the dial plan.
Yes users from other departments can not be seen or called.

 

[AshishKushwaha]

In the new 3CX Multitenant setup, managing multiple companies is a great feature. However, I would like to know if it’s possible to integrate separate CRMs for each company. For example, if I have two companies configured in the 3CX Multitenant, can I integrate the respective CRM systems for both companies? @NicholasP_3CX

 

[Evolute IT]

In the new 3CX Multitenant setup, managing multiple companies is a great feature. However, I would like to know if it’s possible to integrate separate CRMs for each company. For example, if I have two companies configured in the 3CX Multitenant, can I integrate the respective CRM systems for both companies? @NicholasP_3CX

No. If they need CRM integration, you sell them Pro dedicated. Not MT/SMB.

CRM integration is global to the system and there's no plan for this to change.

 

[SteveOAS]

Not sure if this gets answered in the training Webinar but they are all full already

Can a SIP trunk be setup across multiple tenant's and just manager the outbound number for department/Tenant or does each department/Tenant need a dedicated SIP trunk ?

 

[N_G]

@SteveOAS You can have one SIP trunk and use it across departments.In this case you create a system wide SIP trunk which will be seen across departments. You can also set one up per department, or both if you like.

So you have full flexibility.

 

[Ronald Lysmont]

Hi All,
I am sure there are still developments going on in the Alpha version but I wanted to point out the following.
When logged in as a department owner/administrator of a tenant and creating a user, the first extension number offered by the system is starting at 100 and plus.
The expectation is that the first extension number offered is one of the extension number range of the corresponding tenant.
It would be nice if the tenant owner/administrator could get a dropdown list of all available numbers in the corresponding number range.

Thanks for taking this in consideration