Slovenia Porting

The following topics are discussed in this guide. Click a topic to skip directly to this information:

In Slovenia we offer porting for the following number types:

  • Local (386)x
    • (386)1 - Ljubljana
    • (386)2 - Maribor
    • (386)3 - Celje
    • (386)4 - Kranj
    • (386)5 - Koper
    • (386)7 - Novo Mesto

Please note that most of International Phone Numbers have Voice capability only. Below are instructions for porting Slovenian phone numbers into Twilio. You can find porting summary and timelines here.

Slovenia Porting Requirements

General requirements

  • The full list of numbers that you wish to port in E164 format, eg: +[386][XXX XXXX].
  • Letter of Authorization (LOA) signed by the authorized user and/or owner of the number(s). Note that the information on your LOA must match the authorized user name and service address provided by your current carrier. You can find the LOA required for the Slovenian numbers below. The below information is required to be filled out on the LOA: 
      • Donor Operator
      • Company name
      • Company address
      • Account number
      • Phone Numbers to be ported
      • Signature
      • Print name
      • Position in Company (if applicable)
      • Date
  • A scanned or electronic copy of the most recent phone bill (within the last 30 days) that includes the account number and authorized user’s name for all the numbers you would like to port. 
  • Your Twilio Account SID (Your unique ID starting with “AC” that you can find on the main dashboard in Twilio Console).
  • Additionally, upload compliance documents before submitting your port request. You can see the full list of required documents here.
    • Upload your documents in the Twilio Console by selecting “Phone Numbers” > “Regulatory Compliance“ > “Bundles” or follow the link here.
    • Choose the country, the phone number type and follow the instructions. Processing of the compliance documents may take up to several business days. Once your documents have been accepted, please share the associated links that start with "BU" and "AD" along with the porting request via email.

Slovenia Porting Process 

  1. Submit your Porting request with all the requirements in place to porting@twilio.com
  2. Twilio approves the port request. If everything in Step 1 is correct, you can expect Twilio to approve your port request within 24 hours.
  3. Twilio submits number to the Carrier Partner. This can take up to 24 hours. Your request is then submitted to your soon-to-be former carrier as a port request. During this time, do not close your account with your carrier and keep your numbers active.
  4. Twilio’s Carrier Partner reaches out to the Losing Carrier. This can take around one week to complete.
  5. Response from the carrier. At this point, your request is either approved or rejected:
    • Approved: If approved, Twilio will notify you about a porting date. 
    • Rejected: Rejections can occur due to various reasons. For example, invalid VAT Number or invalid/incomplete range of numbers. Read more about common reasons for port request rejections here. Additionally, you will likely need to reach out to your losing carrier to find out what’s needed to move forward. Rejections may add an undetermined amount of time to your porting request.
  6. Twilio reaches out to you with a porting date. Twilio sends you an email with a porting date and time slot if known. Your number is on your Account and can be visible in the Twilio Console.
  7. Configure your number. It is critical to configure your number prior the porting date. This will minimise the service downtime. You can configure the numbers from the Twilio Console.
  8. Your phone number is with Twilio. Once your number(s) is routing to Twilio and everything works as expected, you can remove the number(s) from your former provider.

We charge a one-time porting fee for Slovenia, for more details please reach out to porting@twilio.com.

Common Rejection Reasons

  • Invalid Phone Number
  • Invoice expired (needs to be issued in the last 3 months)
 
Have more questions? Submit a request
Powered by Zendesk