Compare approaches
ANSRZ vs. a chatbot bolted onto your help centre
A published help centre is a useful starting point. A support workspace also needs conversations, internal knowledge and a place for people to finish the answer.
All comparisons ↗Side by side
One question. Two ways to organize the answer.
“Where can I find the answer to this customer's question?”
Published help articles and a customer chat surface.
Work tickets, shared inbox conversations and knowledge together.
Open the conversation, read the related knowledge, review a draft and send the answer. Keep the work in the workspace.
The workflow, including the tradeoffs.
| Dimension | a help-centre chatbot | ANSRZ |
|---|---|---|
| Knowledge | Published help articles and a customer chat surface. | Published articles, source documents and supported integrations in a support workspace. |
| Team workflow | Depends on the chosen tools and process. | Tickets, shared inbox, internal notes and assignment. |
| AI assistance | Depends on the product or implementation. | Ticket and email drafting and analysis under the applicable plan. |
| Human control | Define the review and sending process for the chosen workflow. | Agents review, edit and send support replies. |
| Customer experience | A separate or integrated customer surface, depending on the approach. | Knowledge, customer tickets and an AI assistant in the portal. |
| Maintenance | Your team or provider maintains the selected workflow. | Manage sources, review articles and follow workspace activity. |
Choose the other approach when
Your published help centre already answers the questions customers ask, and a standalone chat surface is enough.
Choose ANSRZ when
You need a shared support workspace with knowledge review, agent replies and a customer portal, using the capabilities of your chosen plan.
Explore ANSRZ
See it work. Then bring your own knowledge.
Explore the demo workspace or talk to our team about the support workflow you need.