Online Conversations
6MM AI Customer Support · Tenant guide
Handle an incoming conversation from first review to handoff. Use this workspace to understand the question, coordinate human support and keep the conversation in context.
- Read the conversation — Review the question and recent messages.
- Choose the handler — Check ownership before joining or transferring.
- Reply and follow up — Answer, invite feedback or continue in a ticket.
Work from one conversation workspace
Open Online Conversations. The human, monitoring and bot tabs organize the conversations visible to your account. Monitoring access and conversation ownership still apply; an agent does not automatically see every tenant conversation.
- Select a conversation and read its recent messages and available visitor information.
- Join, take over, assign or transfer it using the actions your role permits.
- Reply with text, supported attachments or quick replies. Use language recognition and translation when needed.
- Manage visitor upload permission and invite a rating where available.
- Finish the conversation or create/follow up a ticket when further work is needed.
Understand visitor information
A readable visitor name is a display label, not proof of a verified exchange account. Distinguish a signed-in user ID, an entry email and a contact email supplied during support. Use available session details to understand the case; do not assume two visitors with the same email are the same authenticated user.
Check the current conversation before sending. AI-generated text from an external MCP client is not sent merely because it appears in your AI chat; sending through MCP requires the platform’s confirmation flow.
When human support is unavailable
The visitor entry follows the configured availability and fallback behavior. A ticket can preserve a question for later handling. Keep the displayed instructions consistent with your actual staffing and response policy; avoid promising an unsupported response time.
Know which workspace to use
Example: a user asks about exchange integration
- Read the conversation to distinguish a request for documentation from an account-specific issue.
- Use a reviewed knowledge answer or an appropriate quick reply. Check any platform names, links and amounts before sending.
- For another language, use the available recognition and translation controls and review the meaning before replying.
- If a colleague must continue, transfer or assign within your permissions. If the issue needs later investigation, continue through the appropriate ticket workflow.
Before closing: confirm the user received a response, identify any unfinished question and keep the relevant conversation number for follow-up.
Common questions
Why can I see a conversation but not reply?
Check its current owner, your account permissions and whether you need to join or take over first. Monitoring does not automatically grant handling permission.
Does an AI-labelled reply always come from a large model?
No. Saved replies and earlier matching stages can also appear as AI messages. Use the bot flow test when you need to diagnose the response path.