Worth knowing before you set it up rather than after.
- No MMS, and no replies to texts. Email2Phone can send a text, but only a plain one-way SMS of up to 160 characters, one per email.
- No API and no webhook. Email in, call out. That is a limitation and also the reason the list of things that can trigger a call is as long as it is: anything that can send an email already integrates.
- No mobile app. The phone that rings can be a mobile, a landline, a desk phone or a VoIP line; nothing is installed on any of them.
- No on-call rotation management, incident timeline or incident analytics. There are no rotations, no MTTA or MTTR reporting and no handover. If you need those, an incident platform is the right purchase and this is not a substitute; the alternatives pages say when to stay with one.
- No per-message throttle setting. There is no rate limit to configure. For calls the mailbox model makes one largely unnecessary, because a flood becomes one call rather than a queue of them. Texts are one per email, so a flood of emails to a number set to text is a flood of texts.
If what you need is a phone that rings, calls back when nobody answers, and, on a line with voicemail off, counts nothing as delivered until a person presses a key, that is the whole product; how an email becomes a phone call, the long version has all of it.