OK i understand now...
So you could use an active cast widget but i guess depending on what you want to achieve and ultimatly the core contact drivers for your business you might need something a bit more complex and use of REST api giving you a better end result, take a look at my contact us form, this will take you to a pre-defined end point where you can see "deflection content" in the form of knowledge content and community links.
This is by no means the end result for us but will give you an idea of what you could achieve. On each end point the help "knowledge" content is dynamic and speciffic to the contact reason. Today the form content is static and serve as a crude attempt to defect to the community however this space could and will be replace with an api call which will call community content as it loads based on the product selected in the inital steps.
For example, in my case if a customer selected an option for TV troubleshooting we would display content and maybe just accepted solutions we have areounf this topic. I'm not the most technical however this is actually relativly easy to achieve "so i am told" with api knowledge.
Hope this helps.