The current status sync is not really useful. We have the most problems when, for example, we have scheduled an appointment for a visit in the calendar. If this visit is delayed by a minute and then calls me via the intercom or the receptionist, I am not available to take the appointment.
It would be helpful if each status had the same options as the custom status. For example, being able to set calls to go through even when you are set to "Away" or "Do Not Disturb," or being able to add exceptions.
Hold on, you're mixing different topics.
Here's what the O365 integration with 3CX does:
- Read Microsoft 365 users
- Read Microsoft 365 contacts & write personal Microsoft 365 contacts
- Synchronize Microsoft 365 Teams Presence
- [OBSOLETE] Read Microsoft 365 calendars for presence synchronization
- Use SharePoint for backup and recording storage
- Send emails via Microsoft 365
Calendar synchronization is obsolete but still available. You are not required to activate it. It's there to please users who want to continue using it. Many people criticized 3CX for removing features without warning. 3CX listened to its users and maintained this function but marked it as obsolete. Therefore, users are encouraged to transition to MSTEAMS synchronization.
Let’s look at Teams presence synchronization.
If the fact that a particular event changes your status bothers you, simply select the appropriate status when you schedule your meeting.
I’m not sure I understand the benefit of being in "busy" mode if I want to be able to accept calls despite being busy; then, are we available? Just select available. If I want my animal to meow, I adopt a cat, not a dog? (I'm not mocking you; this is an analogy.)
But I understand there can be several exceptional cases indeed.
I would have liked my animal to meow and fetch the stick when I throw it. But I must make a choice or have 2 animals!
Joking aside, if your goal is to publish a status independently of call behavior management, opt for two different systems or two different extensions for the same user.
- One extension for presence (and does not receive calls on this extension / or / redirects to the real extension)
- One extension for calls, whose presence is meant to apply different behaviors for calls.
If you don't like this integration, simply don't use it. Please don't say it's not useful. It just doesn't meet your specific needs, yet it is bug-free and performs as it was designed. However, if your goal is to provide constructive feedback, ideas, or share an edge case, as you did in your second paragraph, that’s different—but please use the appropriate channel with the correct topic. Your idea isn’t related to Teams presence synchronization. It's more about a request to add functionality related to each status in 3CX.
Sincerely,
