<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Desk.com Blog &#187; Product Updates</title>
	<atom:link href="http://www.desk.com/blog/product-updates/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.desk.com/blog</link>
	<description>The Customer Service Blog for the Social Web</description>
	<lastBuildDate>Wed, 22 Feb 2012 18:13:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Showing more records on small screens, and few other updates</title>
		<link>http://www.desk.com/blog/showing-records-small-screens/</link>
		<comments>http://www.desk.com/blog/showing-records-small-screens/#comments</comments>
		<pubDate>Thu, 16 Feb 2012 07:10:45 +0000</pubDate>
		<dc:creator>Greg Meyer</dc:creator>
				<category><![CDATA[Product Updates]]></category>

		<guid isPermaLink="false">http://blogadmin.desk.com/blog/?p=6335</guid>
		<description><![CDATA[Tonight&#8217;s release includes a few changes you&#8217;ve asked for since we launched Desk.com and several bug fixes. We hope you&#8217;ll continue to let us know how we can improve and help you be even more productive. Improved case spacing for &#8230; <a href="http://www.desk.com/blog/showing-records-small-screens/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Tonight&#8217;s release includes a few changes you&#8217;ve asked for since we launched Desk.com and several bug fixes. We hope you&#8217;ll continue to let us know how we can improve and help you be even more productive.</p>
<p><strong>Improved case spacing for smaller laptop screens</strong></p>
<p>You let us know that especially on 13&#8243; laptops, you could only view 2 or 3 cases in Bulk View; we&#8217;ve increased that spacing to show you 5 cases in Bulk View.</p>
<p><strong>Changed color of Macro-affected fields from <span style="color: #ff0000;">Red</span> to a <span style="color: #1b3981;">Cooler Color</span></strong></p>
<p>Many of you told us that you&#8217;d like a different color to alert you to macro-affected text, so we&#8217;ve changed that color to a calmer tone.</p>
<p><strong>Fixed an issue downloading Office Documents from a case</strong></p>
<p>We also resolved an issue that caused  Word, Excel, and Powerpoint attachments to be downloaded as zip files.  Documents received prior to the fix will still download as zip, and will need to be renamed with the proper extension to open.</p>
<p><strong><br />
</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.desk.com/blog/showing-records-small-screens/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Desk.com move complete</title>
		<link>http://www.desk.com/blog/deskcom-move-complete/</link>
		<comments>http://www.desk.com/blog/deskcom-move-complete/#comments</comments>
		<pubDate>Sat, 11 Feb 2012 07:45:14 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Product Updates]]></category>

		<guid isPermaLink="false">http://blogadmin.desk.com/blog/?p=6303</guid>
		<description><![CDATA[Tonight, we have finalized the Desk.com launch by changing the Assistly.com web addresses to Desk.com.  There are no immediate changes, and your Assistly.com addresses will redirect for at least 6 months.  For details of the changes, please see the &#8220;What&#8217;s &#8230; <a href="http://www.desk.com/blog/deskcom-move-complete/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Tonight, we have finalized the Desk.com launch by changing the Assistly.com web addresses to Desk.com.  There are no immediate changes, and your Assistly.com addresses will redirect for at least 6 months.  For details of the changes, please see the &#8220;<a href="http://support.desk.com/customer/portal/articles/341100-what-s-changing-with-desk-com-">What&#8217;s changed with Desk.com?</a>&#8221; knowledge base article.</p>
<p>In addition, we have started to incorporate your feedback, and have made initial changes to the Agent desktop:</p>
<ul>
<li>Removed &#8220;Customer Card&#8221; on left hand case pane for better use of vertical space.</li>
<li>Changed background color of viewed cases in filter view to distinguish from cases that are currently been worked on.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.desk.com/blog/deskcom-move-complete/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Change of Address &#8211; Moving to Desk.com</title>
		<link>http://www.desk.com/blog/addresses-changing-deskcom/</link>
		<comments>http://www.desk.com/blog/addresses-changing-deskcom/#comments</comments>
		<pubDate>Thu, 09 Feb 2012 18:50:16 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Product Updates]]></category>

		<guid isPermaLink="false">http://blogadmin.desk.com/blog/?p=6284</guid>
		<description><![CDATA[When we rolled out the new Desk.com platform on January 31st, we did not change the web addresses for our customer systems as we wanted minimize the impact on your operations.  This weekend, we will be finalizing the Desk.com roll-out &#8230; <a href="http://www.desk.com/blog/addresses-changing-deskcom/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>When we rolled out the new Desk.com platform on January 31st, we did not change the web addresses for our customer systems as we wanted minimize the impact on your operations.  This weekend, we will be finalizing the Desk.com roll-out by switching all web addresses from assistly.com to desk.com.</p>
<p>On Friday February 10th at 11PM Pacific, we will be updating the system for this change.  The update is planned for &lt;15 minutes.  After the update you and your customers will be able to access your Desk.com site at <em>yoursite</em>.desk.com.</p>
<p>To make the transition easy, we will be redirecting your assistly.com address for at least 6 months.  After the update your new address will be yoursitename.desk.com (unless you have a custom SSL certificate with us, in which case there will be no change for you).</p>
<ul>
<li>Your customers can still find you at your assistly.com address, although this is a great opportunity to <a href="http://support.desk.com/customer/portal/articles/1548-how-to-use-your-own-domain-for-the-help-center">set up your own address for your help center</a>.  You should also transition links to the new desk.com address as you have time.</li>
<li>Your employees will be redirected to their desk.com site from the assistly address, but you should begin using the new address to avoid the redirect.  After the update, agents who have chosen to be remembered will need to login.</li>
</ul>
<p>For more detail check out our knowledge base article,  <a title="What's Changing with Desk" href="http://support.desk.com/customer/portal/articles/341100-what-s-changing-with-desk-com-">What&#8217;s changing with Desk.com?</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.desk.com/blog/addresses-changing-deskcom/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Desk.com Mobile—Now Available for Flex Users</title>
		<link>http://www.desk.com/blog/deskcom-mobilenow-flex-users/</link>
		<comments>http://www.desk.com/blog/deskcom-mobilenow-flex-users/#comments</comments>
		<pubDate>Fri, 03 Feb 2012 07:05:55 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Product Updates]]></category>

		<guid isPermaLink="false">http://blogadmin.desk.com/blog/?p=6227</guid>
		<description><![CDATA[The Desk.com Mobile Agent can now be accessed by Flex Agents making it possible to deliver whole company support from anywhere by anyone.   Mobile flex usage works the same as desktop flex usage. Flex users access the mobile agent at http://yoursite.assistly.com/mobile.  For &#8230; <a href="http://www.desk.com/blog/deskcom-mobilenow-flex-users/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The Desk.com Mobile Agent can now be accessed by <a href="http://support.desk.com/customer/portal/articles/305053-glossary-of-terms#flexagent">Flex Agents</a> making it possible to deliver whole company support from anywhere by anyone.   Mobile flex usage works the same as desktop flex usage. Flex users access the mobile agent at http://<em>yoursite</em>.assistly.com/mobile.  For more information on accessing the mobile agent, check out the <a href="http://support.desk.com/customer/portal/articles/351939-how-do-i-access-the-desk-com-mobile-app-">Desk.com Help Center</a>.</p>
<p>The update also adds compatibility with Android 4.0 (Ice Cream Sandwich).</p>
<p><a href="http://blogadmin.desk.com/blog/deskcom-mobilenow-flex-users/mobile-flex/" rel="attachment wp-att-6228"><img class="wp-image-6228 alignnone" title="Mobile-Flex" src="http://assistlyblog.s3.amazonaws.com/blog/wp-content/uploads/2012/02/Mobile-Flex.png" alt="" width="383" height="470" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.desk.com/blog/deskcom-mobilenow-flex-users/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Workaround for intermittent Facebook Comment Issues</title>
		<link>http://www.desk.com/blog/workaround-intermittent-facebook-comment-issues/</link>
		<comments>http://www.desk.com/blog/workaround-intermittent-facebook-comment-issues/#comments</comments>
		<pubDate>Thu, 26 Jan 2012 01:39:29 +0000</pubDate>
		<dc:creator>Greg Meyer</dc:creator>
				<category><![CDATA[Product Updates]]></category>

		<guid isPermaLink="false">http://blogadmin.assistly.com/blog/?p=6130</guid>
		<description><![CDATA[Last night we implemented a temporary patch to manage a Facebook API issue.  The issue has caused intermittent problems retrieving Facebook conversations.  As a temporary solution, we&#8217;ve implemented a fix to continuously monitor posts during the last seven days and &#8230; <a href="http://www.desk.com/blog/workaround-intermittent-facebook-comment-issues/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Last night we implemented a temporary patch to manage a <a title="FQL Issue" href="http://developers.facebook.com/bugs/316607451683448?browse=search_4ed918afb1d889f27914723" target="_blank">Facebook API issue</a>.  The issue has caused intermittent problems retrieving Facebook conversations.  As a temporary solution, we&#8217;ve implemented a fix to continuously monitor posts during the last seven days and to import any comments associated with these posts.</p>
<p>We are continuing to  work with our partner, Facebook, to address the underlying issue.</p>
<p>As always, if you have any questions about your account, please <a href="http://support.assistly.com/customer/portal/emails/new">contact us</a> and we will be happy to help.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.desk.com/blog/workaround-intermittent-facebook-comment-issues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Email Notification Log, and Updates to Standard Email Reply Templates</title>
		<link>http://www.desk.com/blog/email-notification-log-updates-standard-email-reply-templates/</link>
		<comments>http://www.desk.com/blog/email-notification-log-updates-standard-email-reply-templates/#comments</comments>
		<pubDate>Fri, 13 Jan 2012 07:05:18 +0000</pubDate>
		<dc:creator>Greg Meyer</dc:creator>
				<category><![CDATA[Product Updates]]></category>

		<guid isPermaLink="false">http://blogadmin.assistly.com/blog/?p=6062</guid>
		<description><![CDATA[&#160; Update &#8211; January 15, 11:07PM : This update was successfully re-applied.  Thanks for your patience. &#160; Update &#8211; January 13, 12:07AM : We identified an Issue with the January 12th update and have had to revert the changes.  We &#8230; <a href="http://www.desk.com/blog/email-notification-log-updates-standard-email-reply-templates/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<p>Update &#8211; January 15, 11:07PM : This update was successfully re-applied.  Thanks for your patience.</p>
<p>&nbsp;</p>
<p><span style="color: #ff0000;">Update &#8211; January 13, 12:07AM : We identified an Issue with the January 12th update and have had to revert the changes.  We will reschedule the update shortly.</span></p>
<p>Tonight&#8217;s Assistly release brings two changes &#8211; one change that may send you a new email notifying you of system errors, and another change that releases new reply, notification, forward, and acknowledgement templates.</p>
<h3>System Error Email now Sent To Site Contact</h3>
<p>When your site has errors in Assistly, we&#8217;d like you to know about them in a timely fashion. Email notification of system error logs is now required &#8211; the Site Contact will now start to get these notifications. We&#8217;re here to help &#8211; so if you get the email and don&#8217;t know whether it&#8217;s an informational message or an error, feel free to  <a href="http://support.assistly.com/customer/portal/emails/new">contact us</a>.</p>
<h3>New Look for Email Templates</h3>
<p>We&#8217;re also releasing some new default templates for the Reply, Notification, Forward, and Auto-Acknowledgement emails you receive from Assistly. <a href="http://www.assistly.com/blog/improving-email-reply-templates/">Here&#8217;s an example</a> of the changes in style (and if you&#8217;ve customized these templates &#8211; don&#8217;t worry &#8211; nothing&#8217;s changing.)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.desk.com/blog/email-notification-log-updates-standard-email-reply-templates/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>We&#8217;re Improving our Email Reply Templates</title>
		<link>http://www.desk.com/blog/improving-email-reply-templates/</link>
		<comments>http://www.desk.com/blog/improving-email-reply-templates/#comments</comments>
		<pubDate>Wed, 11 Jan 2012 02:03:52 +0000</pubDate>
		<dc:creator>Greg Meyer</dc:creator>
				<category><![CDATA[Product Updates]]></category>

		<guid isPermaLink="false">http://blogadmin.assistly.com/blog/?p=6026</guid>
		<description><![CDATA[Thursday night, we will be making a few simple changes to our Email Reply templates &#8211; these are the templates that style the information you send back to your customers using Assistly. What&#8217;s Changing We&#8217;ve improved the design of these &#8230; <a href="http://www.desk.com/blog/improving-email-reply-templates/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Thursday night, we will be making a few simple changes to our Email Reply templates &#8211; these are the templates that style the information you send back to your customers using Assistly.</p>
<h3>What&#8217;s Changing</h3>
<p>We&#8217;ve improved the design of these templates and also made changes for better compliance in multiple email clients. To demonstrate what&#8217;s changing in our email replay templates, take a look at the same email content, first displayed in the old email template, then in the new template.</p>
<p>An example email, displayed in the old reply template:</p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-6027" style="border-image: initial; border-width: 1px; border-color: black; border-style: solid;" title="emailBefore" src="http://assistlyblog.s3.amazonaws.com/blog/wp-content/uploads/2012/01/emailBefore.png" alt="Default Email Template, Old Version" width="555" height="526" /></p>
<p>The same content, displayed in the new Reply Template:</p>
<p><a href="http://blogadmin.assistly.com/blog/improving-email-reply-templates/newemailreply31/" rel="attachment wp-att-6042"><img class="size-full wp-image-6042 aligncenter" style="border-image: initial; border-width: 1px; border-color: black; border-style: solid;" title="newEmailreply31" src="http://assistlyblog.s3.amazonaws.com/blog/wp-content/uploads/2012/01/newEmailreply311.png" alt="" width="525" height="586" /></a></p>
<h3>What You Need to Do</h3>
<p>If you haven&#8217;t made any changes to your reply template (you&#8217;re using the default), you have two choices:</p>
<ul>
<li>You may adopt the new template, in which case you don&#8217;t need to do anything &#8211; you&#8217;ll get the new email reply template on Thursday night this week.</li>
<li>You may keep the old design by upgrading your account to use Advanced Templates and create a new reply template before Thursday 11 PM Pacific Time.</li>
</ul>
<p>If you&#8217;re already using a custom email reply template today, nothing will change. Your current design will remain unaffected.</p>
<p>Thank you, and if you have any questions, please feel free to <a href="http://support.assistly.com/customer/portal/emails/new">contact us</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.desk.com/blog/improving-email-reply-templates/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Using Textile for Rich Text Markup in Agent Responses</title>
		<link>http://www.desk.com/blog/textile-rich-text-markup-agent-responses/</link>
		<comments>http://www.desk.com/blog/textile-rich-text-markup-agent-responses/#comments</comments>
		<pubDate>Thu, 05 Jan 2012 07:05:19 +0000</pubDate>
		<dc:creator>Greg Meyer</dc:creator>
				<category><![CDATA[Product Updates]]></category>

		<guid isPermaLink="false">http://blogadmin.assistly.com/blog/?p=6000</guid>
		<description><![CDATA[Our latest Assistly release includes support for Textile, a lightweight markup language that allows Agents to preview and send HTML-formatted information back to customers without having to hand-code HTML in their responses. How do I turn on Textile? To enable &#8230; <a href="http://www.desk.com/blog/textile-rich-text-markup-agent-responses/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Our latest Assistly release includes support for <a href="http://en.wikipedia.org/wiki/Textile_(markup_language)">Textile</a>, a lightweight markup language that allows Agents to preview and send HTML-formatted information back to customers without having to hand-code HTML in their responses.</p>
<p><strong>How do I turn on Textile?</strong></p>
<p>To enable Textile for Agent email responses, visit Admin &gt; Channels &gt; Email &gt; Advanced Settings and enabling the option for &#8220;Allow Textile.&#8221;</p>
<p><img class="aligncenter size-full wp-image-6012" title="textile_email_original" src="http://assistlyblog.s3.amazonaws.com/blog/wp-content/uploads/2012/01/textile_email_original.png" alt="Enable Textile in Your Email Responses" width="569" height="414" /></p>
<p>If you&#8217;re using the Q&amp;A feature of your Support Center, you can enable Textile by visiting Admin &gt; Channels &gt; Support Center &gt; Advanced Settings and enabling the option for &#8220;Allow Textile&#8221;.</p>
<p><img class="aligncenter size-full wp-image-6013" title="textile_qna_original" src="http://assistlyblog.s3.amazonaws.com/blog/wp-content/uploads/2012/01/textile_qna_original.png" alt="Enable Textile Response in your Q and A Responses" width="549" height="314" /></p>
<p><strong>How do I preview a Textile-formatted response before I send it?</strong></p>
<p><img class="aligncenter size-full wp-image-6003" title="kbTextilePreview_original" src="http://assistlyblog.s3.amazonaws.com/blog/wp-content/uploads/2012/01/kbTextilePreview_original.jpeg" alt="" width="544" height="173" /></p>
<p><strong>How can I learn more about formatting my responses?</strong></p>
<p>Check out our Knowledge Base Article on <a href="http://support.assistly.com/customer/portal/articles/295943-using-textile-to-create-rich-text-markup-in-agent-responses">Using Textile</a> to get more information and specific examples for formatting content in your responses. If you have additional questions, please <a href="http://support.assistly.com/customer/portal/emails/new">contact us</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.desk.com/blog/textile-rich-text-markup-agent-responses/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Assistly Infrastructure Upgrade 1/7/12: Building a Better, Faster Database</title>
		<link>http://www.desk.com/blog/assistly-infrastructure-upgrade-1712-building-faster-database/</link>
		<comments>http://www.desk.com/blog/assistly-infrastructure-upgrade-1712-building-faster-database/#comments</comments>
		<pubDate>Wed, 28 Dec 2011 22:30:12 +0000</pubDate>
		<dc:creator>gary</dc:creator>
				<category><![CDATA[Product Updates]]></category>

		<guid isPermaLink="false">http://blogadmin.assistly.com/blog/?p=5922</guid>
		<description><![CDATA[In early January, we will be rolling out a major infrastructure upgrade to our database that brings you a faster and more reliable Assistly experience. Here are the details. When:           Saturday, January 7th, 2012   &#8230; <a href="http://www.desk.com/blog/assistly-infrastructure-upgrade-1712-building-faster-database/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><strong>In early January, we will be rolling out a major infrastructure upgrade to our database that brings you a faster and more reliable Assistly experience. Here are the details.</strong></p>
<p><strong>When:<br />
</strong><strong>          Saturday, January 7th, 2012<br />
</strong><strong>          7 PM to 1 AM (next day), Pacific Time</strong></p>
<p>On Saturday, January 7th, 2012, we will be making a substantial upgrade to Assistly’s database infrastructure to improve your experience. During this time, the Assistly Agent and Admin will be unavailable for up to six hours. Your customers will still be able to reach your Help Center. We are confident these enhancements will result in faster performance and increased reliability.</p>
<h3>What is Happening?</h3>
<p>Assistly understands that the integrity and availability of your customers’ information is vital to your business operations and our own success. As a Salesforce.com company, we are deeply investing in the infrastructure that supports your business.</p>
<p>To deliver on the promise of Assistly, we will be upgrading the technology that supports our main database. We will begin the maintenance on Saturday January 7th at 7 PM Pacific Time. Based on our global usage statistics, Saturday evenings are when Assistly has the fewest number of agents working in the system. While we realize there is no perfect time for extended maintenance, we anticipate this schedule will have the least impact on our customers. We hope to make it up to you with an improved experience and we will do our best to minimize the disruption.</p>
<p>In order to fully safeguard your data, we will be taking Assistly offline for four to six hours. We hope to complete our work within four hours — but our number one goal is to safeguard your data, so we are allowing ourselves a full six hours if necessary.</p>
<h3>How do I Prepare?</h3>
<p>During the maintenance, you will not be able to log in to Assistly or use the Admin or Agent interface. Additionally, the API will not be available. However, your customers will still be able to reach your help center. For more information, see <a href="http://www.assistly.com/blog/center-assistly-maintenance/">Your Help Center – Now available during Assistly Maintenance</a>.</p>
<p>During our maintenance windows, your Help Center will be available in “read only” mode. You can take some steps to improve your customers’ experience with your Help Center while it’s in read only mode. For more information, please refer to the help article <a href="http://support.assistly.com/customer/portal/articles/273220-configuring-your-customer-help-center-for-read-only-access">Configuring your Customer Help Center for Read-only Access</a>.</p>
<h3>How do I Monitor the Progress?</h3>
<p>We will provide updates as we begin work and as we move through the process on our <a href="https://twitter.com/#!/assistlyops">@AssistlyOps</a> Twitter account. Please bookmark this page and visit it to follow the progress.</p>
<h3>Details: Building a Better Cloud</h3>
<p>We feel this is an essential upgrade to Assistly and well worth the minor inconvenience of an extended maintenance window.</p>
<p>As way of background, everything in Assistly (including customers and cases) is stored in a high-performance database that is accessed hundreds and thousands of times per second. The speed and reliability of this database is the fundamental building block of your Assistly experience, and it is stored on high-speed hard drives provided by Amazon Web Services — the same web services that Amazon.com uses to provide their online retail storefront, as well as their streaming media services. Amazon Web Services are used by thousands of companies and have become an essential part of the Internet cloud infrastructure.</p>
<p>As a Salesforce.com company, Assistly is able to deeply invest in infrastructure improvements for your benefit. As our growth has accelerated, we’ve started to push against the limits of the basic Amazon Web services. Amazon, as a partner of ours, has identified a high-performance upgrade which allows us to move our database layer to a bare metal direct connect solution. This will increase Assistly’s performance to keep up with your needs, while still allowing us to leverage the power, economy and depth of Amazon’s services.</p>
<p>Thank you in advance for your patience while we perform this critical maintenance that will improve the performance and reliability of our service.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.desk.com/blog/assistly-infrastructure-upgrade-1712-building-faster-database/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Introducing Assistly&#8217;s Browser Support Policy</title>
		<link>http://www.desk.com/blog/introducing-assistlys-browser-support-policy/</link>
		<comments>http://www.desk.com/blog/introducing-assistlys-browser-support-policy/#comments</comments>
		<pubDate>Thu, 15 Dec 2011 00:37:00 +0000</pubDate>
		<dc:creator>Greg Meyer</dc:creator>
				<category><![CDATA[Product Updates]]></category>

		<guid isPermaLink="false">http://blogadmin.assistly.com/blog/?p=5697</guid>
		<description><![CDATA[Assistly strives to support all modern browsers and keep pace with the latest upgrades provided by the major browser providers: namely, Google&#8217;s Chrome, Mozilla&#8217;s Firefox, Apple&#8217;s Safari, and Microsoft&#8217;s Internet Explorer. We wanted to take a minute to share our Browser &#8230; <a href="http://www.desk.com/blog/introducing-assistlys-browser-support-policy/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Assistly strives to support all modern browsers and keep pace with the latest upgrades provided by the major browser providers: namely, Google&#8217;s Chrome, Mozilla&#8217;s Firefox, Apple&#8217;s Safari, and Microsoft&#8217;s Internet Explorer. We wanted to take a minute to share our Browser Support Policy so that you can understand which browser versions work best with Assistly &#8211; both for our Agent tools and for our Support Center web sites.</p>
<h3>What Does it Mean that a Browser is &#8220;Supported&#8221;?</h3>
<p>When we say that a particular browser version is supported, we mean that we have tested it extensively with Assistly and that we prioritize development resources toward fixing any errors or incompatibilities that we discover when using Assistly with those versions. Does this mean that Assistly will stop working with older browser versions (versions no longer supported)? Not at all. On the contrary, we expect that Assistly will continue to operate with older browser versions, perhaps with some slight nuances or incompatibilities, but that major functionality would continue to work unabated.</p>
<p>Here is our official browser support policy:</p>
<h3><strong style="font-size: 13px; line-height: 19px;">Agent Desktop, Admin Panel, Reporting &amp; Analytics</strong></h3>
<p>For our Agent and Administration tools, we support the current and previous major releases of Chrome, Firefox, Internet Explorer, and Safari on a rolling basis. Each time a new version is released, we begin supporting that version and stop supporting the third-oldest version.</p>
<h3><strong style="font-size: 13px; line-height: 19px;">Support Center</strong></h3>
<p>For our Assistly Support Center web sites, we support the current and previous major releases of Chrome, Firefox, and Safari on a rolling basis. Each time a new version is released, we begin supporting that version and stop supporting the third-oldest version. <em>For Internet Explorer, we will support the current and two previous major releases</em>.</p>
<p>Based on expected release schedules, we currently support the following browsers in December 2011:</p>
<p><strong style="font-size: 13px; line-height: 19px;">Agent Desktop, Admin Panel, Reporting &amp; Analytics</strong></p>
<div>
<ul>
<li>Chrome 15 &amp; 16</li>
<li>Internet Explorer 8 &amp; 9</li>
<li>Firefox 8 &amp; 9 (Firefox 9 expected to release late next month)</li>
<li>Safari 4 &amp; 5</li>
</ul>
</div>
<p><strong style="font-size: 13px; line-height: 19px;">Support Center</strong></p>
<div>
<ul>
<li>Chrome 15 &amp; 16</li>
<li>Internet Explorer 7, 8 &amp; 9</li>
<li>Firefox 8 &amp; 9</li>
<li>Safari 4 &amp; 5</li>
</ul>
</div>
<p>As always, if you have any questions or feedback, please <a style="font-size: 13px; line-height: 19px;" href="http://support.assistly.com/customer/portal/emails/new">contact us</a>.</p>
<p style="font-size: 10px;">Note: This post was updated on 12/15/11 to make the following clarifications: 1) our policy begins in January 2011; 2) Chrome 16 is already released; and 3) our note on Firefox 3.6 was removed as that is no longer a supported browser.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.desk.com/blog/introducing-assistlys-browser-support-policy/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

