Coming from ClearFeed?
ClearFeed provides helpdesk workflows in Slack and other supported intake channels. Its AI agents answer from knowledge and can take actions in connected tools. Whenever is an alternative for a custom procedure you describe and supervise through summaries, samples and run history. Optional model replies can vary and use runtime AI; building has weekly limits. The workflow file is yours.
What you get on Whenever
Test each integration before you publish
Choose integrations from Whenever’s 1,400+ catalogue or provide a documented API. Availability and actions depend on the service’s API, permissions, plan and reachability from the hosted runtime; a catalogue listing is not a guarantee that every operation or sign-in method is supported. Test the specific lookup or update before publishing.
Map, summary, run history and code
Review the workflow map, summary and run history. Run and step logs are retained for 7 days on Hobby and 30 days on Pro. The code can be downloaded and handed to a developer; that is not a guarantee that a reported action succeeded in an external service.
What one Whenever plan covers
One plan can run bots and other workflows within its live-workflow, run and AI-spend limits. At a limit, contact Whenever about a larger plan; external services may bill separately. Hobby permits one active workflow.
A concrete decision
Illustrative scenarios, not customer results or recorded runs.
Greg: answer an order question safely
Illustrative decision, not a recorded customer run: Greg wants a team-chat bot to look up an order ID and report shipping status, without issuing refunds. He specifies the allowed lookup and tests found, missing and ambiguous orders with authorised accounts. He checks the returned provider status and run history, not a model’s unsupported “done” message or source code. A failed lookup should be reported as unconfirmed, not as a shipped order. Choose a custom procedure for that cross-tool rule; keep a specialised helpdesk if its ready-made experience fits. Model-written replies can vary and use runtime AI; this example is not proof of a delivered customer action.
Jaunius: choose the trigger before pricing it
Illustrative calculation, not observed traffic: a 15-minute schedule requires Pro and runs 96 times a day, or 2,880 times in a 30-day month, even when nothing arrives. A supported inbound trigger counts the executions it starts: for example, WhatsApp Business messages or Discord slash commands, buttons and modals. Scheduled workflows can also call channel APIs. Jaunius chooses the trigger and tests duplicate events and tool permissions. Compare the subscription, run and AI allowances and external charges; 2,880 checks are not automatically 2,880 messages or a saving.
Helpdesk agents or usage, or workflow runs.
ClearFeed Helpdesk offers agent-based or usage-based pricing, including channels and tickets or requests; AI agents use credits. Whenever subscriptions include run and runtime-AI allowances.
ClearFeed
Helpdesk agents or usage, plus AI credits
Agents, channel/ticket or request slabs, and AI usage
Separate editions for the helpdesk, AI agents and integrations, each with its own meter. Annual billing is discounted.
ClearFeed Helpdesk offers agent-based or usage-based pricing. Internal usage counts Slack channels and tickets in slabs and bills on the higher of the two; External uses channels or requests. Integrations Edition uses tickets; AI agents use monthly credits. Compare the applicable model with Whenever run and AI allowances.
A run is one execution of one workflow, start to finish. AI building and editing are free within weekly usage limits; runs are metered separately.
A closer look
What changes when you describe the job in plain language and code runs it: to build, to run, and to keep.
Repeatable execution logic
ClearFeed
Configured ticketing rules and model-generated answers are different parts of the product. ClearFeed documents prompts, tools and knowledge for AI agents; verify approval and posting behavior for your chosen setup.
Whenever
The published code sets the bot’s allowed tools and execution limits. Review its rules and sample results; source-code inspection is optional. A model can choose wording and offered tools, so identical messages need not produce identical replies. Restrict permissions as well as the offered tools.
Runs per dollar
ClearFeed
Helpdesk is priced per agent or by usage: Internal counts channel and ticket slabs and bills on the higher of the two; External uses channels or requests. Integrations Edition uses tickets, and AI agents have monthly credits.
Whenever
Pro includes 10,000 runs per month; see current US dollar subscription pricing. Each workflow execution counts once within its call budget. Scheduled API checks count even when idle; supported inbound events count when they start a workflow. Runtime model usage draws on the plan’s included AI spend in runs. If you reach a run or AI-spend limit, contact Whenever about a larger plan; no self-serve overage price is published. AI building has separate weekly limits.
What you can express
ClearFeed
Agents are configured with a prompt, knowledge sources and tool actions, and attached to channels. 20+ enterprise integrations connect, including Zendesk, Jira, Salesforce, HubSpot and Okta.
Whenever
Describe the bot’s allowed actions and handoff rules in plain language. Its tools can use 1,400+ integrations or a documented API, subject to permissions, provider-plan support and network reachability from Whenever’s hosted runtime. Review and test the results before publishing.
Export and portability
ClearFeed
Confirm which ClearFeed configuration, data and credentials can be exported and what runtime is needed. This comparison does not treat an undocumented export as proof that none exists.
Whenever
The bot is a TypeScript file: its loop, its tools and its rules. Read it, export it, hand it to a developer. Moving it to another runtime can mean adapting managed connections and triggers.
Debugging a failed run
ClearFeed
Helpdesk Professional lists SLA configuration and reports, audit logs and AI deflection reports with its AI Pack. Integrations Edition does not include service metrics or SLAs.
Whenever
Use the workflow map, summary and run history to inspect what happened, then ask for changes in chat and test representative messages. Run and step logs are retained for 7 days on Hobby and 30 days on Pro. Code is available when you or a developer want to inspect it.
Where the AI cost lands
ClearFeed
AI agents use credits; the documented invocation estimates vary with complexity and some invocations are free. Enterprise lists bring-your-own-model support. Do not assume one answer equals one credit.
Whenever
Optional model-written replies use the plan’s included AI spend in runs. At a run or AI-spend limit, contact Whenever about a larger plan; no self-serve overage price is published. Non-AI API operations do not require model inference, but external services may bill separately.
Where the bot talks
ClearFeed
Helpdesk Starter lists intake from Slack channels, email and web chat; Professional adds Teams, Discord, Telegram channels and a customer portal. ClearFeed’s AI-agent pages describe answering and acting in Slack.
Whenever
Supported inbound events include Slack app events, Telegram bot updates, WhatsApp Business messages through a Meta app, and Discord slash commands, buttons and modal submissions. A scheduled workflow can also call the channel API; each scheduled run counts even when it finds nothing. This does not promise push delivery of ordinary Discord channel messages. Whenever does not host a website chat widget.
Building from your coding agent
ClearFeed
ClearFeed lists an MCP server and Claude plugin on its helpdesk plans. Coding-agent access is not unique to Whenever.
Whenever
Connect Claude Code, Cursor or Codex to the Whenever MCP server. Your coding agent can write and test the workflow and save it as a draft; complete Setup and publish after reviewing the result.
When to keep ClearFeed
ClearFeed
Consider ClearFeed for helpdesk tickets, SLAs and support workflows. Its pricing lists HIPAA Plan and BAA on Enterprise; eligibility and contractual scope need review, not a blanket compliance assumption.
Whenever
Consider Whenever for a custom cross-tool procedure whose rules you want to supervise directly. Check ClearFeed’s integrations and MCP options before assuming the action requires another tool. Whenever is not a ticketing system.
Sources and scope
Official sources captured on the date shown below. These describe published features and billing rules, not independent performance tests. Check the linked documentation for current modes, plans and limits. No competitor dollar price is asserted.
Checked
Slack helpdesk jobs to start from
Starter briefs for related jobs, not recorded runs. Connect authorised accounts, confirm trigger and plan requirements, then review and test the workflow before publishing.
Build this workflowRun an async standup in SlackAsks your team the three standup questions every weekday morning, posts one summary with who has not replied, and logs replies to a sheet.
Build this workflowGet a prep brief before every customer callSends you a written brief each morning covering the customers you are meeting that day.
Build this workflowSpot expansion signals in support ticketsSends the account owner a written read on every support ticket that mentions buying or growth.Build this workflowFlag renewal risk on upcoming Salesforce accountsReviews Salesforce accounts renewing in the next 90 days with their open tickets and posts a written risk note to Slack.
Build this workflowSend a pre-call brief before every customer callAssembles account details, deal history, and open tickets into one brief and sends it to the call owner before the meeting.Build this workflowStart with one Slack request.
Describe the request and permitted actions. Whenever writes a workflow using supported, authorised connections.
Pick the request you answer by hand
Access requests, order lookups, “what’s the status of”: the ones someone answers by opening another tool.
Describe what the bot should do
Say which channel it watches, which tools it may use and when to call a person. Whenever writes it; review the summary and sample outputs.
Try it in a test channel
Send it real requests, the unclear ones included, then publish it on the channel your team uses.