<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.method.me/cs/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Method:Classic General Q&amp;amp;A</title><link>http://forums.method.me/cs/forums/13.aspx</link><description>Ask technical support questions, how do I? Questions... Or anything else you want to know from the Method Team and other Method users.</description><dc:language>en</dc:language><generator>CommunityServer 2007.1 SP2 (Build: 31113.47)</generator><item><title>Re: Case vs Activity</title><link>http://forums.method.me/cs/forums/thread/411.aspx</link><pubDate>Mon, 26 Jan 2009 15:39:17 GMT</pubDate><guid isPermaLink="false">3393c1ec-311b-4812-96cb-ad8c611bba4f:411</guid><dc:creator>Method_Valbon</dc:creator><slash:comments>0</slash:comments><comments>http://forums.method.me/cs/forums/thread/411.aspx</comments><wfw:commentRss>http://forums.method.me/cs/forums/commentrss.aspx?SectionID=13&amp;PostID=411</wfw:commentRss><description>&lt;p&gt;Hi Matt,&lt;br /&gt;&lt;br /&gt;You&amp;#39;ve definitely got the right idea about opportunities linking multiple activities for sales.&amp;nbsp; Now try to think of a campaign as a group of resources with a common goal while the lead source is the actual resources available for your campaigns. Some campaigns can be simple such as promoting a new product at a trade show where the name of the show may be the campaign and &amp;lsquo;Trade Show&amp;rsquo; can end up being the lead source. On the other hand promoting the same product can sometimes have multiple resources assigned to it and might include attending the trade show, mailing prospective customers, advertisements in publications and cold-calling. For this type of campaign you&amp;#39;d want to identify the correct lead source that brings the customer in, how did they hear about the new product?&lt;br /&gt;&lt;br /&gt;Hope that helps,&lt;br /&gt;&lt;/p&gt;</description></item><item><title>Re: Case vs Activity</title><link>http://forums.method.me/cs/forums/thread/409.aspx</link><pubDate>Fri, 23 Jan 2009 23:01:19 GMT</pubDate><guid isPermaLink="false">3393c1ec-311b-4812-96cb-ad8c611bba4f:409</guid><dc:creator>Matt</dc:creator><slash:comments>0</slash:comments><comments>http://forums.method.me/cs/forums/thread/409.aspx</comments><wfw:commentRss>http://forums.method.me/cs/forums/commentrss.aspx?SectionID=13&amp;PostID=409</wfw:commentRss><description>&lt;p&gt;Let me take this one step further.&lt;/p&gt;
&lt;p&gt;A case is a way to link multiple activites for a complaint....&lt;/p&gt;
&lt;p&gt;So an opportunity must be a way to link multiple activites that hopefully lead to a sale. Is that correct?&lt;/p&gt;
&lt;p&gt;Also, what is the difference (When creating an opportunity) between lead source and campaign? Wouldn&amp;#39;t all lead sources be a campaign (even though some lead sources such as word of mouth, or saw a crew at a jobsite are technically campaigns)?&lt;/p&gt;</description></item><item><title>Re: Case vs Activity</title><link>http://forums.method.me/cs/forums/thread/408.aspx</link><pubDate>Fri, 23 Jan 2009 22:51:53 GMT</pubDate><guid isPermaLink="false">3393c1ec-311b-4812-96cb-ad8c611bba4f:408</guid><dc:creator>Matt</dc:creator><slash:comments>0</slash:comments><comments>http://forums.method.me/cs/forums/thread/408.aspx</comments><wfw:commentRss>http://forums.method.me/cs/forums/commentrss.aspx?SectionID=13&amp;PostID=408</wfw:commentRss><description>&lt;p&gt;In a nut shell... a case is a way to link multiple related activites.&lt;/p&gt;
&lt;p&gt;Thank you. Yes that does make a lot more sense.&lt;/p&gt;</description></item><item><title>Re: Case vs Activity</title><link>http://forums.method.me/cs/forums/thread/407.aspx</link><pubDate>Fri, 23 Jan 2009 20:11:58 GMT</pubDate><guid isPermaLink="false">3393c1ec-311b-4812-96cb-ad8c611bba4f:407</guid><dc:creator>Anonymous</dc:creator><slash:comments>0</slash:comments><comments>http://forums.method.me/cs/forums/thread/407.aspx</comments><wfw:commentRss>http://forums.method.me/cs/forums/commentrss.aspx?SectionID=13&amp;PostID=407</wfw:commentRss><description>&lt;p&gt;Hi Matt,&lt;/p&gt;
&lt;p&gt;Well, really the ultimate choice will be up to you as to whether calls should be entered as cases or activities.&amp;nbsp; But, hopefully I can shed some light on the situation for you to make things clearer.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;An Activity is an individual task that someone does, such as recording an email received, or making an outgoing phone call.&amp;nbsp; You can log these in individually and track them by user or you can view them in the Sales Center or Call Center dashboard, etc.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;A Case is one or more activities that are related to a particular outstanding issue, concern, or problem that a customer is trying to have resolved.&amp;nbsp; A case would be opened for this customer and all activites that are performed in trying to resolve this issue can be related back to that particular instance via the Case Number.&amp;nbsp; Then, once resolved, you can post a Solution for the issue so that others who view the record can see how the situation was resolved for that customer.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;I used to work at a call center as an inbound call rep a few years ago.&amp;nbsp; We took inbound calls for an auto manufacturer.&amp;nbsp; Calls would range from compliments (although &lt;em&gt;VERY RARE&lt;/em&gt;!), to warranty issues, to &lt;strong&gt;MY CAR&amp;#39;S A LEMON&lt;/strong&gt; complaints (those were always the fun ones!).&amp;nbsp; For every inbound call we received, we created a new case and entered a new activity right away for that case.&amp;nbsp; The activity reflected the inbound call that we received.&amp;nbsp; Now that case could be tracked in a variety of ways, and provided other reps with details of what transpired on the call.&amp;nbsp; We used to have to sometimes deliver some bad news to the customer and it was commonplace for disgruntled customers to&amp;nbsp;call up again in hopes to receive a different rep who might give them a different answer!&amp;nbsp; No such luck for them because once saved, any rep could pull up a case and see everything that was going on and everything that was already&amp;nbsp;done for that customer.&amp;nbsp; &lt;/p&gt;
&lt;p&gt;We were evaluated on our &amp;quot;One Call Resolution&amp;quot; which was a goal in which we strived to resolve most customer complaints in just one call, preventing the need for us or the customer to have to make another call before closing the case.&amp;nbsp; The call center manager can create a report based on cases that shows him/her the average number of calls it takes for a customer&amp;#39;s issue to be resolved.&amp;nbsp; The manager can then use this data to try and enhance the &amp;#39;one call resolution&amp;#39; procedures already in place. &lt;/p&gt;
&lt;p&gt;So, really it&amp;#39;s up to you how you should enter inbound calls.&amp;nbsp; Hopefully I&amp;#39;ve made the differences between Activities and Cases clearer for you.&amp;nbsp; &lt;img src="http://methodintegration.com/cs/emoticons/emotion-2.gif" alt="Big Smile" /&gt;&lt;/p&gt;</description></item><item><title>Case vs Activity</title><link>http://forums.method.me/cs/forums/thread/406.aspx</link><pubDate>Fri, 23 Jan 2009 18:49:48 GMT</pubDate><guid isPermaLink="false">3393c1ec-311b-4812-96cb-ad8c611bba4f:406</guid><dc:creator>Matt</dc:creator><slash:comments>0</slash:comments><comments>http://forums.method.me/cs/forums/thread/406.aspx</comments><wfw:commentRss>http://forums.method.me/cs/forums/commentrss.aspx?SectionID=13&amp;PostID=406</wfw:commentRss><description>&lt;p&gt;&amp;nbsp;I&amp;#39;m just trying to get a better feel for the logic that went into setting up the CRM the way it is. Hypothetically...... If our company receives a phone call, should it be logged as a case or an activity with the type of phone call? Or both? and Why? &lt;/p&gt;</description></item></channel></rss>