<?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>
									Listing Policies - Ticket Attendant Forum				            </title>
            <link>https://www.ticketattendant.com/community/listing-policies/</link>
            <description>Ticket Attendant Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 19 Apr 2026 11:10:09 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Account Surrender Policy</title>
                        <link>https://www.ticketattendant.com/community/listing-policies/account-surrender-policy/</link>
                        <pubDate>Wed, 18 Sep 2024 16:45:29 +0000</pubDate>
                        <description><![CDATA[If tickets are non-transferable and we cannot fulfill them, the next solution is Account Surrender. This involves providing the account login and password to Ticket Attendant for the buyer t...]]></description>
                        <content:encoded><![CDATA[<p dir="ltr"><span>If tickets are non-transferable and we cannot fulfill them, the next solution is Account Surrender. This involves providing the account login and password to Ticket Attendant for the buyer to use at the door for entry.</span></p>
<p> </p>
<p dir="ltr"><span>Note that not all exchanges will allow Account Surrender. Use of this strategy should be evaluated on a case-by-case basis. Ticket Attendant will attempt to work with exchanges to ensure successful entry but will not be held responsible in the event that an exchange does not honor Account Surrender as a delivery method.</span></p>
<p> </p>
<p dir="ltr"><strong>SeatGeek, Stubhub, TicketsNow, and TM+ do not allow entry via Account Surrender.</strong></p>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/listing-policies/">Listing Policies</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/listing-policies/account-surrender-policy/</guid>
                    </item>
				                    <item>
                        <title>Ticket Masking Policy</title>
                        <link>https://www.ticketattendant.com/community/listing-policies/ticket-masking-policy/</link>
                        <pubDate>Wed, 18 Sep 2024 16:44:42 +0000</pubDate>
                        <description><![CDATA[If you choose to mask your tickets, you run the risk of cancellations. While we recommend you follow the guidelines below, it is up to exchanges to accept or reject masked seats as they see ...]]></description>
                        <content:encoded><![CDATA[<p dir="ltr"><span>If you choose to mask your tickets, you run the risk of cancellations. While we recommend you follow the guidelines below, it is up to exchanges to accept or reject masked seats as they see fit. We cannot guarantee your masked seats will be accepted. As such, clients will ultimately be accountable for penalties or cancelations on masked seats.</span></p>
<p> </p>
<p dir="ltr"><span>When masking tickets, take note of the following requirements:</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>Do not mask seat numbers.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Do not mask tickets for exchanges that are integrated with the venue.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Do not mask tickets such that the section and row match with real tickets you already own. For example, if you own Section A Row 10 and Section A Row 12, you can mask Row 10 to Row 11, 13, and so on, but not Row 12 as the section and row would match.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Tickets must be unbroadcast before masking.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Masking is not allowed for orders over $1000</span></p>
</li>
</ul>
<p> </p>
<p dir="ltr"><span>Please also be aware of exchange-specific restrictions:</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>Do not mask Flash seats.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Vivid does not allow masking on orders over $1000.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Mercury/TND requires additional approval for masking or substitute tickets. We recommend you exclude broadcasting masked seats to Mercury/TND. Their official policy is below: </span></p>
</li>
</ul>
<p> </p>
<p dir="ltr"><span>“<em>Mercury orders may be upgraded no more than one row without approval from the buyer via TicketNetwork® customer service. Approval is also required for any alternate tickets if the original listing was located within the first ten rows of the field or stage (in that case closer may not be better). All other substitutions for Mercury orders must be approved.”</em></span></p>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/listing-policies/">Listing Policies</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/listing-policies/ticket-masking-policy/</guid>
                    </item>
				                    <item>
                        <title>Piggyback Policy</title>
                        <link>https://www.ticketattendant.com/community/listing-policies/piggyback-policy/</link>
                        <pubDate>Wed, 18 Sep 2024 16:42:34 +0000</pubDate>
                        <description><![CDATA[A piggyback ticket is a ticket that is in front of or behind another; two seats in different rows but same seat number. For example, I have Seat 8 in Row A and Row B - these are piggybacks....]]></description>
                        <content:encoded><![CDATA[<article id="article-body" class="article-body">
<p>A piggyback ticket is a ticket that is in front of or behind another; <span>two seats in different rows but same seat number</span>. For example, I have Seat 8 in Row A and Row B - these are piggybacks.</p>
<div id="1726678593.143279" class="c-virtual_list__item" role="listitem" data-qa="virtual-list-item" data-item-key="1726678593.143279">
<div class="c-message_kit__background c-message_kit__background--hovered p-message_pane_message__message c-message_kit__message" role="presentation" data-qa="message_container" data-qa-unprocessed="false" data-qa-placeholder="false">
<div class="c-message_kit__hover c-message_kit__hover--hovered" role="document" data-qa-hover="true">
<div class="c-message_kit__actions c-message_kit__actions--above">
<div class="c-message_kit__gutter">
<div class="c-message_kit__gutter__left" role="presentation"> </div>
<div class="c-message_kit__gutter__right" role="presentation" data-qa="message_content"><span class="offscreen" aria-hidden="true" data-qa="aria-labelledby-primary-C07MNCEMVKL-1726678593.143279-sender"></span>
<div class="c-message_kit__blocks c-message_kit__blocks--rich_text">
<div class="c-message__message_blocks c-message__message_blocks--rich_text" data-qa="message-text">
<div class="p-block_kit_renderer" data-qa="block-kit-renderer">
<div class="p-block_kit_renderer__block_wrapper p-block_kit_renderer__block_wrapper--first">
<div class="p-rich_text_block" dir="auto">
<div class="p-rich_text_section">Our policy does <strong>not</strong> allow for listing piggyback tickets.</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</article>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/listing-policies/">Listing Policies</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/listing-policies/piggyback-policy/</guid>
                    </item>
				                    <item>
                        <title>Local Pick Up, Walk In at Venue, Will Call Policy</title>
                        <link>https://www.ticketattendant.com/community/listing-policies/local-pick-up-walk-in-at-venue-will-call-policy/</link>
                        <pubDate>Wed, 18 Sep 2024 16:33:31 +0000</pubDate>
                        <description><![CDATA[Local Pick Up, Walk In at Venue, and Will Call tickets cannot be sold on Stubhub.
 
Ticket Attendant is not responsible for any issues whatsoever relating to any of these delivery methods....]]></description>
                        <content:encoded><![CDATA[<p dir="ltr"><span>Local Pick Up, Walk In at Venue, and Will Call tickets cannot be sold on Stubhub.</span></p>
<p> </p>
<p dir="ltr"><span>Ticket Attendant is not responsible for any issues whatsoever relating to any of these delivery methods.</span></p>
<p> </p>
<p dir="ltr"><span>Please note that Ticket Attendant reserves the right to refuse listing these delivery methods on a per client basis.</span></p>
<h3 dir="ltr"> </h3>
<h3 dir="ltr">How to set up your tickets for the following:</h3>
<h3 dir="ltr"><span style="font-size: 18pt">Local Pick Up Tickets</span></h3>
<p dir="ltr"><span>Stock type</span><span>:  Hard stock or Paperless</span></p>
<p dir="ltr"><span>Internal Note</span><span>: -SH Contact Name and Phone Number (Do not use commas or punctuation in INTERNAL notes)</span></p>
<p dir="ltr"><span>External Note</span><span>: Local pickup</span></p>
<h3 dir="ltr"> </h3>
<h3 dir="ltr"><span style="font-size: 18pt">Walk In at Venue Tickets</span></h3>
<p dir="ltr"><span>Stock type</span><span>:  Hard stock or Paperless</span></p>
<p dir="ltr"><span>Internal Note</span><span>: -SH Contact Name and Phone Number (Do not use commas or punctuation in INTERNAL notes)</span></p>
<p dir="ltr"><span>External Note</span><span>: Walk in at venue</span></p>
<h3 dir="ltr"> </h3>
<h3 dir="ltr"><span style="font-size: 18pt">Will Call Tickets</span></h3>
<p dir="ltr"><span>Stock type</span><span>:  Hard stock or Paperless</span></p>
<p dir="ltr"><span>Internal Note</span><span>: -SH Contact Name and Phone Number (Do not use commas or punctuation in INTERNAL notes)</span></p>
<p dir="ltr"><span>External Note</span><span>: Will Call</span></p>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/listing-policies/">Listing Policies</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/listing-policies/local-pick-up-walk-in-at-venue-will-call-policy/</guid>
                    </item>
				                    <item>
                        <title>Last Minute Services Policy (LMS)</title>
                        <link>https://www.ticketattendant.com/community/listing-policies/lms-policy/</link>
                        <pubDate>Wed, 18 Sep 2024 16:32:52 +0000</pubDate>
                        <description><![CDATA[Please be sure to put “LMS” in the internal notes when setting up a Last Minute Services (LMS) listing.
 
Ship the tickets on your own or have our office forward tickets to LMS if we have ...]]></description>
                        <content:encoded><![CDATA[<p dir="ltr"><span>Please be sure to put “LMS” in the internal notes when setting up a Last Minute Services (LMS) listing.</span></p>
<p> </p>
<p dir="ltr"><span>Ship the tickets on your own or have our office forward tickets to LMS if we have them in-hand. Please make requests before 3PM CST.</span></p>
<p> </p>
<p dir="ltr"><span>For LMS, we strongly suggest the following:</span></p>
<ul>
<li dir="ltr">
<p dir="ltr"><span>Have all of your tickets actively shared and with the LMS internal note before your tickets arrive to LMS.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Include all tickets in one shipment and have them sub-divided in the envelope based on how your active groups are split. You must also fill out the Stubhub LMS form.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>Once your tickets become active on Stubhub we strongly suggest only changing the prices. LMS activation is based on the Stubhub Listing ID and taking any other actions besides changing the price will result in the listing changing, making it go to a pending status on Stubhub, meaning your tickets will no longer be reflected as LMS on their end. Actions such as adjusting the groups (splitting tickets), unbroadcasting, changing split rules, and adding notes can all affect your listing.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>We will do our best to get any tickets that fall into a pending status back up on Stubhub but it requires emails and phone calls plus work from the Stubhub LMS team so it will not be immediate. Unfortunately, this is a limitation of the LMS system.</span></p>
</li>
<li dir="ltr">
<p dir="ltr"><span>In general, we encourage clients to do their best to sell inventory before shipping to LMS and we will not be responsible in situations where inventory drops off of Stubhub that are beyond our control. As always, we will do everything we can to get it back up for you.</span></p>
</li>
</ul>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/listing-policies/">Listing Policies</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/listing-policies/lms-policy/</guid>
                    </item>
				                    <item>
                        <title>Resale Restricted Tickets Policy</title>
                        <link>https://www.ticketattendant.com/community/listing-policies/resale-restricted-tickets-policy/</link>
                        <pubDate>Wed, 18 Sep 2024 16:32:04 +0000</pubDate>
                        <description><![CDATA[Resale restricted tickets cannot be listed on integrated exchanges. This rule applies to all resale restricted tickets. Listing these tickets on these exchanges will result in cancellations....]]></description>
                        <content:encoded><![CDATA[<p dir="ltr"><span>Resale restricted tickets cannot be listed on integrated exchanges. This rule applies to all resale restricted tickets. Listing these tickets on these exchanges will result in cancellations.</span></p>
<p> </p>
<p dir="ltr"><span>Ticket Attendant will do our best to ensure that tickets are listed correctly. However, penalties that result from incorrectly listing resale restricted tickets may ultimately be the responsibility of the client.</span></p>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/listing-policies/">Listing Policies</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/listing-policies/resale-restricted-tickets-policy/</guid>
                    </item>
				                    <item>
                        <title>Broadcast Policy</title>
                        <link>https://www.ticketattendant.com/community/listing-policies/broadcast-policy/</link>
                        <pubDate>Wed, 18 Sep 2024 16:31:21 +0000</pubDate>
                        <description><![CDATA[You are responsible for checking on the accuracy of all tickets POed either by our Operations Team or by PurchaseNow. 
 
By broadcasting your tickets, you are acknowledging that your inven...]]></description>
                        <content:encoded><![CDATA[<p dir="ltr"><strong>You are responsible for checking on the accuracy of all tickets POed either by our Operations Team or by PurchaseNow. </strong></p>
<p> </p>
<p dir="ltr"><span>By broadcasting your tickets, you are acknowledging that your inventory is correct. It is up to the client to ensure that event information, date and time are all accurate, and that your inventory includes the correct stock type/in-hand dates/notes/disclosures.  At this time, disclosures are not automatically added, so it is important to verify that the correct disclosures are included on your listing before broadcasting.  </span></p>
<p> </p>
<p dir="ltr"><span>Please keep in mind that PurchaseNow is an automation tool designed to reduce mistakes associated with manual POing, but it is not a replacement for your company to verify that your purchases are correctly represented.</span></p>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/listing-policies/">Listing Policies</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/listing-policies/broadcast-policy/</guid>
                    </item>
				                    <item>
                        <title>Speculation Policy</title>
                        <link>https://www.ticketattendant.com/community/listing-policies/speculation-policy/</link>
                        <pubDate>Wed, 18 Sep 2024 16:30:14 +0000</pubDate>
                        <description><![CDATA[Speculation is disallowed. You cannot speculate on tickets or list tickets you do not personally own. You must be able to show proof of ownership at any time. If you have any questions, plea...]]></description>
                        <content:encoded><![CDATA[<p>Speculation is disallowed. You cannot speculate on tickets or list tickets you do not personally own. You must be able to show proof of ownership at any time. If you have any questions, please contact us. </p>]]></content:encoded>
						                            <category domain="https://www.ticketattendant.com/community/listing-policies/">Listing Policies</category>                        <dc:creator>Regan O&#039;Brien</dc:creator>
                        <guid isPermaLink="true">https://www.ticketattendant.com/community/listing-policies/speculation-policy/</guid>
                    </item>
							        </channel>
        </rss>
		