Guidesstep by step for the closed beta
Four short guides for the current closed beta: reviewing a fan profile, capturing your Fansly session in Chrome, setting up a creator persona, and handing a conversation to a teammate. Each one covers what you need first, the steps, what to expect, and what to do if something goes wrong.
Fansly sync
Background
Drafts
You review
Every send
Approved
Availability
Closed beta
Reviewing a fan profile
Check what PixelFlirt has recorded about a fan against the latest conversation, and correct the lifecycle phase when it is wrong.
Capturing your Fansly session in Chrome
For existing closed-beta access: install the connector our team provides so desktop Chrome can capture your Fansly session locally.
Setting up your creator persona
Describe the creator's voice, boundaries, and reply rules on the Model page so drafts start closer to how the creator writes.
Handing off a conversation respectfully
Give a teammate the context they need from the conversation and fan profile, without pressure or invented details.
Guide
Reviewing a fan profile
Before you start
You need access to a Fansly account that is already set up in PixelFlirt. Select that account before you start. Changing the lifecycle phase requires the owner or admin role.
Steps
- With the correct account selected, open Fans and choose the fan you want to review.
- Read Profile facts and the Relationship summary, and compare them with Recent messages on the same page.
- Check Extraction status to see when the profile was last processed and whether processing is pending or failed.
- If the lifecycle phase is wrong and you are an owner or admin, choose the right phase under Manual lifecycle phase, add an optional reason, and select Save phase.
What you should see
A profile you have checked against the conversation, with the lifecycle phase corrected where needed. Profiles are deliberately compact: they are not a complete record of everything a fan has said, and not every fan has extracted details yet.
If something goes wrong
A missing detail does not mean something never happened, so check the latest conversation instead of filling the gap from memory. If the profile does not load, select Back to clients, confirm the selected account, and open the fan again. If you cannot see Fans or the lifecycle controls, ask your team about your role or account setup.
Guide
Capturing your Fansly session in Chrome
Before you start
You need existing closed-beta access plus the connector package and instructions from our team. Contact us about availability; access and new account setup are not guaranteed. Use Google Chrome on a desktop computer (PC or Mac), in the same Chrome profile you use for Fansly.
Steps
- Install or load the connector package in Chrome as our team's instructions describe.
- In the same Chrome profile, open Fansly, log in if needed, and refresh the inbox once.
- Return to the PixelFlirt tab and select Check again to see whether the connector is detected and has captured a session.
- Tell our team that capture is complete. For existing beta access, the team connects the captured session to PixelFlirt's authorized sync service manually.
What you should see
PixelFlirt shows that the connector is detected and that a session is captured locally. This status describes this browser only: capture does not create an account, complete secure pairing, or show that sync has finished, so setup can still look incomplete until the team has connected the session and the first sync is done.
If something goes wrong
If the connector is not detected, check that it is installed in the same Chrome profile, then refresh the PixelFlirt tab after installing or reloading it (select Refresh page if PixelFlirt asks). If no session is captured, log in to Fansly in that profile and refresh the inbox. If it still does not work, contact our team. Never send session details, cookies, or copied values by email or chat, and never post them anywhere.
Guide
Setting up your creator persona
Before you start
You need the owner or admin role for the account. Select the correct account, then open Model.
Steps
- Fill in Bio / persona, Tone of voice, Boundaries, and Default response rules in plain language. Under Writing samples, add a few short messages the creator wrote and is comfortable using as style references.
- Select Save model and wait for the saved confirmation.
- Optional: under Analyze creator style, choose a date range and select Generate preview.
- Review and edit the proposed sections, remove anything too personal or specific, and choose a Merge strategy. The default, Append examples, adds examples without changing text fields; Fill empty fields only fills blank sections; Replace generated fields replaces the selected generated fields. Then select Apply selected edits to form.
- Check the form and select Save model again. Applied preview edits are not saved until you do.
What you should see
A saved persona that future drafts use as context. Writing samples and generated examples guide tone and rhythm; they are not phrases drafts must repeat, and every draft still needs review and approval.
If something goes wrong
If saving fails, your edits stay in the form: select Save model again and wait for the saved confirmation instead of reloading the page. Run and apply strategy is not the preview step: it runs a new analysis and saves the result straight to the persona, so use it only when you do not need to review the changes first.
Guide
Handing off a conversation respectfully
Before you start
Everyone involved needs existing access to the account. Members can prepare and edit drafts, viewers can only read, and only owners and admins can approve and send. Account → Members lists who has access, with their roles and status; it does not invite people or change permissions.
Steps
- Confirm the selected account and the fan before you start.
- Read the latest conversation in Inbox and the fan's compact profile under Fans.
- When you brief a teammate, share only verified context that helps the reply, such as what the fan asked for and preferences they stated. Leave out guesses and anything the fan would not expect to be passed on.
- Prepare or edit the draft in the conversation.
- An owner or admin reviews the recipient, text, media, and price, then approves it.
What you should see
A draft grounded in the actual conversation and approved by someone with the right role. Nothing is sent without that approval.
If something goes wrong
If the fan writes again before approval, read the new messages and review the draft again. If delivery is uncertain, check the conversation and the draft's status before approving anything again. Never invent personal details or use fan context to pressure anyone.