Overview
After Scripts are truly exhausted, Telestars can compare eligible bundles with the latest fan request, recent conversation, sourced preferences, real media context, prior delivery and purchase history, cooldown, and Content tier.
- Improve match quality through accurate media context.
- Understand why a strong request still cannot bypass eligibility.
- Reduce unrelated or repeated offers.
Before you start
- Select the bot whose autonomous Gallery inventory you want to manage.
- Upload and prepare the media assets before adding them to a bundle.
- Understand that Gallery becomes eligible only after the complete Scripts-first path.
Step by step
- Review each bundle and confirm its media has accurate, non-invented context.
- Use distinct bundles for meaningfully different scenes, media types, or content themes.
- Confirm the fan has completed the entire Scripts-first path before testing matching.
- Send a clear natural fan request and note which eligible bundle is chosen.
- Repeat with a relationship-only message and confirm Telestars can continue the conversation instead of forcing an unrelated offer.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Current signal | The latest fan request and recent conversation help rank content that is already eligible. |
| Durable context | Sourced media preferences, prior previews, offers, and purchases can improve relevance. |
| Media truth | Matching depends on real bundle and member context and cannot invent details that are not known. |
| Eligibility boundary | No match can bypass disabled state, readiness, prior consumption, cooldown, Waiting Payment, or Scripts-first order. |
| No forced mismatch | When no relevant bundle is available, Telestars should not force unrelated content. |
Verify the result
- The selected bundle is relevant to the current conversation and its media context supports the caption.
- No disabled, blocked, consumed, or already purchased bundle is selected.
- A relationship-only fan message does not automatically trigger a paid offer.
Troubleshooting
| If you see this | What to check |
|---|---|
| A bundle is visible but not selected | Check enabled state, readiness, prior use, Script state, relevance, cooldown, and the current fan turn. |
| Paid media cannot be added or delivered | Check the asset paid-delivery readiness and Secretary Mode permissions. |
| The same bundle appeared twice | Confirm the first attempt was actually delivered; only failed or provably unsent attempts stay eligible. |
Best practice
Matching quality starts with accurate media context and a clean eligible catalog; Content tier cannot compensate for generic or misleading metadata.