How about I make this easy: Use 43717 for the promo code and any member of this forum will get free port ins for the next 30 days

Hey Guys,

We’re going to be reviewing this first thing on Monday. @JaredBusch had a strong argument about Microsoft in his email.

I can say that we will be removing the 1 cell phone number per account limit and allowing a certain number of new accounts per month instead (so you can create 5 or so accounts per month before our system stops you). We’re also going to be reviewing the credit card idea but that may take more time.

I’ll update you all once we have a new policy in place and it’s deployed.

Hi All

We have decided to introduce SIP Registration support in a forthcoming update on Skyetel. Our goal it to roll it out in Mid-Late November, but it may come sooner or later than that depending on our testing period. I am posting this because I would like to see if anyone here is interested in acting as a beta tester for us when its further along in development.

While it is in Beta, there will be some limitations:

1. International Calling will not be supported
2. You will be limited to 30 concurrent calls on our network (15 per SIP Region - more on that later)
3. You will be limited to 1 call per second

Our SIP Registration deployment will support 2/4 regions - NW and NE. Your PBX will need to be configured to register to both regions and we will round robin from our regions to support multi-region redundancy. If we do decide to roll it out to all 4, your PBX would need to register to 4 regions in the config (which would be a pita to configure).

It is our intention to still strongly encourage the use of IP Authorization instead of SIP Registration. So we will probably have a few limitations for SIP Registration that do not exist with IP Auth. We also will not support connecting a desk phone or ATA directly to our network, even though technically it will be possible to do so.

A few things we're still thinking about:

1. We have not decided yet if we want to add registration to all 4 of our regions, or only support it in two.
2. We have not decided if we want to include SIP Registration in our SLA or leave it as a "Best effort" service. (TBH, I'm leaning toward including it in the SLA)
3. We have not decided on the Registration timeouts - some carriers enforce a full 1800 seconds and won't let you re-register faster than that. We're leaning toward a 6 minute Registration timeout, and providing guidance that you should re-register every 5 mins.
4. We are worried about fraud risk with SIP Registration. Since it is possible to get your carrier credentials compromised on an old PBX, it becomes possible for a Skyetel account to be compromised itself, rather than through a PBX. So we're thinking about having different balance requirements, or different verification methods, etc. We may also block SIP Registration on old PBXs (please people, stop using Trixbox for the love of god).

I'm interested in your gentle (cough Jared cough ) feedback. What have you guys had experience with, what suggestions or ideas do you have?

Hey Guys,

Behold our new sign up page!

From the feedback here, we made the following changes:

1. You can now re-use your mobile number on 5 new accounts per month (so go nuts @JaredBusch )
2. The new field "Direct Contact Number" serves as the direct phone number for the customer; this is the number we call if there is a fraud event or a porting emergency. (so please make it a real phone number)
3. We made it prettier

Thanks for everyone's feedback - feel free to take it out for a spin!

@Skyetel said in Skyetel needs to get over 11 digit numbers:

@JaredBusch said in Skyetel needs to get over 11 digit numbers:

FFS I cannot do a damned thing in their system without issues with fucking 11 digit numbers..

Today it was opening a support ticket.

1. Yes, I intentionally did not put the 1 in there. I knew that it would probably bitch.
2. Point 1 is not important though, as I do not have a DID that comes to me. That DID goes to an IVR. So I have to put an extension in there. But no, you can only ever use an 11 digit number on anything you ever do in the Skyetel portal.
3. Aside form the extension issue, like my point about the tenant contact info, the contact info for the person they need to call need not be a US based person. Just because I am working with a US based carrier on a US based number does not mean that I have to buy a US based number for you to call me when I am in Tokyo or London or WTF ever.

@Skyetel Have you all never thought about anything like this at all? Seriously?

Okay. You're right. We're over it.

Now you can use 10 digits so long as the first digit does not start with 1

... and you can add extensions into the support ticket request form

Signups will do the same tomorrow.

It is a Cloudflare outage, and it impacts about 30% of the internet. Details here: https://www.cloudflarestatus.com/

60F85B623E

Good till Saturday.

https://portland.craigslist.org/clk/sad/d/vancouver-telecom-support-tier-or/7426015530.html

Come join our team!

@scottalanmiller said in Skyetel is a scam:

I think that the situation here is that Jared has discovered a fringe use case that just isn't foreseen and was overlooked (and is eleven cents so no one has thought about it before.) No one is scamming over eleven cents, that's ridiculous, and if any of us posted this, Jared would be the first to tear into us.

Should those services be mentioned somewhere so that in this bizarre edge case there is a warning that you might lose a few cents for services you didn't check? Sure, I'll bite and say that that might make sense to have it somewhere so that people aren't surprised on an edge case like that by a few cents that they had not anticipated or to know to look to go turn it off in case they aren't going to want it.

But what needs to be understood is that this is a port of active numbers. Porting an active number that you don't want to use is really odd. Nothing wrong with doing that, just totally bizarre. If you don't care about the number why bother porting it? Because this is so weird, I think it has fallen through the cracks of simply being a use case no one anticipated. I certainly would not think of it, the nature of porting a number creates the assumption (which is almost always correct) that you also plan to use it. Otherwise we'd expect that you'd get a new, immediate number rather than doing an "expensive" port.

But jumping from "someone made a mistake and didn't anticipate that anyone wouldn't want this situation because everyone else probably does, I know I do" to "it's a giant scam trying to get my eleven cents" is a crazy leap that just doesn't add up.

@scottalanmiller this edge case was never really considered. We'll be adding the following to our port in page ASAP:

• Once your number finishes porting, usage and feature costs will begin billing immediately
• Caller ID Lookups & Spam Prevention is enabled by default.`

@JaredBusch said in Skyetel needs to get over 11 digit numbers:

FFS I cannot do a damned thing in their system without issues with fucking 11 digit numbers..

Today it was opening a support ticket.

1. Yes, I intentionally did not put the 1 in there. I knew that it would probably bitch.
2. Point 1 is not important though, as I do not have a DID that comes to me. That DID goes to an IVR. So I have to put an extension in there. But no, you can only ever use an 11 digit number on anything you ever do in the Skyetel portal.
3. Aside form the extension issue, like my point about the tenant contact info, the contact info for the person they need to call need not be a US based person. Just because I am working with a US based carrier on a US based number does not mean that I have to buy a US based number for you to call me when I am in Tokyo or London or WTF ever.

@Skyetel Have you all never thought about anything like this at all? Seriously?

Okay. You're right. We're over it.

Now you can use 10 digits so long as the first digit does not start with 1

... and you can add extensions into the support ticket request form

@Dashrender We refunded the mistake back to the credit cards if there was an auto-recharge. The refund should clear before the initial transaction does, meaning your credit card should only be charged what you should have actually paid.

Sorry about the headache this caused.

We rewrote our entire billing system and it worked perfectly... except for a single typo. Believe it or not, it was caused by a rouge "%" in a SQL query.

Full RFO to come

@JaredBusch I should clarify - IPO is not the plan. IPO being thrown around is because our volumes are now equivalent to publicly traded companies. Sorry for the confusion.

@JaredBusch said in Skyetel Acquired ...:

@scottalanmiller My only concern is that, while HFA was a simple PE firm, something is changing.

To be honest, this is actually a good thing. It's pretty hard to explain just how much I had to deal with that was completely unrelated to Skyetel's core products and services.

A lot of that crap are things I'm not great at. Dealing with HR issues, FBI subpoenas, contract reviews, changing federal regulations, etc all have nothing to do with what Skyetel actually does. I want to focus on the actual nuts and bolts of our products and services, and build cool things.

The team I'm surrounded by is really impressive. We have an attorney on staff now, a full group of HR people who know all the things about employment law, and a team of people who can help with all the other little things. It also more than tripled our development team, and quadrupled our support team (and all of those people report to me directly).

So it's scary when you read it in an email, but from my perspective, it's a huge relief. I'm just going to build cool things, and drive our innovation. Someone else can deal with regulations.

It's just some family friends of the founder and the founder joining teams.

This hits the nail on the head. HFA isn't some big greedy investment group - and I wasn't looking to retire. When we combine the traffic volumes of their holdings into Skyetel's network, we become big enough to where the letters IPO have been thrown around. It's insane.

The goal is to simply disrupt the market further. Many of Skyetel's competitors are now our customers - that's the scope of scale I'm excited about.

Shameless Plug
https://support.skyetel.com/hc/en-us/articles/360041178773-Voicemail-Transcription

We charge per VM, with no minimums or weird setups. You just use us for the PBXs SMTP server and we catch the VM in flight, transcribe it, and embed it in the email. It's one of our most popular features.

@romo said in Skyetel is Hiring:

Canada/US

Canada and US only.

@gjacobse said in Skyetel is Hiring:

@stuartjordan said in Skyetel is Hiring:

Looks like a nice position, shame i'm in the UK. I like the potato filter lol.

Item H: Remote Only Position

Though it does mention Anywhere in the US - but I don't see that as a true limiter...

We can't legally pay payroll to people in the UK without getting setup there first - so that's why it's limited to North America. There's also the timezone problem. We want to expand our support hours to include the east coast, hence this position is expected to work those hours.

"Potato" helps us insure people are actually reading the posting. Otherwise we just get SPAM

https://portland.craigslist.org/clk/sad/d/vancouver-telecom-support-tier-or/7426015530.html

Come join our team!