Classification automations for Slack
Classify Slack messages with AI. Turn outcomes into actions.
Choose the channels. Describe what a message means in your team’s words. Jev triages each message against your outcomes and triggers the reactions, thread replies and channel posts you configured.
Two weeks free, the first without a payment method. USD 5 per active human member per month, excl. VAT. Model processing included.

Read the demo description
Maya Chen posts “My password reset link has expired.” in #help-desk, a channel watched by the rule First-line support triage. The rule asks “Can first-line support resolve this?” and passes the message through the {{message_text}} variable. Its outcomes are Yes, for routine how-to requests and password resets, and No, for issues that need specialist investigation. The example assigns Yes 96% and No 4%. For Yes, the configured actions add an eyes reaction and reply in the thread. The Activity log then lists the run as Completed with both actions, without storing the message text. Jev selects the outcome; the administrator defines the actions. Names, messages and scores are synthetic, and the animation makes no Slack or model requests.
Your context
One message. A clear question.
Use explicit Slack variables to choose what reaches the model. There is no hidden whole-workspace context.
Your decisions
Outcomes you can explain.
Define yes/no, single-choice or multiple-choice answers. Give each one the criteria your team works by.
Your workflow
Actions you can preview.
Jev picks from your configured outcomes. Your templates determine the exact message or reaction that follows.
From conversation to action
Give your team’s criteria a place to run.
Is this a routine support request? Which product area should see this feedback? Does a message contain more than one useful signal? Turn recurring decisions into rules, right where the conversation happens.
Choose the conversation
Select channels accessible to both Jev and the rule owner and run on new messages, edits, or when someone adds a chosen reaction.
Describe the distinction
Write a question and explain what each answer means. Insert message context from the variable picker.
Close the loop
Attach actions to answers, preview a real message, and review results in a 14-day activity log.
Inside Slack
Manage every rule from App Home.
Create classification automations, review the Activity log and control Data processing without leaving Slack. Watch the App Home tour below.

Read the demo description
An admin opens Data processing, selects Enable processing and confirms. In Classification automations, Create automation opens the three-step wizard. The rule Billing questions watches new messages in #help-desk and asks “Is this a billing question?” with the {{message_text}} variable. Yes means invoices, charges, refunds or payment methods; No means anything else. For Yes, the rule posts to #billing with {{message_link}}. Save and enable adds it to the list, and the admin enables Incident escalation. In the Activity log, Retry now completes a run that was waiting to retry, and Activity details shows the selected outcome, probabilities of 97.0% and 3.0%, and the delivery state, without message bodies. Rule names, runs and scores are synthetic, and the animation makes no Slack or model requests.
How it works
Three steps to a rule.
A preview before you rely on it.
Explore the native Slack modal workflow. These are illustrative examples, with synthetic messages and results.
Start at 25%. Name the automation, select channels and message triggers, choose future-only behavior, and write a question using explicit Slack variables.
Create automation
Apply only to messages created after this rule
{{message_text}}At 50%, choose Yes / No, single choice, or multiple choice. Describe every answer so Jev knows which criteria to apply. Multiple choice supports a probability threshold.
Create automation
Routine how-to questions, password resets and known issues covered by our support documentation.
Engineering changes, new features or incidents that need specialist investigation.
Each answer has its own description. For multiple choice, each outcome is selected independently against your threshold.
At 75%, attach reactions, thread replies, or channel messages to the answers you defined. Back keeps your draft. Save automation enables the rule.
Create automation
Routine questions covered by our support documentation.
Needs specialist investigation.
{{message_link}}Paste a Slack message URL to test a saved rule. Review model probabilities, chosen answers, and rendered actions. A dry test does not execute any Slack actions.
Test automation
Planned actions for Yes
- Add reaction
eyes · original message in #help-desk
- Reply in thread
Thanks for the question. Our support team will help you in this thread.
Illustrative interface, not an embedded Slack session. Use the tabs above to explore all four views.
Explicit Slack context
Use the message values your rule needs.
Insert variables into your prompt and outcome descriptions with the help picker. Values used only in action text stay out of the classification request. Unknown variables fail validation.
{{message_text}}{{message_link}}{{channel_name}}{{channel_id}}{{user_id}}{{message_ts}}{{thread_ts}}{{workspace_name}}Three ways to act on an outcome
Action text comes from your templates. Jev can respond to a conversation without changing what someone else wrote.
Add a reaction
Add a configured emoji reaction to the source message, such as eyes or white_check_mark.
Reply in a thread
Post your configured response in the message thread. Use Slack variables to include relevant context.
Post to a channel
Send a configured message to an accessible destination channel, with a link back to the original conversation.
The app does not edit other people’s messages. Slack access and channel membership still apply.
Processing under your control
Your workspace decides when processing starts.
Explicit authorization
A workspace administrator or owner authorizes external model processing in Data processing. Consent is checked before classification and each action. Withdrawing it cannot recall a request already sent.
Selected channels
Rules run in channels selected by an administrator and accessible to the bot. Direct messages and bot messages are excluded. Administration is checked on the server.
Configured model input
The prompt, outcome descriptions and referenced Slack values go to OpenRouter and TypeSafe. Input exceeding the complete 30,000-byte request budget fails with guidance, without silent truncation.
A fixed retention window
Activity, pending work and action receipts expire 14 days after the original receipt. Retries do not extend the deadline. Rules have separate retention and remain until deleted or uninstalled.
The app runs on Cloudflare Workers with D1 storage. AI processing takes place outside Slack. Review security controls and data processing details.
Activity and recovery
See the decision. Follow the result.
Activity log brings the message reference, rule, scores, selected outcomes and action results together. Model probabilities are estimates, not a guarantee that a decision is correct.
14 days of activity
Review automatic runs and dry tests without storing full message bodies, expanded action text, or credentials in activity.
Recovery after an outage
Captured, eligible events wait for service recovery and retry transient failures with backoff, within their original deadline.
Retry with current checks
Retry now requests an immediate attempt. Recovery rechecks consent, rule revision, enabled state and current message visibility.
Disabling, editing or deleting a rule invalidates its queued work. Recovery cannot reconstruct events never delivered to the app.
Built for workspace administrators.
native App Home
Three focused sections
Manage Classification automations, inspect Activity log, and control workspace Data processing inside Slack.
yes/no · single · multi
Your choice of answers
Choose a yes/no decision, one named outcome, or multiple independent outcomes with a probability threshold.
created · edited · reaction
Channels and triggers
Choose the channels and message events for each rule. Future-only rules use the original message timestamp.
message URL → preview
Test before taking action
Paste an accessible Slack message URL. See probabilities, selected outcomes, and rendered actions without posting or reacting.
explicit variables
Only the context you choose
Reference Slack values in prompts and outcome descriptions. Action-only variables are expanded inside the app.
14-day recovery
Pick up after an outage
Eligible pending classifications retry after transient failures. Review the queue or request Retry now in Activity log.
Simple workspace pricing
One workspace.
Your team’s automations.
$5USD per active human member
per month, excl. VAT
No workspace minimum. VAT added where applicable.
Two weeks free. Start with a free week in Slack App Home, no payment method needed, then add one for 7 more trial days without the free-week limits.
Jev processing is included.
- Publisher-funded model usage. No API key to supply.
- 1,800 Jev requests per member each month, pooled across the workspace.
- 3 automations per billed member.
- Yes/no, single-choice and multiple-choice automations.
- Reactions, thread replies and channel messages.
- Dry tests, a 14-day activity log and recovery controls.
- Workspace-isolated rules, activity and processing consent.
Only active human members count: guests, bots and deactivated accounts are free. The free week includes up to 500 requests and 5 automations, and nothing is charged unless you add a payment method. Prices exclude VAT. Cancel anytime, and canceling during the trial means no charge. Full details are in the App Terms.
Frequently asked
The questions admins ask first.
How do I get Jev for Slack?
Use Add to Slack to authorize Jev for your workspace, then activate the service in App Home. Your workspace may require administrator approval. Jev for Slack is independently published; no Slack Marketplace approval is claimed.
How much does it cost?
The price is USD 5 per active human workspace member per month, excluding VAT, with no workspace minimum, and the first two weeks are free. VAT is added where applicable. Guests, bots and deactivated accounts do not count. Subscriptions renew monthly until canceled in the billing portal, effective at the end of the billing period; canceling during the trial ends it before any charge. Uninstalling Jev also schedules cancellation at the end of the current period, or at the end of the trial. We cover model usage, so you do not need an AI account or API key. Each member adds 1,800 Jev requests per month to a shared workspace pool.
How does the two-week trial work?
Week one is a free week, with no payment method needed. A workspace admin or owner starts it with Start free week under Billing in Jev App Home. It includes up to 500 Jev requests and 5 automations for the whole week, and processing still needs Data processing consent. About a day and a half before it ends, Jev sends a reminder in Slack to the admin who started it, or to the installer if they are no longer an admin. If you do nothing, the free week ends, automations pause and nothing is charged. To keep going, an admin selects Add payment method in Billing. The free-week limits lift right away and a Stripe trial starts with the normal per-member limits. It ends 7 days after the later of opening Checkout and the end of the free week, so unused free days are kept. You can also skip the free week and go straight to a 7-day trial. About a day and a half before the trial ends, Jev sends a heads-up before the first payment, which is taken when the trial ends. Each workspace gets one free week, offered only before any trial or subscription, and one trial; after that, Checkout subscribes without a trial.
Is Jev for Slack the same as TypeSafe's Jev model?
No. Jev for Slack is an independent Slack app published by We The Folks. It sends the values your rules reference to TypeSafe's Jev classification model through OpenRouter and turns the selected outcomes into Slack actions. The model cost is included in the subscription.
Can the AI make mistakes?
Yes. Classifications are probabilistic and can be wrong. Write clear outcome criteria, use dry tests with probabilities before enabling a rule, choose a confidence level for multiple-choice rules, and keep people in the loop for decisions that matter. Activity shows the scores behind every run.
Who can buy and manage the subscription?
Only Slack workspace admins and owners. They start the free week, add a payment method and open the billing portal from Billing in Jev App Home to update the card, download invoices or cancel. Other members do not see billing controls.
What happens when the request limit is reached?
Each billed member adds 1,800 Jev requests per month to a pool shared by the workspace. Each billed member also adds 3 automations. When the pool is used up, messages received until the next month are not classified and no actions run for them; they are not processed later. The pool resets on the first day of each month (UTC). During the free week, the limits are 500 requests and 5 automations for the whole week instead; adding a payment method lifts them right away.
What can a rule do?
Each selected outcome can add a reaction, reply in the source thread, or post a configured message to a channel. Message text comes from your templates. Jev does not edit another person’s message or invent actions.
Who can manage automations?
Workspace administrators and owners manage rules, dry tests, activity, and processing consent from Jev’s App Home. The app checks administrative access on the server.
Does Jev read every conversation?
No. Rules select specific channels accessible to the bot. Direct messages and bot messages are not observed. Model requests use the prompt, outcome descriptions, and explicitly referenced Slack variables; there is no implicit whole-workspace context.
What happens when I save a rule?
Saving enables it for the selected future message events. It does not backfill old messages. The future-only setting compares the original message timestamp with the rule’s creation time, so editing an older message does not make it new.
What does a test do?
A test sends the configured input from an accessible message to the model and shows probabilities, chosen outcomes, and fully rendered actions. It does not post messages or add reactions. Workspace processing consent, an active free week, trial or subscription, and access to a message in a channel selected by the rule are required.
What happens during an outage?
Captured, eligible events can wait for recovery for up to 14 days from their original receipt. Transient failures retry with backoff. Retry now requests another attempt; it does not bypass permissions, processing consent, or provider availability.
Will edited messages create duplicate replies?
Within their 14-day retention window, persisted event and action receipts prevent repeated events and message edits from intentionally stacking the same completed action. This protection is not permanent. If a post may have succeeded but cannot be confirmed, it requires review instead of a blind retry.
What leaves Slack?
The prompt, outcome criteria and their referenced Slack values are sent through OpenRouter to TypeSafe’s Jev model. The app is hosted on Cloudflare Workers with D1 storage. External providers have their own processing and retention terms.
What is retained?
Activity, pending recovery and action receipts have a fixed 14-day deadline from the original event receipt. Retries do not extend it. Activity and recovery logs exclude full message bodies and expanded action text. Temporary dry-test modal results can contain rendered action text, including message content, for up to 30 minutes. Rules remain until deleted or uninstalled; billing history is separate.
Can I use my own outcome criteria?
Yes. Write a description for every outcome, including both Yes and No. The three-step wizard separates the question, answer definitions, and actions. A variable help picker explains each supported Slack token.
Jev for Slack
A clearer next step for every conversation.
Install Jev in your workspace, start your free week in App Home with no payment method needed, and build your first classification rule. Your workspace keeps its own rules, activity and processing consent.
USD 5 per active human member per month, excl. VAT, with no workspace minimum after the trial. Jev for Slack is independently published. Read the App Terms and Privacy Policy.