Migrate RCS to Bird
Move the brand, launch-market configuration, rich content and interaction handling together. A previous provider’s sender identifier is a reference for the transition; it is not a Bird channel identifier.
Choose your current provider
Prepare the change
- Record the current configuration, active customer work and the application records that must remain accessible.
- Complete the Bird setup with a separate test workflow. Map the current request to Channels API receiver, body or template, and map delivery states separately from read/click interactions.
- If the existing provider handles fallback, configure the Bird Navigator and authored SMS content. Test native RCS, a definite reach failure, an opt-out and an uncertain result. Reconcile the original attempt before retrying.
- Move a bounded part of traffic, inspect the outcome and retain the previous service until the transition is verified.
Build the receiving integration
Verwandte Ressourcen
Weiter mit der Dokumentation, Anleitungen und Beispielen zu diesem Thema. Die Ressourcen sind auf Englisch.