In the first post in this series, I provided some basic guidance on how to plan for you main number scenarios. In this post, I’ll outline each of the technical options that you can use to address you main number requirements.

Your call handling functions include:

SfB Response Group Hunt Groups

Response Groups are a hunt group/IVR solution built into SfB on-prem. Response Groups have three components: groups, which are your users who will handle calls, queues that present the calls to groups, and a workflow that will play a greeting and send the call to a queue.

Workflows have options for business hours, holidays, music on hold, recorded or text-to-speech greetings. A call can be distributed to a queue, or based on work hours and holidays it can be disconnected (really? Who would ever do that?) or forwarded elsewhere.

Response Groups have some other features like Agent Anonymity so that you don’t reveal the name, SIP address, or number of the agent receiving or placing a call. A Response Group can be Formal or Informal. With Formal Response Groups, Agents must log in and out of the Response Group, whereas with informal Response Groups they’re always “logged in”.

You can also scope a Response Group to a manager, so that you can easily delegate all the fiddly settings like greetings and hours and group membership to an administrator.

Once the call is in a queue, there are a variety of timeout and overflow options. Within Groups, you can set the method used to pick which agent(s) is offered the call, and how long the call will ring before it’s sent back up to the queue for alternate handling.

SfB Response Group IVR

The Response Group type I described above is a Hunt Group, where an incoming call has only one destination queue. An IVR Response Group allows you to provide options to the caller, and route their call to a different queue based on their responses. This can be via keypress or speech recognition. You can also record that ubiquitous “Please listen carefully as our menu options have changed” greeting that everybody seems to have, regardless of how old their IVR structure is.

Response Groups are pretty versatile (and free) and are commonly used because of this. However, they’re not without their limitations. I’ll explore these more in a future post.

Exchange Auto-Attendants

Exchange Auto-Attendants aren’t an SfB feature, they’re a component of Exchange Unified Messaging. They’re available online or on-prem, and are fairly simple to configure. When an Auto Attendant is called, a greeting is played and the call can do things like an address book looking, enter an extension, or similar to the IVR Response Group, press keys or use voice recognition to play messages or reach destinations. You also get business hours and holidays, and can change behavior based on these.

Unlike Response Groups, there are no queues or groups in Auto Attendants, however the Auto Attendant doesn’t care what’s at the number that you forward a call too, so you could forward a call from an AutoAttendant to another AA, Response Group, user, or your annoying coworker’s mobile.

SfB Standalone/Phantom “user” or Common Area Phone

You could also chose to have a main number ring a regular phone or SfB client, typically one that isn’t assigned to a person. I’ve seen these called “Standalone” phones or “Phantom users”. This solution is common when your call volume is low, or when you have a rotation of people through a reception desk. The users can logon to the PC as themselves, and would have a phone on the desk for the main number. I have also seen organization load an Attendant console on a small form factor PC with a touch screen, and have this sit on the desk beside the regular office PC.

You can use a standard SfB user for this, or a Common Area Phone. Using a SfB user consumes a license, where a CAP does not. However, CAPs are not yet available in SfB Online, and cannot offer voicemail.

SfB Team Ring or Delegation

When a standalone phone or phantom user proves too limiting, such as when there isn’t a reception desk or you need a ring a group of people, you can use Team Ring or Delegation.

Team Ring allows one user – your phantom user – to have their calls ring on their teammates SfB clients or phones after some delay (0-15 seconds). They’ll get a unique ring/toast so they can identify that the call isn’t to their individual number.

Team Ring and Delegation are very similar, with one key difference. With Team Ring, you can only answer calls on behalf of the phantom user. With Delegation, you can receive and place calls on behalf of the phantom user.

This is a popular, free (other than the SfB license for the phantom user), self-serve option, but it’s not a scalable solution.

SfB Simultaneous Ring

A similar option to Team Ring is to use the Simultaneous Ring feature. However, Simring only allows you to assign one destination user or phone number, so you can’t alert multiple people for an incoming call. This option is useful for a single user or phantom user, when the person who would normally answer the call is away from their desk – an admin person making some photocopies, or a security officer doing a patrol. They can setup simring to a mobile or cordless phone, and wander away from their desk while being able to answer the phone. Note that options for call transfers are limited in this scenario.

They could also simring a coworker who is staying at their desk, who would have the usual SfB call transfer options.

Call Pickup

Call pickup is a relatively new option in the SfB world. The idea is that when your phone is ringing, your coworkers can enter a code on their phone to pickup your call. This was a popular function in traditional PBX environments that didn’t have things like delegation or team ring. Call pickup is a bit of a pain to administer. Frankly, I get the feeling that this feature was added to SfB to satisfy a large customer, or to gain another point or two when organizations are scoring RFP responses.

Shared Line Appearance

A Shared Line Appearance is another legacy PBX features that has crept into the SfB world, at least partially. The idea here is that you would have a button (or two or three) on your phone that would be a duplicate of the line on another phone. Think of an admin who can have buttons on their phone for the main number, the bosses’ number, and maybe a coworker. They can hit this button to answer the other line(s) when they ring. In most legacy PBXs, the button also offered a busy light, and could either act as a speed dial to call that person, or a “place call on behalf of” function. In SfB, this functionality is limited at present to just Polycom VVX phones, it’s not available on other phones or the SfB clients. The button also doesn’t do anything other than answer the call.

I’ve seen limited uptake of this feature, and again I suspect it’s to provide some level of comfort to a large SfB customer or for RFP scoring. There are better, less limited ways to handle most scenarios where SLA is mentioned.

Coming soon to the SfB offerings are Cloud PBX Organization Auto Attendant and Cloud PBX Call Queues. These are meant to offer functionality similar to SfB Response Groups in Online deployments, and to eliminate the need for the Exchange UM role for Auto Attendant functionality. These features are currently in preview, and I’m hopeful that they’ll be released soon so that I can provide more concrete details.

AudioCodes Auto Attendant

AudioCodes offers an application that they call AutoAttendant, though it’s more like the Response Group than Exchange Auto Auto attendant. There are no directory lookups, but there are decent options for queueing and IVR handling of calls.

Full-blown Contact Center

If these solutions don’t meet your requirement, you may need to look at a full blown contact center solution like Computer Talk ICE, Clarify Connect, or Enghouse’s offerings. This isn’t as daunting of a concept as it once was. You no longer need to deploy one or more servers and installing software. Most call centre software is now available in the cloud as a service, with functionality and pricing on a per-user, per-month basis.

Next up…

In the next several posts, I’ll provide more in-depth details on each of the items above. If I’ve missed your favorite main number handling option, hit me up in the comments!