Coming from Aviso Agent Studio?
Aviso Agent Studio builds revenue agents from CRM, email and call context, with natural-language graph generation. Whenever offers custom workflow procedures for other team jobs too, using authorised integrations subject to API, plan and network limits. Review the summary and sample results; model replies can vary and use runtime AI. Building has weekly limits; the file is yours.
What you get on Whenever
Built for the job you describe
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.
A proposal, or a price on the page.
Aviso offers a tailored proposal; the captured pricing page does not establish a per-user rate. Whenever publishes plan pricing, with separate run and runtime AI allowances and weekly AI-building limits.
Aviso Agent Studio
Tailored proposal
Confirm scope and billing with Aviso
The captured pricing page offers a tailored proposal for Aviso’s revenue platform.
Aviso invites a tailored proposal. The captured pricing page does not establish a per-user rate or how model usage is included. Ask for those terms and compare the same workload with Whenever run and runtime 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
Aviso Agent Studio
You configure trigger nodes and conditional branches. Aviso describes agents that reason over revenue context, switch paths through MCP when a tool fails, and use feedback to optimise their paths; this is a vendor description, not measured reliability.
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
Aviso Agent Studio
Aviso offers a tailored proposal; the captured page is not sufficient to infer a per-user rate or unit allowance.
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
Aviso Agent Studio
Describe a revenue outcome and refine the generated graph by adjusting trigger nodes and conditional branches in a drag-and-drop interface. Aviso lists 200+ native connections and ready-to-use agents for GTM roles.
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
Aviso Agent Studio
Confirm which Aviso Agent Studio 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
Aviso Agent Studio
Aviso’s Agent Inbox tracks live performance and mission success rates. Its sandbox workspace shows trust scores and impact metrics before production.
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
Aviso Agent Studio
Ask Aviso how model and tool usage are included or charged in your proposal. No model-cost inclusion is inferred here.
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 agent works
Aviso Agent Studio
Aviso describes connected CRM, email, calls and other revenue context. Those data sources do not by themselves establish which messaging surfaces execute an agent.
Whenever
Slack and Telegram, answering the moment a message arrives, on a schedule, or on a webhook from any tool. It works from what its integrations can read, not from a revenue model built for you.
Building from your coding agent
Aviso Agent Studio
Aviso documents building and refining agents in Agent Studio. The captured pages do not address authoring from a coding agent; that omission is not proof it is unavailable.
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 Aviso
Aviso Agent Studio
Keep it for forecasting, pipeline inspection and conversation intelligence, and for agents grounded in your pipeline and deal context in Aviso.
Whenever
Use Whenever for agents and bots you want as workflow files on a published plan, for revenue work or any other team.
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
Sales 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 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 workflowBring every lead source into one CRM recordCollects new leads from Typeform and a Google Sheets tab and creates or updates a single HubSpot contact with its original source.
Build this workflowAnnounce closed-won deals in SlackCelebrates each won deal in Slack with the numbers and a short recap of how it was won.Build this workflowCapture a form lead and start the follow-upEnriches each form lead, drafts the right follow-up email in Gmail, and opens a task for the rep who owns the contact.
Build this workflowSend a weekly pipeline summary to the teamPulls open HubSpot deals every Monday, groups them by stage and owner with totals, and shares the write-up in Slack.
Build this workflowStart with one job a rep does by hand.
Describe the job. Whenever writes it as code you can read, at a price that is on the page.
Pick a repeatable request
“Log this call to the deal”, “what did this account buy last year”, “chase the unsigned contract”.
Describe it and connect the tools
Say where the request comes from and which apps the bot may read and change. Whenever writes it; review the summary and sample outputs.
Test it on real deals
Run it against a handful of real requests before the team relies on it.