<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[ATTN: MOA TECHNICAL SUPPORT]]></title><description><![CDATA[<p dir="auto">Hey all- just wanted to drop a little info and try to explain something.<br />
— I can only speak for myself but I’m sure I’m not alone</p>
<p dir="auto">— When we bring an issue to your attention through chat. I normally do for ppv and loading issues. We tell you our issue. Then we are told to do the same “troubleshooting”. Assume we have already done that. Then, one person who goes by the name “hector” (in chat), will literally tell me the issue I’m having is just me. That everything is working fine. I then proceed to tell him and send him pictures of the issue. He then again tells me it’s my issue. It’s on my end. I explain to him again, that every other streaming service I use is working fine. My internet speed is over 1 gig. I am using the device they recommend for their app. But he still insists it’s my issue. Then after we go around for 10 minutes, he MIGHT actually take a look and say “I fixed the link”. Which is what I told him the entire time.</p>
<p dir="auto">— here is my point   As a customer, I do not want to waste my time talking to someone.  If I am taking the time to say there is an issue. Maybe believe us</p>
<p dir="auto">Thank you</p>
]]></description><link>https://community.channelmoa.com/topic/1667/attn-moa-technical-support</link><generator>RSS for Node</generator><lastBuildDate>Thu, 04 Jun 2026 00:30:31 GMT</lastBuildDate><atom:link href="https://community.channelmoa.com/topic/1667.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 23 May 2026 17:45:59 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to ATTN: MOA TECHNICAL SUPPORT on Sun, 24 May 2026 03:46:51 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/arthur" aria-label="Profile: Arthur">@<bdi>Arthur</bdi></a></p>
<p dir="auto">Thank you for the reply.  Please review more of our conversations between hector and I.  You will see that it is a pattern of his to blame the customer, then find out it was on the Moa end.  Not exactly professional.</p>
]]></description><link>https://community.channelmoa.com/post/10797</link><guid isPermaLink="true">https://community.channelmoa.com/post/10797</guid><dc:creator><![CDATA[billysellas]]></dc:creator><pubDate>Sun, 24 May 2026 03:46:51 GMT</pubDate></item><item><title><![CDATA[Reply to ATTN: MOA TECHNICAL SUPPORT on Sat, 23 May 2026 19:02:15 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/billysellas" aria-label="Profile: billysellas">@<bdi>billysellas</bdi></a></p>
<p dir="auto">Hello Billy,</p>
<p dir="auto">Regarding your report, if the issue originated from our end during the PPV, we would typically expect a significant increase in traffic; however, no one else reported any problems throughout the event. I sincerely apologize for the situation you encountered.</p>
<p dir="auto">To be candid, there are times when issues can arise on our end, but we addressed them promptly. There’s no shame in acknowledging a mistake if it happens. I reviewed the conversation last night between you and Hector, and I noticed that some information was lacking from Hector's side. I apologize for that oversight.</p>
<p dir="auto">For major PPV events, we implement several backup streams to ensure smooth streaming. Some of these streams operate in FHD quality, which may cause issues during peak times due to ISP throttling. That’s why we also provide HD backup sources. I hope this clarifies the situation.</p>
<p dir="auto">Thank you for your understanding.</p>
]]></description><link>https://community.channelmoa.com/post/10794</link><guid isPermaLink="true">https://community.channelmoa.com/post/10794</guid><dc:creator><![CDATA[Arthur]]></dc:creator><pubDate>Sat, 23 May 2026 19:02:15 GMT</pubDate></item></channel></rss>