<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Disgraceful Service in Devices</title>
    <link>https://community.three.co.uk/t5/Devices/Disgraceful-Service/m-p/41132#M3418</link>
    <description>&lt;P&gt;UPDATE: Once the pairing addon/contract was cancelled the watch worked perfectly and I was able to add it to the plan and I spoke to billing who said they've raised a credit for the £115&lt;BR /&gt;&lt;BR /&gt;Anyone else having this issue needs to get the addon/contract for the esim for the watch cancelled and then start a new one. Very difficult to do as the customer service team don't seem to understand this is the the problem but once done it works&lt;/P&gt;</description>
    <pubDate>Thu, 21 Nov 2024 12:00:59 GMT</pubDate>
    <dc:creator>richdolman</dc:creator>
    <dc:date>2024-11-21T12:00:59Z</dc:date>
    <item>
      <title>Disgraceful Service</title>
      <link>https://community.three.co.uk/t5/Devices/Disgraceful-Service/m-p/41128#M3416</link>
      <description>&lt;P&gt;I have never had such a terrible customer service experience in my entire life.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I have an apple watch ultra 2 which I upgraded from apple watch ultra 1.&amp;nbsp; The ultra 1 worked fine, now I can't activate the mobile service on the watch 2. I spoke to one guy who took the error message (that it was already paired) and then said that the pairing contract needed to be cancelled and re-started, so he put me through to someone who then put me on hold and hung up.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I call back and have to start the entire process again with someone who now doesn't understand what needs to happen. I explain the issue and they clearly have no idea what is going on so I'm on the phone for an hour again.&lt;BR /&gt;&lt;BR /&gt;I'm still no closer to being able to use my watch as it's meant to be.&lt;BR /&gt;&lt;BR /&gt;Wild how you guys can get away with this&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2024 10:01:01 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Devices/Disgraceful-Service/m-p/41128#M3416</guid>
      <dc:creator>richdolman</dc:creator>
      <dc:date>2024-11-21T10:01:01Z</dc:date>
    </item>
    <item>
      <title>Re: Disgraceful Service</title>
      <link>https://community.three.co.uk/t5/Devices/Disgraceful-Service/m-p/41129#M3417</link>
      <description>&lt;P&gt;Starting to think this is some kind of joke - someone said they understood the problem, you've not cancelled my contract (within the cooling off period) and now want to charge me £115&lt;/P&gt;&lt;P&gt;Can someone at 3 please call me&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2024 10:16:36 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Devices/Disgraceful-Service/m-p/41129#M3417</guid>
      <dc:creator>richdolman</dc:creator>
      <dc:date>2024-11-21T10:16:36Z</dc:date>
    </item>
    <item>
      <title>Re: Disgraceful Service</title>
      <link>https://community.three.co.uk/t5/Devices/Disgraceful-Service/m-p/41132#M3418</link>
      <description>&lt;P&gt;UPDATE: Once the pairing addon/contract was cancelled the watch worked perfectly and I was able to add it to the plan and I spoke to billing who said they've raised a credit for the £115&lt;BR /&gt;&lt;BR /&gt;Anyone else having this issue needs to get the addon/contract for the esim for the watch cancelled and then start a new one. Very difficult to do as the customer service team don't seem to understand this is the the problem but once done it works&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2024 12:00:59 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Devices/Disgraceful-Service/m-p/41132#M3418</guid>
      <dc:creator>richdolman</dc:creator>
      <dc:date>2024-11-21T12:00:59Z</dc:date>
    </item>
  </channel>
</rss>

