Skip to main content

    Filter by status

    Filter by product area

    775 Ideas

    Sebastian Riehle
    Sebastian RiehleUp-and-comer

    Automations for undelivered WA messagesNew

    Hi Manychat team,I face a problem with a small but consistent percentage of WhatsApp users and would like you to consider a new feature: Currently, there's no way to automatically identify and handle contacts who didn't receive a WhatsApp message due to:a) WhatsApp-ID subscribed via API does not existb) temporary unavailabilityc) Meta's delivery restrictions.Suggested solution: Implement an automated system in Manychat that can detect undelivered WhatsApp messages, flag affected contacts, trigger specific automations based on delivery status, and provide options to retry sending messages or remove opt-ins if desired. For example a connector in flow builder like the one for user input "user did not reply within x minutes" --> "contact did not receive message within x minutes"So I can followup with a normal action block and guide users another way through the automations at points of interest within flow builder. "The benefit would be for the community, all WhatsApp Chatbot creators, agencies, agency-clients and WhatsApp users likewise. Use case: We run ads that subscribe contacts via API to WhatsApp and leads get their first message template immediately. For leads not reachable I need to notify an Admin, so they can call the person in time. Or send an API call to my CRM-System or Update a Google Sheet and so on… Use case #2: We subscribe gym members with their checkin via API to Manychat. If there are any problems, sending our initial welcome message, we need to know about it automatically to set further actions. Use case #3: We subscribe user via API after appointment bookings for confirmation and followups. If the contact is not reachable, we need to know about it to chose other ways of communication. A solution would help maintain cleaner contact lists, improve overall message delivery rates, and allow for more targeted follow-up strategies. It would save time on manual list management and improve engagement rates.Thank you very much for your consideration :-)Best regardsSebastian

    Heric
    HericSmooth talker

    Advanced Permission and Visibility Settings per Team MemberNew

    Hi Manychat Team, I’d like to suggest a significant improvement regarding team member permissions and visibility controls within the platform.Currently, the only customizable access available for a team member is billing-related. It would be extremely helpful to have more granular control over permissions and visibility for each individual team member — rather than applying settings globally. Key Suggestions: Allow admins to assign specific permissions individually, such as: Access to add or delete contacts without requiring admin status. Ability to view conversations of specific team members (not all). Ability to access conversations in the "Unassigned" inbox. Ability to create, edit, or delete tags. And ideally, the ability to assign any permission that an admin currently holds to a specific member, depending on their role.  Use Case Examples: I want a team member to manage contacts, but not access billing or platform settings. I want a supervisor to view conversations from selected team members only, without granting full access to everyone’s inbox. I want to allow a support agent to monitor unassigned conversations, but not see automations or settings they don’t need. I want to allow a member to create and manage tags, without making them an admin.  Additional Request – Visibility Controls:It would also be helpful to control which resources each member can see: Automations Custom fields Sequences Menus Templates Configuration tabs  For example, a support agent doesn't need to see all flows or system configurations that are irrelevant to their tasks. Restricting visibility helps avoid confusion and keeps each team member focused on what matters to their role.This level of customization would make Manychat much more scalable and secure for teams of any size, especially those who work with sensitive data or need clear role separation. Could you help me with this, ​@Raquel C , ​@Marina? Thank you for considering this improvement!Best regards,Heric Fernandes