Share Your Feedback

At the moment, it's only possible to choose from one of the following pre-defined permissions for users: Administrator Developer Finance Messaging Sometimes it is necessary to have more refinement over the permissions, to be able to customise them. For example, being able to chec

It should be possible to forward incoming calls to own seven-numbers to a customers SIP trunk.

When a WhatsApp recipient responds to a message by adding a reaction (for example a thumbs-up) instead of typing a reply, the reaction is visible in Conversations but no webhook is dispatched, so API customers have no way to know it happened. Meta clearly delivers reaction events

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

Ist-Zustand: Mehrere Zahlungsmethoden werden aktuell technisch dargestellt, z. B.: Mastercard *1234 Mastercard 3456 Problem: Keine klare, menschliche Zuordnung möglich Nutzer müssen sich die Karte über Endziffern merken Unpraktisch bei mehreren Karten gleichen Typs Anforderung: Z

Hi, we need to know if a number support WhatsApp messages.

Es währe cool, wenn man die spätere Plattform als Whitelabel Lösung für unsere Kunden anbieten kann.

The phone call api should detect voicemail at the client side and start playing the text after the beep.

If a SIM or a number is not working it would be great to have much more transparency into issues, before a customer notices them. Somesort of status page / overview per number would be great.

It would be nice to have the option to create a static URL that has been shortened, maybe even using a custom URL (instead of a random generated string). The URL should still be usable in SMS but can also be used in other transport media as for example E-Mail. The main goal of th