I have a use case that's currently using Genesys for inbound calls and Dialogflow to handle conversations flow. I need to evaluate Vapi as an alternative but the Genesys is a requirement of the project. Does it have native integration or we can build a custom inbound integration to have Genesys+Vapi?

@Diego Alves Vapi offers flexible integration options that can work with various systems, including Genesys. While Vapi may not have a native integration with Genesys out-of-the-box, you can certainly build a custom inbound integration to connect Genesys with Vapi. To evaluate Vapi as an alternative for handling inbound calls, you would typically follow these steps: 1. **Setting Up Your Local Development Environment**: This involves installing necessary software and tools to create a local development setup where you can test and develop your integration. 2. **Configuring Vapi with Custom LLM**: You can configure Vapi to work with a custom Language Learning Model (LLM) that suits your conversation flow requirements, similar to what you might have with Dialogflow. 3. **Understanding the Communication Flow**: It's crucial to understand how Vapi handles inbound calls, including how it receives calls, processes them, and interacts with other systems. For integrating with Genesys, you would need to develop an adapter or middleware that can communicate between Genesys and Vapi. This would involve using Genesys's APIs to handle the telephony aspect and Vapi's APIs to manage the voice interactions. If you need detailed technical guidance or support on how to achieve this integration, please ask support for more info on this. They can provide you with specific documentation, SDKs, or API references that you might need for your project.

Can I have a support to detail more how to achieve this integration and relevant links to build this middleware between genesys and vapi?

@Diego Alves you have to use SIP for it and yeah soon it will be available for public use.