<?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: Seperate emails needed for broadband and mobile? in Account and services</title>
    <link>https://community.three.co.uk/t5/Account-and-services/Seperate-emails-needed-for-broadband-and-mobile/m-p/20344#M3845</link>
    <description>&lt;P&gt;1password.com&lt;/P&gt;</description>
    <pubDate>Mon, 23 Oct 2023 10:12:50 GMT</pubDate>
    <dc:creator>sc1999</dc:creator>
    <dc:date>2023-10-23T10:12:50Z</dc:date>
    <item>
      <title>Seperate emails needed for broadband and mobile?</title>
      <link>https://community.three.co.uk/t5/Account-and-services/Seperate-emails-needed-for-broadband-and-mobile/m-p/20338#M3840</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have a pay monthly contract, had it for 3 months. I then signed up for 5g broadband about a month ago.&lt;/P&gt;&lt;P&gt;It seems that I need to setup a new email address to be able to log in to the broadband account, as they cannot both be registered to one email address. Despite signing up for both using one email address. Live chat confirmed this. Is this a known/common issue or am I missing the point somewhere?&lt;/P&gt;&lt;P&gt;Seems a bit unnecessary to have to create an email address to access a second service? It will be the only service I'd use the email address for I'd imagine.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Oct 2023 09:38:54 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Account-and-services/Seperate-emails-needed-for-broadband-and-mobile/m-p/20338#M3840</guid>
      <dc:creator>skg</dc:creator>
      <dc:date>2023-10-23T09:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: Seperate emails needed for broadband and mobile?</title>
      <link>https://community.three.co.uk/t5/Account-and-services/Seperate-emails-needed-for-broadband-and-mobile/m-p/20339#M3841</link>
      <description>&lt;P&gt;Your post is the latest in a long list. Yes, you do need separate emails for each number. No&amp;nbsp; we have no clue why and we have not heard the reasoning why from 3's&amp;nbsp; genius who thought it would be a good idea. Just how a company with dozens of numbers to manage are coping I have no idea.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Oct 2023 09:46:52 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Account-and-services/Seperate-emails-needed-for-broadband-and-mobile/m-p/20339#M3841</guid>
      <dc:creator>sc1999</dc:creator>
      <dc:date>2023-10-23T09:46:52Z</dc:date>
    </item>
    <item>
      <title>Re: Seperate emails needed for broadband and mobile?</title>
      <link>https://community.three.co.uk/t5/Account-and-services/Seperate-emails-needed-for-broadband-and-mobile/m-p/20340#M3842</link>
      <description>&lt;P&gt;Thanks - good to know I'm not missing something. Now to devise a system whereby I can remember the new email address details in 23 months time when they are next needed...&lt;/P&gt;</description>
      <pubDate>Mon, 23 Oct 2023 09:49:25 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Account-and-services/Seperate-emails-needed-for-broadband-and-mobile/m-p/20340#M3842</guid>
      <dc:creator>skg</dc:creator>
      <dc:date>2023-10-23T09:49:25Z</dc:date>
    </item>
    <item>
      <title>Re: Seperate emails needed for broadband and mobile?</title>
      <link>https://community.three.co.uk/t5/Account-and-services/Seperate-emails-needed-for-broadband-and-mobile/m-p/20344#M3845</link>
      <description>&lt;P&gt;1password.com&lt;/P&gt;</description>
      <pubDate>Mon, 23 Oct 2023 10:12:50 GMT</pubDate>
      <guid>https://community.three.co.uk/t5/Account-and-services/Seperate-emails-needed-for-broadband-and-mobile/m-p/20344#M3845</guid>
      <dc:creator>sc1999</dc:creator>
      <dc:date>2023-10-23T10:12:50Z</dc:date>
    </item>
  </channel>
</rss>

