Help center
Run your store, not our infrastructure.
Practical setup and recovery guidance for the private beta.
Add your store
Use the official public website. Start with a product, collection, or home page that shows real products and images. Fama reads only the submitted page unless a selected same-origin product needs controlled detail enrichment.
Connect Instagram
Use a professional Business or Creator account. The direct Instagram Login flow does not require a Facebook Page. Reconnect only when the product reports a genuine authorization or credential problem.
Create a content queue
Paste a useful storefront page and choose Create post. The queue ranks grounded candidates. Creating a fresh queue replaces pending analysis; unchanged stores may produce similar products.
Publish manually
Review the current draft, edit caption and hashtags, confirm the real product image, and publish. Only the current eligible queue item can publish. The queue advances only after Instagram confirms success.
Schedule approved drafts
Choose a future time and timezone. Automatic scheduled publishing must also be enabled for the store. Manual schedules take priority over autopilot.
Use autopilot safely
Off keeps everything manual. Draft suggestions can prepare content for review. Full autopilot may generate, approve under fixed safety rules, schedule and publish one Instagram post per day. It is never enabled automatically.
Publishing is paused
A paused state protects the store. Check whether automatic publishing is off, autopilot is off, the beta team paused the store, or the global service is temporarily unavailable. Existing drafts and history remain.
A post failed
Read the plain-language action on the current draft. A failure before Instagram receives the final request may be safely retryable. An uncertain final request remains locked to prevent duplicates. Do not force a retry.
Reconnect only when required
Reconnect when the product explicitly reports an expired, revoked or missing publishing authorization. A healthy connected account should not be reconnected just because a different operation failed.
Why the beta has limits
Conservative store, generation, queue and schedule limits prevent accidental jobs and duplicate publications while the service is invite-only. They are product limits, not hidden errors, and an administrator can review account-specific overrides.
Still need help?
Support contact details must be configured by the project owner before external invitations begin.
Account and data deletion