Jump to content

Rick Guyton

Customers
  • Posts

    628
  • Joined

  • Days Won

    41

Posts posted by Rick Guyton

  1. If the copy tool is only used for same make and model, no problem. 
    Sweet! Have the in the utility next week then? ;)

    In all seriousness, Karl uses dirty Polycoms, I use awesome Yealinks and some crazy people out there even use Ciscos. But, we all pretty much "Make" exclusive and we all pretty much deploy the same models across our networks. For example, I deploy all T27Ps with a few T46Gs here and there for execs or receptionists. But if in a 40 phone network, I only had to configure one T27 and one T46 and then copy, copy, copy. That would save us hours of work... Hours of mind numbingly tedious work. AND it'd be 100% accurately copied across whereas when we do it manually, we eventually mess up somewhere...
  2. We always ask the client if they've ever actually used it before. If they have, they know how bad it is. and we say something like "we don't offer it because even goggle does it terribly. We figure if they can't get it done well, no one can". Most times they nod and agree, and move one. At that point we'll tell them if they really want it, they can use myscribbit.com for $5/month/mailbox and we'll help them set it up. NO ONE has taken us up on this.

    If they haven't used it before we tell them it's one of those things that sounds really awesome until you actually use it because it's so inaccurate. Then, we generally get the head nod and go down the same path. Still no takes thus far.

    We really like talking about myscribbit.com though. That way we aren't saying no. They are deciding it isn't worth it.
  3. Hi Darren, I'd imagine that you wouldn't try to make sure both accounts are under the same re-seller at all. I'd think you would setup a "secret key", maybe use the existing API key value of an account. Then, when you "link" accounts the account exchange secret keys and have access to each other. At that point, they obviously have an affiliation so what does it matter if one is a CleaRing client and the other is a Slable client? As for call flows, I see that issue. I'd imaging you'd have a "feature code" for accessing another account. Like Account A would subscribe to AccountB#100 for a BLF to see BLF for ext 100 in account B.

    Of course, I say this as someone who's never even looked at your code and has a basic understanding of the architecture. And I get that.

    I see two separate use cases here. First is for a single company with multi-locations. For them, really it'd be mostly about using Smart PBX. Man oh man it's hard to convert someone from using Smart PBX to ADV callflows just because they add a location. They hate it. Second though is separate companies that want to be affiliated for some reason. For instance, I had three clients that shared adjoining suites. They relied on each other heavily and wanted to be able to page/intercom/ect so I put them into one account. Well, then they eventually split up and went their separate ways. Man that was rough. I've also had a virtual receptionist company approach me wanting a way to see status of their clients.It was really hard to see a multi-hundred handset account walk because I had no solution for that. But, oh well...
  4. I've been wanting this forever too. It'd be amazing if accounts could see eachother's BLFs and easily transfer to eachother. It would also resolve my bigges frustration with SmartPBX, that it doesn't support multi-location. We could just create separate accounts for all of them, then bridge them. 

    I don't know about you all, but I'm willing to put my money where my mouth is on this one. I wonder how much it'd take to get 2600hz to develop this...
  5. It would be very helpful if there was a "Play Media" option in the SmartPBX call menu. Many of my clients want to give their customers an option to hear address, fax and business hours information. This is impossible to do with out going into advanced callflows. and I'm really trying to do most of my work in SmartPBX where possible.
  6. Hi Kristin, thanks for the description of the situation. It made me remember that when you change something in account settings it warns you that it will generate all new config files. Made me wonder if perhaps that would force it generate a config for that new MAC. Sure enough, I changed the admin password in account settings, saved it, accepted that all new configs would be generated and BOOM, there was my phone. When I have some spare time, I'll replicate the problem and the solution again a couple times just to be sure. But, it sounds like a good work around to me.
  7. Thanks Kristin, I got one in today. The screen size was almost identical to a T22P as was the feature set. So, I tried that provisioning profile and it provisioned flawlessly. I made a few test calls to an echo test and was incredibly impressed. I called a few of my friends and walked around the room. They could tell it was a speaker phone, but thought it was very clear sounding for a speaker phone. I'm going to deploy it to a new client next week. I'll let you know what they think of it.
  8. Hi Karl. Yea, we were using FlowRoute to manage all our toll free number for exactly this reason. Then 2600hz decided that that'd cost me $200/month to continue doing (for BYOC). So... I figured my potential downside on international calls was not nearly as high as $200/month. And with that logic, I somewhat begrudgingly ported them over and sucked it up on potential international calls.

    Now that I'm able to run these reports though, I see that I've really been raking it on on these toll free numbers. Not a single account has ever exceed $30 in tolls in a month. I think because all of these accounts also have local numbers as well and they all call out with the local caller ID. So their clients are much more likely to save the local number than the toll free.
  9. Hi Katie,
    I've looked at it and I like what I see. It's really nice to be able to pull a report and make sure that I'm profitable across all of my accounts. And I really like the ability to do this.

    What'd be nice is if I could pull the Calls to UNITED STATES - INBOUND TOLL FREE. from an API somehow. What we do right now is just charge a flat $30/month for a toll free number, then hope that toll fees don't exceed the $30.

    Also, we don't currently allow international calling at all. Because, well we can't really bill for it.

    You might say that I could just pull this report every month and get these figures, then add them to the bill. To that, I'd say you are right. But, we only offer items that can be billed out automatically. 
×
×
  • Create New...