Feature request
Add native message forwarding to the CRM chat, similar to WhatsApp.
Currently there is no convenient way for an agent to forward an existing message, attachment, image, audio, video, or document from one conversation to another contact/conversation.
Expected behavior
Add a Forward action to the message actions menu.
Flow:
- Agent opens the message actions menu
- Clicks Forward
- A modal opens with search
- Agent can search for contacts/conversations
- Agent can select one or multiple destinations
- Click Forward
- The original message or attachment is sent to the selected conversations
Message types
Forwarding should support, where possible:
- Text
- Images
- Videos
- Audio / voice messages
- Documents/files
- Other supported message attachments
UX
Example message menu:
- Reply
- Copy
- Forward
- Delete
The Forward modal should provide:
- Search by contact name
- Search by phone number
- Search by conversation
- Multi-select destinations
- Selected recipient count
- Cancel / Forward actions
Important behavior
Forwarding should create a proper outgoing message in the destination conversation and use the destination channel/provider normally.
It should not simply move or re-parent the original database message.
The original message should remain unchanged in the source conversation.
Acceptance criteria
A backend change may be required for attachment reuse/copying and forwarding semantics; if so, a companion issue can be created in evo-ai-crm-community.
Feature request
Add native message forwarding to the CRM chat, similar to WhatsApp.
Currently there is no convenient way for an agent to forward an existing message, attachment, image, audio, video, or document from one conversation to another contact/conversation.
Expected behavior
Add a Forward action to the message actions menu.
Flow:
Message types
Forwarding should support, where possible:
UX
Example message menu:
The Forward modal should provide:
Important behavior
Forwarding should create a proper outgoing message in the destination conversation and use the destination channel/provider normally.
It should not simply move or re-parent the original database message.
The original message should remain unchanged in the source conversation.
Acceptance criteria
A backend change may be required for attachment reuse/copying and forwarding semantics; if so, a companion issue can be created in
evo-ai-crm-community.