Skip to main content

    630 Ideas

    Sebastian Riehle
    Sebastian RiehleRising Conversationalist

    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
    HericChannel Explorer

    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

    Idea para ManyChat: integración JSON para flujos desde ChatGPTNew

    ¡Hola equipo de ManyChat! 👋Soy Lourdes, especialista en marketing digital y lanzamientos de infoproductos centrados en embudos de venta por Instagram. Actualmente me estoy especializando en chat funnels.Últimamente he empezado a usar ChatGPT para esbozar estructuras de flujos conversacionales antes de construirlos manualmente en ManyChat. Esto me ahorra mucho tiempo en la fase creativa, pero el traspaso manual a la plataforma es repetitivo y consume demasiados recursos.Por eso, me encantaría proponer lo siguiente:✅ Una funcionalidad que permita importar estructuras de flujos a través de archivos JSON generados por herramientas de IA (como ChatGPT) o plataformas low-code, directamente al constructor de ManyChat.¿Por qué esto sería potente? Ahorro de tiempo enorme para creadores avanzados y agencias Colaboración fluida entre humanos e inteligencia artificial Escalabilidad: más fácil clonar, iterar y reutilizar flujos Impulso a la creatividad: estructuramos con lógica, diseñamos con alma Sé que actualmente los flujos solo se pueden duplicar manualmente o entre espacios de trabajo. Pero permitir la importación vía JSON (quizá a través de una estructura validada o un endpoint API) abriría la puerta a una forma mucho más ágil de trabajar para los usuarios más avanzados.Ya sea como funcionalidad nativa o como una capa de integración con partners verificados, esto podría revolucionar la manera en que construimos y escalamos automatizaciones dentro de ManyChat.Gracias por considerar esta idea y por construir una plataforma tan potente. ¡Estoy deseando saber qué opináis!—Lourdes Pallas@lourdespallas.mkt

    nocodedude
    nocodedudeUp-and-Comer

    Enable Second-Level Granularity in Conditional FiltersNew

    Hi ManyChat team and fellow builders,I’d like to propose adding second-level filtering in Conditional blocks (and anywhere we compare timestamps). Right now the smallest time unit we can work with is one minute. For most automations that’s fine, but when you’re trying to build responsive, conversational experiences it becomes a real bottleneck.Why seconds matter Smart Delay + Conditional check loops A common pattern is: set a short Smart Delay, check the last user message time, decide whether to bundle new input or push a follow-up. With minute-only precision we’re forced to wait at least 60 seconds before the Condition can evaluate, which feels like an eternity in live chat. Message grouping & spam prevention Many builders try to merge multiple quick user replies into a single logical block, or throttle highly active users so we don’t spam agents. We currently can’t distinguish someone who answered 3 s ago from someone who answered 58 s ago. Proposed change Allow seconds as a valid unit anywhere we compare or add time (e.g., {{last_input}} is less than 15 seconds ago). If UI clutter is a concern, hide “seconds” behind an “Advanced” toggle—builders who need it will find it. Impact Faster user experience → conversations feel natural, which improves retention and conversion. Cleaner flows → no more hacky work-arounds (multiple branches, external APIs, or unnecessary tags). Competitive edge → other bot platforms already allow sub-minute delays; adding this keeps ManyChat best-in-class. If you’ve run into the same limitation—or have ideas on implementation—please add your voice below. The more real-world examples we share, the easier it’ll be for the product team to prioritize.Thanks for considering, and happy building! 🚀