<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Latest posts for the topic "Speedy SR Entry"]]></title>
		<link>http://www.sysaid.com/Sysforums/posts/list/112.page</link>
		<description><![CDATA[Latest messages posted in the topic "Speedy SR Entry"]]></description>
		<generator>JForum - http://www.jforum.net</generator>
			<item>
				<title>Speedy SR Entry</title>
				<description><![CDATA[ I want to start up a discussion on any possible ideas that would make admin SR entry any faster. We have yet to fully incorporate SysAid into our organization due to the amount of time it takes for us to input them, especially as our organization is experiencing much growth. Idea's anyone?<br /> <br /> One idea I have is for Ilient to spend a lot of time continuing to familiarize themselves with ajax technology. The more ajax we can get in there, the more options there are for speed, at least in my opinion.]]></description>
				<guid isPermaLink="true">http://www.sysaid.com/Sysforums/posts/preList/3364/15272.page</guid>
				<link>http://www.sysaid.com/Sysforums/posts/preList/3364/15272.page</link>
				<pubDate><![CDATA[Mon, 14 Dec 2009 08:42:25]]> GMT</pubDate>
				<author><![CDATA[ RGarber]]></author>
			</item>
			<item>
				<title>Re:Speedy SR Entry</title>
				<description><![CDATA[ Hey RGarber...<br /> <br /> Since version 6.5, we have included Ajax compatibilities in some places in SysAid. Our prospective is to expand this on all SysAid modules. This functionality will be on our future releases. <br /> <br /> Best Regards.<br /> Ori Sharon.]]></description>
				<guid isPermaLink="true">http://www.sysaid.com/Sysforums/posts/preList/3364/15280.page</guid>
				<link>http://www.sysaid.com/Sysforums/posts/preList/3364/15280.page</link>
				<pubDate><![CDATA[Mon, 14 Dec 2009 10:11:19]]> GMT</pubDate>
				<author><![CDATA[ Ori]]></author>
			</item>
			<item>
				<title>Speedy SR Entry</title>
				<description><![CDATA[ RGarber,<br /> <br /> I suppose to only advise I could offer is;<br /> <br /> Either use the Phone Call Page to capture the basics or Use the New SR with quicklist items. You can set up quicklist items which is only visible to the admins.<br /> <br /> The quicklist option will cut down on the entry time.<br /> <br /> My three cents worth!!!???<br /> ]]></description>
				<guid isPermaLink="true">http://www.sysaid.com/Sysforums/posts/preList/3364/15297.page</guid>
				<link>http://www.sysaid.com/Sysforums/posts/preList/3364/15297.page</link>
				<pubDate><![CDATA[Mon, 14 Dec 2009 20:10:57]]> GMT</pubDate>
				<author><![CDATA[ SysAid#1]]></author>
			</item>
			<item>
				<title>Re:Speedy SR Entry</title>
				<description><![CDATA[ We already use the phone call page, which we suitably renamed (in our translation file) "Quick Entry". The problem is that we're a very small IT operation for a company that has nearly 30 branch offices. We are constantly on the phone and we simply cant keep up with call volume. To add on to these details, there aren't many problems that occur often. Our phone calls' topics vary quite a bit, making it nearly impossible to plan them all out in efforts to create quicklist entries.<br /> <br /> Advice? Let it be known that my boss wants to put as little work as possible on the end user.<br /> <br /> Also, as a side note, I'd like to make clear that I do understand that Ilient is indeed attempting to dive into ajax technology. My comment was merely an "i'm looking forward to.." type of thing. The more ajax we get, the less popup windows we need to load to fill in an SR. For example, specifying the end user pops up a separate browser window for our selection. If we could have something similar to "google suggestions" where, as we type, sysaid can quickly figure out the name we're in the process of typing and allow us to simply select it and it would finish filling in the box and complete the end user "attachment" to the SR.]]></description>
				<guid isPermaLink="true">http://www.sysaid.com/Sysforums/posts/preList/3364/15322.page</guid>
				<link>http://www.sysaid.com/Sysforums/posts/preList/3364/15322.page</link>
				<pubDate><![CDATA[Tue, 15 Dec 2009 08:28:31]]> GMT</pubDate>
				<author><![CDATA[ RGarber]]></author>
			</item>
			<item>
				<title>Speedy SR Entry</title>
				<description><![CDATA[ RGarber,<br /> <br /> You do indeed have a unique situation. Do you think the incoming email option will work??<br /> <br /> Users send emails all day, so sending one about a problem should not bother them too much??<br /> <br /> ]]></description>
				<guid isPermaLink="true">http://www.sysaid.com/Sysforums/posts/preList/3364/15337.page</guid>
				<link>http://www.sysaid.com/Sysforums/posts/preList/3364/15337.page</link>
				<pubDate><![CDATA[Tue, 15 Dec 2009 17:18:05]]> GMT</pubDate>
				<author><![CDATA[ SysAid#1]]></author>
			</item>
			<item>
				<title>Speedy SR Entry</title>
				<description><![CDATA[ RGarber,<br /> <br /> I have to say I agree with SysAid#1. Maybe the issue you need to address isn't how your team are entering in SysAid, but more the education of your users.<br /> <br /> I had a similar issue when first implementing at my company, where I am a one-man IT department. I was finding call volumes and entering into SysAid wasn't working. The only solution was to re-educate the users to use SysAid themselves. <br /> <br /> I now have a great system (after much time and effort :p ) whereby most tickets will come through either the EUP or via email, with only major faults (the computer won't start) coming via the phone. This does not add any time for the user, because rather than being on the phone they can spend that same time writing the emails or filling out the online form.<br /> <br /> Would this be an option for you?<br /> <br /> M]]></description>
				<guid isPermaLink="true">http://www.sysaid.com/Sysforums/posts/preList/3364/15415.page</guid>
				<link>http://www.sysaid.com/Sysforums/posts/preList/3364/15415.page</link>
				<pubDate><![CDATA[Fri, 18 Dec 2009 06:50:07]]> GMT</pubDate>
				<author><![CDATA[ BJINS]]></author>
			</item>
	</channel>
</rss>