Sender Identity
Learn about Sender Identities and how to get one provisioned for your account
Last updated
Was this helpful?
Jump to...Create Free API Account
Learn about Sender Identities and how to get one provisioned for your account
Last updated
Was this helpful?
When sending iMessages you will use a dedicated Sender Identity to identify your brand when communicating with your subscribers.
A Sender Identity consists of the characters at the top of an iMessage conversation to iMessage-enabled recipients. This is the contact information that your recipients will see when interacting with your brand via iMessage.
A Sender Identity looks like an email address, consisting of the sending name and a domain. One or more Sender Identities can be used when sending iMessages via Mobile Text Alerts. You can select which to use, just like when selecting an outbound longcode for SMS.
and ask about getting an iMessage Sender Identity. Include the name of your brand in your request so that we can get a Sender Identity setup that closely corresponds to your business.
Upon enrollment in the iMessage sending program, a Sender Identity will be provisioned for your account. You can supply a desired name for your Sender Identity, but it will come with a pre-configured domain that is verified for iMessage sending.
Mobile Text Alerts also provides support for for Sender Identities. You can request additional Sender Identities be provisioned for your account. Depending on the number of identities requested, it may take up to three days to complete the provisioning process. Once provisioned, each Sender Identity will be attached to an outbound longcode on your account. When sending messages, each selection of a specific longcode will correspond to a specific Sender Identity. If Mobile Text Alerts detects that a recipient is iMessage enabled, it will use the Sender Identity associated with the outbound longcode and send via iMessage instead of SMS.
Custom domains are supported but require additional configuration and setup before use. After submitting a request for a custom domain, MTA will identify the particular domain for use and will either purchase and maintain the domain on your behalf depending on the use case. Domains provisioned and managed by MTA have an additional cost, or you can purchase and provide one.
Finally, DNS entries will need to be configured to properly set up the custom domain. After this initial configuration, all future Sender Identities can be provisioned using this domain.