There are business processes that require parsing important information from the text of an email and then creating a voice message for making a phone call.

When We Need to Parse an Email into a Voice Call

Using the EmailToVoice.Net service, you are able to make a phone call by using any commonly available email interface. EmailToVoice.Net provides the ability to convert the content of an Email to voice using text-to-speech (TTS) and call a phone number. This is extremely useful when monitoring software or a business application can only send an email; but a phone call is necessary to be an effective alert.

But, the content of a voice call can sometimes need to be quite different than an email. For example, the signature section of an email is not needed in a phone call and may sound quite unusual to the phone recipient.

The email signature can be excluded from the voice conversion process. This can be done at the Account level by making the request through the contact us form, or by inserting the EmailToVoice.Net tag called “<End Message>” into the text of the email. Thereby, the email signature is not converted to voice. This makes the call sound more natural for a phone call. And, this also helps in reducing the size of the voice message.

Sometimes Email needs to be parsed into a voice message

Eliminating the email signature can sometimes not be enough. The text of the email may need to be parsed to make an intelligible voice communication, if the original email has tables or is inherently cryptic.

There are several alternatives to parse content of an email into a voice message when using EmailToVoice.Net. One solution is Microsoft Flow. We discussed this service in our Blog post call Using Microsoft Flow with EmailToVoice.Net to Forward an Alert to a Phone. In that post we explain:

So, what is the solution to the dilemma of needing to make a phone call from a general purpose email monitoring service.

One solution is to use Microsoft Flow with EmailToVoice.Net. Following is an example of steps to set up a Microsoft Flow that will accept the alert from the Monitoring Service from a general purpose email address into the customer-owned email address that is authorized to send messages to EmailToVoice.Net. When Microsoft Flow detects an arriving alert message into the customer’s email, Microsoft Flow will trigger an email to be sent from the customer’s email (forwarded) to the EmailToVoice.Net with the same alert message generated by the Monitoring Service.

However, Microsoft Flow can be used for even more than what we discussed in our previous blog post. Flow can be used to parse the content of the email into a smooth flowing message. When the message is converted to a voice by our service, this parsed text will sound natural for the person listening to the voice call. In the U2U blog there is a post explaining the Definition Language used in Microsoft Flow: Using the Workflow Definition Language in Microsoft Flow

What I would like to show in this blog post is how you can extend your flows with a bit more advanced behavior by using the Workflow Definition Language.

In addition to Flow, there are other alternatives to parse an email before it is sent to EmailToVoice.Net such as MailParser and Parserr.

EmailToVoice.Net Staff Can Help

So, there are several effective methods to parse information from an email coming from monitoring software or a business application into a smooth sounding voice call delivered through EmailToVoice.Net. Do not hesitate to contact us if we can assist you further in meeting your business requirements.