Flexible pricingfor every service setup

Most Flomni CS services are full functional modules of the platform, not standalone components that can be fully embedded into an external system. For example, the agent workflow in Dialogs cannot be completely moved into your CRM interface.

At the same time, the selected scenario may include integrations with other platforms, allowing employees to receive the information they need directly in their existing workspace. In this case, additional access to Flomni CS may not be required for every user.

For questions about platform capabilities, integrations, and access management, please contact our specialists.

Yes. We can discuss a configuration that fits your needs and define which services, modules, and options are required at launch. Some services and options cannot be fully excluded because they are part of the base plan or connected to other platform capabilities.

The final price depends on the selected plan, the agreed solution configuration, and any additional modules or integrations required for your scenario.

MAX is not connected as a standalone service. In our case, MAX Messenger integration works only within the Flomni CS platform services. The platform is required to configure the channel, connect it with scenarios, manage communications, and track results.

However, we can build a configuration focused primarily on MAX, without adding unnecessary channels or features at launch.

We are responsible for configuring the platform, scenarios, and channels, participating in the launch, supporting the implementation, and providing post-launch support.

On the client side, we need the scope of work, configuration data, access or required actions in your systems, such as CRM, website, and bot accounts, as well as participation in testing and acceptance.

The scope of work and level of support may vary depending on the selected plan, so final responsibilities should be confirmed when approving the scope of work.