Outbound calls masked per called location/region.

[Mark G]

Hi, I have a difficult task that I need help with. I have a department who had a small group of users (9) who were calling overdue accounts and were getting little results. I then had an idea and created a bridged appearance with 3 local lines for each region they were calling and 3 people each shared. For example, if they were calling someone in New Mexico, they would hit the "New Mexico" bridged appearance and call the customers in New Mexico who were way past due on their accounts. I did the same for the other 2 regions (Oregon and Colorado for example). The problem I now have is that was very successful. People were answering and were paying since they saw a local number calling. Now that department wants to place that on 36 more agent phones. I do not have nor do I want to add that many DID's for this project. Is there any other way of doing this?

Thanks!

 

[phoneguy55]

public unknown tables. Use a group of extensions for each location of the county and have your agents login/logout of their phones.

But IMO, I think you success is short lived. When I see the same area code and exchange as mine, I know its spam.

 

[Mark G]

Thanks phoneguy55. Do you mind sharing an example? The way I have it set up now is:

Ext. 1111 (DID is 719-xxx-xxxx) Colorado DID
Ext. 2222 (DID is 801-xxx-xxxx) Utah DID
Ext. 3333 (DID is 512-xxx-xxxx) TX DID

3 agents share those extensions. And the next 3 agents share 3 different DID's.

I appreciate you.

Thanks!

 

[Wanebo]

You have to be careful sending caller ID information on a number that is not owned by your company especially if the calls purpose is telemarketing or debt collection. FCC regs require telemarketers to show a number that the receiver of the call can call back during regular business house and contact someone to be removed from the call list, and the FCC many times dumps debt collection calls into the telemarketer classification.

Just because the authorities have been lax about prosecuting spoofers doesn't mean that as a legitimate business you should violate the regulations. And with implementation of STIR and SHAKEN coming on fast you might find that carriers will no longer route your calls, leaving you more troubles than you are trying to avoid by not getting those local numbers.

If the campaign is so successful and they want to expand it you should really obtain local numbers for those areas before you send that information out as caller ID.

 

[Mark G]

Great point but we have nothing to worry about as we do own the DID numbers we are utilizing. Also, the number that shows is a number that can be called to reach our corporation. I am just not sure if public numbering would work because I need the agents to select "Oregon" when calling out to Oregon or to select "New Mexico" when calling out to New Mexico.

 

[kyle555]

If you have only a single trunk group in one location, you don't have many options. If your system happened to have gateways with PRIs in each place, you could do something like an ARS code like "9 for ARS" and then something like 999-101 for CO, 999-102 for NM, 999-103 for OR etc and then in your route pattern strip those 6 digits off and send it to the trunks in CO/NM/OR and have the public table reflect outgoing CLID in CO/NM/OR for those particular trunk groups.

Even if you have only a single location, you can have many trunk groups with one signaling group.
Suppose you had a facility associated signaling PRI - to say, 23B+D. You are able to make as many trunk groups as you want. So, trunk 1 could have channels 1-10, trunk 2 could have channels 11-23. Each PRI trunk group specifies what B channels comprise it in the later pages of the trunk group form and each member can be associated to a signaling group.

So, say you had non-facility associated signaling PRI - so, 2 PRI with active/standby D + 4 more PRI that were 24B all signaled by the active D channel, you could have sig group 10 that picks trunk 10 for channel selection (for incoming calls) and make trunk 10 have 100 members. You'd have 142 B of which 100 would be for trunk 10.
Then you can make trunk 20 for CO and give it 10 of the remaining B channels that all point to sig group 10, same for trunk 30 for NM and trunk 40 for OR.

And then you can split the pub table per trunk group number - if you call out trunk 20, send a CO number.

Heck, you can skip the ARS altogether and just let the people dial by the trunk access code. Though you'd probably want something in ARS like a steering code so you don't let people get international access and stuff.

 

[phoneguy55]

change public-unknown-numbering 1               
                      NUMBERING - PUBLIC/UNKNOWN FORMAT
                                           Total
Ext Ext           Trk       CPN             CPN
Len Code          Grp(s)    Prefix          Len
                                                 
 4  1                       17195551000     11  
 4  2                       18015551000     11
 4  3                       15125551000     11