So it is sending service requests and getting a response but showing the following in the service response:
"content": "SessionSpeechlet - Error parsing results.",
heroku logs show the following:
2016-10-11T17:34:33.852920+00:00 app[web.1]: Requested intent: PlayRandomMovie
2016-10-11T17:34:33.853131+00:00 app[web.1]: Trying to play a random movie
2016-10-11T17:34:33.853192+00:00 app[web.1]:
http://*myaddress**.no-ip.biz
2016-10-11T17:36:41.654399+00:00 heroku[router]: at=info method=POST path="/" host=mighty-cliffs-37745.herokuapp.com request_id=e8ae8d9c-1137-4cd5-8645-02e811302f29 fwd="72.21.217.173" dyno=web.1 connect=0ms service=6ms status=200 bytes=492
2016-10-11T17:36:41.640404+00:00 app[web.1]: Requested intent: PlayMovie
2016-10-11T17:36:41.640434+00:00 app[web.1]: Trying to play the movie applesauce
2016-10-11T17:36:41.640435+00:00 app[web.1]:
http://*myaddress*.no-ip.biz
2016-10-11T17:36:51.883967+00:00 heroku[router]: at=info method=POST path="/" host=mighty-cliffs-37745.herokuapp.com request_id=dff61824-e441-4d76-8fee-7047dfedcc8f fwd="72.21.217.175" dyno=web.1 connect=0ms service=3ms status=200 bytes=492
2016-10-11T17:36:51.870283+00:00 app[web.1]: Requested intent: PlayMovie
2016-10-11T17:36:51.870302+00:00 app[web.1]: Trying to play the movie applesauce
2016-10-11T17:36:51.870323+00:00 app[web.1]:
http://*myaddress**.no-ip.biz
Update: I rebuilt the Heroku from scratch and tried again and all working correctly!! It's pretty damn quick. Awesome feature and thanks to developer!