Tricks to manage an international Company?

Status
Not open for further replies.

davide.bonavita

Premier Customer
Joined
Apr 17, 2020
Messages
136
Reaction score
29
Hello fellow colleagues,
we are using 3CX as our global phone system for our company that has multiple small offices scattered all around the world. Everything is working smoothly, but I'm still wondering how to manage the issues coming for having our people in like 6 different timezones and a variety of local national holidays to handle.

- Office Opening Hours for inbound calls: overriding the global office hours and setting specific office hours for every inbound route has done the trick (e.g. I've set up the inbound route for our peruvian office from 15.00 to 23.30, considering that the PBX is in UK). I double check them when the timezone changes from BST to GMT and viceversa, but it's fine.

- Public Holidays: there is no way to set up holidays for a single inbound route (e.g. día de la España on 12th October only for our spanish office) and even if it's a global holiday like Christmas, that would kick in at the wrong time for the offices in different timezones

I suppose adding the concept of "Office" to the system and assigning local language, timezone and holidays to it, and attaching the routes to the "office" would be the best solution. I wanted to add this to the Ideas posts, but I'm not authorised to do so
 
Last edited:
At the moment, the only way to have that kind of organisation is to have multiple smaller 3CX for each timezone/region and bridge them together.

I agree that this is a big limitation for international customers.
 
You could use call flow apps for each of your DDIs or try having a different SIP trunk per office and specify office hours for these trunks as this will take priority over global office hours.
 
Hello Davide,

Have you considered having a PBX in each office, bridged together? Granted it would require multiple licenses but they may be able to be scaled down in size. Each PBX can handle its own Office Hours, Public holidays, DIDs and more.
 
  • Like
Reactions: Evolute IT
Hello Davide,

Have you considered having a PBX in each office, bridged together? Granted it would require multiple licenses but they may be able to be scaled down in size. Each PBX can handle its own Office Hours, Public holidays, DIDs and more.

We would need like 7 different Enterprise licenses (and 7 instances on AWS), sometimes only to manage a 5 people team that would maybe receive 5 calls per day, not considering that the calls auditing and managing the call reports and the recordings, the crm integration, the internal chat and the live chat would be a nightmare. The whole Covid situation has made us decide to switch to a global PBX, luckily everything is going fine and we're actually improving our production working from home. We are getting rid of the smaller physical offices and started hiring the right people all around the world, so we would need a license for basically every country we hire people into
 
Last edited:
In that case, you could place a CFD App in front of all Inbound Rules, this could then determine if its a Public Holiday for each and route calls accordingly.
 
  • Like
Reactions: Evolute IT
In that case, you could place a CFD App in front of all Inbound Rules, this could then determine if its a Public Holiday for each and route calls accordingly.
I'll try this way, thank you :)
 
  • Like
Reactions: NickD_3CX
Status
Not open for further replies.