Beam

RCS and SMS fallback guides

Beam uses iMessage for eligible iPhones, RCS for supported Android phones and SMS fallback where available. Channel support, delivery status and the requirements of the SMS sending route should be checked before a client rollout.

Start with the iMessage API channel routing, then use these articles to test the details of your client workflow.

Understand the delivery route

Handle delivery and opt-outs

Frequently asked questions

Can an Android contact receive iMessage?

Beam uses RCS when the Android phone and carrier support it, with SMS fallback otherwise. A line capable of iMessage does not make an Android recipient an iMessage recipient.

Does iMessage remove SMS registration requirements?

iMessage and FaceTime Audio run outside carrier A2P 10DLC. SMS fallback remains subject to the applicable carrier requirements for its sending route.

Does delivered mean the person read the message?

No. Delivery and read status are different. Beam reports read status only when the channel supplies a real event.

Should an uncertain message be sent again immediately?

Check the recorded message status first. An uncertain iMessage delivery is not automatically resent or switched to SMS.

Continue with Beam documentation or contact the Beam team.