Contact Classification

What it does

Job titles are unstandardized across companies and countries, and title matching by keyword sends the wrong message to the wrong person at scale. This skill classifies to department and seniority rather than matching strings, handles the ambiguous titles explicitly, and routes each contact to a persona with a stated confidence.

When to use it

• classify these job titles
• route contacts by persona
• who should I contact at this company
• messy title data
• seniority filtering

What it needs from you

• contacts: names and titles, with company domain where available
• personas: your personas and what distinguishes them
• routing: what each persona should receive

Live data it reads

Classification runs per title with optional position verification, so a title that is out of date can be caught rather than routed on. - contact-classifier: department, seniority and role classification from a job title Store page: https://apify.com/mambalabs/contact-classifier Runnable example input:

How it works

1. Classify to department and seniority first, and only then to persona. Persona is a business concept and it changes; department and seniority do not.
2. Handle the ambiguous families explicitly rather than letting them fall to a default: founder titles at small companies that cover several departments, regional titles that look senior and are not, and consultant or advisor titles that indicate no authority at all.
3. Verify position where the list is old. A title that was right two years ago routes a message to someone who left.
4. Set the seniority floor per persona and state what happens to contacts below it: dropped, or kept as a coach rather than a buyer.
5. Report the unclassifiable share. A high share means the titles need a different source, not a better classifier.
6. Attach a confidence and route low confidence contacts to a generic sequence rather than a persona specific one, because a wrong persona message is worse than a general one.

What you get back

The classified table with department, seniority, persona, confidence and route; the ambiguous families flagged; and the unclassifiable share.

The quality bar

• Department and seniority are derived before persona
• Ambiguous title families are handled explicitly, not defaulted
• The unclassifiable share is reported
• Low confidence contacts route to a generic sequence

Where it runs

• Claude Code
• Codex CLI
• Cursor
• MCP-compatible agents