New Denali Features: Voice Mail Transcriptions, Missed Call Notifications, and More!

To help you bring in the new year in style, we’ve got a great batch of new features which are sure to please! With things like Missed Call notifications and Voicemail Transcriptions, we’re confident we have something for everyone in this release. Below are a few of the heavy-hitters, but feel free to check out the full Release Notes via Base Camp.

Voice Mail Transcriptions

We’re pretty excited about delivering this functionality as it’s one of the first big requests we received through Base Camp (shameless plug for use of the Feature Request section of the Community). The ability to receive transcriptions of your voice mails, delivered via email along with the audio file is now available!

After spending many long weeks researching and developing the best method to be able to provide this feature, we came to the realization that in order to get the needed transcription quality, we would have to go with a best-of-breed, paid solution. As a result, there is a cost for this feature. If this sounds like something you’d like to take advantage of, just reach out to our Customer Success team to find out more!

New Features – SFDC 

While VM Transcriptions is available for everyone, we do have a few features which are now available for Salesforce (SFDC) users. As you may know from previous releases, a couple of these were already features in Denali for Dynamics (DfD). Now, we’re bringing that same power over to SFDC.

Missed Call Notifications 

We’re very excited to announce a real crowd-pleaser in Missed Calls! This is something we’ve been working on for quite some time and are excited to finally be bringing you the first client-facing iteration.

Basically, this works exactly as missed calls do on your cellphone, with a record for each missed call showing in red text in the History section of Denali.

Task Logging for Missed Calls 

This brings us to our next exciting feature add, which is the ability to log separate Tasks for each missed call. Missed Calls will now each create a record if enabled, and will allow you to return the calls for known callers (numbers that match a record). In the Standard package, if the number is Unknown (i.e., does not match a record in Salesforce), the task will include the number that called in the Comments. In the Enterprise package, it will allow you to return all calls directly through Denali, including Unknown numbers by using the DialSource Action object.

We’ve allowed this to be selectable by account in Settings in case you would prefer not to add the additional storage space. However, the functionality is (in our humble opinion) more than worth the storage consumed (approx. 2kb/task):

Outbound Call Linking 

You know that handy feature for Inbound where you can link a call to a record of your choice?

Wouldn’t it be nice if you could do the same for Outbound calls? Let’s say you call your contact (Contact A) at XYZ Company, but for whatever reason, they need to transfer you to another person (Contact B). As it stands today, because you placed the original call to Contact A, the call, along with all associated data will log against Contact A.

No longer! Part of version 2.0/2.1 is the ability to use the same Link function you’re familiar with for Inbound, but on Outbound calls.

Configurable Fields on Dispositions (Denali for Dynamics)

I know you didn’t think we were going to leave our Dynamics friends out in the cold… And believe me when I say SFDC folks should be jealous on this one!

Starting today, we now support the use of additional fields in conjunction with Dispositions.

What this means is that when your user selects “Interested,” you have the ability to define at an administrative level what additional fields you would like the reps to complete, in addition to whatever fields are already filled in via the Disposition logic. These fields can either be required or optional, and will display in the left-hand dial panel after clicking the Disposition (the same functionality as the existing Notes box).

Additional fields can either exist on the entity being called, or the phone call entity itself. Fields can be configured (added/removed) via the Disposition Manager and will appear if the user is calling on the appropriate entity.

There is a decent amount of configuration that will need to be done in order to utilize this feature, so we recommend setting up some time with one of our Implementation Engineers. To do so, please reach out to your Customer Success Manager.

Want to learn more about these features or how DialSource Denali can help your team reach peak sales performance? Contact our team.

Contact DialSource