Inbound founder email intent
Sort inbound email to a founder into sales, partnership, hiring, press, customer support, or spam so the right teammate sees it and cold pitches do not sit next to real customer issues.
F@fLimits to keep in mind
This routes attention only. It does not send replies or share anyone's contact details.
Problem
Founder inboxes mix customer outages, partnership pitches, recruiter mail, podcast asks and spam. Urgent customer problems wait behind a sales PDF, and genuine partnership notes get archived as cold outreach.
Goal
Label each inbound message so it can go to sales, partnerships, hiring, press, support, or the spam pile, and hold for a human when the intent is mixed or thin.
Input / state
The inbound email, including subject and body.
- subject
- The email subject line.
- body
- The email body, with quoted history removed if possible.
Decision question
founder_email_intentWhy did this person email the founder? Use sales_inquiry to buy, compare plans, or book a demo. Use partnership_or_integration for integrations, reseller, or co-marketing. Use hiring_or_recruiting for applications, recruiter pitches, or intros. Use press_or_podcast for interviews or speaking. Use customer_support when an existing user reports a bug, billing issue, or needs help. Use spam_or_irrelevant for unrelated marketing or mail not about this company. Use unclear when two intents are mixed or the ask is too vague to route.
Options
sales_inquiryThey want to buy, compare plans, or book a product demo.partnership_or_integrationThey propose an integration, reseller deal, or co-marketing partnership.hiring_or_recruitingA job application, recruiter pitch, or candidate introduction.press_or_podcastAn interview, podcast, speaking, or other media request.customer_supportAn existing customer needs help, reports a bug, or has a billing issue.spam_or_irrelevantUnrelated marketing, a blast, or mail that is not about this company.unclearThe ask is missing, contradictory, or mixes two intents evenly.
Allowed outcomes
Decided in your code from the answer and its confidence. Thresholds are yours to set and test.
- Founder reviews itConfidence is below your threshold: probability is spread across options.
- Send to salesChoice is sales_inquiry and confidence meets your threshold.
- Send to partnershipsChoice is partnership_or_integration and confidence meets your threshold.
- Send to hiringChoice is hiring_or_recruiting and confidence meets your threshold.
- Send to pressChoice is press_or_podcast and confidence meets your threshold.
- Send to supportChoice is customer_support and confidence meets your threshold.
- Treat as spamChoice is spam_or_irrelevant and confidence meets your threshold.
- Ask what they needChoice is unclear and confidence meets your threshold.
Example scenarios
Predefined demonstrations. No model is called; the outcome shown is an illustrative judgment.
Example state
{
"body": "We are evaluating vendors for our Series B finance team and would like a 30-minute demo of your API and Team plan pricing next week.",
"subject": "Demo of your analytics API"
}Outcome
IllustrativeChoice is sales_inquiry and confidence meets your threshold.
Why
They want a demo and pricing to buy.
Using it well
- If an existing customer leads with an outage or billing break, use customer_support even if they also mention upgrading.
- A vendor selling SEO or guest posts to the company is spam_or_irrelevant, not a partnership.
- Do not mark mail as spam only because it is cold; a specific relevant partnership note is partnership_or_integration.
Request definition
POST https://api.typesafe.ai/v1/systemone{
"model": "jev-latest",
"state": {
"subject": "<subject>",
"body": "<body>"
},
"questions": {
"founder_email_intent": {
"type": "choice",
"instructions": "Why did this person email the founder? Use sales_inquiry to buy, compare plans, or book a demo. Use partnership_or_integration for integrations, reseller, or co-marketing. Use hiring_or_recruiting for applications, recruiter pitches, or intros. Use press_or_podcast for interviews or speaking. Use customer_support when an existing user reports a bug, billing issue, or needs help. Use spam_or_irrelevant for unrelated marketing or mail not about this company. Use unclear when two intents are mixed or the ask is too vague to route.",
"criteria": {
"sales_inquiry": "They want to buy, compare plans, or book a product demo.",
"partnership_or_integration": "They propose an integration, reseller deal, or co-marketing partnership.",
"hiring_or_recruiting": "A job application, recruiter pitch, or candidate introduction.",
"press_or_podcast": "An interview, podcast, speaking, or other media request.",
"customer_support": "An existing customer needs help, reports a bug, or has a billing issue.",
"spam_or_irrelevant": "Unrelated marketing, a blast, or mail that is not about this company.",
"unclear": "The ask is missing, contradictory, or mixes two intents evenly."
}
}
}
}Request shape from the System One API reference; a Kev server accepts the same body. Replace the placeholder state with your data. Requests need your own API key or server.
Version History
Initial version