Jump to content

Rick Guyton

Customers
  • Posts

    628
  • Joined

  • Days Won

    41

Posts posted by Rick Guyton

  1. Well, yea. In the base fee senario, I'm still paying the $500 a month, but it's not really getting me anything. It's just turning the app on. In the minimum scenario, my costs are at least going to pay for the queues. So, at 30 agents, I'm still paying $500/month. As opposed to $590 for base fee + per agent costs.

    Even if you had a solution with a lower base rate with the agent cost + queue cost, I'd still rather pay a minumum on a straight up per agent cost. Then I know that I have a clear pathway to be profitable on it. The per agent+per queue+the flat rate thing... the only pathway I see to profit is to code out a replacement using pivot and real time call control eventually.
  2. See, you threw another feature in there to justify the cost. Call recording. I do see a $10 markup with hosted providers. But, to my mind the markup seemed to mostly due to the fast that those users are going to be on their phones more, using more minutes. $10 markup for a queue breaking down to $5/month/queue license + $3-4/month/to cover increased carrier costs + $1-2/month to cover recording. Maybe it's just me though...
  3. @Darren: Your example is really confusing. You are throwing call recording (that we can't offer yet) and faxing (still limited) into the mix there. What's your thought on the value by itself of a single call queue license for an agent/device? To me, it's about $5/month. And that's my gripe. So, if we are doing only small accounts with these queues like you've asked, say an average of 5 phones, at $3/user + $10/queue I'm getting NO markup there. Then I have to pay $500 and I've got a new feature to support on my side. It really doesn't matter how much volume you throw at these numbers, I'm still loosing out on the feature.


    @Jeff: LOL, I think you think I'm a lot bigger than I am man. :)
  4. With the new Yealink firmwares, the ones you have to support for the new models, there's an option for "include:config". This allows you to reference a separate file that's included in the provisioning profile. If put the custom settings into a seperate file and used the include:config, you now have an easy way to toggle their custom settings. Now, in that senario here's the answers to your questions:

    1) Step one for a suspected provisioner issue is now disable the custom file on that phone. You'd want it to be toggleable in the GUI. And factory reset the phone. If it works, it's on the reseller to fix.

    2) This kind of comes down to limiting your tolerance for custom configs. You'd want to set some max amount of hours you'll invest before requesting a removal/reset as referenced in step 1. Maybe you tell the reseller that you can only put an hour into the investigation before you need to replicate it with a clean un-customized config.

    3) Custom config overwrites generic config. Easy peasy. That's the default mode actually.

    4) Yea, I kind of agree that firmware would have to stay standardized.

    Finally, with the separate config file, before really delving into anything, you can easily check to make sure the reseller hasn't done something hair brained.

    Oh, and I'm 99% sure this is a thing on Polycoms too.
  5. No. We "PreProvision" some of our phones for things like this. Basically, we setup our phone to first provision via our web server where we host some generic configs. That apply a few little things, then points to the zswitch provisioner. There's two problems with this though. First is you can't set any settings that the zswitch server will override such as combo button settings. Second is that you basically only get one shot at applying settings. If you decide you want to add more custom settings later, you are up a creek.
  6. Well, I think we've had more than two. But yea, it's low enough that I don't really care. And I've never had one break while under warranty. The only concern is that technically, phones purchased through grey market don't qualify for use with their RPS system. And it's really nice that when someone factory resets one of our phones, it just reprovisions with us automatically. I've never seen a phone that actually wouldn't provision because of this. But, I'm not buying may phones that way either.
  7. We have a deal for 75 phones coming up right now. To get it done, we are going to have to pull onto two separate vendors to get all t46g. And we are definitely going to get sub optimal pricing because of it. I'm not sure that this is a crisis right now. But, it sure isn't going to be long before it is.

    EDIT: to be clear, I am excited about OPUS. But, I certainly don't think it's going to sell any deals.
×
×
  • Create New...