Scriptus / Compare / Voiceflow
Scriptus vs Voiceflow
Voiceflow is a capable conversation-design platform. Scriptus was first programmed on it, then rebuilt — not because Voiceflow is a bad tool, but because a general agent kit does not own the job Scriptus is for. If you need a visual flow canvas, omnichannel telephony, and a construction environment for many different agents, Voiceflow is the better product. If you have a book or methodology and want it working as a branded, cited, monetized embed, you do not need that kit. You need the product.
Build any agent, or ship one knowledge product
Last researched: 23 September 2026
You are a CX, product, or agency team designing agents across web, WhatsApp, SMS, and phone. You want environments, evaluations, model choice, and a visual builder. You will operate the agent after you draw it. That is what Voiceflow sells, in their words: the complete platform for enterprise CX teams.
You want one purpose-built knowledge product: your material, your brand, citations, entitlements, durable history, and reader billing — without staffing a conversation-design practice. You would rather pay for a finished engagement than operate a canvas.
| Dimension | Scriptus | Voiceflow | Choose on this row if |
|---|---|---|---|
| Where it lives | |||
| Where the reader meets it | Operator’s website via Scriptus embed — floating widget, embedded panel, full page, or full application SourceEmbedded on the operator’s site. The operator pays Scriptus. Their readers are the users. | Chat widget on website: floating widget, popover, or embedded; voice and chat channels on marketing pricing SourceThe widget supports text and voice input, and can be displayed as a floating widget, popover, or embedded directly into your page. … Deploy across every channel: voice and chat https://docs.voiceflow.com/documentation/deploy/widget/embedding-the-chat-widget | You want web, WhatsApp, SMS, and voice on one agent — or a site embed first with optional in-chat voice, not an IVR platform. |
| Technical prerequisites | A website that can load the Scriptus embed snippet; operator checkout on Woo, Kajabi, Stripe, or Whop when monetizing SourceCheckout stays on WooCommerce, Kajabi, Stripe, or Whop — not on getscriptus.com. | Publish a version of your agent before adding the widget; copy snippet into website codebase SourceBefore adding the widget, you'll need to publish a version of your agent. Once published, open the Widget tab in the sidebar, then copy the code snippet into your website's codebase. https://docs.voiceflow.com/documentation/deploy/widget/embedding-the-chat-widget | You will operate the agent after you draw it — or you would rather pay for a finished engagement than staff a conversation-design practice. |
| What the reader gets | |||
| Citations | When sources are on, a panel shows work title, chapter, page, and a short passage (up to three) SourceWhen sources are on, the chat shows work title, chapter, page, and a short passage, or the bot says it does not know. | Not published | You will design grounding and guardrails in a flow canvas — or chapter-and-page citations beside every answer, or a refusal, as the product. |
| Access control / entitlements | Anonymous trial, member grants after webhook/SSO, magic-link for members | Team roles and permissions (Business marketing list); Environments for production pipelines SourceCollaborate with team roles and permissions … Environments enable real production pipelines, from development to staging, and then to final production. | You will assemble billing, access control, and identity on top of the kit — or accounts, sessions, durable history, and reader entitlements built in. |
| Refusal when sources do not cover it | Designed to say it does not know when the corpus does not cover the question | Not published | You will wire guardrails in the flow canvas — or a source panel that prints work, chapter, and page, or the bot says it does not know. |
| Published model | Not published | Access to all major model providers / Avoid model lock-in; choose biggest LLM providers or bring your own SourceAccess to all major model providers … Avoid model lock-in. Choose from the biggest LLM providers, or bring your own model. | You want a visual flow canvas as the product — or a branded embed where visitors never draw branches to go live. |
| Money | |||
| What you pay the vendor | $5,000 setup + $500/month. No revenue share. No usage meter. SourceSetup $5,000. Then $500/month. No revenue share. No usage meter. | Live https://www.voiceflow.com/pricing (2026-09-23): For Agencies & Partners — Free trial, no credit card required; Transparent, usage-based billing. For Businesses — Book a demo / Request pricing. Dollar matrix not printed on live /pricing. First-party story Last updated April 10, 2025 (https://www.voiceflow.com/stories/introducing-voiceflow-credits): Starter Free 100/mo credits; Pro $60/mo $648/yr (10k/mo); $90/mo $972/yr; $120/mo $1,296/yr; Teams $150/mo $1,620/yr; $250/mo $2,700/yr; $500/mo $5,400/yr; Teams renamed to Business as of April 29th, 2025. Docs: view current pricing inside Plans and Billing (login). Additional editor seats $50 per month (credits story). SourceBook a demo Request pricing … Free trial, no credit card required … Transparent, usage-based billing … Starter Free 100/mo … Pro $60/mo $648/yr 10k/mo 120k/yr … $90/mo $972/yr … $120/mo $1,296/yr … Teams* $150/mo $1,620/yr … $250/mo $2,700/yr … $500/mo $5,400/yr … Additional editor seats are now just $50 per month … You can view current pricing for plans, add-ons, and credit bundles inside Voiceflow by opening Plans and Billing tab from your Voiceflow dashboard. | You want a builder subscription starting around $60/month plus credits and seats — or $5,000 setup + $500/month for a deployed knowledge product with no credit meter. |
| Cost to run several | $5,000 setup + $500/month platform fee. Year one = $11,000. The platform fee does not grow with subscriber count. Operator LLM/voice keys (when BYO) bill the operator separately at provider rates — not a Scriptus per-reader meter. SourceSetup $5,000. Then $500/month. No revenue share. No usage meter. | Credits shared across workspaces; editor seats $50/mo additional (story); concurrent calls add-on SourceCredits are shared across all workspaces in your organization. … Additional editor seats are now just $50 per month https://docs.voiceflow.com/documentation/account-management/billing | You want environments and evaluations for many agents across channels — or one purpose-built knowledge product from your book or methodology. |
| Checkout rail | WooCommerce, Kajabi, Stripe, or Whop — cards never touch Scriptus SourceCheckout stays on WooCommerce, Kajabi, Stripe, or Whop — not on getscriptus.com. | Not published | You will build reader billing on top of Voiceflow — or a 3-question trial or free access with checkout on your Woo, Kajabi, Stripe, or Whop. |
| Message / usage limits | No per-message meter on the operator engagement; trial caps are per agent when configured | Credit-based usage for messages, LLM responses, TTS, phone calls; allotments by plan SourceVoiceflow Credits provide a unified way to measure usage across all platform capabilities: Automated phone calls, LLM (Language Model) responses, Text-to-Speech minutes, Messages https://www.voiceflow.com/stories/introducing-voiceflow-credits | You accept usage credits and seats on top of the builder invoice — or a flat $500/month operator retainer with no usage meter on the engagement. |
| Who keeps reader money | No Scriptus cut of reader subscriptions | Not published | You pay for the kit and keep what you build on reader revenue — or flat operator pricing with no Scriptus share of reader subscriptions. |
| Operations | |||
| Who builds and operates it | Scriptus builds and maintains; operator owns the offer | Teams build agents; Implementation support: self-serve or fully managed (Business marketing) | You want your team to own the canvas, credits, seats, and integrations — or you want Scriptus to maintain the platform while you own the offer and the IP. |
Visual design. Collaboration for designers and engineers. Environments. Evaluations. Model choice. Web, app, WhatsApp, SMS, and voice on one agent. Agency and enterprise CX workflows. If that is your job, stay. Scriptus will not grow a flow canvas to chase that buyer.
Three meters — do not collapse them.
Sticker: The $60 Voiceflow invoice is real. We still pay it. On sticker, Voiceflow wins.
Cost to operate a monetized book bot: that $60 is not the bill. Credits, extra editor seats ($50/mo published for additional editors), telephony, and everything you still have to build — identity, entitlements, durable history, citations, reader checkout, tenant isolation — sit on top. They have not published a clean per-reader AI dollar we can turn into a 30- or 50-subscriber crossover. We will not invent one. Scriptus's $5,000 + $500 is the engagement that includes those product pieces; the platform fee does not grow with subscriber count.
We will not claim Voiceflow is expensive for a CX team shipping many agents. For an author who does not want a second job as a conversation designer, sticker is the wrong meter.
| Side | Published price |
|---|---|
| Scriptus | $5,000 setup + $500/month. No revenue share. No usage meter. SourceSetup $5,000. Then $500/month. No revenue share. No usage meter. |
| Voiceflow | Live https://www.voiceflow.com/pricing (2026-09-23): For Agencies & Partners — Free trial, no credit card required; Transparent, usage-based billing. For Businesses — Book a demo / Request pricing. Dollar matrix not printed on live /pricing. First-party story Last updated April 10, 2025 (https://www.voiceflow.com/stories/introducing-voiceflow-credits): Starter Free 100/mo credits; Pro $60/mo $648/yr (10k/mo); $90/mo $972/yr; $120/mo $1,296/yr; Teams $150/mo $1,620/yr; $250/mo $2,700/yr; $500/mo $5,400/yr; Teams renamed to Business as of April 29th, 2025. Docs: view current pricing inside Plans and Billing (login). Additional editor seats $50 per month (credits story). SourceBook a demo Request pricing … Free trial, no credit card required … Transparent, usage-based billing … Starter Free 100/mo … Pro $60/mo $648/yr 10k/mo 120k/yr … $90/mo $972/yr … $120/mo $1,296/yr … Teams* $150/mo $1,620/yr … $250/mo $2,700/yr … $500/mo $5,400/yr … Additional editor seats are now just $50 per month … You can view current pricing for plans, add-ons, and credit bundles inside Voiceflow by opening Plans and Billing tab from your Voiceflow dashboard. |
There is no one-click import of a Voiceflow canvas. We take your source material — book, course, frameworks — and build the Scriptus tenant from that, not from your flow chart. Export any transcripts you still need before you cancel a Voiceflow workspace. Parallel run is possible: leave the old widget up until the new embed is signed off. We do not keep Voiceflow as a runtime after launch.
Choose Voiceflow if you are building agents as a practice. Choose Scriptus if you already have the knowledge and want the product without the practice. Choose Botpress, Vapi, or Retell if you specifically want a developer kit or a phone runtime — then you are still in Voiceflow's family, not ours. If you only need anonymous Q&A over a PDF, use NotebookLM.
No. Scriptus was prototyped on Voiceflow and then rebuilt so identity, history, entitlements, citations, and reader commerce are the product. The snippet on your site is similar on purpose. The platform behind it is not Voiceflow.
Because you are buying different things. $60 is a builder subscription. $500 is the retainer on a deployed knowledge product, after a $5,000 build, with no share of reader revenue. If you love operating the canvas, keep Voiceflow. If the canvas is the work you wanted to stop doing, the invoices are not substitutes.
Often, yes — with enough flow work, integrations, and a billing stack you own. That is the point. Scriptus is for people who do not want that project.
Same family: general kits. Read Botpress, Vapi, Retell, or Synthflow if that is the logo you already pay. The fit test is identical. If the job is "construct an agent platform," they win. If the job is "my book should work on my site," they are the long way around.
Not as the runtime. Launch architecture is the Scriptus embed. Voiceflow is the beta we are leaving, not a dependency we sell.