Stacker Chatbot using Chatwoot
Goal: Display a chatbot to your users, so they can talk to your team (sales, support, etc.)
<aside>
đź’ˇ Chatwoot acts as an omnichannel support center.
That means it can centralize all requests, no matter their origin. (email, chatbot, SMS, etc.)
Your team only needs to use Chatwoot, the reply will be sent through the same canal the user used in the first place.
</aside>
Benefits
- Displays a Chatbot to your users, so they can ask questions to a support/sales team, etc.
- Configure several “inboxes” and centralize all requests within Chatwoot
- Supported 3rd parties: Website, Messenger, WhatsApp, SMS, Email, API, Telegram, Line
- Automatically keeps contacts in-sync with Chatwoot CRM, which makes the life of your team easier
- It is possible to track any user’s dimensions, if you’d want your team to have access to those information on Chatwoot (usually to make them more efficient)
- Display the chatbot to specific users
- Display different chatbots to different users, based on a criteria (e.g: user role)
- Send SMS/Email campaigns to your users
- Other advanced options:
- Pre-qualify the user by asking additional information, before they write to you (chatbot)
- Centralize everything in Slack, so your team doesn’t even need to use Chatwoot
- Self-hosting is possible, as Chatwoot is open-source and under the “MIT Expat” license
Recommandations
If you want to give me this mission, I suggest asking yourself a few questions beforehand:
- What teams need access to Chatwoot? Will they need different features? Do you need different chatbots depending on the user?
Having a clear understanding of your needs will definitely help with the implementation. You might only want to use it for a Support team and things will be straightforward in such case. But you also might want to use it for Sales acquisition, depending on the user’s current step or role. Having a draft of those functional needs will definitely help me advise you better.
- Do you need to keep users in-sync with Chatwoot CRM? What should be tracked?
The integration will do it by default, but you might want to disable that behavior, or, on the contrary, to track specific metrics. If so, having a list of such metrics will help me do the job faster. Those metrics can also be added afterwards.
Average duration of the mission
Implementing Chatwoot in your Stacker app will take me: