<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									General - Ticket Attendant Forum				            </title>
            <link>https://www.ticketattendant.com/community/general/</link>
            <description>Ticket Attendant Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Wed, 29 Apr 2026 17:59:15 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>PO Request Policy</title>
                        <link>https://www.ticketattendant.com/community/general/po-request-policy/</link>
                        <pubDate>Wed, 18 Sep 2024 16:26:37 +0000</pubDate>
                        <description><![CDATA[PO requests are a core function of our Operations Teams. When requesting that our Operations Team PO tickets on behalf of your company, please keep the following in mind:    


Depending ...]]></description>
                        <content:encoded><![CDATA[<article id="article-body" class="article-body">
<p dir="ltr"><span>PO requests are a core function of our Operations Teams. When requesting that our Operations Team PO tickets on behalf of your company, please keep the following in mind:</span><span><span class="Apple-tab-span">    </span></span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>Depending on the time of year, our Operations team might have many requests. If the event is in the next few days, you may instead choose to PO your tickets through Terminal in order to get them broadcast faster.</span><span><span class="Apple-tab-span">    </span></span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>When requesting that our team PO tickets, it is important to clearly list the event dates AND event time as there are many situations where</span><span><span class="Apple-tab-span"> </span></span><span>the headliner could be performing multiple times in a given day. </span><span><span class="Apple-tab-span">    </span></span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>When requesting sporting tickets be POed, please provide the full team name, sport, and venue.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>In your request, please provide us with all necessary information to prepare your inventory for fulfillment, including the account and password where your inventory lives and the website to gain access to the inventory.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Any extra notes about the inventory.  For example, notes about exclusions.</span></p>
</li>
</ul>
<p dir="ltr"><span>Ticket Attendant will not take responsibility for tickets that are incorrectly PO'd by our team (incorrect stock type, wrong event or event date, missing tickets, etc.). It is your responsibility to ensure everything is accurate and complete after the purchase order is finalized.</span></p>
<p> </p>
<p dir="ltr"><span>The following is an example of a good PO request:</span></p>
<p> </p>
<div dir="ltr" align="left">
<table><colgroup><col width="585" /></colgroup>
<tbody>
<tr>
<td>
<p dir="ltr"><span>Please PO the entire season and preseason for Chicago Blackhawks at the United Center.</span></p>
<br />
<p dir="ltr"><span>Section</span><span>: 424</span></p>
<br />
<p dir="ltr"><span>Row</span><span>: B</span></p>
<br />
<p dir="ltr"><span>Seats</span><span>: 3-4</span></p>
<br />
<p dir="ltr"><span>Quantity</span><span>: 2</span></p>
<br />
<p dir="ltr"><span>Stock Type</span><span>: Mobiles QRs</span></p>
<p dir="ltr"> </p>
<p dir="ltr"><span><strong dir="ltr">Delivery Method: </strong>URL</span></p>
<br />
<p dir="ltr"><span>Website</span><span>: https://am.ticketmaster.com/blackhawks</span></p>
<br />
<p dir="ltr"><span>Log In</span><span>: emaill@gmail.com</span></p>
<br />
<p dir="ltr"><span>Password</span><span>: Password</span></p>
<br />
<p dir="ltr"><span>Notes</span><span>: (if any)</span></p>
</td>
</tr>
</tbody>
</table>
</div>
</article>
<hr />]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/general/">General</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/general/po-request-policy/</guid>
                    </item>
				                    <item>
                        <title>Communication and Abuse Policy</title>
                        <link>https://www.ticketattendant.com/community/general/communication-and-abuse-policy/</link>
                        <pubDate>Wed, 18 Sep 2024 16:25:50 +0000</pubDate>
                        <description><![CDATA[We at Ticket Attendant pride ourselves on customer service.  To ensure that we provide the highest level of service, we strive to provide a safe and happy working environment for our employe...]]></description>
                        <content:encoded><![CDATA[<article id="article-body" class="article-body">
<p dir="ltr"><span>We at Ticket Attendant pride ourselves on customer service.  To ensure that we provide the highest level of service, we strive to provide a safe and happy working environment for our employees.  We have a strict policy in line with industry standards regarding customer behavior and interactions.</span></p>
<p> </p>
<p dir="ltr"><span>This document is intended to provide guidelines and is not an exhaustive list of our policy.  We reserve the right to amend this document or at any time without notice, and to designate any interaction as abuse or harassment at our discretion.</span></p>
<h3 dir="ltr"><span>Abuse and Harassment</span></h3>
<p dir="ltr"><span>We will not abide abuse or harassment towards any of our employees.  </span></p>
<p> </p>
<p dir="ltr"><span>Abuse takes many forms, and this document will not attempt to outline obvious forms of abuse or harassment like sexual harassment, racism, or physical assault. In the event that any such abuse is directed towards our employees, we will take swift action.  This document will address some of the more subtle forms of abuse.</span></p>
<h3 dir="ltr"><span>Verbal Abuse</span></h3>
<p dir="ltr"><span>While we understand that everyone gets angry from time to time, it is important that anger doesn’t turn into abuse.  We will not abide verbal abuse towards any of our employees.  This includes abuse that is face to face, over the phone, or through emails or other chat programs.</span></p>
<h4 dir="ltr"><span>What is considered verbal abuse?</span></h4>
<p dir="ltr"><span>We define verbal abuse as anything that makes an employee feel uncomfortable or unsafe.  This includes, but is not limited to:</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>Swearing</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Targeted Attacks on Character, Ability, Competency, Work Ethic, etc</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Name calling</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Threats</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Bribery</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Responses that do not advance the goal of the support ticket or call</span></p>
</li>
</ul>
<p> </p>
<h4 dir="ltr"><span>Examples of verbal abuse</span></h4>
<p dir="ltr"><span>This list is not exhaustive, and is meant only to clarify some of the items above. </span><span> </span></p>
<p> </p>
<p dir="ltr"><span>Targeted Attacks on Character, Ability, Competency, Work Ethic, etc.</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>“You’re stupid”</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>“Do you know how to do your job?”</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>“You sound like you have no idea what you’re doing.”</span></p>
</li>
</ul>
<p> </p>
<p dir="ltr"><span>Threats</span></p>
<p dir="ltr"><span>When it comes to threats, there is only one acceptable threat:  “I will raise this up to your manager.”  Anything outside of that is unacceptable.</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>“I will raise this up to your manager and get you fired.”</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>“I’ll make sure you never work at another company in Chicago again.”</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>“If you don’t do this for me now, I’ll &lt;do something&gt;”</span></p>
</li>
</ul>
<p> </p>
<p> </p>
<p dir="ltr"><span>Bribery</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>“I know this is against policy, but I’ll Venmo you $50 if you take care of it.”</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>“I’ll pay you an extra $100 if you take care of this tonight instead of tomorrow.”</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>“I’ll buy you a drink in Vegas if you take care of this tonight instead of tomorrow.”</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>“I’ll send pizza to your office if you take care of this tonight instead of tomorrow.”</span></p>
</li>
</ul>
<p> </p>
<p dir="ltr"><span>Responses that do not advance the goal of the support ticket or call</span></p>
<p dir="ltr"><span>When submitting a support ticket or calling our office, our goal is to resolve your issue.  To ensure that we are able to address your needs in a timely manner, it is important that you work with our employees rather than against them.  If a comment does not progress the issue, then it can be considered abusive, as it is antagonistic rather than helpful.</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>When asked for login credentials</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>“You already have my information”</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>“It’s the same as it’s always been”</span></p>
</li>
</ul>
</li>
<li dir="ltr">
<p dir="ltr"><span>When asked for information about tickets, like a listing id, seat information, or the website where the tickets can be located</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>“Look it up”</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>“It’s right there, can’t you see it?”</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>“It’s on the PO”</span></p>
</li>
</ul>
</li>
</ul>
<h3 dir="ltr"><span>Consequences of Abuse </span></h3>
<p dir="ltr"><span>First and foremost, if our employees feel uncomfortable or unsafe during an interaction with a customer, we encourage them to respectfully terminate the conversation where the offending behavior is occurring, and to raise the issue up to a senior team member and/or management.  Our employees are not expected to tolerate abuse and will remove themselves from the abusive situation if they deem it necessary.</span></p>
<p> </p>
<p dir="ltr"><span>If our team identifies an instance of abuse or harassment, we may take a variety of actions.  For extreme cases, we may choose to immediately terminate our relationship with the customer.  For other cases, we will take an escalating approach to protecting our employees.  In each case, the customer will be notified about their status and about the offending incident.</span></p>
<p dir="ltr"><span>It’s important to note that if we have reached the point of issuing a warning or a notification of a repeat offense, that communication will not be a discussion - the decision has already been made and arguing will not be productive.</span></p>
<p> </p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>First Offense - Warning</span><span> - For the first instance of significant abuse or after a pervasive pattern of issues have been identified by our team, a senior team member or management will reach out to the customer to issue a warning.  We will note this warning and monitor the customer for repeated offenses.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Second Offense - Restrictions on contact methods</span><span> - If a customer has been warned about a behavior but continues to exhibit the behavior, we will take measures to protect our employees for the customer.  Depending on the behavior, we may instruct our employees to not answer phone calls or reply to support tickets from the customer unless the employee is a senior team member or management.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Third Offense - Further restrictions on contact methods</span><span> - On a third offense, we may choose to refuse all communication via phone or email, depending on the problematic behavior.  We may also choose to assign a specific individual to handle the customer such that no communication from the customer will be allowed through other channels.  This stage may affect the customer’s business as they will not be able to contact us unless the designated individual is in the office - we will not be responsible for any impact on the customer’s business as they had two opportunities to correct the behavior before reaching this extreme stage.</span></p>
</li>
</ul>
</article>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/general/">General</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/general/communication-and-abuse-policy/</guid>
                    </item>
				                    <item>
                        <title>Support Staff Best Practices</title>
                        <link>https://www.ticketattendant.com/community/general/support-staff-best-practices/</link>
                        <pubDate>Wed, 18 Sep 2024 16:24:37 +0000</pubDate>
                        <description><![CDATA[For matters that require urgent support (i.e. same-day event), please add the prefix “URGENT” in your subject line when writing to our team.    


When communicating with our Operations t...]]></description>
                        <content:encoded><![CDATA[<ul>
<li dir="ltr">
<p dir="ltr"><span>For matters that require urgent support (i.e. same-day event), please add the prefix “URGENT” in your subject line when writing to our team.</span><span><span class="Apple-tab-span">    </span></span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>When communicating with our Operations team, please be as </span><span>precise and detailed as you can</span><span> as it will lead to fewer errors, less need to contact your company, and a better overall client experience.  Please keep in mind that while these things may seem obvious to you, our team is constantly growing so not everyone might be familiar with your account or inventory</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>Include External Reference Numbers or Listing IDs whenever available</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Accurate login information</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>The website where you can obtain or access the tickets</span></p>
</li>
</ul>
</li>
</ul>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/general/">General</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/general/support-staff-best-practices/</guid>
                    </item>
				                    <item>
                        <title>Support Staff and Hours</title>
                        <link>https://www.ticketattendant.com/community/general/support-staff-and-hours/</link>
                        <pubDate>Wed, 18 Sep 2024 16:22:35 +0000</pubDate>
                        <description><![CDATA[Ticket Attendant hours are 7:00am-12am CST 7 days a week.
You can reach our Operations Team during these hours at (773) 888-3048.
 
Depending on the nature of your request, emailing suppo...]]></description>
                        <content:encoded><![CDATA[<p dir="ltr"><span>Ticket Attendant hours are 7:00am-12am CST 7 days a week.</span></p>
<p dir="ltr"><span>You can reach our Operations Team during these hours at (773) 888-3048.</span></p>
<p> </p>
<p><span>Depending on the nature of your request, emailing</span><span> <a href="http://support@ticketattendant.com" target="_blank" rel="noopener">support@ticketattendant.com</a></span><span> i</span><span>s the best way to </span><span>get access to our Operations team. Emails sent to </span><a href="mailto:consignment@ticketattendant.com"><span>consignment@ticketattendant.com</span></a><span> </span><span>are redirected to the same Freshdesk service.</span></p>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/general/">General</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/general/support-staff-and-hours/</guid>
                    </item>
							        </channel>
        </rss>
		