I'm looking for advice on setting up a phone system for customers to call in. We've experimented with both Twilio and Grasshopper and had some reliability issues (calls not going through, voicemails being left on employees phone, etc).<p>Any operationally heavy startup out there figured out a good option on a budget?<p>Matt - Founder at ScriptDash
If you want something you understand and can control, you could build your own phone system with Asterisk. Inbound calls could come via VoIP (if you can find an upstream phone company you trust) or PSTN (if you're willing to invest in having the necessary ISDN/phone line installed, and in the hardware to connect to those).<p>If you're doing it for the first time, you might be best served with specialised Linux distribution (e.g. Elastix[0] or PIAF[1]).<p>The cool thing about this type of setup is that you can do pretty much what you want (e.g. triggering scripts when calls come in, setting up fancy call routing rules, ...). The not-so-cool thing is that there's a learning curve and, if you doing anything fancy, then someone will need to make sure those things are working solidly. Also, as with any other server, you need to arrange for backups and disaster recovery.<p>[0] <a href="http://elastix.org/" rel="nofollow">http://elastix.org/</a>
[1] <a href="http://nerdvittles.dreamhosters.com/pbxinaflash/" rel="nofollow">http://nerdvittles.dreamhosters.com/pbxinaflash/</a>
It sounds like primarily a level of service problem.<p>This might [0] be a case where having your own POTS [1] hardware makes sense. There is a vast expert technical infrastructure to support POTS and it is dedicated to reliability. The marketplace is highly competitive across market segments, by which I mean that there is heavy competition for two line systems and five hundred line systems. Above a certain threshold many systems are modular and provide 2x-4x linear growth.<p>Sure, maybe it won't scale out to a vast distributed team and you'll have to swap it out in two years and that will be painful. In two years your company will be swapping out phone systems if it is successful anyway...or it will be putting up with a system that's designed for the wrong larger scale until your company grows into it. That friction will probably reduce the the odds of getting there.<p>Telephony is hard enough to have given us Unix, C, Erlang, and information theory. For a business (and it looks like your company may be one) that will live and die by it's telephone system, controlling the hardware is consistent with Spolsky's approach to StackOverflow: it has its own servers because it can't afford to have critical infrastructure maintenance and repair happen on someone else's timeline. [2]<p>Good luck.<p>[0]: Or might not.<p>[1]: I'm cheating a little with "POTS", probably there's a VOIP component, but the big idea is a box in the closet with some telephony company's logo on it and a box of user manuals on a shelf.<p>[2]: edit - I might double down on controlling telephony as critical because of HIPPA.<p>[3]: edit - Outsourcing may make sense for non-patient call streams...e.g. sales and vendors and other generic business operations where a lower level of service might be acceptable.
I have heard good things about these guys. They got accepted into TechStars and rejected the offer and are doing very well. They have great reviews for their services. Here it is <a href="http://talkroute.com" rel="nofollow">http://talkroute.com</a>
Mightycall looks solid. I currently use TalkDesk - but do not like it - so am also in the market for a switch. I also found Bitrix42 but seems to offer way more features than I need. any others out there?
i like 2 options:<p>1_ Mightycall (<a href="http://www.mightycall.com" rel="nofollow">http://www.mightycall.com</a>)<p>2. Skype with a business phone number.<p>Wasnt too happy with grasshooper which I also tried.