One customer request queue
VK conversations appear next to your website and other connected channels.
VK integration
VK community messages in the shared queue
Operators handle VK community requests next to website, marketplace and messenger conversations.
Free start: 300 delivered operator push targets. The web chat keeps working after the limit; FCM, WebPush and SMS become available with a license.
What you get
Context stays visible
Operators see the source, history and attachments supported by the channel.
Reply from a browser or Android
Handle a new conversation wherever it is more convenient.
How it works
Connect the channel
Add the community token and confirm callback settings through the EasyChat connection check.
EasyChat verifies access
The integration screen shows connection health and safe diagnostics without exposing tokens.
Run a two-way test
Check an incoming message and an operator reply before moving the channel into production.
Self-hosted
What to know upfront
Conversations, files, users and settings stay on your server.
- The community needs message and callback permissions; attachment support depends on the VK API.
- The exact attachment and action set depends on the channel API.
- Conversations, files, users and settings stay on your server.
Frequently asked questions
Does AI reply automatically?
Only when an administrator explicitly enables AI for an eligible conversation type. Service events and read-only channels are skipped.
Can I disable this channel?
Yes. Each channel is controlled independently and does not disable website chat or other integrations.
Where is the setup guide?
The step-by-step VK guide is available in the EasyChat documentation.
Next step
Start freeVerify EasyChat with your own workflow
Start free. Move to a license only after the widget, operator panel and phone work together in your environment.