We noticed that Ben has not been operating as intended, resulting in failures during conversations. We’re busy addressing these issues and are making steady progress. We recently changed how Ben operates on the backend to give us more control, but some of his functionality has been effectively inoperable.
Over the next day or two, Ben should return to normal operation, and many of the advanced features made possible by bringing development “in-house” should begin to operate normally.
We’ll continue to update this blog post with our progress.
August 13: We’re still adjusting things, but Ben is definitely working better than before. We’re hoping to have everything back to full working order by the weekend!