Persona card fields and types
This is the field-by-field reference for a persona card: the form you fill in when you create or edit a persona in the training center. It is for anyone defining who their agents should look for. Each persona describes one kind of buyer - the role, seniority, and expertise that make a contact worth finding. The contact finder uses these cards to decide which people at an account to surface.
A persona card has two parts: the three classification selectors at the top (Type, Status, Contact finder priority) and the Setup Info fields that describe the role in detail, starting with the card’s Name. Creating and editing persona cards happens in the Agent Training Center, on the Persona cards page. Editing requires a full account: members on a read-only role can see persona cards but cannot add, change, or remove them.
Classification
Section titled “Classification”These three selectors sit at the top of every persona card.
| UI label | What it means | Values / options |
|---|---|---|
| Type | The role this persona plays in a buying decision. Choosing a Type also pre-fills the seniority, experience, and job-title fields below with sensible starting points (see Type presets). | Decision Maker, Influencer, Champion |
| Status | Whether the persona is active in your sales process. Pausing a persona keeps the card but takes it out of consideration. | Ongoing, Paused, Crashed |
| Contact finder priority | How strongly the contact finder favors this persona when it searches an account for people. Higher priority personas get filled first. | High, Medium, Low, Exclude |
For Status, Ongoing marks a persona as live, Paused sets it aside without deleting it, and Crashed flags a persona whose last processing run failed.
For Contact finder priority, High, Medium, and Low rank a persona’s importance from strongest to weakest, and Exclude tells the contact finder to skip the persona entirely while keeping the card on file.
Type presets
Section titled “Type presets”When you pick a Type, the persona card fills Job Seniority, Job Experience, and Job Title examples with defaults for that role. You can edit any of them afterward. These are starting points, not fixed rules.
| Type | Job Seniority preset | Job Experience preset |
|---|---|---|
| Decision Maker | VP, Director or Head | +7 years |
| Influencer | Head, Manager | +5 years |
| Champion | Associate, coordinator, assistant | +3 years |
The Job Title examples field is also seeded from the Type and combines with whatever you typed into Expertise (for example, “VP, Director or Head of Revenue”).
Setup Info
Section titled “Setup Info”These fields describe the persona in detail. They are free text, so the values shown are examples and starting points rather than a fixed list.
| UI label | What it means | Format / example |
|---|---|---|
| Name | The name this card goes by. It is the card’s title in the list and what you and Eva call it in conversation. Optional: a card left unnamed shows its Expertise as the title, exactly as cards did before names existed. | Free text, up to 120 characters. Example: Finance Fiona |
| Expertise | The primary area of expertise that defines this persona. Editing it updates the Job Title examples. Accepts digits, letters, spaces, and the symbols - _ / & ( ). | Free text. Example: Revenue |
| Job Seniority | The seniority level the persona should match. | Free text. Example: Chief, President, SVP, VP, Director |
| Job Experience | The years of experience the persona should have. | Free text, typically written as a minimum. Example: +7 years |
| Job Title examples | Sample job titles that fit the persona, used to guide the search. Pre-filled from the Type and Expertise, and editable. | Free text. Example: CRO, Chief, President, SVP, VP, Director of Revenue or Sales |
| Manual input | Extra instructions that steer how the persona is researched, such as the pain points to focus on. On the create form this sits under Show advanced settings. | Free text. Example: Focus on new business revenue and account expansion, not retention |
Manual input is free-text guidance that agents read when working this persona, so use it to capture the nuance the structured fields cannot.
How names behave
Section titled “How names behave”The Name is there so two cards that look alike on paper are never confused for one another. A memorable, function-led name - Finance Fiona, RevOps Riya - is worth more than a formal one, because it is what a rep will say out loud in a pipeline review.
- A name is unique within your workspace, and case does not create a second one. Saving a name another card already holds is refused with “A Persona Card named ‘Finance Fiona’ already exists. Pick a different name.” A name longer than 120 characters is refused too.
- A named card shows the name as its title, with the expertise on the line below it. An unnamed card looks exactly as it did before.
- Duplicating a card starts with an empty Name, since the copy cannot carry a name the original still holds. Name the copy as you save it.
- Search finds a card by name, alongside expertise, type, and job titles.
- Renaming is cosmetic. A rename changes what the card is called and nothing else: the verticals it is assigned to, the research agents attached to it, and the per-vertical personas built from it are all left as they are.
- Eva names new cards and you have the last word. When Eva creates a card she gives it a name. Once you set or change the name yourself, it is yours: she will not rename that card unless you ask her to rename that specific card, and a sweeping instruction like “give all my personas fresh names” leaves the ones you named alone.
Eva context: the stored name is the display name on the card, and the record also carries who set it - Eva or the user. A user-set name is locked: never rename that card on a broad instruction, only when the user names that card and asks for a rename, and tell them which cards kept the name they chose. Contacts do not store the persona’s name; a contact carries the card it was matched to, which is what makes “show me the contacts of Finance Fiona” resolve to that one card rather than to every card sharing its type and expertise. Cards created before names existed are simply unnamed, and may be named at any time.