• MrsDoyle@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    6
    ·
    6 hours ago

    A human at my bank told me the best way to deal with their chatbot is to not say anything at all. Not even “I want a human”. Maintain silence and it will eventually put you through to a human.

    • im_fine_sandy@nord.pubOP
      link
      fedilink
      English
      arrow-up
      6
      ·
      5 hours ago

      I usually just press star or hash on the number pad a bunch of times

      • beep
      • I’m sorry I don’t…
      • beep
      • I’m sorry…
      • beep
      • I’m…
      • beep beep beep
      • <on hold music>
      • bedwyr@piefed.ca
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 hours ago

        0 and # repeatedly used to work, but it doesn’t now, not the last 5 + years, I try it regularly if stuck on the automated corporate customer service loops. Idk about chatbots that don’t pretend to be a real person though.

        • im_fine_sandy@nord.pubOP
          link
          fedilink
          English
          arrow-up
          4
          ·
          4 hours ago

          It depends on the software / configuration / script.

          In any sane set up, if the user fails to navigate the menu n times you get dumped to an operator. 0 or * or # aren’t special hacks, you just need invalid navigation.

          I imagine what you have noticed is that increasingly there just isn’t an operator to talk to, or at least the org you’re calling really doesnt want to talk to you, so this kind of navigation failure just dumps you back to the start or something.