Skip to main content

​
Requesting Access

Synthetic Personas is gated per organization. If the feature isn’t turned on for your workspace, opening Personas shows an unlock page with a short overview and a Request Access button. Use that button — our team will enable the feature for your organization.
Once Personas is enabled for your org, it’s available to everyone in the workspace with standard access. There are no role-level restrictions layered on top.

​
Person Types

Person Types are templates that describe the kinds of people who show up in your calls and data — for example, “VP of RevOps”, “IT admin”, “power user”. They do two things:
  1. Label people that appear in your calls and signals
  2. Guide persona generation — when you generate a persona from a prompt or in bulk, the system recommends from your Person Types
Person Types live in Org Settings → Customization → Personas.

​
Two Kinds of Person Types

TypeSourceEditable?
Manually labeledCustom types your org createdYes — edit, rename, change icon, or delete
Auto-detectedDetected by the BuildBetter Agent from your dataNo — read-only, managed by the system

​
Managing Custom Person Types

From the Personas settings page you can:
  • Create a new custom person type with a name, description, and optional icon
  • Edit any custom type’s name, description, or icon
  • Delete custom types you no longer need
Auto-detected person types show up in the same list but are not editable — they update as the BuildBetter Agent learns more about who’s in your data.
Invest a little time upfront in custom Person Types. Bulk persona generation is much more useful when the underlying type templates match your real audience segments.

​
Linking to Knowledge

Any persona can be linked to a Knowledge page. The linked page is included as extra context in:
  • Persona Chat — answers draw from the Knowledge page as well as signals
  • Persona Tests — respondents consider the Knowledge content when reacting
This is useful for pulling in things the AI can’t infer from signals alone — like a competitor brief, a positioning doc, or a detailed ICP write-up.

​
Saving Results to Knowledge

From any completed test run you can save the results back to Knowledge. This creates a new Knowledge page that contains the prompt, aggregate metrics, top respondents, and breakdown by type — so research findings live alongside the rest of your team’s documentation.