If you are a .NET shop, is there a reason you've not mentioned MS Dynamics CRM ?
While there is a cost associated with it, there is a huge amount of customisation you can do, and if, at some point, you decide to look at telephony, it'd be straightforward to do that too.
I have built CRM systems that integrate with a PBX based dialing system. We had a lot of success with home grown systems.
I would advocate a build from my personal experience for the CRM portion.
What you are asking about, however, is the Dialing side of the system. This can be built as well - the API's for the Dialogic cards lend themselves nicely to .Net implementations. Now that is going to take some work, and most cheap dialers have some decent functionality out of the box to do what we want it to do.
It is when you get to complex functionality that they give up the ghost and by that time you are already so far tied into them that going into a new system is not feasible. I have seen this happen over and over again too.
If you have decent talent on hand, I would advocate writing the dialing system as well if you see yourself having to handle issues more intricate than your basic off-the-shelf dialer can handle.
发布评论
评论（2）
如果您是一家 .NET 商店，您是否有理由没有提到 MS Dynamics CRM？
虽然存在相关成本，但您可以进行大量定制，如果您在某个时候决定考虑电话技术，那么这样做也很简单。
If you are a .NET shop, is there a reason you've not mentioned MS Dynamics CRM ?
While there is a cost associated with it, there is a huge amount of customisation you can do, and if, at some point, you decide to look at telephony, it'd be straightforward to do that too.
我构建了与基于 PBX 的拨号系统集成的 CRM 系统。我们在自主开发的系统方面取得了很大的成功。
我主张根据我个人的经验来构建 CRM 部分。
然而，您所询问的是系统的拨号端。这也可以构建 - Dialogic 卡的 API 非常适合 .Net 实现。现在这需要一些工作，而且大多数便宜的拨号器都有一些开箱即用的不错的功能来完成我们想要它做的事情。
当你接触到复杂的功能时，它们就会放弃幽灵，到那时你已经与它们捆绑在一起，进入一个新系统是不可行的。我也一次又一次地看到这种情况发生。
如果您手头有不错的才能，如果您发现自己必须处理比您的基本现成拨号器可以处理的更复杂的问题，我建议您也编写拨号系统。
I have built CRM systems that integrate with a PBX based dialing system. We had a lot of success with home grown systems.
I would advocate a build from my personal experience for the CRM portion.
What you are asking about, however, is the Dialing side of the system. This can be built as well - the API's for the Dialogic cards lend themselves nicely to .Net implementations. Now that is going to take some work, and most cheap dialers have some decent functionality out of the box to do what we want it to do.
It is when you get to complex functionality that they give up the ghost and by that time you are already so far tied into them that going into a new system is not feasible. I have seen this happen over and over again too.
If you have decent talent on hand, I would advocate writing the dialing system as well if you see yourself having to handle issues more intricate than your basic off-the-shelf dialer can handle.