Docs

Personas

A persona is the character your AI embodies. Its name, vibe, backstory, and a library of photos it can draw on in conversation. You build one in the Persona Forge, then pair it with an engine to run a live chat.

Open the Persona Forge to create and manage your personas. Each persona has three tabs: Identity (who they are), Vibe (how they behave), and Gallery (their photos). When you finish, the persona is used inside an engine. See the engine builder for how a persona drives a conversation.

Creating, editing & deleting personas

  • Create: use the new-persona button in the sidebar to start a fresh persona, then fill in the tabs and save.
  • Edit: select a persona to open it in a workspace tab, change any field, and save.
  • Delete: remove a persona from the sidebar; you will be asked to confirm first.

No cloning for personas

Unlike engines, personas cannot be cloned. Each one is built fresh. The number of personas you can have is set by your plan's persona limit, so plan your roster accordingly. See billing & plans for limits.

Identity

The Identity tab holds the factual profile of the persona. Every field has a length or range cap:

  • Name: up to 30 characters.
  • Age: a number from 0 to 100.
  • City (origin): up to 60 characters, e.g. "London, UK". This also drives the timezone (see the gotcha below).
  • Work (job): up to 60 characters.
  • Biography: a short backstory, up to 600 characters.

Language & matching the lead

  • Main language: the persona's default language. Supported options are English, Spanish, Portuguese, German, Italian, Swedish, and Dutch. The default is English.
  • Match lead's language: a toggle (off by default). When on, the persona auto-switches to the language the lead is writing in.

Match language only covers supported languages

"Match user language" only switches to languages FluidTalk supports. If the lead writes in an unsupported language, the persona falls back to its own main language rather than attempting the unsupported one.

Timezone

The timezone is shown on the Identity tab but is not directly editable: it is auto-detected from the City you enter.

A wrong or unknown city silently falls back to UTC

Because the timezone is derived from the City, a misspelled, vague, or obscure city can't be resolved and silently falls back to UTC. That quietly breaks anything time-aware: bot send-timing, day/night photo rotation, and follow-up scheduling will all run on the wrong clock. Always enter a real, well-known major city (e.g. "New York", "London, UK") so the timezone resolves correctly.

Personality (the Vibe tab)

Three sliders set the persona's baseline personality. Its "base soul". Each runs from 0 to 100%:

  • Flirtiness: Platonic to Romantic. Default 50.
  • Temperament (rudeness): Sweet to Alpha. Default 20.
  • Reply depth (length): Concise to Expressive. Default 50.

These are baseline values; individual engine stages can override them where needed.

Behaviour toggles

  • Decline meeting requests: on by default. The persona hard-refuses any request to meet in real life, keeping the conversation online.
  • Ignore duplicate leads: off by default. When on, the first account to engage a given lead keeps that lead; if the same lead later reaches a different account of the same persona, that duplicate is dropped. Accounts are told apart by their username, or by the API key used.

Hobbies vs. Style Tags

Both are tag lists on the Identity tab, but they work differently:

  • Hobbies / Interests: freeform. Type your own and press Enter to add them. Use these for specific, personal interests ("rock climbing", "K-pop").
  • Style Tags: chosen from a fixed library. Open the tag library and toggle the ones you want. Use these for consistent, recognized style descriptors.

Photos (the Gallery tab)

appDocsContentPersonasContent.photos.intro

Uploading: AI auto-analyze vs. manual

  • AI Auto-Sort: upload a batch and let the AI analyze each photo for you: it fills in the description, tags, and other metadata automatically.
  • Manual Entry: you set the shared description, tags, and time-of-day yourself for the batch you upload.

What the AI detects (CV metadata)

AI analysis attaches computer-vision metadata to each photo, which also powers the gallery filters:

  • Location: where the photo was taken (environment).
  • Outfit: what the persona is wearing.
  • Activity: what they are doing.
  • Mood: the overall feel of the shot.

Per-photo fields

  • Description: a sentence describing the photo so the AI knows what it shows.
  • Tags: keywords (e.g. gym, mirror, selfie) for filtering and selection.
  • Time of day: Day (sunlit), Night (dark), or Timeless (safe to send 24/7), so photos match the time a message is sent.
  • Day-set (virtual day): pins a photo to a specific day of the relationship. Leave it unassigned and the photo is eligible on all days.
  • Verification photos: photos flagged as verification (e.g. a hand-gesture shot) get a badge so you can keep them separate from regular content.

Gallery filters, bulk actions & processing states

  • Filters: narrow the grid by day-set, time of day, tag, location, outfit, activity, mood, or verification status. A Needs Review filter surfaces photos that are missing a description or tags and aren't yet usable in chat.
  • Bulk actions: select multiple photos (or select-all the filtered set) to bulk edit metadata, delete, or re-analyze them with AI. Re-analyzing overwrites existing descriptions and tags.
  • Processing states: a freshly uploaded or re-analyzed photo shows an Analyzing spinner while the AI works, then resolves to done (ready to use) or Failed if analysis didn't complete.

Storage quota

Photos count against your account's storage quota. When you hit the limit, further uploads are blocked until you free space by deleting photos. See billing & plans for your storage allowance.

Once your persona has an identity, a vibe, and a stocked gallery, head to the engine builder to put it to work in a conversation.

Personas: FluidTalk Docs | FluidTalk