LearningFlow LearningFlow vs Chatbase
Chatbase builds a customer-facing support agent and puts it where customers already are: a website widget, WhatsApp, Instagram, email, the phone. LearningFlow is not a better chatbot. A handbook bot here is an app with its own address and sign-in, reading a shared, spreadsheet-style database the organisation keeps.
Chatbots · Sources last read 13 September 2026
Choose Chatbase if
The job is a customer-facing support agent that answers enquiries end to end.
- An admissions bot on the public website that also answers on WhatsApp at 11pm
- Fee enquiries that become tickets, get routed to a person, and can be taken over mid-chat
- A monthly resolution rate and sentiment report for the head of student services
Choose LearningFlow if
The bot is one part of a job that ends in files, classes and records the organisation keeps.
- A staff handbook bot behind a sign-in, reading only the tables an administrator has named
- The same answer has to arrive as a .docx rubric or an .xlsx budget, not as a chat reply
- A Year 7 class needs accounts, a join code and an assignment, and the work stays after July
Where the two are built differently.
One app, one database.
One app means one door. Whatever the form is allowed to do, it is allowed to do everywhere. Stopping a parent from reading the other thirty replies is a rule you write inside the app, and have to keep writing correctly.
Several apps, one base, a contract each.
Each app holds its own contract: which tables, which columns, which rows, and which of read, insert, update and delete. The reminder never sees a medical note. Suspend one app and the other two keep running.
What each one does.
Written from each product's own documentation. Where something is true only on a higher tier, the row says so.
| Chatbase | LearningFlow | |
|---|---|---|
| Per-person permissions | Four fixed roles below Enterprise, with optional scoping to named agents. Custom roles are Enterprise only. | Seven capabilities are switched per member. A role grants the key, then the member opts in. |
| What you can hand out | Chat logs as JSON, PDF or CSV. An uploaded source comes back as extracted .txt, not the original file. | A real .pptx, .xlsx, .docx or .mp4. The spreadsheet arrives with working formulas. |
| What you pay for | A workspace subscription with message credits: $40 Hobby, $150 Standard, $500 Pro. Each includes one agent, and a second is $25 a month. | Credits rather than seats, from separate personal, organisation and enterprise wallets. No subscription is required. |
| Who owns the work | The workspace. Agents, sources and chat logs stay when a member is removed. | The organisation. It is stamped on the work when it is made and never moves. |
| Calling it from your own code | Two REST APIs with streaming, from the Standard plan at $150 a month. Version 2 rejects lower plans. | Every flow has an address. POST /task/:taskId with an x-api-key, streaming optional. |
| Where the bot can answer | One agent publishes to a widget, a help page, WhatsApp, Messenger, Instagram, Slack, email and the phone. | A published app has a web address and a sign-in, and can send through WhatsApp, Gmail or Resend. No Instagram, Messenger or phone. |
| Tickets and human takeover | A helpdesk with custom statuses, teams, auto-assignment, saved views, AI-drafted replies and takeover by a person. | None of it. No ticket queue, no resolution rate, no sentiment report. |
| Course records | Conversation logs and analytics. No xAPI or learning record store anywhere in the documentation. | xAPI package ingest, a self-hosted SQL record store, or statements sent to the organisation's own one. |
What comes with it here.
Files, not transcripts
Ask for a term budget and get an .xlsx whose formulas still calculate, built by Python on a real Linux box.
59 tools already built
Lesson plans, marking rubrics, quizzes, worksheets, report comments and text levelling, in a public gallery.
A narrated whiteboard video
One sentence becomes an MP4 in 16:9, 9:16 or 1:1, with subtitles burned in, supplied as a separate .srt file, or left off.
Students with their own logins
A student joins a class by code and receives assignments. They are users, not anonymous visitors.
Where Chatbase is the better choice
If the bot faces the public, buy Chatbase. A student services team that wants one assistant answering fee questions on the website at 11pm, on WhatsApp on a Saturday and on the phone will get there faster. Its model list covers Claude, GPT, Gemini, Llama and Mistral, and it publishes what each message costs, 1 to 6 credits. It also has everything that happens after the answer: ticket statuses, auto-assignment, human takeover, resolution rate and sentiment. We have none of that, so a college buying a support agent should stop reading here.
The whole stack against Chatbase.
The table above compares the two at the job they share. This one runs every capability past both, because what a school is choosing between is usually a tool that does one job and a workspace that does many. Hover any mark to see what it means, and a partial one to see exactly what is limited.
| LearningFlow | Chatbase | |
|---|---|---|
| Ask and read | ||
| Chat with AI | ||
| Research the web and write it up | ||
| Read text off an image or a scan | ||
| Agent browses the live web | ||
| Make | ||
| PowerPoint deck | ||
| Spreadsheet with working formulas | ||
| Word document | ||
| Image generation | ||
| Video generation | ||
| Narrated whiteboard video, corrected scene by scene | ||
| Voice-over | ||
| Song generation | ||
| Interactive web page | ||
| Edit what it made, online | ||
| Slide and design templates | ||
| Presenter on camera, from a photo you supply | ||
| Teach | ||
| Ready-made teacher tools | ||
| Build your own tool, no code | ||
| Lesson that branches on the answer | ||
| Hears them read aloud, checks pronunciation | ||
| Assign to a class with a join code | ||
| Assignments and submissions | ||
| Student accounts | ||
| LTI link from your LMS | ||
| Learning records to your own LRS | ||
| SCORM 1.2 package out | ||
| Build | ||
| Working app | ||
| Full working platform templates | ||
| Several apps over one database, rights each | ||
| App sends email or WhatsApp | ||
| App runs on a schedule | ||
| App accepts webhooks | ||
| Generate real-time apps | ||
| Generate AI-driven apps | ||
| Shared database | ||
| Revoke one app's access, not the others | ||
| Run | ||
| Run any tool from your own software | ||
| Choose the AI model, on every plan | ||
| Switch a feature off per group | ||
| Organisation keeps the work when staff leave | ||
| We do not do this | ||
| Transcribe a video or audio file | ||
| Custom domain for a published app | ||
Before they decide.
We already run Chatbase on our website. Do we have to replace it?
No, and most schools should not. Keep Chatbase on the public enquiry line and use LearningFlow for authoring, files and class work. A LearningFlow flow has an address, so a Chatbase custom action can call it when someone asks for something the bot cannot write.
If we do move, can we take the trained content with us?
Partly. Chatbase exports its training sources, but an uploaded file comes back as extracted .txt rather than the original PDF, and snippets come back as Markdown in a .zip. Re-upload the originals from your own drive, and export the chat logs as CSV to see what people actually ask.
What does Chatbase cost for three departments?
More than the headline. Hobby is $40 a month with 700 message credits, 2 seats and 1 agent. Standard is $150 with 4,000 credits and 3 seats, and Pro is $500 with 15,000 credits and 5 seats. Every one of those plans includes a single agent, so a second department is $25 a month more, and one message spends 1 to 6 credits depending on the model.
Can an administrator decide, per person, what each member can do?
In Chatbase, only on Enterprise. Below that you pick one of four roles, Owner, Member, Support Associate or Viewer, and can scope someone to named agents. Audit logs and single sign-on are Enterprise only too. In LearningFlow seven capabilities are switched per member, with no tier to reach first.
The teacher who built our bot leaves in July. What happens?
Both products keep the work. Chatbase agents, sources and chat logs belong to the workspace, so removing her account leaves all of it in place. In LearningFlow the organisation is stamped on the work when it is made and never moves, so removing her deletes her membership row, not her work.
Where this came from. Read on 13 September 2026. Chatbase changes its product and its prices without telling us, so check anything that decides a purchase.
- Chatbase — Pricing (plans, seats, agent caps, add-ons) ↗
- Chatbase Docs — Workspace settings (roles, custom roles, seats, API keys, audit logs) ↗
- Chatbase Docs — Manage (workspace ownership, Owner and Member) ↗
- Chatbase Docs — Build (model list and per-model message credit costs) ↗
- Chatbase Docs — Activity (conversation, lead and source export formats) ↗
Try it on your own work.
Teachers get credits every month, free. No card, no seat count.