<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>ChurchLead</title>
<link>https://www.churchlead.com</link>
<atom:link href="https://www.churchlead.com/inc/blog?blog=1223" rel="self" type="application/rss+xml" />
<description>I began ChurchLead to help churches become more effective through leadership development, strategy creation, tactical planning and technology utilization.</description>

<item>
<title>Take Responsibility for Visitor Connection</title>
<link>https://www.churchlead.com/home/view/1716</link>
<pubDate>Fri, 22 Jul 2011 23:46:00 CDT</pubDate>
<author>Rob Overton</author>
<guid>https://www.churchlead.com/home?blogm=view&amp;blogid=1716</guid>
<description><![CDATA[<font size="2"><em><img vspace="4" hspace="4" border="0" align="right" src="https://o.b5z.net/i/u/6077994/i/top7-125.jpg" alt="" />This is the first installment of the series: <a href="http://www.churchlead.com/home/view/1712/top_7_ways_to_connect_visitors_to_your_church">The Top 7 Ways to Connect Visitors to Your Church</a></em></font><strong><br />
<br />
1. Take Responsibility for Visitor Connection</strong><br />
<br />
The fundamental question that must be answered before building a visitor connection process is <em>&quot;Who's job is it to connect visitors to your church?&quot;</em>&nbsp;  Historically, the burden has fallen to the visitor to connect  themselves.&nbsp; This sounds silly, but most churches respond to a first  visit with a letter, postcard or even gifts.&nbsp; Then they wait for the visitor to  return so that they can respond again.&nbsp; This puts the next move  squarely on the shoulders of the visitor. &nbsp; I believe that pastors and  staff must take responsibility for visitors as an issue of stewardship.&nbsp;  A new visitor, or even an entire family,&nbsp; represents a gift with which  God has entrusted to you and your church. This should not be taken lightly.&nbsp; When I work with pastors who are  struggling to determine an effective connecting process, I ask this  question:&nbsp; <br />
<blockquote>
<div align="center">     <hr width="100%" size="2" />
<font size="4" face="Times New Roman"><em><strong>What actions would constitute faithful stewardship of the<br />
gift (the visitor) that God gave you?</strong></em></font><br />
<br />
<em><font size="4" face="Times New Roman"><strong>The answer to this question should become your connection process.&nbsp;</strong> </font></em><br />
<hr width="100%" size="2" />
</div>
</blockquote> It  is fine to acknowledge a second or third visit if they let you know by  filling out your welcome card or signing your book again.&nbsp; In fact, you  <em>had better</em> respond.&nbsp; The problem is that this is NOT a connection  process!&nbsp; It is just a reaction to what happened.&nbsp; We all know by now  that any visitor who attends three times is highly likely to join a  church.&nbsp; But what do you do that increases the chance of that actually happening?&nbsp; A connection process where the church has accepted the  responsibility of connecting visitors to them will involve proactive contacts that encourage  involvement regardless of whether or not a visitor returns right away.&nbsp;  In addition, the <em>quality </em>of the contacts will be&nbsp; higher than a  standard form letter or e-mail.&nbsp; Perhaps a phone call rather than a  letter.&nbsp; It could even involve a Facebook or texting conversation.&nbsp; The  best method must be determined by the situation at hand and what action  would have the highest chance of making the visitor feel welcome and  accepted.&nbsp; People respond to a genuine interest in their lives.&nbsp; They will spot an obligatory phone call a mile away!&nbsp; <br />
<div align="center"><blockquote><em><font size="4" face="Times New Roman"><strong>Real responsibility involves using methods that<br />
have a high probability of being effective.</strong><br />
</font></em></blockquote></div>
<hr width="100%" size="2" />
Next: 2. Focus on Households]]></description>
</item>

</channel>
</rss>

