<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.tntware.com/tntconnect/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>Task Types</title><link>https://www.tntware.com/tntconnect/help/en/pages/taskhistory-tasktypes.aspx</link><description>Task Types &amp;quot;Task Types&amp;quot; are used for both tasks you have not completed (the &amp;quot;scheduled tasks&amp;quot;) as well as the ones you have completed (&amp;quot;history&amp;quot;). Most of the time, tasks are not scheduled. For example, because you can use</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Debug Build: 40407.4157)</generator><item><title>re: Task Types</title><link>https://www.tntware.com/tntconnect/help/en/pages/taskhistory-tasktypes.aspx#26078</link><pubDate>Mon, 12 May 2014 20:27:23 GMT</pubDate><guid isPermaLink="false">1fa7c37c-d68d-46f5-9639-4669b01a21c5:26078</guid><dc:creator>rynetyme</dc:creator><description>&lt;p&gt;That&amp;#39;s perfect!! Thank you so much for the detailed response. God bless you and this ministry tool! &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://www.tntware.com/tntconnect/aggbug.aspx?PostID=26078" width="1" height="1"&gt;</description></item><item><title>re: Task Types</title><link>https://www.tntware.com/tntconnect/help/en/pages/taskhistory-tasktypes.aspx#26077</link><pubDate>Mon, 12 May 2014 20:22:10 GMT</pubDate><guid isPermaLink="false">1fa7c37c-d68d-46f5-9639-4669b01a21c5:26077</guid><dc:creator>Bob Mac Leod</dc:creator><description>&lt;p&gt;rynetyme--&lt;/p&gt;
&lt;p&gt;Good news! There is already a task type for exactly the situation you describe. A PRE-CALL LETTER is the task type for the letter you send in advance of your initial contact with a person. A SUPPORT LETTER is what is used when you are asking an existing ministry partner to give a gift of some kind (typically a special gift, and associated with a &amp;quot;Special Gift Appeal&amp;quot;. A &amp;quot;LETTER&amp;quot; is any other personal communication, which typically means hand-written. This could be a &amp;#39;letter&amp;#39;, but it could also be a &amp;quot;Thinking of You&amp;quot; note card, a Sympathy card, etc.&lt;/p&gt;
&lt;p&gt;This may be more than you asked for, but here&amp;#39;s some more expansion on this topic...&lt;/p&gt;
&lt;p&gt;If the &amp;#39;letter&amp;#39; is *intended* as a Thank You, then typically the THANK task type would be used. As I see it, function always trumps form, so I use &amp;quot;Thank&amp;quot; task type for a Thank, regardless of how I completed the thank (letter, card, call, email). BUT, if the primary function is a different task type, then I choose that type and just mark it as a Thank in the Details tab. For example, if I personally visit a partner to thank him for a gift, then I record it as an APPOINTMENT, with the Thank box checked. Or if I send them a gift as a token of my appreciation for their part in my ministry, I record it as a PRESENT, with the Thank box checked. The gift was an *expression* of thanks, but the primary purpose was to send a Present. (Note the word &amp;quot;present&amp;quot; instead of a &amp;quot;gift&amp;quot;; this helps differentiate between a *gift* that a donor gives vs. a *present* implying a tangible object given to/from me.)&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://www.tntware.com/tntconnect/aggbug.aspx?PostID=26077" width="1" height="1"&gt;</description></item><item><title>re: Task Types</title><link>https://www.tntware.com/tntconnect/help/en/pages/taskhistory-tasktypes.aspx#26076</link><pubDate>Mon, 12 May 2014 20:05:19 GMT</pubDate><guid isPermaLink="false">1fa7c37c-d68d-46f5-9639-4669b01a21c5:26076</guid><dc:creator>rynetyme</dc:creator><description>&lt;p&gt;Just curious would you consider the initial contact you make through a letter that details your ministry, what you are doing, and informs the potential you will be calling to set-up an appointment to talk about support and vision a &amp;quot;letter&amp;quot; or a &amp;quot;support letter&amp;quot; under the tasks? You mentioned &amp;quot;letter&amp;quot; was for more personal use, but that &amp;quot;support letter&amp;quot; was for someone who was already on your team. Thanks for the help.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://www.tntware.com/tntconnect/aggbug.aspx?PostID=26076" width="1" height="1"&gt;</description></item><item><title>re: Task Types</title><link>https://www.tntware.com/tntconnect/help/en/pages/taskhistory-tasktypes.aspx#8662</link><pubDate>Sat, 01 May 2010 01:25:00 GMT</pubDate><guid isPermaLink="false">1fa7c37c-d68d-46f5-9639-4669b01a21c5:8662</guid><dc:creator>Bob Mac Leod</dc:creator><description>&lt;p&gt;A new edition of TntMPD Help was posted today, with the task types updated as you suggested. There is also a topic specifically on &amp;quot;Mass Mailings&amp;quot; and the Newsletter task type.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://www.tntware.com/tntconnect/aggbug.aspx?PostID=8662" width="1" height="1"&gt;</description></item><item><title>re: Task Types</title><link>https://www.tntware.com/tntconnect/help/en/pages/taskhistory-tasktypes.aspx#7552</link><pubDate>Mon, 11 Jan 2010 16:43:18 GMT</pubDate><guid isPermaLink="false">1fa7c37c-d68d-46f5-9639-4669b01a21c5:7552</guid><dc:creator>John Fleming</dc:creator><description>&lt;p&gt;Troy and Friends: this page needs to be updated to show the latest version&amp;#39;s list of tasks, including the new NEWSLETTER option, which I am grateful was added since &amp;quot;Letter&amp;quot; was somewhat ambiguous and the other task types didn&amp;#39;t really seem to match up to a true newsletter mailing.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="https://www.tntware.com/tntconnect/aggbug.aspx?PostID=7552" width="1" height="1"&gt;</description></item></channel></rss>