<?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>iDesk Support &#187; iDesk</title>
	<atom:link href="http://www.idesksupport.com/category/tips-hints-and-information-about-idesk/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.idesksupport.com</link>
	<description>Support, Tips, Hints, Guides and more for iDesk</description>
	<lastBuildDate>Fri, 01 May 2009 19:07:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>User profiles</title>
		<link>http://www.idesksupport.com/2009/05/01/user-profiles/</link>
		<comments>http://www.idesksupport.com/2009/05/01/user-profiles/#comments</comments>
		<pubDate>Fri, 01 May 2009 19:07:00 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[iDesk]]></category>

		<guid isPermaLink="false">http://www.idesksupport.com/2009/05/01/user-profiles/</guid>
		<description><![CDATA[The user profile is probably one of the most boring pages on iDesk. It serves very little function other than to change an email address or a password.
But there are two important items on the user profile.
The first is Ticket Notification. If your help desk isn&#8217;t busy you can check this box and iDesk will [...]]]></description>
			<content:encoded><![CDATA[<p>The user profile is probably one of the most boring pages on iDesk. It serves very little function other than to change an email address or a password.</p>
<p>But there are two important items on the user profile.</p>
<p>The first is Ticket Notification. If your help desk isn&#8217;t busy you can check this box and iDesk will send you an email when you receive a ticket or a ticket is replied to in the department you are assigned to.</p>
<p>The second is ticket signature. A signature can actually save you time even if it&#8217;s only to save you from typing your name at the bottom of each email reply.</p>
<p>Of course you can always do something interesting like include a coupon code in your signature or a link to your signup page or shopping cart.</p>
<p>Anywhere that you can help to market yourself is a great help for your business. Remember to use the user profile to help you in this regard.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.idesksupport.com/2009/05/01/user-profiles/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Departments (again)</title>
		<link>http://www.idesksupport.com/2009/04/26/departments-again/</link>
		<comments>http://www.idesksupport.com/2009/04/26/departments-again/#comments</comments>
		<pubDate>Sun, 26 Apr 2009 18:58:00 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[iDesk]]></category>

		<guid isPermaLink="false">http://www.idesksupport.com/2009/04/26/departments-again/</guid>
		<description><![CDATA[Personally I just can&#8217;t get enough of the use of departments.
They are so useful and helpful in organizing your support requests. Lets take Nicecoders help desk as an example. We currently have 8 departments.
Eight? Yes.
One department for general support. Then one department for each of our products as &#8220;level 2&#8243; support. Then a department for [...]]]></description>
			<content:encoded><![CDATA[<p>Personally I just can&#8217;t get enough of the use of departments.</p>
<p>They are so useful and helpful in organizing your support requests. Lets take Nicecoders help desk as an example. We currently have 8 departments.</p>
<p>Eight? Yes.</p>
<p>One department for general support. Then one department for each of our products as &#8220;level 2&#8243; support. Then a department for custom work, installations and license issues.</p>
<p>Generally tickets are assigned to the department they are sent to. Emails to support get sent to the General department. Emails to custom are sent to the custom work department and so on.</p>
<p>This helps us to know ahead of time what the issue might be. It also helps us to know who is supposed to look at a particular ticket. For example, for iDesk Level 2 Support the person who looks at those tickets is Dewa, who is the iDesk programmer.</p>
<p>But as I said in a previous article, the Level 2 Departments are not available to users. Meaning that a user can not send a ticket to any Lever 2 department.</p>
<p>We do this creating the department and making it a Staff Only department. Then when a request comes in to support and it requires Level 2 support, we simply assign it to the appropriate Level 2 Department and that user then takes care of it.</p>
<p>It&#8217;s an excellent way to process tickets and to ensure that the right user sees what they are supposed to.</p>
<p>If you want to go further, you can assign users so that the only tickets they will see are tickets in one specific department. This helps to ensure that you&#8217;re not wasting a programmers time by making them wade through simple support requests so they can find the one ticket they need to asnwer.</p>
<p>Departments help to save time, allow for faster response times from the people who need to view tickets and offer better internal organization.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.idesksupport.com/2009/04/26/departments-again/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Messaging System</title>
		<link>http://www.idesksupport.com/2009/04/23/messaging-system/</link>
		<comments>http://www.idesksupport.com/2009/04/23/messaging-system/#comments</comments>
		<pubDate>Thu, 23 Apr 2009 18:53:00 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[iDesk]]></category>

		<guid isPermaLink="false">http://www.idesksupport.com/2009/04/23/messaging-system/</guid>
		<description><![CDATA[One of the nice features of iDesk is the Message system.
The Message system can be used to send a message to all staff or to an individual staff member.
Sending a Message to all staff would be like making an announcement. Lets say for instance that you ran a large web host and you have 8 [...]]]></description>
			<content:encoded><![CDATA[<p>One of the nice features of iDesk is the Message system.</p>
<p>The Message system can be used to send a message to all staff or to an individual staff member.</p>
<p>Sending a Message to all staff would be like making an announcement. Lets say for instance that you ran a large web host and you have 8 staff on the help desk who all worked in different locations.</p>
<p>You could send out an email to everyone, but you&#8217;re not always sure email will be received. You could call them, but that can take a whole bunch of time and has a physical cost associated with it in the form of long distance.</p>
<p>Instead you could message all of your staff to inform them that the server will be undergoing maintenance at 11:00 PM so that when they receive support tickets, your staff don&#8217;t have to try and troubleshoot the issue. They already know about and can inform the customers.</p>
<p>Using the Message feature of iDesk is a convenient way to communicate with your staff and since they are already using the help desk, there is no need to use a secondary method of communication.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.idesksupport.com/2009/04/23/messaging-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The knowledgebase</title>
		<link>http://www.idesksupport.com/2009/04/21/the-knowledgebase-2/</link>
		<comments>http://www.idesksupport.com/2009/04/21/the-knowledgebase-2/#comments</comments>
		<pubDate>Tue, 21 Apr 2009 18:51:19 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[iDesk]]></category>

		<guid isPermaLink="false">http://www.idesksupport.com/2009/04/21/the-knowledgebase-2/</guid>
		<description><![CDATA[What can I say about the knowledgebase other than it can save you a ton of support requests.
By offering up frequently asked questions that are sorted by category, users can find out all the basic items they really want to know.
Categories you can offer can be as simple as

How to contact us
How to cancel your [...]]]></description>
			<content:encoded><![CDATA[<p>What can I say about the knowledgebase other than it can save you a ton of support requests.</p>
<p>By offering up frequently asked questions that are sorted by category, users can find out all the basic items they really want to know.</p>
<p>Categories you can offer can be as simple as</p>
<ul>
<li>How to contact us</li>
<li>How to cancel your account</li>
<li>Hours of operation</li>
<li>Telephone support and sales numbers</li>
<li>Version numbers for the latest versions of your software</li>
<li>Your billing address or mailing address</li>
<li>Forms of payment that you accept</li>
<li>Anything else you can think of!</li>
</ul>
<p>Of course you can always offer more detailed issues as well, going as far as to show how to fix particular issues in some situations or procedures on how to fix/repair commonly broken things.</p>
<p>The knowledgebase is typically underutilized. By putting in some time and building a thorough KB you can help yourself out as well as your customers and potential customers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.idesksupport.com/2009/04/21/the-knowledgebase-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The schedule system</title>
		<link>http://www.idesksupport.com/2009/01/27/the-schedule-system/</link>
		<comments>http://www.idesksupport.com/2009/01/27/the-schedule-system/#comments</comments>
		<pubDate>Tue, 27 Jan 2009 23:11:01 +0000</pubDate>
		<dc:creator>Bruce</dc:creator>
				<category><![CDATA[iDesk]]></category>

		<guid isPermaLink="false">http://www.idesksupport.com/2009/01/27/the-schedule-system/</guid>
		<description><![CDATA[Admins can add scheduled items under the Management menu. Adding a scheduled item is quite easy.
Simply click on Add (the green plus sign), choose the time that you want the scheduled item to be performed and the description of the item and then click Add.
Now when you click on Schedule (under Management) you and your [...]]]></description>
			<content:encoded><![CDATA[<p>Admins can add scheduled items under the Management menu. Adding a scheduled item is quite easy.</p>
<p>Simply click on Add (the green plus sign), choose the time that you want the scheduled item to be performed and the description of the item and then click Add.</p>
<p>Now when you click on Schedule (under Management) you and your staff will see the new scheduled item. The Done column will be blank until the user click on Toggle Done.</p>
<p>This way you can check on users to make sure they are checking their schedule, and performing any tasks that you have assigned.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.idesksupport.com/2009/01/27/the-schedule-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
