Rules first, a model second

Every reply that comes into Cold Leads is sorted by intent: positive, neutral, negative, unsubscribe or auto-reply.
The cheap part runs first. Plain rules, in five languages, settle the obvious cases on their own: out-of-office replies and "please remove me".
Everything else goes to a small language model, with a timeout. If the model is slow or unavailable, the rules make the call instead.
An unsubscribe reply opts the contact out automatically. A human reply moves a cold contact to "lead".
Rules for what's certain, a model for what's ambiguous. That split keeps it fast, cheap and predictable.
Where do you draw the line between rules and AI in your product?
Build on Cold Leads
REST API, the Node SDK @coldleads/sdk and the MCP server @coldleads/mcp-server. Plans from $19 a month; new accounts get 5 days free (card required).