It is important to note that requires that the email message sent to EmailToVoice.Net be from your company email address. That means that the email address must have the same domain as your company URL or your company has exclusive rights to the email address.

However, sometimes the application originating the message will send from its own general-purpose email address.

For instance, monitoring software will send an alert email from an email address within their own service domain. The customer wants to get that alert message as a phone message instead of an email. So, we convert the content of the Email into a nice-sounding voice, dial the phone number of the customer’s recipient who needs to hear the message, etc. An example of the recipient’s TO field would be something like: or

Now, there is a sophisticated alternative to solve the issue that an application or service is sending the Email FROM a general-purpose email address not exclusively owned by the customer.


X-headers are email headers that are added to the email in addition to the standard headers, such as the To, From, and Subject, according to the specific needs of the sender.  

Using Microsoft Mail flow rule actions in Exchange Online you can add a Header Name and a Header Value. For more info on this Mail flow rule actions in the Exchange Online feature:

This means you would not need to change the FROM address. You can set up a rule to add a header to any message received from a general address.

  • For the message header Name, set this as: X-Header-ID.
  • For the Header value: insert a random string of your choice. Add this random string in the Customer Portal / My Details for the customer account.

This enables processing email to TTS via any FROM Email address as long as it gets to, and we use this embedded identifier to authorize and route the message through the appropriate customer account.

For those interfacing with the Email ToVoice.Net programmatically, several parameters can be included in the email header fields. These are:


“X-Header-ID” is an alternate method of user identification. If a field called “X-Header-ID” is
found in the header of an email to broadcast request, the system searches for a user with a
matching the “X-Header-ID” value setup in their user profile, and using that account to send the

If this field is found then the sender’s email address is not used to identify the user account.


If an “X-Header-ID” field exists, then an additional field “X-ReportTo” can be added to the email
header. This should consist of a valid email address, and if this is found, then job reports are
sent to this address instead of the address linked to the user’s Account. This allows multiple
users to send jobs and receive job reports through a single account.


For accounts set with embedded password authentication, the password can be sent in an “X-
EtoB-PW” header field instead of in the body of the message.


In the special case where the “TO” address is not a standard
format address, as can be the case when a Mailing List is used to send emails to Broadcast
requests, then the system will check for one or more “X-Receiver” header fields for appropriate addresses, and use these to get the destination addresses.

Additional account selection options

If you can not edit the email headers, and you are stuck with a fixed sender address, you can
also identify your account by adding “<EtoBcode>*my xheader id*</EtoBcode> to the start of
your email body.

If we can assist you further, don’t hesitate to reach out.