LDSTechForumProjects

Talk:Administrative office

(Redirected from Talk:Administration office)

On 21 Sep 2007 a Tip of the Week about assisting wards with issues was created. Local Unit Support requested content from this tip to be added to the Clerk Wiki. The tip focused on Local Unit Support and applied to US and Canada units so it was added under that part of the page. Petersenga 15:06, 30 April 2009 (UTC)

The principle of clerks first contacting their stake clerk is relevant worldwide, so I have moved that part of the article to the lead. The other changes were to take out unnecessary headings and convert them to bullet points. --Steve 18:40, 1 May 2009 (UTC)
Why does the content added from the 21 Sep 2007 Tip of the Week use a different e-mail address for Local Unit Support? In the section "Anywhere in the world" we see the msrmail@ldsmail.net address, but in the Local Unit Support section, we see the mlssupport@ldschurch.org address. I don't see why they should be different, and since the topic is any "clerk-related issue," the "mlssupport" address seems like its scope is too narrow. Is there any reason not to change the Local Unit Support e-mail address to be msrmail@ldsmail.net? -- Aebrown 18:46, 1 May 2009 (UTC)
Speaking as an employee of the team, the msrmail@ldsmail.net address is the real only line of contact to reach the team. The other address is for outgoing messages that we will send to stake and personal email accounts. Hope this clarifies things a little bit. I have edited the page to reflect the change. Thanks for the input brethren :). --Caleb 19:53, 1 May 2009 (UTC)
I agree with Caleb. In addition, I will check more carefully before I include information from the Clerk and Technology Specialist Site. Apparently, information there is not as accurate as it should be. I will also go to that site and change the e-mail address. Petersenga 20:01, 1 May 2009 (UTC)
This page was last modified on 21 April 2011, at 12:30.

Note: Content found in this wiki may not always reflect official Church information. See Terms of Use.