Support
Help with installation, automations, classification results, and data questions. Start with the checks below or contact We The Folks.
Get help
Email [email protected] for installation, automation, billing and classification questions. Support is provided by email; no specific response time or round-the-clock coverage is promised.
Getting started
Use Add to Slack to authorize Jev for your own workspace. Your workspace may require an administrator to approve installation. Open Jev for Slack in Apps and go to Home.
A workspace administrator or owner authorizes external model processing in Data processing and activates the service through hosted Stripe Checkout. Each workspace’s one-time 14-day trial starts when checkout is completed, and a payment method is collected. Review renewal and cancellation terms before confirming.
Create an automation: choose channels and triggers, write a question with Slack variables, describe the answers, and attach actions. Saving enables it. Use Test with a message URL to inspect the result without executing actions.
When an automation does not run
Check that the rule is enabled, processing is authorized, and the subscription or trial is active. Confirm the message is in a selected channel accessible to Jev and matches the created/edited trigger.
Future-only rules compare the original message timestamp to the rule’s creation time. Editing an older message does not make it eligible. Bot messages and DMs are excluded.
Read Activity log for validation errors, pending recovery or uncertain delivery. Safe errors distinguish service, access and input problems. Do not repeatedly create equivalent rules to work around an outage.
Check a classification safely
Choose Test for a saved rule and paste a Slack message URL from a channel selected by that rule. The bot and current rule owner must have access, and processing consent plus an active subscription or trial are required. Inspect probabilities, chosen answers and rendered actions. Tests use the external model but do not post messages or reactions. Temporary modal results, including expanded action text, expire after 30 minutes.
Use synthetic or appropriate non-sensitive examples when refining a rule. A result can be incorrect even with a high probability. Refine the prompt and descriptions, then test again.
Understand activity results
Completed means the recorded actions finished. A dry test shows a preview only. Waiting indicates eligible work is pending retry after a transient problem. Needs review means delivery could not be confirmed and a post was not blindly repeated.
Use Retry now to request an attempt for pending work. It respects permissions, consent, rule state and the original 14-day expiry. Successful actions are not intentionally replayed during recovery.
Members, trial and billing
The monthly price is USD $5 per active human workspace member, with no workspace minimum. Active means a non-deactivated workspace account, not online presence or recent activity. Human guests count. Bots, Slackbot, app/workflow users, suspended accounts, pending invitations, profile-only accounts and external/non-member users do not.
Each workspace receives one 14-day trial, beginning on completion of hosted Stripe Checkout with a payment method. Trial and billing history survive reinstall. Member counts refresh daily; quantity changes have no proration and affect the next invoice.
Manage payment methods, invoices and cancellation through the billing portal from App Home. Cancel before uninstalling: uninstall removes application data but does not automatically cancel recurring Stripe billing. Contact support if the app has already been removed.
An active or trialing subscription within its access deadline is required for classifications, tests and new actions. Administration and consent withdrawal remain available when billing blocks processing.
What to include in a support request
Share the workspace identifier, rule name, approximate time, activity status and sanitized error. A short synthetic example and screenshot with private content removed can help.
Do not email passwords, Slack tokens, model API keys, authentication headers, full conversation exports or unredacted sensitive content. We do not need your Slack credentials.
Data and privacy questions
Email [email protected] for privacy requests or data-processing agreements. Consult the guides for the current data flow and controls.
Contact
Jev for Slack support: [email protected].
Provided by We The Folks sp. z o.o. Please send only the information needed to investigate.