sendingtk / chatwoot Goto Github PK

License: Other

Dockerfile 0.05% Shell 0.93% JavaScript 24.28% Ruby 41.68% Makefile 0.02% Procfile 0.01% SCSS 1.47% Vue 28.93% HTML 2.33% Liquid 0.16% MDX 0.14% TypeScript 0.02%

chatwoot's Introduction

Chatwoot

Customer engagement suite, an open-source alternative to Intercom, Zendesk, Salesforce Service Cloud etc.

Chatwoot is an open-source, self-hosted customer engagement suite. Chatwoot lets you view and manage your customer data, communicate with them irrespective of which medium they use, and re-engage them based on their profile.

Features

Chatwoot supports the following conversation channels:

Website: Talk to your customers using our live chat widget and make use of our SDK to identify a user and provide contextual support.
Facebook: Connect your Facebook pages and start replying to the direct messages to your page.
Instagram: Connect your Instagram profile and start replying to the direct messages.
Twitter: Connect your Twitter profiles and reply to direct messages or the tweets where you are mentioned.
Telegram: Connect your Telegram bot and reply to your customers right from a single dashboard.
WhatsApp: Connect your WhatsApp business account and manage the conversation in Chatwoot.
Line: Connect your Line account and manage the conversations in Chatwoot.
SMS: Connect your Twilio SMS account and reply to the SMS queries in Chatwoot.
API Channel: Build custom communication channels using our API channel.
Email: Forward all your email queries to Chatwoot and view it in our integrated dashboard.

And more.

Other features include:

CRM: Save all your customer information right inside Chatwoot, use contact notes to log emails, phone calls, or meeting notes.
Custom Attributes: Define custom attribute attributes to store information about a contact or a conversation and extend the product to match your workflow.
Shared multi-brand inboxes: Manage multiple brands or pages using a shared inbox.
Private notes: Use @mentions and private notes to communicate internally about a conversation.
Canned responses (Saved replies): Improve the response rate by adding saved replies for frequently asked questions.
Conversation Labels: Use conversation labels to create custom workflows.
Auto assignment: Chatwoot intelligently assigns a ticket to the agents who have access to the inbox depending on their availability and load.
Conversation continuity: If the user has provided an email address through the chat widget, Chatwoot will send an email to the customer under the agent name so that the user can continue the conversation over the email.
Multi-lingual support: Chatwoot supports 10+ languages.
Powerful API & Webhooks: Extend the capability of the software using Chatwoot’s webhooks and APIs.
Integrations: Chatwoot natively integrates with Slack right now. Manage your conversations in Slack without logging into the dashboard.

Documentation

Detailed documentation is available at chatwoot.com/help-center.

Translation process

The translation process for Chatwoot web and mobile app is managed at https://translate.chatwoot.com using Crowdin. Please read the translation guide for contributing to Chatwoot.

Branching model

We use the git-flow branching model. The base branch is develop. If you are looking for a stable version, please use the master or tags labelled as v1.x.x.

Deployment

Heroku one-click deploy

Deploying Chatwoot to Heroku is a breeze. It's as simple as clicking this button:

Follow this link to understand setting the correct environment variables for the app to work with all the features. There might be breakages if you do not set the relevant environment variables.

DigitalOcean 1-Click Kubernetes deployment

Chatwoot now supports 1-Click deployment to DigitalOcean as a kubernetes app.

Other deployment options

For other supported options, checkout our deployment page.

Security

Looking to report a vulnerability? Please refer our SECURITY.md file.

Community? Questions? Support ?

If you need help or just want to hang out, come, say hi on our Discord server.

Contributors ✨

Thanks goes to all these wonderful people:

chatwoot's People

Contributors

Stargazers

Watchers

Forkers

egorky antonionnigomes kabaweb marcosgunha mastolai ssteeltm neliocaa brunospagi aireset lucascs1 francisbreit dfn-master icaruus22 repositoriomaster jskfox developexi central-atende ruben18salazar3 ricardocarrer doug-fsg antoniocruzdev michaelrodriguesoficial vgnogueira sandrolborges frdaga xoiurp saggerbr neocol83 pagezine thallisson1887 ubiratanlima juniorcsa2022 kraussthing eduardoaldrimf pp-contrib rodneyoliveira guilhermejansen allchat-com-br lucirlei wkarts lucascampuus pedrofnts andermarcebr hermesmacedo doug-goncalves torresmga xiribitarp mtuliosan rodtanci rafaelmallquii mauroprojetos eltonciatto williamsantos96 themenotti imagenet

chatwoot's Issues

Cant create Meta Cloud API channel

I'm trying to create a new WPP Cloud API channel and when I fill in all the infromations nothing happens when I click on Create Button.

The button simply remains unclickable.

Custom logo not persisting

When a new image deploy happens or even new deploy with the same version, logo returns to chatwoot default, different from conversation data that is persisting ok. Is it possible to also persist custom logo?

Erro ao mencionar um agente de outro time - mensagem privada

Describe the bug

Quando um agente de outro time é mencionado em uma conversa privada para pedir apoio a solução de alguma situação, as menções não entram no @menções.

To Reproduce

Recebo a mensagem na caixa de e-mail ao mencionar o agente ela não consegue ver a mensagem a qual foi atribuida.
Ao entrar na mensagem privada e digitar @ aparece todos os agentes cadastrados na base, mas ele não consegue visualizar a mensagem o qual foi mencionado.
Estou usando Hetzner - Instalação via portainer - Versão 3.10.3

Expected behavior

Ao mencionar um agente na mensagem privada, entrar no @menções do usuário.

Environment

Linux VM

Cloud Provider

Other [please specify in the description]

Platform

Browser

Operating system

ubuntu 20.04

Browser and version

No response

Docker (if applicable)

No response

Additional context

pelo fato de ser possivel selecionar qualquer agente cadastrado na mensagem privativa me faz enterder que posso acionar internamente qualquer agente para auxilio com a demanda.

Error upload file in chatwoot + evolution api

Ao realizar um upload de uma imagem percebo o seguinte erro:

Ao investigar percebo que tenho o seguinte erro:

response: {
    **status: 404,**
    statusText: 'Not Found',
    headers: Object [AxiosHeaders] {
      'cache-control': 'no-cache',
      'content-type': 'text/html',
      'referrer-policy': 'strict-origin-when-cross-origin',
      'strict-transport-security': 'max-age=63072000; includeSubDomains',
      'x-content-type-options': 'nosniff',
      'x-download-options': 'noopen',
      'x-frame-options': 'SAMEORIGIN',
      'x-permitted-cross-domain-policies': 'none',
      'x-request-id': '32977e64-5934-4d7b-8905-073df47ce379',
      'x-runtime': '0.004957',
      'x-xss-protection': '0',
      date: 'Fri, 07 Jun 2024 14:35:42 GMT',
      'transfer-encoding': 'chunked'
    },
    config: {
      transitional: [Object],
      adapter: [Array],
      transformRequest: [Array],
      transformResponse: [Array],
      timeout: 0,
      xsrfCookieName: 'XSRF-TOKEN',
      xsrfHeaderName: 'X-XSRF-TOKEN',
      maxContentLength: -1,
      maxBodyLength: -1,
      env: [Object],
      validateStatus: [Function: validateStatus],
      headers: [Object [AxiosHeaders]],
      responseType: 'stream',
      method: 'get',
      **url: {dominio}/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcGdCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--6234657dcfa80405492a2ef2e9182829cd13cef0/image.png',**
      data: undefined
    },

Pelo meu entendimento a URL gerada não esta sendo acessivel.

Configuração de armazenamento

- ACTIVE_STORAGE_SERVICE=amazon

 image: sendingtk/chatwoot:v3.7.0

Agent Super Vision

Para mejorar un modo de Supervisor de Agente, vale considerar que la función "agent_conversation_viewed" a veces dificulta para quien es el agente debido al número de informaciones, pero es muy buena y excelente en su función para el agente que supervisa la atención. Sería interesante agregar la posibilidad de seleccionar solo a los agentes que pueden ver quién vio los mensajes en lugar de que todos tengan la opción de ver.

Hablando más sobre la visualización, también es muy útil para quienes supervisan la atención la función de poder visualizar las conversaciones pero sin que chawoot las marque como leídas. Es decir, este agente tendría la posibilidad de visualizar las conversaciones sin dejar rastros y también supervisar la atención.