TENANT TEST WORKSPACE
Test what the platform can do
Every number below is loaded from this tenant's Core API. Provider actions only become available after their connection is configured.
Calls
βchecking
All call records Β· active shown separately
Messages
βinbound + outbound
SMS, WhatsApp, Telegram and connected channels
Appointments
βtenant records
Created from calls, messages or forms
Active connections
βchecking
Credentials remain in the protected backend
Functional test centerOpen a module, create a real tenant record and verify its complete workflow.
Live API data
π
AI voice callsOutbound call, inbound history, join and end controls
Open β
π§Human queue & takeoverQueue, accept, join, take over and complete
Open β
π¬AI messagingInbound/outbound SMS, WhatsApp and Telegram
Open β
π
AppointmentsCreate and review tenant bookings
Open β
πWebsite formsBuild, publish, embed, upload and book
Open β
π‘οΈTools & approvalsGrant AI tools and approve sensitive actions
Open β
π₯Video sessionsZoom, Google Meet, Teams and WebRTC
Open β
π¨οΈConversationsRead channel history and AI responses
Open β
π₯ContactsCreate customers used by calls and bookings
Open β
β‘WorkflowsBuild tenant automation records and triggers
Open β
π§ KnowledgeManage grounding sources for AI agents
Open β
πProvider connectionsInspect channel readiness and resources
Open β
Provider readinessConfigured connections reported by the backend
Manage βLoading connectionsβ¦
Start hereA safe first end-to-end test
- 1Create a contactAdd your own test phone and channel address.
- 2Configure a providerAdd credentials in the operator console, then activate its tenant connection.
- 3Create an AI agentGive it instructions and enable only the tools it needs.
- 4Run one real testUse Voice or Messages and inspect Conversations, Events and Usage.
Honest status: records and controls are backed by the real tenant API. Calls and messages cannot reach public networks until the matching carrier/provider credentials, webhook and firewall settings are valid.