[civsa] Ambassador Leadership Teams

Wed Oct 5 13:33:00 CDT 2016

Hi Molly!
We are in the same boat! Here are a few things we've started doing.. One of our Ambassadors started a Group Me text group and they communicate REALLY well there. I have one of the Student Ambassadors manage the logistics of who all is in it and he acts as my liaison .. so if I need to get the word out he does it for me.  I have found sometimes they listen to each other better than me and when you find the medium that they all are in tune with you get a better response from them!
[cid:image001.jpg at 01D21F15.564E9310]
I have also started a weekly newsletter that goes out on Friday's.. just a few bullet points and they seem to really enjoy it.  I think the newsletter is also something that I will be having a student ambassador take over next year as well.. they know best how to connect with one another and then I just make sure I have them add the things that I need them to know! I've attached our last week's edition for you to see.

We have a long way to go but we are on the right path here. Best of luck to you and let me know if you have any other questions or suggestions for us!
Take care,
Erin

Erin M West
Visit Coordinator
Office of Admission
University of Mount Union
330-829-2769
westem at mountunion.edu
[Color Logo and Tagline - small]

From: listserv [mailto:listserv-bounces at civsa.org] On Behalf Of Winter M. Aguilar
Sent: Wednesday, October 05, 2016 2:18 PM
To: listserv at civsa.org
Subject: Re: [civsa] Ambassador Leadership Teams

At Texas Wesleyan we have something a little different when it comes to leadership positions.

We currently have 17 student tour guides. 5 are in our leadership positions. Here's the breakdown:

1)      Student Director of Tour Guides - reports directly to me. Oversees entire program, conducts training sessions every month, assists with the hiring process of new tour guides, and acts in my place with the group should I not be available.

2)      What we call our "District Heads" (thanks to the popular Hunger Games) - each District Head is in charge of 3 other tour guides. Our District Heads are veteran tour guides and are there to guide the newbies and keep the order of things flowing. But they also have outside responsibilities listed below.

a.       District Head 1 - Office Liaison

                                                               i.      Point of contact for any communication between the Office of Admission and the tour guide program. Specifically in regards to our university program dates where we need tour guides to work.

b.      District Head 2 - Campus Liaison

                                                               i.      Point of contact for any communication between Student Life and the tour guide program. This will consist of any on campus events (orientations, President's Picnic) involving student organizations.

c.       District Head 3 - Social Media Guru

                                                               i.      Publicity/promotion of our tour guide program through our social media platforms. Our tour guides decided they wanted to try something new so we are working on building our Instagram and Snapchat game.

d.      District Head 4 - The Warden

                                                               i.      Carries out disciplinary actions, monitors tour guide performance/attendance, and keeps everyone in line. Any disciplinary actions of severe nature will go directly through me but so far this has been working out very well.

The breakdown keeps everyone accountable and in the loop. It also provides new tour guides with an immediate point of contact for any questions if I'm not available. They are really good about reaching out to their district head on clarifications if university information has changed, tour expectations, day to day info, etc. The added responsibilities allow for more leadership positions and growth within the program. Any major organization decisions are usually made by the entire leadership team and myself. Our tour guides are big fans of the new leadership roles.

Let me know if I can answer any more questions on how we operate :)

Winter M. Aguilar
Campus Visit Coordinator
Office of Admission
Texas Wesleyan University
1201 Wesleyan St.
Fort Worth, Texas 76105
Office: 817.531.4422
[https://txwes.edu/media/twu/content-assets/documents/communications/toolbox/TxWes-email-125.png]

From: listserv [mailto:listserv-bounces at civsa.org] On Behalf Of Scott Kirkessner
Sent: Wednesday, October 05, 2016 12:33 PM
To: listserv at civsa.org<mailto:listserv at civsa.org>
Subject: [civsa] Ambassador Leadership Teams

Hey all!

I am looking for examples of Ambassador/Student Tour Guide Leadership Teams/Executive Boards/Chairs/Directors, etc.  I am planning to rebuild our LT here at Utah.  I am most interested in learning more about leadership models that DO NOT have your typical President/Vice President structure, and are doing something different.

:)

Scott

[Block U Logo]

Scott Kirkessner, M.Ed.
Assistant Director, Campus Experience
Advisor, University Ambassadors
The University of Utah
201 South 1460 East, Room 250s
Salt Lake City, UT 84112
Office: 801.585.1995
scott.kirkessner at utah.edu<mailto:scott.kirkessner at utah.edu>
admissions.utah.edu/visit
Follow us!

[cid:image004.png at 01D21F08.E4A95DF0]<https://www.facebook.com/UtahAdmissions/>  [cid:image005.png at 01D21F08.E4A95DF0] <https://twitter.com/UtahAdmissions>    [cid:image006.png at 01D21F08.E4A95DF0] <https://www.instagram.com/utahadmissions/>    [cid:image007.png at 01D21F08.E4A95DF0] <https://www.snapchat.com/add/utahadmissions>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://civsa.org/pipermail/listserv_civsa.org/attachments/20161005/1feb08fe/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 36436 bytes
Desc: image009.png
URL: <http://civsa.org/pipermail/listserv_civsa.org/attachments/20161005/1feb08fe/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.gif
Type: image/gif
Size: 2062 bytes
Desc: image010.gif
URL: <http://civsa.org/pipermail/listserv_civsa.org/attachments/20161005/1feb08fe/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 720 bytes
Desc: image011.png
URL: <http://civsa.org/pipermail/listserv_civsa.org/attachments/20161005/1feb08fe/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 1044 bytes
Desc: image012.png
URL: <http://civsa.org/pipermail/listserv_civsa.org/attachments/20161005/1feb08fe/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.png
Type: image/png
Size: 1328 bytes
Desc: image013.png
URL: <http://civsa.org/pipermail/listserv_civsa.org/attachments/20161005/1feb08fe/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.png
Type: image/png
Size: 1010 bytes
Desc: image014.png
URL: <http://civsa.org/pipermail/listserv_civsa.org/attachments/20161005/1feb08fe/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 12538 bytes
Desc: image001.jpg
URL: <http://civsa.org/pipermail/listserv_civsa.org/attachments/20161005/1feb08fe/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 5643 bytes
Desc: image004.jpg
URL: <http://civsa.org/pipermail/listserv_civsa.org/attachments/20161005/1feb08fe/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 10-01-16.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 373205 bytes
Desc: 10-01-16.docx
URL: <http://civsa.org/pipermail/listserv_civsa.org/attachments/20161005/1feb08fe/attachment-0001.docx>