Send an Apple Messages app experience
Use App experience when your organization already owns a published iMessage app or an App Clip that the customer can open. Bird sends the interaction; app development, publication, and compatible-device behavior remain your app team's responsibility.
Have the app team supply the published identity, payload format, and a test procedure before authoring the message. A URL pointing to an ordinary website does not turn it into an iMessage app.
Configure a published iMessage app
- Open Templates and select New template > App experience.
- Enter the draft name, Title, and Message in Content.
- In Apple delivery, set App experience to Published iMessage app.
- Fill in the fields provided by your app team:
| Field | What it identifies |
|---|---|
| Published app ID | The published app's identifier. |
| App name | The name shown for the interaction. |
| PNG app icon URL | The public icon URL; follow the media constraints. |
| Extension identifier | The extension identity in com.apple.messages.MSMessageExtensionBalloonPlugin:team-id:extension-id form. |
| App payload URL | Content interpreted by your app, such as its agreed order-view parameters. |
| Session identifier | The app interaction's session value. |
| App bubble layout | Static layout or Live layout, according to the app's implementation. |
Customize the received and reply bubbles if needed. Select the business, save the draft, and prepare the message.
Configure an App Clip preview
In the same message type, choose App Clip preview under App experience and supply App Clip URL. Preparation obtains the Apple-generated preview for the supported URL. App Clip publication and invocation must already be configured by the app team.
Verify the app on a device
Send to an authorized test conversation on a device suitable for the app. Open the message and check that the correct app or App Clip handles the payload. Follow the intended action to its final result, including cancellation and a missing or expired business record.
Bird's browser preview does not install or execute the app. Known built-in capability checks do not establish that a custom app is installed or works. Offer a web or text alternative for customers who cannot complete the interaction.
If preparation or processing fails, inspect the error, published identity, icon URL, and payload format. Use message history to separate a failed send from an app that opened but could not complete its business action.