This is a CSS conflict. We have used very unique IDs and classes for the styling of the widget, but some of your site's generic rules may be affecting the widget, since technically it becomes part of your site's HTML when it loaded (e.g. it's not an iframe).

The most common conflict we've seen are rules that change some of the defaults of a <div> element, such as making it inline instead of block.