nocode-js" Based Telephony System
Budget: $1,500 – $3,000 USD
General Description:
Development of an independent telephony system focused on designing telephonic processes using a graphical interface (Sequential Workflow Designer), operating solely on the client-side without Sequential Workflow Machine or Sequential Workflow Editor only the Sequential Workflow Designer that should output json and debug session
Modules/Actions:
get_variables_from_api: Implementation of retrieving variables from an API.
open_webhooks: Ability to open and configure Webhooks.
hangup: Option to disconnect a call.
recordsound: Recording sounds during a call.
if: 'If' condition action for logical decision-making.
dial: Dialing given numbers.
ivrmenu: Creating a dynamic IVR menu.
playfile: Playing audio files.
playvalue: Playing dynamic values.
send_sms: Sending text messages.
send_email: Sending Email messages
voice_mail: voice mail that record message and send it to email
if_schedule: Executing actions according to a schedule.
spam_blocker: voice captcha to block spam
Sequential Workflow Designer Capabilities:
Version Saving: Ability to save up to the last 10 versions and revert to them.
Mobile-friendly Interface: An interface that is adapted and easy to use on mobile browsers.
Handling Audio Files via AJAX Requests:
For the playback of audio files, AJAX requests will be used. This section will include: Implementation Details: Technical details on how AJAX requests will be structured and handled within the system to retrieve and play audio files.
Debugging Features:
Audio File Playback: In DEBUG mode, enable the playback of audio files .
Phone Keypad Simulator: For components requiring user input (DTMF) like ivrmenu , include a simulator of a phone keypad for script debugging.
like this example
image.png
Flexibility in JSON Structure:
Despite having an existing JSON structure, there is full flexibility for changes to accommodate server-side operations programmed in the telephony environment.
Rights and Publication:
The code for the development will not be published and will not be part of the open source.
Documentation:
Include comprehensive documentation of the system, including guides for users and technicians, API documentation, and troubleshooting guides.
Adding New Modules:
To ensure flexibility and scalability of the system, it is important to include clear and detailed instructions in the system documentation for adding new modules. This will include:
Module Development Guidelines: Description of the system's internal interfaces, including technical details like API interfaces, conventions, and expected module behavior.
Documentation Requirements for New Modules: Standards for documenting new modules, including technical specifications, how to for the developer .
Development of an independent telephony system focused on designing telephonic processes using a graphical interface (Sequential Workflow Designer), operating solely on the client-side without Sequential Workflow Machine or Sequential Workflow Editor only the Sequential Workflow Designer that should output json and debug session
Modules/Actions:
get_variables_from_api: Implementation of retrieving variables from an API.
open_webhooks: Ability to open and configure Webhooks.
hangup: Option to disconnect a call.
recordsound: Recording sounds during a call.
if: 'If' condition action for logical decision-making.
dial: Dialing given numbers.
ivrmenu: Creating a dynamic IVR menu.
playfile: Playing audio files.
playvalue: Playing dynamic values.
send_sms: Sending text messages.
send_email: Sending Email messages
voice_mail: voice mail that record message and send it to email
if_schedule: Executing actions according to a schedule.
spam_blocker: voice captcha to block spam
Sequential Workflow Designer Capabilities:
Version Saving: Ability to save up to the last 10 versions and revert to them.
Mobile-friendly Interface: An interface that is adapted and easy to use on mobile browsers.
Handling Audio Files via AJAX Requests:
For the playback of audio files, AJAX requests will be used. This section will include: Implementation Details: Technical details on how AJAX requests will be structured and handled within the system to retrieve and play audio files.
Debugging Features:
Audio File Playback: In DEBUG mode, enable the playback of audio files .
Phone Keypad Simulator: For components requiring user input (DTMF) like ivrmenu , include a simulator of a phone keypad for script debugging.
like this example
image.png
Flexibility in JSON Structure:
Despite having an existing JSON structure, there is full flexibility for changes to accommodate server-side operations programmed in the telephony environment.
Rights and Publication:
The code for the development will not be published and will not be part of the open source.
Documentation:
Include comprehensive documentation of the system, including guides for users and technicians, API documentation, and troubleshooting guides.
Adding New Modules:
To ensure flexibility and scalability of the system, it is important to include clear and detailed instructions in the system documentation for adding new modules. This will include:
Module Development Guidelines: Description of the system's internal interfaces, including technical details like API interfaces, conventions, and expected module behavior.
Documentation Requirements for New Modules: Standards for documenting new modules, including technical specifications, how to for the developer .