The document provides an update on Talis Aspire from their June 2011 User Group meeting. It summarizes that since December, Talis has launched new support and idea sharing sites, handled over 200 support tickets and 150 knowledge base articles. A survey showed users wanted more training, FAQs and videos. The roadmap includes improvements to widgets, time periods, pages, licenses and performance monitoring.
8. Customer Service
support.talisaspire.com
Launched You raised We published We shot
Feb 200+ 150+ 58
2011 tickets KB articles video tutorials
ideas.talisaspire.com
Launched You raised ...of which ...of which
Mar 190 53% 55
2010 ideas addressed in product!
13. More, more, more!
• More training for quicker resolutions
• More FAQs and answers to common
problems
• More videos, esp. on new areas of the
system
attribution
34. Performance Improvements
• More hardware capacity - DONE
• More efficient data handling - DONE
• Improved database server config - DONE
• Content Delivery Network - TO DO
• Google Analytics blocking pages - TO DO
• Improve code efficiency for some key
workflows - TO DO
• Continue to monitor closely - ONGOING
attribution
35. Questions?
Find us on:
Web: talisaspire.com
Twitter: @talisaspire
YouTube: youtube.com/user/TalisAspire
Facebook: facebook.com/talisaspire
Support: support.talisaspire.com
36. Find us on:
Web: talisaspire.com
Twitter: @talisaspire
YouTube: youtube.com/user/TalisAspire
Facebook: facebook.com/talisaspire
Support: support.talisaspire.com
Editor's Notes
\n
\n
Tackle in reverse order...\n\n\n
Support was talis-centric not product-centric\nResolutions took too long - not close enough to dev team\nTicket system was poor and KB non-existent\n\n\n
Support was talis-centric not product-centric\nResolutions took too long - not close enough to dev team\nTicket system was poor and KB non-existent\n\n\n
Support was talis-centric not product-centric\nResolutions took too long - not close enough to dev team\nTicket system was poor and KB non-existent\n\n\n
Also going to share results of survey....\n
\n
\n
\n
\n
\n
New site - only phase 1 though\n- Better homepage\n- Customer showcase\n- More “user experience” videos\n
Connected to dev system\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Up next... working on collaborative features..\n
Federated login done, Aspire in UK Federation and AAF. New customers only for now, migrations later if there is demand\nRollover largely done, time periods, new API, last feature to complete\nManagement info started (first feature in dev now)\n
\n
Federated login done, Aspire in UK Federation and AAF. New customers only for now, migrations later if there is demand\nRollover largely done, time periods, new API, last feature to complete\nManagement info started (first feature in dev now)\n
\n
Continuous Performance / Next 6 months / Performance\n
Invested in tools and techniques to deeply monitor Aspire\nAverages but also individual requests\n
Can trace individual long running requests in depth, deep code instrumentation\n
Overall, app server performance looked OK \nHowever, end user in-browser monitoring shows us network is actually biggest delay\n