Skip to main content
Solved

A keyword is being required to be typed 2x before flow starts

  • February 24, 2025
  • 4 replies
  • 45 views
Alicebot Co

Hi friends, 

Help please. I have a flow that is “password protected” and we are using the keyword as a way to get access to the rest of the content. Unfortunately, the flow will not trigger and start the flow without typing in the keyword 2x. This leaves clients stuck and confused. We have found no way around this with 504 users from december to present. Anyone have experience with troubleshooting this? It’s not happened with our flows in the past. 

 

Thank you,

Tiffany

Best answer by Fabio Gaulke

​@Alicebot Co, thanks for sharing!

 

As Rogerio already said, I also consider using the Data Collection block a better approach to your scenario.

This is how I would build it:

  1. Greeting Message
  2. Data Collection asking for the password and storing it to a Custom Field
    • I've created a Text Field called PASSCODE for this example

    •  

  3. A condition checking if PASSCODE contais your password (here you insert the password. But you could also create a Bot Filed, set your password there ans reference it in this condition)
  4. If the password is correct, it continues and send the content
  5. If the password is incorrect, sends a message informing that and goes back to the Data Collection step.

 

This should do what you are looking for with just one flow. 😉

 

 

    4 replies

    Fabio Gaulke
    Forum|alt.badge.img+3
    • Fabio Gaulke
    • Manychat Community Moderator
    • February 24, 2025

    Hi, ​@Alicebot Co!

     

    Could you share how your flow is built? (just the “validation” part is probably enough)

    This seems like some gap in the flow logic.

    @fabio.gaulke | @monada.ag
    Alicebot Co
    • Alicebot Co
    • Author
    • Up-and-Comer
    • February 26, 2025

    Thank you fabio. 

     

    Flow 1: Client clicks ref URL to start flow. Client is greeted with a welcome message and then prompted to enter keyword “PASSWORD” for content. Action set to type text

     

    Flow 2: Trigger set to accept keyword through “USER SENDS A MESSAGE”. The keyword had a few ways to be typed originally to prevent from getting stuck do to a misspelling or missing caps. We know this is not a requirement with manychat like old versions. example keyword(s):

     

    Team; Teams; team; teams

     

    We’ve tried updating to one word only. 

     

    Nothing corrects needing to submit the keyword twice.  

    rogerioaraujo
    Forum|alt.badge.img+2
    • rogerioaraujo
    • Flow Scholar
    • February 26, 2025

    From what I understand, the second flow is triggered by a keyword that matches the password.
    Wouldn't it be better to insert a text collection block in the first flow and, after the user enters the text, use a condition block to check if the correct word was entered?
    If the user typed it correctly, you direct them to the second flow. Otherwise, ask for the correct password.

    Fabio Gaulke
    Forum|alt.badge.img+3
    • Fabio Gaulke
    • Manychat Community Moderator
    • Answer
    • February 26, 2025

    ​@Alicebot Co, thanks for sharing!

     

    As Rogerio already said, I also consider using the Data Collection block a better approach to your scenario.

    This is how I would build it:

    1. Greeting Message
    2. Data Collection asking for the password and storing it to a Custom Field
      • I've created a Text Field called PASSCODE for this example

      •  

    3. A condition checking if PASSCODE contais your password (here you insert the password. But you could also create a Bot Filed, set your password there ans reference it in this condition)
    4. If the password is correct, it continues and send the content
    5. If the password is incorrect, sends a message informing that and goes back to the Data Collection step.

     

    This should do what you are looking for with just one flow. 😉

     

     

    @fabio.gaulke | @monada.ag
    rogerioaraujo
    Alicebot Co
    Community Terms & ConditionsCookie settingsAccessibility statement