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.
Last researched: 4 September 2026. Voiceflow’s public pricing page that day asked teams to request pricing. A current Scriptus operator still pays $60/month for Voiceflow.
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.
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.
Botpress, Vapi, Retell, and Synthflow sit in Voiceflow’s column. Different surfaces — developer canvas, voice API, enterprise phone — same job: a general construction kit. Each now has its own page: Botpress, Vapi, Retell, Synthflow. This page stays the Voiceflow comparison, including why Scriptus was rebuilt off this kit.
| Decision | Scriptus | Voiceflow (and similar kits) |
|---|---|---|
| Job the software is for | One knowledge product from your book or methodology | Design and run many kinds of chat and voice agents |
| Who operates it after launch | Scriptus maintains the platform; you own the offer and the IP | Your team owns the canvas, credits, seats, and integrations |
| Identity and history | Accounts, sessions, and durable conversation history are part of the product | A host platform that owns state typically gives you session-scoped chat unless you build the rest |
| Reader paywall | 3-question trial or free access; checkout on your Woo, Kajabi, Stripe, or Whop | You assemble billing, access control, and identity on top of the kit |
| Citations and refusal | Answers from your pages, or it says it does not know. We will demo a refusal. | You design grounding and guardrails. Possible, not the default offer. |
| Visual flow canvas | Not the product. You do not draw branches to go live. | Voiceflow’s strength. This is why CX teams buy it. |
| Omnichannel voice / WhatsApp / SMS | Site embed first. Optional in-chat voice. Not an IVR platform. | Voiceflow’s strength. Vapi, Retell, and Synthflow are stronger still if phone is the job. |
| What you pay | $5,000 setup + $500/month. No credit meter for the operator engagement. No revenue share. | A current Scriptus operator pays $60/month for Voiceflow as of 4 September 2026. The next step is commonly described as about $150/month. Public Voiceflow pricing that day was “request pricing,” plus seats and usage credits on older grids. Verify current totals in your Voiceflow bill. |
The $60 Voiceflow invoice is real. We still pay it. It is also not the cost of a book bot. Credits, extra editor seats, telephony, and everything you still have to build — identity, entitlements, durable history, citations, reader checkout, tenant isolation — sit on top of that invoice. Scriptus’s $5,000 + $500 is the engagement that includes those pieces. If you compare sticker to sticker, Voiceflow wins. If you compare “my methodology is a product my readers can pay for,” the kit’s line item is the start of the spend, not the end.
We will not claim Voiceflow is expensive. For a CX team shipping many agents, $60 or $150 can be cheap. For an author who does not want a second job as a conversation designer, it is the wrong meter.
Voiceflow price note: first-party operator invoice, $60/month, 4 September 2026. Next bump (~$150–$160) is the operator’s recollection of the published step, not a screenshot of Voiceflow’s current public grid.
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.
Purpose-built. The first Scriptus programming lived on Voiceflow. The rebuild happened because a host platform that owns identity and state cannot give you accounts, entitlements, or history that survive a refresh as a first-class product. That is a structural limit, not a missed toggle. Scriptus owns those layers so a book bot can be a product: cited answers, a trial wall or a free lead-gen bot, checkout on your rail, IP that stays in your tenant and is deleted if you leave.
The embed still looks like a snippet you drop on a site. The difference is what sits behind it.
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.