<?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: Number transfer failed THREE TO THREE in Network</title>
    <link>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15696#M2530</link>
    <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.three.co.uk/t5/user/viewprofilepage/user-id/6694"&gt;@Avondale&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Yeah primarily for changing provider, this is the exception rather than the rule. We're carrying out some system updates this year and once our PAYG and Pay Monthly systems are synced up the PAC shouldn't be necessary for this type of switch.&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jul 2023 10:12:36 GMT</pubDate>
    <dc:creator>JonathanB</dc:creator>
    <dc:date>2023-07-27T10:12:36Z</dc:date>
    <item>
      <title>Number transfer failed THREE TO THREE</title>
      <link>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15568#M2510</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;i am transferring my old three payg number to one of the new three payg sims, I got the pac code and requested the transfer on Thursday. It was supposed to be complete today. Unfortunately an online agent has informed me the transfer failed as there was an issue with the PAC and I should request a new one. Another agent has told me nothing can be done as I already used the first pac and the number is disconnected. Can anything be done am I now resigned to completely losing the number?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 10:51:25 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15568#M2510</guid>
      <dc:creator>KingDogg</dc:creator>
      <dc:date>2023-07-24T10:51:25Z</dc:date>
    </item>
    <item>
      <title>Re: Number transfer failed THREE TO THREE</title>
      <link>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15653#M2522</link>
      <description>&lt;P&gt;&lt;a href="https://community.three.co.uk/t5/user/viewprofilepage/user-id/8142"&gt;@KingDogg&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you need a PAC if you are staying with the same network ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I must confess that I thought that PACs were used to move between different networks.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2023 19:14:44 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15653#M2522</guid>
      <dc:creator>Avondale</dc:creator>
      <dc:date>2023-07-25T19:14:44Z</dc:date>
    </item>
    <item>
      <title>Re: Number transfer failed THREE TO THREE</title>
      <link>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15666#M2526</link>
      <description>&lt;P&gt;I was under this assumption aswell, the agent I spoke with from the new PAYG team told me it was the only way I could get my existing number onto the new data packs. A moderator on here replied to another customer with the same query and confirms a pac was needed so I’m unsure what could have gone wrong. it appears the port has partially gone through as I am now able to receive texts to the transferred number on the new sim but I can’t send texts, receive calls or activate iMessage and FaceTime as they’re all showing the number that came with the new sim. Dialling 333 and selecting the option to read out my number also gives the transferred number successfully&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 09:21:23 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15666#M2526</guid>
      <dc:creator>KingDogg</dc:creator>
      <dc:date>2023-07-26T09:21:23Z</dc:date>
    </item>
    <item>
      <title>Re: Number transfer failed THREE TO THREE</title>
      <link>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15696#M2530</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.three.co.uk/t5/user/viewprofilepage/user-id/6694"&gt;@Avondale&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Yeah primarily for changing provider, this is the exception rather than the rule. We're carrying out some system updates this year and once our PAYG and Pay Monthly systems are synced up the PAC shouldn't be necessary for this type of switch.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 10:12:36 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15696#M2530</guid>
      <dc:creator>JonathanB</dc:creator>
      <dc:date>2023-07-27T10:12:36Z</dc:date>
    </item>
    <item>
      <title>Re: Number transfer failed THREE TO THREE</title>
      <link>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15697#M2531</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.three.co.uk/t5/user/viewprofilepage/user-id/8142"&gt;@KingDogg&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;There's two possibilities here, you may have a split port, where the transfer hasn't completed. If they haven't already then the PAYG customer services team should be able to report this to the porting teams to fix.&lt;/P&gt;
&lt;P&gt;There's also occasionally issues with iOS when porting, if you edit your number in your iPhone settings, then switch iMessage off and back on in settings then this usually fixes that type of issue.&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;BR /&gt;JonathanB&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 10:14:48 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Network/Number-transfer-failed-THREE-TO-THREE/m-p/15697#M2531</guid>
      <dc:creator>JonathanB</dc:creator>
      <dc:date>2023-07-27T10:14:48Z</dc:date>
    </item>
  </channel>
</rss>

