- Communities and brands that already receive support requests in VK.
- Teams that want one inbox instead of a separate VK-only process.
- Deployments where AI should answer routine cases and operators should handle exceptions.
VK channel
Handle VK community messages inside BldBot.
Use VK when customers already write to your community and you want those messages handled by AI and operators in the same workflow as other channels.
- VK messages land in the same conversation system as your other live channels.
- The agent can answer from knowledge, call APIs, and hand the dialog to operators when needed.
- Operators see VK inside the same operational queue instead of switching tools.
- VK is community-based, so the setup depends on the community token and callback path.
- Like other live channels, success is proven by a real inbound message and a real reply.
- VK is a good fit when you already have audience trust in the community inbox.
Setup instructions
- Create the community access token in VK management.
- Activate VK on the agent page and fill the required values.
- Finish the callback or connection settings on the VK side if they are required for the community.
- Send one real VK message and confirm the dialog and reply in BldBot.
What to verify after activation
- The community message appears in the shared conversation list.
- The reply returns to the same VK dialog.
- The conversation can still move through operator queues and back to AI.
Typical issues
- The token belongs to the wrong community or lacks the needed access.
- The callback or platform-side settings were not completed.
- The team tested only the settings state and never sent a real message from VK.
Ready to launch this channel?
Open the app, connect the channel, and test it with one real message before you scale it further.