Channels
Zild Assist operates across multiple communication channels through the Zild Platform’s channel abstraction layer. Channels represent the surfaces where users interact with your AI agents. Supported channel types include:- Webchat
- API-based messaging channels
Channel Architecture
Zild Assist follows this routing structure: Channel → App → Agent → Conversation → Workflow → Response Each channel is connected through an App, which:- Receives inbound messages
- Normalizes payload structure
- Identifies the Tenant
- Routes to the assigned Agent
- Formats outbound responses
- Customer support
- Lead qualification
- Sales automation
- Appointment scheduling
Message Flow
- User sends message via WhatsApp
- Provider forwards webhook to Zild
- App validates and normalizes payload
- Agent processes message
- Response is returned through WhatsApp API
Capabilities
- Text messages
- Media handling
- Template messaging
- Session-based conversations
- Delivery status tracking
Best Practices
- Keep responses concise
- Use structured replies when appropriate
- Clearly define escalation paths
- Monitor template approval status
Webchat
Webchat allows Zild Assist to operate directly on your website.Typical Use Cases
- Website lead capture
- Pre-sales assistance
- Support automation
- Product information
Deployment Flow
- Configure Webchat App
- Generate embed script
- Add script to website
- Messages route to assigned Agent
Capabilities
- Real-time messaging
- Persistent session handling
- Customizable appearance
- Domain restrictions
Best Practices
- Align chat tone with website branding
- Trigger chat proactively (if configured)
- Capture structured lead information early
- Monitor abandonment rates
API-Based Messaging Channels
Zild Assist can integrate with custom systems via API. This allows:- Internal system messaging
- Mobile app integration
- Embedded enterprise tools
- Custom communication layers
Integration Model
- External system sends structured request
- Zild processes via assigned Agent
- Response returned in structured format
Multi-Channel Strategy
Because channel logic is abstracted:- One Agent can serve multiple channels
- Channel-specific formatting is handled by the App layer
- Workflows remain consistent across channels
- Lead captured on Webchat
- Continued conversation on WhatsApp
- CRM workflow triggered regardless of channel
Channel-Specific Considerations
Rate Limits
Each communication provider may enforce rate limits. Zild handles:- Structured retry logic
- Response queueing
- Error logging
Session Rules
Some channels (e.g., WhatsApp) have session restrictions. Ensure:- Templates are configured for out-of-session messaging
- Automation respects provider rules
Media Handling
Channel capabilities vary:- Some support rich media
- Some restrict attachment size
- Some limit interactive elements
Channel Assignment
Each App must be linked to an Agent. Configuration steps:- Create App
- Select channel type
- Assign default Agent
- Configure escalation routing
- Activate
Escalation & Routing Across Channels
Escalation rules apply consistently regardless of channel. If escalation is triggered:- Conversation is assigned to group or user
- Human operator can respond within same channel
- Conversation history is preserved
Monitoring by Channel
Supervisors and Administrators can monitor:- Conversation volume by channel
- Escalation rates
- Response latency
- Conversion rates (for sales flows)
Security Considerations
All channels operate within:- Tenant isolation
- Role-based access control
- Webhook signature validation
- Encrypted communication (HTTPS)
Summary
Zild Assist supports:- Webchat
- API-based messaging channels
- Deploy AI once
- Scale across channels
- Maintain consistent business logic
- Preserve tenant isolation
- Ensure secure and auditable operations