The Fan Profile
Everything your business knows about one relationship, on one screen. This is what turns a chatter who has never spoken to someone into a chatter who sounds like they have known them for months.
The profile is available on the dashboard and, in a working form, on the Fan tab of the side panel — so a chatter never has to leave the conversation to see it.
Identity
Section titled “Identity”- Display name and platform handle
- Creator — which relationship this is
- First contact and last activity
The three text fields, and why they are separate
Section titled “The three text fields, and why they are separate”This is the most important distinction on the page. Three fields hold written information about a fan, and each has a different owner and a different job.
Two of them sit side by side on the Profile tab; the third has a tab of its own, because nobody on your team writes it.
| Field | Where | Written by | Seen by the AI | Use it for |
|---|---|---|---|---|
| Notes | Profile | Your team | Yes — every reply, as background | Stable facts in your own words: “works nights, only free after 11”, “collects vintage watches”, “do not discuss his divorce” |
| Instructions for the AI | Profile | Your team | Yes — every reply, as an order | Standing orders for this fan: “never mention his ex-wife”, “always confirm the price before offering”, “he responds to being teased, not to compliments” |
| AI memory | Memory | The platform | Yes — every reply | Durable facts the fan has shared, maintained automatically. See AI Memory |
- Notes — what is true about this fan, in your words. Not orders to the AI.
- Instructions for the AI — a standing instruction for this fan only. An order, not a fact.
The difference between the first two is not who reads them — it is how they are read. Notes are background the AI writes from; instructions are rules it writes within. If you want behaviour changed, put it in Instructions for the AI: a directive always outranks background.
⚠️ There is no field the AI cannot see
Section titled “⚠️ There is no field the AI cannot see”All three fields go into the prompt for every draft. Do not use Notes as a private staff channel. Internal risk assessments, opinions about a fan, chargeback history, real names, your own pricing floor, “handled by Maria” — none of that belongs here, because all of it reaches the model and can surface, rephrased, in a message to that fan.
Keep internal commentary in your own systems. This profile is the fan’s record, and it is written for the AI as much as for your team.
The platform never overwrites what your team wrote. Both fields on the Profile tab belong to your team. The AI maintains its own field and only its own field.
Agency tip. Instructions for the AI is the single most underused feature in the platform. One line — “he is here for conversation, not content; do not pitch” — prevents a category of mistake that otherwise recurs on every shift, with every chatter, forever.
Your segmentation labels for this fan. Apply them freely: tags drive the fan directory’s filters and are how you build campaign audiences.
Commercial position
Section titled “Commercial position”| Field | Meaning |
|---|---|
| Lifetime value | Everything this fan has ever spent, kept current automatically as purchases are logged |
| Finances | The itemised purchase history — tips, PPV unlocks, subscriptions and customs — with LTV, purchase count, average and last purchase above it |
| Funnel stage | Where this conversation currently sits on the path to revenue |
| Conversation health | A flag raised when a conversation is engaged but no longer deepening — a signal to change approach |
The funnel stage is maintained by the platform on every exchange, so you can work your directory by readiness. See Key Concepts for the stages.
Relationship indicators
Section titled “Relationship indicators”| Indicator | What it tells you |
|---|---|
| Warmth | How your creator currently feels toward this fan. Takes priority over the creator’s general mood, so a close fan gets a warmer reply even on a low-energy day |
| Closeness | How much the creator opens up to them — this governs which life events and personal moments this fan is allowed to hear |
Both are maintained automatically as the relationship develops.
Language
Section titled “Language”| Setting | Effect |
|---|---|
| Fan language | The language this fan writes in. Detected automatically |
| Lock language | Pins your choice permanently. Once locked, automatic detection never changes it again |
Lock the language for any fan who switches between languages, or where the detected value is not the one you want to sell in. A manual choice always outranks automatic detection.
If your chatter works in a different language from the fan, enable bilingual drafts in your personal settings — the chatter then reads and edits in their own language while the fan receives the reply in theirs. See Writing Replies.
Automation for this fan
Section titled “Automation for this fan”Reply mode on the profile overrides the creator’s setting for this one conversation. The same control appears on the side panel’s Fan and Autopilot tabs — it is one setting, wherever you change it.
Leave it on Same as the creator for almost everyone. Set it explicitly when a specific relationship needs different treatment:
| Situation | Setting |
|---|---|
| A whale you want hand-written, on an otherwise automated creator | Manual |
| A high-maintenance fan you want drafts prepared for, but never sent automatically | Draft only |
| A low-value, low-risk conversation on an otherwise manual creator | Draft and send |
The platform deliberately does not decide this from spend. A fan becomes manual because a person decided they should be — never because a threshold guessed.
To move a whole cohort at once, use the fan list — see Changing Many Fans at Once.
Content already sent
Section titled “Content already sent”The profile tracks which items from your media vault this fan has already received, so nobody re-offers content they have already paid for. Items are recorded automatically when a draft that offered them is sent, and you can mark or unmark them by hand.
Follow-ups
Section titled “Follow-ups”Schedule a next action with a due date — “ping Friday about the custom set”. Follow-ups appear in the Follow-ups section of the profile, in the conversation context in the side panel, and in the Operator queue on the Dashboard. Mark done keeps the record rather than deleting it.
Shared photos
Section titled “Shared photos”Fans often send photos of themselves. Upload them to the fan’s album with a caption so any chatter picking up the relationship has the same visual context the previous one did.
Conversation history
Section titled “Conversation history”The complete message history, in order, with anything the fan purchased in context. This is what the platform reads before writing each draft, and it is what your team reads when a relationship needs a human decision.
See Conversation History for how history is imported and kept current.
Activity and export
Section titled “Activity and export”Each profile carries an activity summary — total messages, drafts generated, first contact and volume by month — and a full export of the relationship on request.