Skyetel's Spring Update



  • Hey Guys - we just announced our Spring Update. This update is the largest update in our history.

    Check out the details here:
    https://skyetel.com/skyetel-spring-update/



  • Wow! That’s quite an update! I need preferred pricing shoot me a PM 😉



  • @Skyetel give me an API to upload my own recorded calls for transcription. Or an email to send them to. I don’t want all calls on any phone number transcribed.

    Currently only a few users want voicemails transcribed.

    I’m using a service (Nexiwave) for that now, where I have to email the wav file.

    Edit: new features are good. Didn’t mention that.



  • @JaredBusch said in Skyetel's Spring Update:

    @Skyetel give me an API to upload my own recorded calls for transcription. Or an email to send them to. I don’t want all calls on any phone number transcribed.

    Currently only a few users want voicemails transcribed.

    I’m using a service (Nexiwave) for that now, where I have to email the wav file.

    Edit: new features are good. Didn’t mention that.

    Thanks @JaredBusch

    For Voicemail Transcription, we actually offer that as a separate feature entirely:
    https://skyetel.atlassian.net/wiki/spaces/SUG/pages/67174401/Voicemail+Transcription
    You can access it here:
    https://login.skyetel.com/#voicemail-transcription
    (Depending on your voicemail volume, we might be cheaper than Nexiwave)

    We didn't think about an email -> call transcription idea. I'll suggest it for you to our development team 🙂



  • Awesome stuff. Looking forward to using a lot of this!



  • @Skyetel

    Perhaps this deserves another thread entirely, but I use Flowroute at the moment, so feel free to fork this if that is best.

    How does Skyetel differ from Flowroute?

    I know that is a very open ended question, but you guys look awesome. I've had almost no problems with Flowroute, but am always on the lookout.



  • Hey @fuznutz04

    I'll let you fork this if it gets too crazy - I don't want to clutter the board if this is a sufficient answer :).

    The short answer is features and rates. While Flowroute is regarded as one of the very best telecom carriers, they have fewer features than we do. (This is probably because they always intended to be bought by a regular telco and didn't want to complicate their core business - but this is me speculating and I could be wrong). To name a few features we offer that they don't: Voicemail Transcription, Spam Call Prevention, Fax to Email, Call Recording, and PBX Health monitoring (My Favorite Feature!).

    Our retail pricing is also lower and our relationship pricing is much lower. We also don't have a lot of the volume requirements that they do to get into the more aggressive pricing (we do have other requirements detailed here: https://mangolassi.it/topic/19453/skyetel-relationship-pricing)

    I'd also say our support and porting is better, but those are subjective and I'm obviously biased 😛



  • @Skyetel said in Skyetel's Spring Update:

    Our retail pricing is also lower and our relationship pricing is much lower. We also don't have a lot of the volume requirements that they do to get into the more aggressive pricing (we do have other requirements detailed here: https://mangolassi.it/topic/19453/skyetel-relationship-pricing)

    Thanks! What about the underlying technology? In other words, Flowroute has their "Hyper network" to minimize outages, and also directly routes audio traffic. According to the documentation I found on your site, it appears that you have the same type of technology. Is that correct?

    Another thing that Flowroute that they market as a positive, is that they are a carrier themselves. Is Skyetel also a carrrier?



  • @fuznutz04 said in Skyetel's Spring Update:

    @Skyetel said in Skyetel's Spring Update:

    Our retail pricing is also lower and our relationship pricing is much lower. We also don't have a lot of the volume requirements that they do to get into the more aggressive pricing (we do have other requirements detailed here: https://mangolassi.it/topic/19453/skyetel-relationship-pricing)

    Thanks! What about the underlying technology? In other words, Flowroute has their "Hyper network" to minimize outages, and also directly routes audio traffic. According to the documentation I found on your site, it appears that you have the same type of technology. Is that correct?

    Another thing that Flowroute that they market as a positive, is that they are a carrier themselves. Is Skyetel also a carrrier?

    Yes - we both route our calls so that we are not in the audio path. Flowroute and Skyetel are both legal carriers, but we have different classifications in the "Carrier" bucket. Flowroute is a CLEC and Skyetel is an IVP (Interconnected VoIP Provider). Both allow us to do the same thing, but the numbering authority IVPs have weren't available when Flowroute became a CLEC and at the time it was their only option. I suspect that if Flowroute was reviewing their regulatory options today, they would have have chosen the IVP + NA (numbering authority) instead of CLEC (this is what Telynx did). However, I am again speculating. They may have had other reasons for pursuing a CLEC license at the time that I don't know about.

    In terms of the outage minimization - we have different philosophies on how best to do it. Those get crazy detailed and specific lol. A fundamental architecture summary I can give is this: Skyetel prefers Multi-Primary to Primary/Failover. The simple explanation here is that it takes much more for our backend architecture to fail (because all of our datacenters and interconnects need to fail at the same time and they are all active), but if a situation does present itself where everything does fail, it would take us longer to recover and it would be a total outage. Flowroute's architecture will cause them to fail more frequently, but recover more quickly; also they are more prone to regional issues rather than network-wide ones. Both have their pros & cons.

    To give credit where credit is due - Flowroute's architecture is excellent. I obviously think our network is better, but Flowroute is one of the carriers we have a lot of respect for.



  • @Skyetel said in Skyetel's Spring Update:

    To give credit where credit is due - Flowroute's architecture is excellent. I obviously think our network is better, but Flowroute is one of the carriers we have a lot of respect for.

    Excellent. Thanks for the explanation here! I'm sure I'll have more questions later. 🙂 I''ll get in touch with you later to discuss directly.


Log in to reply