Please tell me I'm wrong: When using S4B to call a business that has a telephone auto-attendant, our S4B dialpad works just fine. However, if I and an employee call a business together in a S4B call, the dialpad buttons do not work. MS tends to suggest that this is a known bug. We're about to agree and leave it at that... and leave S4B.
But really? What an obvious thing to need to do. We REALLY need to do this to train our employees on calling clients, etc.
MS seems to be moving from S4B to Teams. Teams seems to be entirely geared toward pre-scheduled meetings where all attendees have agreed to join. This is not our need AT ALL. We need on-the-fly ability to add a voice call to an existing voice call AND be able to punch a dialpad for auto-attendants.
Therefore, we're looking for economical (5 users or less) solutions for our VOIP needs. MS Office 365 E3 (which we'll keep) runs us $20/month, but in addition, for Skype PTSN dialing we also need $12/month/user for Domestic Calling Plan and $8/month/user for Phone System. Therefore, our phone system needs are $20/month/user.
Can someone recommend some economical VOIP solutions? Thank you, yes we've looked - but that process is EXTREMELY unproductive (i.e. false/misleading claims on websites, feature listings are incomplete, etc., etc.)