Loading...
Answers
MenuHow to Create a Smart Phone Support in a Virtual Business?
We want a system to plug into that doesn't require hardware and infrastructure but allows us to route calls to different people at different times - smart attendant, etc.
Answers
If you want a system that doesn't require any hardware or infrastructure, then a virtual PBX is the best bet. These systems just use your existing phone numbers (cell phones or whatever) and routes the calls among them.
The big player in this space is http://grasshopper.com/ They have been around for quite awhile and have a lot of features for managing calls. They're well known for their reliability and customer service.
I've also used http://www.ringcentral.com/ and they are very good as well. Never had any issues and they support various softphones and hardware phones as well.
I've also heard about a new up-and-comer https://aircall.io/ - But I know very little about them and they look to still be in beta. But you should definitely try it for comparison.
Related Questions
-
In what situations should a SAAS company offer phone support? In what situations should it only be email support?
In my opinion, phone support is frequently requested but hardly ever needed. I worked at Twilio and as part of my role as a Developer Evangelist I responded to help desk tickets part of the week. We didn't do any phone support and we were able to help people effectively. The key is to be very detailed, thorough and courteous in all your correspondence and also to ask for clarification if you don't understand their questions. You should also have a library of online resources like documentation, frequently asked questions and forums that you can refer people to so they can easily find answers for themselves once you point them in the right direction. One caveat to all that though: I worked at another company that provided phone support but it was something you had to schedule and pay for in advance. At first, I thought it was crazy but our phone support people were busy all day helping customers. It wasn't a lot and it didn't even cover our costs but it prevented your phone from ringing off the hook and people calling to ask really stupid questions. Hope that helps! Also, if you're looking for technical advice on setting up phone support options I'd be glad to help you... over the phone! :)AW
-
Good resources for structure/flowchart of an onboarding & ongoing support process?
I've helped lots of SaaS companies improve their onboarding processes over the years, but I just published my best (high-level) piece on doing this right: http://sixteenventures.com/customer-onboarding The bottom line is (though I suggest reading the entire article) you need to know what success looks like for your customer - what their Desired Outcome is - and then reverse engineer the steps necessary to get there. Going through that process will reveal the steps necessary to get them to that Desired Outcome outside of the product; we're not talking about functional steps within the product yet. Map this out using flow charts, line lists, mind map, white board, etc. The tool isn't important as much as doing this right. Now, once you understand the process required to move them from Step 0 - deciding to take action to reach their desired outcome to Step z - achieving their (at least initial) Desired Outcome, you can start laying out, designing, and building the in-product processes necessary to achieve those success milestones and ultimately, their Desired Outcome. You should then peg your email (or other lifecycle messaging) flow to those success milestones (rather than doing a timed follow-up), where each message is sent like this: "have they done this milestone? yes, then send this message to get them to the next one." Since each user and customer will achieve success on their own cadence, it's best to not have a timed autoresponder sequence but to actually trigger based on milestones reached. The good news is that this is relatively easy to do given the availability of lifecycle messaging services. See this post for more on this topic: http://sixteenventures.com/email-follow-up-sequence Hopefully this helps, but if you want more details or - more importantly - want to figure out how to apply this thinking directly to your situation, request at least a 15-minute call with me.LM
-
Are there standard ratios that are used to calculate first level support staff needed for a SAAS product that is a non-technical product?
Hi. I'm a Business Intelligence consultant with most of my customers being call centers. There are definitely guidelines you can apply but it will be based on several factors. Your question references ratios, which I assume means you would like to know how many agents per customer. That number will vary greatly depending on a number of other factors including: -what is your ASA target (Average speed of answer)? -what percentage of calls should meet the ASA? -are their penalties below a certain threshold (if less than 80% of calls meet ASA in 24 hours, for example) -how long are calls waiting when they don't meet ASA? -what is the call distribution by day of week, time of day and holiday v. non-holiday. -what is the average call duration? -what is the % of calls requiring escalation or call back versus calls resolved on first contact? To simplify it though, the two most important (IMO) will be call volume and your target for ASA (assuming you aren't answering then putting them back on hold, etc). To simplify though, the top 3 are: ASA, Call length and call volume. Regardless of the size of customer base. A good reporting system that combines live metrics and daily/weekly/monthly analysis will help a great deal. Feel free to set up a call if you'd like to talk about this in more detail.RL
-
I am a non tech entrepreneur desperately trying to find answer to highly technical and nuanced questions on the cheap.
The best way would be to hire an expert on oDesk, etc. which is fairly cheap and also reliable. But It sounds like you want to go even cheaper than that. Try posting on StackExchange, which is free. Another cheap option is to check local Meetup.com tech gatherings in your area and ask some experts directly for free advice. Good luck!II
-
I have an idea of a new type of wearable device, which I think is really huge. But I have neither the team nor funding, how should I proceed?
The best avenue for funding would likely be Kickstarter, but that presumes that the idea of a gesture-reading device is likely to have broad-enough appeal, which I'm not sure of based on the one line description. When I think about reading gestures, I think about a market primarily aimed at people with vision impairments. If that's the case, you might even want to look at foundations or organizations who might fund some of the research, but that will almost inevitably slow your pace of innovation. You might want to setup a call with Clay Hebert if you decide to go the Kickstarter route. https://clarity.fm/clayhebert Best of luck. Curious to hear more.TW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.