Skyetel tenant functionality



  • https://skyetel.atlassian.net/wiki/spaces/SUG/pages/664141827/Tenants+Invite+Only+Alpha

    @Skyetel said in I guess Skyetel doesn't want business:

    @JaredBusch said in I guess Skyetel doesn't want business:

    @Skyetel said in I guess Skyetel doesn't want business:

    @JaredBusch said in I guess Skyetel doesn't want business:

    @Skyetel said in I guess Skyetel doesn't want business:

    The ideal situation is to have the end user create their own account and have the IT team administer it. You don't have to share an account - you can create a new account for the IT Administrator and he can administer it directly without sharing credentials. (Thats what @scottalanmiller does)

    There is no menu, that I can find, to create a sub account on my account to enable someone else to log in and administrate my account.

    Shoot in a support ticket and they create them for you along with a temporary password.

    Part of this?
    https://skyetel.atlassian.net/wiki/spaces/SUG/pages/664141827/Tenants+Invite+Only+Alpha

    Tenants is being designed for use cases such as this and is under active development. It will also include a Tenant Portal where end users can view their assets (like phone numbers or call recordings or faxes) without being able to make changes or with different permissions from the Administrator.

    So with the issues of being able to get a Skyetel account created soon to be mitigated, I'm looking at the functionality I need out of them for the client that started me down this road in the first place.

    This client has multiple offices and needs/wants to be able to track out billing separately for each office.

    With most SIP trunk providers this has meant multiple accounts with multiple email addresses. Twilio was the first provider I found that I could set up one account and then have sub accounts all with separate billing.

    Skyetel does not yet have anything public, but as was mentioned in my previous thread, they have some tenant functionality in alpha testing.

    I dug into the linked article andI'm not sure if it will work well for my scenario or not. For a place reselling phone service via Skyetel, this looks like a solid solution in the works.

    But for this client, they just want to know that when I recharge $200 with their credit card that it is all going towards Office C and not Office B. Tenant reporting seems to all be in arrears. and not something designed for this billing scenario.

    Are any of the @Skyetel users in this community using this functionality yet?
    How is it working?
    Would it fit my billing need?



  • @JaredBusch said in Skyetel tenant functionality:

    This client has multiple offices and needs/wants to be able to track out billing separately for each office.

    Tenants has two intended use cases:

    1. People who are reselling Skyetel's services, and want to be able to track, brand and re-bill our services under their own name
    2. Companies who want to be able to break out different parts of their usage into groups that are meaningful for reporting and reimbursement.

    In both cases, there is only one billing relationship. So we would bill the Skyetel account holder, and then based on how each of the Tenants used our services, the account holder would see where the money was spent. Each Tenant does not have their own Skyetel account - and it would be up to the Skyetel account owner to sort out being reimbursed if the owner of the Skyetel account is different than the user of our services.

    That being said, we have been discussing a Reimbursing concept. (This would kinda be a third option) The idea would be that BundyIT would own the Skyetel account and your customer would only have access to Tenants (basically a read-only version of the Skyetel portal). They would associate their credit card to that Tenant account, and at the end of the month we'd charge it and "reimburse" your Skyetel balance whatever the amount that Tenant used. The downside to this is that there would be a period of time where you are sorta floating them. The upside is that it does keep things sticky between you and your customer and prevents them from making changes that are harmful. (this also prevents you from having to worry about the taxes and things - since the Tenant would clearly see they are Skyetel customers)

    This wouldn't apply to your use case, but we also plan on building a billing system for our resellers where they can add markups, pricing plans, etc.

    We have also talked about creating a separate feature where one Skyetel login would give you access to multiple Skyetel accounts. So you could sign up your customer for us - they'd have their own account and their own billing - but your login would let you manage all of their numbers and endpoints along with every other customer you have approved access for. We tend to prefer the idea of Tenants and Reimbursement to this, but if guys have more feedback about it, let me know. (Multiple accounts per login wouldn't be built till after tenants, and would be a huge change to our authentication system - so this would take months to build)

    We're building all of this right now and can make changes based on feedback. So please feel free to give us ideas and suggestions 🙂



  • @Skyetel said in Skyetel tenant functionality:

    We're building all of this right now and can make changes based on feedback. So please feel free to give us ideas and suggestions 🙂

    That's why I posted.



  • @Skyetel said in Skyetel tenant functionality:

    @JaredBusch said in Skyetel tenant functionality:

    This client has multiple offices and needs/wants to be able to track out billing separately for each office.

    Tenants has two intended use cases:

    1. People who are reselling Skyetel's services, and want to be able to track, brand and re-bill our services under their own name
    2. Companies who want to be able to break out different parts of their usage into groups that are meaningful for reporting and reimbursement.

    This is what I got from my reading and the post in the prior thread. Neither of these scenario's fit this client's needs.

    I do not resell. So that entire part of your design is something I exclude. Now, that does not mean I cannot still make use of some of those features if it works. But knowing that it was not the designed target means I do not try and shove it where it does not fit, though I still try it on.

    Here is the scenario in a little more detail.

    Client has 4 offices. All costs are tracked separately for each location. Basically they are mostly treated as wholly separate companies.

    Recurring costs paid by credit card, like voice service, are all paid with a single card. So with VoIP.ms, I setup 4 separate accounts with email aliases for each branch.

    Obviously, I can do this with Skyetel also, but honestly, it is a pain in the ass to have to have 4 separate accounts.

    With Twilio, I was able to create a project for each location.
    01fb975e-0e39-4d97-8355-4f25a2024503-image.png

    Each project has its own billing setup, same card at each, but when it is recharged, I know which project it was for, as they all track separately, and I can send a note to the client's accounts payable person that Jeff City just added $20. Then accounting will make a note in their system that the $20 on July 5th, 219 was is charged against company X in their ERP.

    b305e42e-3309-4bed-9904-5b6f960e15c8-image.png

    So those are different scenarios for how I have dealt with a situation like this. Your tenant infrastructure does not feel like the right fit for this need. Close, but it is size 12 boot, while the client wears a size 10 Wide.