Larry -
Our systems are up & running. We have not experienced downtime today (& not for quite a long time).
We have automated tracking sensors that trip whenever any subsystem fails - so we would know.
Also - our customer support would be overwhelmed.

Must have been a local disruption of internet service or network connectivity.
Are you still experiencing a problem?
LMK
Gil

Hi Tony -
This issue is now resolved.
Full body characters are now displayed in HTML5 on Chrome (as well as on mobile devices of course)
We will apply the same to other browsers in the coming weeks - as we gradually phase out Flash.

Let me know if you notice any problem.
Best,
Gil

ps. interesting workaround - good to know!

Hi Tony - we're working on it. Some problems have been noted, and are being addressed. The process should be concluded within several days.

Tony -
Your characterization of the problem is spot on.
The full body character currently takes advantage of Flash where available - and HTML5 otherwise.
We will be making a change to play back using HTML5 on Chrome.This change will be made in the next several days - it is being tested now.
Regards,
Gil

Hi Emiliano -

The new full body characters were recently launched - and they fully support dynamic API functions on mobile devices.
The API implementation is identical on desktop and mobile - use sayAIResponse.

The user experience is nearly identical - the only difference on mobile is that the user must touch the character (once) before it can speak. This is a browser requirement on mobile browsers on both iOS and Android.

Please check it out - more information here -
http://www.sitepal.com/fullbody/

Let me know if any comments or questions.
Regards
Gil
SitePal Team

Hi Terence - 
Are you still experiencing a problem?
We looked into your account and everything seemed normal. 
Please let me know
Regards
Gil 
SitePal Team

seems to be working for me.
try clearing your browser cache - and try again.
Regards
Gil
SitePal Team

Hi Jimson - 

Some voices are more "punctuation responsive" than others - it depends on the "voice family" (also noted in the documentation as the "engine id")

I think engine #3 voices, such as Paul and Julie are better about inflecting the voice for a question mark, and introducing an appropriate pause for a comma etc.

Try it and let me know what you think.

You can also introduce precisely timed pauses by using SSML tags. These are documented in the API reference document (see appendix) or see examples of use here - 
http://www.oddcast.com/support/NeoSpeech_SSML.html

Regards
Gil 
SitePal Team