Skip to main content
New Participant
August 12, 2024
Question

LLM chatbot intergration with RoboHelp Frameless output

  • August 12, 2024
  • 1 reply
  • 182 views

Hi,

 

We are currently looking to implement a chatbot in our help system. I can see there is some basic chatbot functionality out of the box with RoboHelp - using micro content for prescribed questions and answers, however, this does not suit our needs as we want a smarter chatbot that can search for the relevant information in our help system and present it to users, regardless of what they type (LLM)

 

Currently, we are looking to develop an LLM ourselves and apply this to our generated HTML5 (Frameless) output from RoboHelp and have encountered a couple of issues.

 

1) Web scraping only works up to the first subheading in our content - and so only the top paragraph is searched/returned.

2) We see a 403 - forbidden error on the first landing page (index) which prevents it from being scraped. 

 

Is there anything particular to the RoboHelp output that could explain these issues? Or anyone who has tried to do something similar who has encountered similar issues? We have successfully managed to take this approach for other content generated by a different program (also HTML output) in a directory in the same location as the RoboHelp generated content we're trying to implement this on. 

 

Any advice on this would be greatly appreciated.

 

Thanks

    This topic has been closed for replies.

    1 reply

    Peter Grainge
    Community Expert
    August 12, 2024

    Your overall objective is outside my knowledge area but let me see what I can come up with.

     

    Web scraping only works up to the first subheading in our content - and so only the top paragraph is searched/returned.

    On the basis that a CTRL F search of any topic in your browser, works isn't the issue you are facing an issue with the tool being used?

     

    We see a 403 - forbidden error on the first landing page (index) which prevents it from being scraped. 

    Are you saying that if you try to open the index page in a browser in the normal way you get that error or just with the tool being used? You shouldn't see it with the first option and if it is the second option, again that seems like an issue with the tool being used.

     

    Sorry I can't be more helpful.

    ________________________________________________________

    My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

     

    Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.