Library embeds

Several Phantom modules let you post styled embeds — Scheduled Messages, Ticket Panels, Interactive Panels. Library embeds let you build an embed once in the Embed Builder and reuse it across as many of those modules as you like.

Edit the embed in one place and every spot that uses it updates automatically.

When to use one

• You post the same announcement embed from three different scheduled messages (one per timezone) and want them to stay identical.
• You have a "support hours" panel on every ticket and the hours change every quarter.
• You want one source of truth for the embed your interactive panels open with, so a typo only needs to be fixed once.

If an embed is genuinely one-off, just define it inline like you always have. The library is for the cases where you'd otherwise be copy-pasting.

How to use one

1. Build the embed in Utility → Embed Builder. Give it a memorable name — Support hours, VIP welcome, #partner-spotlight banner.
2. Open the page where you want to use it (for example, Community → Scheduled Messages → edit a row).
3. Under Source, pick your saved embed from the dropdown.
4. Your changes save automatically.

The inline embed fields on that page are kept but ignored while a library embed is selected. Switch the dropdown back to "define inline below" at any time to use the inline values again — nothing is lost.

Keeping things safe

Library embeds belong to the server that created them. A page in Server A can never accidentally pull an embed from Server B.

What happens if I delete a library embed?

The pages that referenced it fall back to whatever inline embed they had. If they didn't have one, the embed simply won't show until you pick a new library embed or fill in the inline fields. Nothing breaks.

How fast do updates show up?

Edits propagate within a few seconds. The dashboard updates immediately on save, and the bot picks the new shape up on its next post.

What about the API?

Library embeds aren't exposed through the REST API yet. For now, you read and write the consuming rows (a scheduled message, ticket panel, etc.) and Phantom applies the library embed at send time. A dedicated endpoint may come later.