2
WABA templates are currently not accessible via API. If a customer of ours wants to use WABA functionality via WhatsApp, he must first manually provision templates via the seven.io console. If we could instead allow programatic access to the template endpoints, we could fully int
Feature1
2
Hi, we need to get the list and maybe the content of the defined templates for WhatsApp.
Integrations0
1
It should be possible to set a status for a chat, for example "completed" or "open". Assigning labels to conversations would also be an option.
Feature0
1
It would be very helpful to have desktop notifications for incoming messages. This ensures that employees are immediately informed when a new message arrives. This is especially important in daily operations, so that no customer request is missed and response times stay short.
Feature0
1
We have partners / customer in French overseas territories. Sending SMS messages there should be possible. However, voice calls to French overseas territories are not supported. This is necessary for our service. Country codes are: +594 (French Guiana), +590 (Guadeloupe), +596 (M
Feature0
8
Currently if a duplicate SMS is sent within 180s and the setting "Prevent duplicate SMS" is on the sms will fail with status "FAILED". It seems that there is no other way then checking the journal if it failed due to this function. Introducing a new state like "BLOCKED" will sepe
Feature1
4
There should be a role like 'Messaging' that can access contacts but is not allowed to add, edit, or view their contact information. Additionally, members of this role should not have the ability to add or edit groups, nor add or delete contacts from groups.
Feature2
3
It would be nice to be able to user filters/searches in the journal. e.g. status = failed recipient = 1234 ...
Feature0
3
Dear Seven.IO Team, i would like to customize the JSON Payload for Webhooks in order to connect the api directly to our Mattermost Server: https://developers.mattermost.com/integrate/webhooks/incoming/
Feature0
2
The main overview of all conversations is well designed. But with many messages, it becomes hard to keep a clear view. For example, we send many SMS messages for appointment reminders. All of them appear in the same list. At the same time, some employees only handle customer repl
Feature2
