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
-
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
-
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
-
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
-
What SaaS should I use to coordinate email communication with customers so our whole marketing team has one consistent voice?
HelpScout, ZenDesk or Desk.com. HelpScout (help desk software) would be a great start – less options but even when I ran a 6 person customer support team (with over 500 emails a day), we never needed the complex features of Desk.com. Have one person create 'saved replies' to quickly answer your customers in a cohesive voice and with consistent responses. (However, encourage your entire team to inject some of their personality!) This seems like a huge task, but if they dig through their sent emails, it can be done pretty quickly. Good luck!DM
-
What is the best technology for developing a new mobile app from scratch?
There are two sides to that question. One is the mobile app itself and the other is the backend. If I misunderstood in any way and you didn't mean "native" app I apologize in advance. On the backend, there is no clear cut answer to which is the "best". It depends solely on the developers you are able to get. We for example use Node.js , mongoDB, redis, elasticsearch and a couple of proprietary tools in the backend. But you have your pick of the litter now both on the backend api and the datastore with the myriad of options available and touted as the "best" currently on the market. Now on the app side again it solely depends on what you need your mobile app to do. Experiencing first-hand "develop once, run anywhere" I can say it's more like "develop once, debug everywhere" to quote a Java saying. We have tried Phonegap and Titanium Appcelerator and we have switched to native (ObjC and Java) after a couple of months of trying to go the hybrid route. The reasons behind the choice are as follows: - anything that breaks the pattern of how those frameworks NEED to operate is just a huge technical debt that keeps accruing a huge interest. - anything that uses css3 accelerated animations on Android is buggy at best and slow as hell at worst on any lower (< 4.1 I think) versions of Android I hope this gives you some insight. If you need/want to ask me anything feel free to contact me. MihaiMP
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.