6/11/2023 0 Comments Visual dialplan for asteriskI would say the order is fix bugs, fix bugs, improve call routing, enhance mobile applications. We too have to loop calls in all kinds of hackish ways to meet our customer's needs with the existing very basic routing options. Discussed this numerous times with you historically and even provided a very detailed writeup on call flow either on the forums or in an email to you on the need for improved call flow (Matt's "6c") with custom flow destinations and variables. Create global phone templates (If you can today let please let me know)Ĭouldn't agree with Matt more. ![]() Combine/link operator and time based routes - now we have to loop callsħ. Route on Labor day, Thanksgiving & day after, etc instead of having to update every year - Ĭ. Yealink phone apps (I could see paying per seat for this)ī. Current documentation for administrators/resellersĥ. Improving mobile applications - it is rapidly going to a mobile first worldĤ. I would rather see every penny spent toward:ģ. ![]() ![]() If you move forward please budget to have professional documentation produced we can give to the end user. ![]() If it took one person 2 days to code it would be a nice selling feature but it would take longer to train the user on how to use it than to do it ourselves. In my experience customers very rarely change their IVR once it is programmed. I am assuming you mean something like the picture I attached.
0 Comments
Leave a Reply. |