Partner Guide: Onboarding Tenants to Expertflow Cloud
This guide is for partners who sell and manage tenants hosted directly on the Expertflow Cloud Infrastructure.
Key Takeaway: Hardware sizing (CPU, RAM, Disk) is entirely managed by Expertflow. The partner focuses on licensing, tenant resource allocation, and ensuring end-user connectivity.
☁️ Deployment Model & Abstraction
In this model, the underlying infrastructure, including Kubernetes clusters, databases, media servers, and ETL orchestrators, is provisioned, scaled, and maintained by Expertflow.
Component | Responsibility | Notes |
Server Hardware | Expertflow | Includes provisioning, HA/DR, backups, and OS/Kubernetes management. |
Core CX Platform | Expertflow | Includes CX-Core, Data Pipeline Orchestrator, and CX Analyzer base infrastructure. |
Per-Tenant Scaling | Expertflow (Capacity Allocation) | Expertflow manages the horizontal scaling of shared components based on aggregated tenant load. |
🤝 Partner Responsibilities
The partner's focus shifts from CapEx to OpEx and ensuring network readiness for the end-customer.
Requirement | Description |
Agent Workstations | Standard PC/Laptop with modern browser (Chrome/Firefox) |
Network Connectivity | Stable, high-speed internet connection (LAN/VPN) |
Licensing | Partner manages the licensing bundle (Agents, Channels, Add-ons) per tenant based on contracted capacity with Expertflow. |
Connectivity Integration | Partner is responsible for configuring the customer's SIP trunks, digital channel accounts (WhatsApp, Facebook, etc.), and any required CRM integration endpoints (APIs). |
🏠 Tenant Onboarding & Capacity Planning
Partners must allocate capacity based on the tenant's needs, which translates to a licensing model for Expertflow.
Base Tenant Capacity (Includes Digital Channels, Voice, WFM, Surveys and Campaigns)
When a new tenant is created, they consume a base capacity unit from the shared infrastructure for the following core services.
Service | Scaling Metric | Unit Allocation |
CX-Core (Routing/Agent Mgmt) | Concurrent Agents | Allocated based on licensed agent count. |
Core Voice Capacity (Media Server) | Concurrent Voice Calls | Included in base license. Allocated capacity is based on licensed agent count (e.g., 1:1 agent:call capacity). |
WFM / Surveys and Campaigns | Concurrent Agents | Included in base license. Capacity is based on licensed agent count. |
Digital Channels | Concurrent Sessions | Allocated based on licensed digital capacity (e.g., 50 concurrent digital chats). |
CX Analyzer | Data Storage/Access | Standard shared storage is provided; additional capacity may require a storage uplift license. |
✨ Add-on Consumption
For optional, resource-intensive add-ons, capacity must be licensed per tenant.
Add-on Component | Capacity Metric | Scaling Factor for Licensing |
Base components | for each new tenant | 1 vCPU, 2 GB |
WFM | 2 vcpu, 4 gb | |
Jambonz (Voicebot) | Concurrent Voicebot Sessions | Licensed based on the expected concurrent conversational IVR sessions (e.g., 50 concurrent bot sessions). |
Third-Party AI/LLM | Transactions Per Second (TPS) / GPU | Licensing is often managed based on consumption rates or dedicated GPU hours (where applicable). |