How do you route customer email automatically? A five-step build with Jev and Zapier

Jev is a model from a company called TypeSafe that does not write text at all. It reads something — an email, a ticket, a form entry — and returns a decision: yes or no, one option from a set you define, or a rating on a scale. Every answer comes back with a confidence score.

Those models generate text. Jev only decides. It will not draft your emails or write your essays, and it produces no output tokens at all, which is why it is cheap to run at volume. The tradeoff is that it only does the one job, so you use it where you want a decision rather than a document.

Because they match words, not meaning. An ad reading “URGENT: forty percent off office chairs” contains the word a filter is looking for. An email reading “our whole team is locked out, we have a client presentation in two hours” does not. The filter flags the ad and drops the emergency, which is exactly backwards.

Three. Yes or no, which is deterministic if-then logic. Pick one from a list of options you supply, such as billing, tech support, sales or other. Or a scale, such as how frustrated a customer sounds, from calm to furious. You set the questions and the allowed answers to fit your own workflow.

Be specific about what you actually care about. “Does this message describe a problem that needs action today to prevent a business interruption?” works. “Is this email important?” leaves far too much to interpretation, and you will get inconsistent answers because you asked an ambiguous question.

Write down the answers you expect before you build anything, using real messages your business received. Then feed those messages through and compare Jev's answers against your list. That is a real test. Reading the output and deciding it looks reasonable is not — it is an eyeball test, and it will let bad routing through.

You set a minimum confidence level in the Zapier integration, and anything below it comes back as unsure. From there you can stop the workflow or branch to a separate path where a person reviews the message, checks the customer's history and routes it properly. This is the step that keeps a low-confidence guess from landing in the wrong department.

Zapier has a native TypeSafe Jev integration. Search for it in the Zap editor, connect your account, and select “Ask Questions.” Then Paths branches the workflow on whatever Jev decided. There is no code and no custom connection to build between the apps.

At the price TypeSafe published as of recording, just over four cents per million input tokens, with no output-token charge at all because it never writes text. On an example of roughly 200 million input tokens a month — in the region of 100,000 emails — that works out to about $8.40. Check the current published price before you plan around it.

Worked through as an example: twenty people spending half an hour a day sorting messages, across twenty-two working days, is 220 hours a month. If the workflow removes three quarters of that, the team gets 165 hours back, which at $50 an hour in staff costs is $8,250 a month, or $99,000 a year in time. Payroll does not shrink — what changes is that those hours go to customers and leads instead of sorting.

No. The Jev integration is a single step in the Zap editor, and Paths handles the branching. That is the appeal of a deterministic workflow: once it is set up properly, it just runs.