There are times when you want to control caller ID on an outbound call. Maybe you are in the office but want to show the mobile number. Or vise versa, you are on your mobile but want to show the office caller ID. Some office phones will only show a switchboard number and you want to show a direct dial number as caller ID. Last, there are times that you want a local market presence. You have a team calling from Dallas, the prospect is in Los Angeles and the Los Angeles office will maintain the account. FastCall will allow you to call with a Los Angeles caller ID from the Dallas office.
FastCall gives you a few options for caller ID. Each user can set one personal inbound number, and this number can be used as caller ID. The user inbound number can have voicemail, and can either simulring two phones together, or overflow from one phone to another. See the page for inbound call routing for more info.
User can also verify numbers they control as caller ID. These existing numbers can be used as caller ID but do not route inbound calls with FastCall.
With BeLocal, multiple local numbers are provisioned to use as caller ID. BeLocal matches the exact area code of the phone number on the Salesforce record. If a match is not found, the default caller ID is used. Inbound calls to BeLocal numbers are routed using the FastCall ACD.
BeLocal numbers used for caller ID are provisioned in FastCall, one phone number for each area code. Typically, 50 or more local area codes are provisioned, but this will be determined by your needs, and the markets you are calling into. These numbers will be provisioned by you, so you want to set aside a few hours to set up BeLocal.
Note: BeLocal is available in the Sales+ Edition of FastCall and is not available during a trial period.