iachat/spec/services
Pranav Raj S b7c9f779ad
fix: Avoid processing reactions, ephemeral, request_welcome or unsupported messages (#8780)
Currently, we do not support reactions, ephemeral messages, or the request_welcome event for the WhatsApp channel. However, if this is the first event we receive in Chatwoot (i.e., there is no previous conversation or contact in Chatwoot), it will create a contact and a conversation without any messages. This confuses our customer, as it may appear that Chatwoot has missed some messages. There are multiple cases where this might be the first event we receive in Chatwoot. One quick example is when the user has sent an outbound campaign from another tool and their customers reacted to the message.

Another event like this is request_welcome event. WhatsApp has a concept for welcome messages. You can send an outbound message even though the user has not send a message. You can receive notifications through a webhook whenever a WhatsApp user initiates a chat with you for the first time. (Read the Welcome message section: https://developers.facebook.com/docs/whatsapp/cloud-api/phone-numbers/conversational-components/ ). Although this can help the business send a pro-active message to the user, we don't have it scoped in our feature set. For now, I'm ignoring this event.

Fixes https://linear.app/chatwoot/issue/CW-3018/whatsapp-handle-request-welcome-case-properly
Fixes https://linear.app/chatwoot/issue/CW-3017/whatsapp-handle-reactions-properly
2024-01-25 11:40:18 +04:00
..
agent_bots feat: Add native support for CSML in agent_bot API (#4913) 2022-06-23 19:17:46 +05:30
auto_assignment chore: Enable the new Rubocop rules (#7122) 2023-05-19 14:37:10 +05:30
automation_rules fix: SQL error when rules with missing attributes is triggered (#8673) 2024-01-22 16:09:34 +05:30
contacts fix: Avoid joining tables to fix the distinct value query (#7965) 2023-09-22 19:48:56 -07:00
conversations fix: Update query to support multiple tag conditions (#8054) 2023-10-05 10:47:42 +05:30
facebook fix: Update the message status to failed if the outgoing Facebook message fails. (#8258) 2023-10-31 17:40:17 -07:00
instagram chore: Update MarkMessagesAsReadJob to accept delivered status (#8319) 2023-11-08 13:44:57 -08:00
internal feat: Add job to remove stale contact inboxes (#8096) 2023-11-06 20:24:30 -08:00
labels fix: Update associations when a label is updated (#3046) 2021-09-21 10:16:32 +05:30
line feat: Add sticker support in Line channel (#8488) 2023-12-10 20:45:44 -08:00
macros feat: Add the ability to self-assign conversations in macros (#8048) 2023-10-10 09:38:23 +05:30
message_templates chore: Disable message hooks for conversations without incoming message (#7620) 2023-07-26 20:38:49 +03:00
messages chore: Change primary actor to Conversation for all the notification types. (#8435) 2023-12-06 10:43:09 +05:30
microsoft Feat: Support for Microsoft Oauth in Email Channel (#6227) 2023-01-17 02:39:05 +05:30
notification chore: Switch to web-push gem (#6390) 2023-02-03 18:55:22 +05:30
sms feat: Bandwidth sms channel delivery reports (#8198) 2023-10-27 14:07:15 -07:00
telegram fix: Check the file attachment URL exists before downloading attachments in Telegram. (#8679) 2024-01-11 17:25:46 -08:00
twilio fix: Twilo attachment download fallback to the step where authorization headers are not passed. (#8681) 2024-01-11 17:23:31 -08:00
twitter chore: Enable the new Rubocop rules (#7122) 2023-05-19 14:37:10 +05:30
whatsapp fix: Avoid processing reactions, ephemeral, request_welcome or unsupported messages (#8780) 2024-01-25 11:40:18 +04:00
action_service_spec.rb fix: undefined method 'zero?' for nil:NilClass (#8689) 2024-01-15 15:07:36 +05:30
search_service_spec.rb chore: Enable the new Rubocop rules (#7122) 2023-05-19 14:37:10 +05:30