Scritch vs. support chatbots
Last updated 19 September 2026
A support chatbot and a recovery agent do different jobs. A support chatbot answers questions from your knowledge base: billing policies, how-to guides, password resets. Scritch recovers blocked users: it reads the specific failure that stopped them, fixes the issue with their approval, and verifies the change worked. A chatbot tells people what your docs say. Scritch gets them unstuck when something your app refused to do.
| Support chatbot | Scritch | |
|---|---|---|
| Primary job | Answer questions from your knowledge base | Recover blocked users from technical failures |
| When it helps | User has a question about how something works | User got blocked by a form rejection or server refusal |
| What it reads | Your help docs and FAQs | The real server response, form rules, your monitoring, auth state |
| Does it change anything | No, it answers and routes | Yes, with user approval, and it verifies the fix |
| Outcome | An answer or a handed-off ticket | A verified recovery or a complete escalation |
| Pricing shape (as of Sep 2026) | Per conversation / seats / monthly base | Per recovery that actually worked, capped |
Where support chatbots win
- Answering frequently asked questions about how your product works.
- Routing tickets to the right team based on the user's description.
- Handling password resets, billing questions, and other self-service tasks.
- Teams with a rich knowledge base who want to deflect “how do I” questions before they become tickets.
Where Scritch wins
- Recovering users blocked by technical failures: rejected imports, refused invoices, expired sessions, failed uploads.
- Reading the actual server response and fixing the issue, not just explaining what the docs say about it.
- Verifying the fix worked before declaring success, instead of handing the user a help article and hoping.
- Teams where blocked users file support tickets because the error message doesn’t explain what went wrong or how to fix it.
Can you run both?
Yes. Most teams that need one eventually want both. A chatbot handles “how do I” and “what does this mean” questions. Scritch handles “I tried to do X and your app blocked me” failures. They cover different halves of the support queue. A chatbot can also hand off to Scritch when it detects a technical failure, rather than trying to answer it with docs.
When you only need a chatbot
- Your support volume is mostly how-to questions and policy clarifications.
- Technical failures are rare, or already well-handled by clear error messages and self-service flows.
- You want to deflect common questions before they reach your team, not fix broken workflows.
When you need recovery instead
- Users get blocked by technical failures: rejected forms, expired sessions, failed imports.
- Your error messages don’t explain the real cause, so blocked users write in to ask what went wrong.
- You want failures fixed, not just explained — with proof the fix worked.
Next step
Start at scritch.xyz, or read how Scritch works. For the broader category, see what user-facing error recovery is, or compare Scritch to an error monitor and manual appeal queues.