Paminga IQ: Persona Classification Agent
When this action fires, a Paminga IQ agent reads what you know about each contact — their job title first and foremost — weighs it against the Personas you've defined, and records the one that best applies.
From there, the contact's Persona is yours to use:
- When using Paminga IQ to draft emails, landing pages, and CTAs
- Segment on it anywhere Paminga's Segment Builder appears.
This means you can score, customize content, trigger alerts, and more based on Persona - It's visible on the contact record itself, in Contacts
This agent classifies contacts against the Personas you've defined in Account Settings › Personas. Until at least one Persona exists, there is nothing to classify against — the action's settings will point you there.
Rather than writing them from scratch, run Persona Discovery on that page. It drafts your Persona library from whatever you already have: the buyers your ICPs name, the job titles your contacts actually hold, and the pages on your own site that speak to a particular role. Any one of those is enough to start.
These are not the same thing as the Personas you use to serve different content inside an email or landing page. Those are audience definitions for personalization. These describe who a person is — their role, their seniority, what they care about — and a contact holds exactly one.
One Persona Per Contact
A contact has one Persona at a time. Assigning a new one replaces the old one, whether a person does it by hand or the agent does it.
That's deliberate. A Persona answers "who is this person?", and a contact who is both a Marketing Ops Manager and a CTO is not a contact — it's two. Keeping it to one means everything downstream, from a segment condition to an AI-drafted email, has a single unambiguous answer to work from.
What the Agent Reads
The contact's job title is the signal that does most of the work. The agent matches it against the job titles, seniority, and departments each of your Personas names — and it matches on substance rather than on exact wording, so "Head of Revenue Operations" still finds a Persona whose stated title is "Director of Revenue Operations."
A little about their company — industry, size, and the account's ICP if it has one. A Director of Operations at a 40-person agency and one at a 9,000-person manufacturer are different buyers, and this is what tells them apart.
Your contact's custom fields, in case that's where you keep the role information that isn't in the job title field.
Their company's team and leadership pages, but only when the job title is missing. If a contact has a title, that's enough and the agent doesn't go looking. When it is missing, the agent reads the company's site for the contact by name — an "our team" page naming them and their role settles it. Contacts at the same company share one read of that site rather than each triggering their own.
"Too Little Evidence" Is a Real Answer
Plenty of contacts arrive with an email address and not much else. The agent doesn't guess at those.
When nothing it can read says what a person does, the agent records no Persona and leaves the contact eligible — so the next time the action fires, after an import or a CRM sync has filled in their title, it tries again. A contact is never written off for being incomplete today.
This is worth knowing before you enable the action: if your contacts largely don't have job titles, expect most of them to come back unclassified until that changes. Enriching your contact data is what moves that number.
"None of My Personas" Is Also a Real Answer
Different from the above, and the agent keeps them apart. When it does know what a person does and none of your Personas describe them — a student, a competitor, a job applicant — it records that verdict rather than forcing a match.
That counts as classified. In "do not re-classify" mode the contact won't be re-evaluated; with a re-classification window, it gets another look once the window passes.
For segmenting, this means a contact with no Persona is either "not yet classified" or "confidently none of them," so segment on specific Personas rather than on the absence of one.
Re-Classification
People change jobs, and so do your Personas. The action gives you two modes:
- Do not re-classify contacts that have already been classified — each contact is classified once. This is the default.
- Re-classify if the contact's Persona classification is older than (days) — a contact becomes eligible again once its last classification is older than the window you set. Use this when the action runs on recurring triggers (CRM sync, workflows) and you want classifications to stay current.
Your Own Assignments Win
If you or a colleague assigns a contact's Persona by hand, the agent leaves it alone. A scheduled action and a bulk run will never undo somebody's deliberate choice.
The one exception is you, acting on that contact: classify it directly and the agent will replace your earlier assignment, because that's plainly what you asked for.
The same protection applies mid-flight. If someone changes a contact's Persona while the agent is working on it, the person's choice is kept and the agent's answer is discarded.
Tuning the Agent
Like Paminga's other classifiers, this one reads guidance you control. Go to Settings › AI › AI Agents and open Persona Classifier guidance to see exactly what the agent reads, in order, and to add your own rules — how to treat seniority, which Persona to prefer when two of them fit, anything particular to how you go to market.
Your guidance sits alongside instructions Paminga owns and you can't edit away, including the rule that a Persona describes a person rather than a company, and that text read from a website is evidence about a contact and never an instruction to follow.
Where You Can Trigger It
Like all Paminga Actions, this one is available everywhere actions are: form submissions, contact imports, CRM sync, workflows, lead scoring thresholds, Action Sets, and more — including as a Conditional Action, so you can classify only the contacts that meet conditions of your choosing.
