3CX Call Flow Design, with database scheduling
- or -
Post a project like this£23/hr(approx. $29/hr)
- Posted:
- Proposals: 1
- Remote
- #3455550
- Expired
Description
Experience Level: Expert
Estimated project duration: less than 1 week
We have a requirement for a 3CX Call Flow Designer to create a call flow service.
With the extra functionality as above also.
The requirement:
We have a 3CX Linux server and a database server accessible to the 3CX server.
We need a caller to call into our 3CX server out of hours choose from a menu the product and leave a voicemail. This will be for X amount of voicemail boxes. One per product.
That voicemail should then be noticed by the service, triggering an outgoing call to a scheduled on call engineer. And an update to the database, to show the voicemail file, and that the voicemail is not yet heard. Calls should be logged in the database and if the call was answered.
The engineer may not answer and the call should not be long enough to go to the engineers voicemail. So 15 seconds (As below parameters).
If the engineer does answer, they should be presented with the voicemail. Then the engineer must acknowledge, once listened to the voicemail, this should trigger an update to the database that the voicemail is heard and accepted. Thereby stopping any further chasing of engineers.
Or if refused, enabling further chasing of engineers.
If the engineer does not answer, then there should be another call triggered. There should be an on call rota of engineers, within the database.
The rota will have different priorities of engineer, so that an escalation happens.
If there is nobody scheduled for on call. Then there should be a default schedule to follow. There should never be a voicemail on the out of hours voicemail extensions not listened to, without the system calling engineers.
Configuration parameters stored in the database should be set, and used for the following:
Time to call (initially 15 seconds)
Time between call attempts (initially 180 seconds)
Also the Voicemail extension(s) to monitor
Outgoing calls should take place in the following pattern. (eng meaning engineer)
eng1
eng2
eng3
eng4
and so on
As opposed to:
eng1
eng1,eng2
eng1,eng2,eng3
eng1,eng2,eng3,eng4
and so on
So only one concurrent chasing call at any one time. All unheard voicemails would need to be offered and played to the engineer in that one call.
Systems:
Linux 3CX server on AWS. (Version 18 of 3CX)
Windows Server on AWS with IIS and MSSQL installed also 3CX CFD (Version 18).
Please let me know if there are more details required in order to quote.
With the extra functionality as above also.
The requirement:
We have a 3CX Linux server and a database server accessible to the 3CX server.
We need a caller to call into our 3CX server out of hours choose from a menu the product and leave a voicemail. This will be for X amount of voicemail boxes. One per product.
That voicemail should then be noticed by the service, triggering an outgoing call to a scheduled on call engineer. And an update to the database, to show the voicemail file, and that the voicemail is not yet heard. Calls should be logged in the database and if the call was answered.
The engineer may not answer and the call should not be long enough to go to the engineers voicemail. So 15 seconds (As below parameters).
If the engineer does answer, they should be presented with the voicemail. Then the engineer must acknowledge, once listened to the voicemail, this should trigger an update to the database that the voicemail is heard and accepted. Thereby stopping any further chasing of engineers.
Or if refused, enabling further chasing of engineers.
If the engineer does not answer, then there should be another call triggered. There should be an on call rota of engineers, within the database.
The rota will have different priorities of engineer, so that an escalation happens.
If there is nobody scheduled for on call. Then there should be a default schedule to follow. There should never be a voicemail on the out of hours voicemail extensions not listened to, without the system calling engineers.
Configuration parameters stored in the database should be set, and used for the following:
Time to call (initially 15 seconds)
Time between call attempts (initially 180 seconds)
Also the Voicemail extension(s) to monitor
Outgoing calls should take place in the following pattern. (eng meaning engineer)
eng1
eng2
eng3
eng4
and so on
As opposed to:
eng1
eng1,eng2
eng1,eng2,eng3
eng1,eng2,eng3,eng4
and so on
So only one concurrent chasing call at any one time. All unheard voicemails would need to be offered and played to the engineer in that one call.
Systems:
Linux 3CX server on AWS. (Version 18 of 3CX)
Windows Server on AWS with IIS and MSSQL installed also 3CX CFD (Version 18).
Please let me know if there are more details required in order to quote.
Dean T.
0% (0)Projects Completed
-
Freelancers worked with
-
Projects awarded
0%
Last project
25 Apr 2024
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies