Side Conversation
定義
A side conversation is a separate thread branched off a main support ticket — with a different set of participants, such as an internal team, a vendor, or another department — used to gather information without cluttering the customer-facing conversation.
How it works
While handling a ticket, an agent starts a side conversation to loop in someone outside the main thread — emailing a warehouse about stock, messaging engineering about a bug, or asking a manager for approval. That exchange lives attached to the ticket but stays invisible to the customer.
Unlike a simple internal note, a side conversation is a full two-way thread with its own recipients and channel (email, Slack, or a linked ticket), so the back-and-forth is captured in one place tied to the original request.
Why it matters
Side conversations keep the coordination that resolving a ticket often requires out of the customer's view while preserving it for context. The customer sees a clean thread; the agent keeps every internal exchange documented against the ticket — useful for auditing, for the next agent who picks it up, and for training AI on how issues actually get resolved.
よくある質問
What is the difference between a side conversation and an internal note?
An internal note is a one-way comment left on the ticket for colleagues; a side conversation is a full separate thread with its own participants and channel, letting you actually correspond with a third party without leaving the ticket.
Can customers see side conversations?
No. Side conversations are internal by design — they branch off the ticket for coordination and stay hidden from the customer-facing thread.
関連用語
Support Ticket
A support ticket is a single trackable record of a customer's request or issue, holding the full conversation and metadata — status, priority, assignee, tags — from when it's opened until it's resolved..
Human Handoff
Human handoff is Macha's principle of keeping a person in the loop on anything customer-facing — most concretely through confirmation gates that pause an agent before any write action in interactive chat, and escalation patterns that route hard cases to your team..
Shared Inbox
A shared inbox is a single email address (like support@ or help@) that a whole team can access and manage together, with visibility into who's handling which message so replies aren't missed or duplicated..
Escalation
Escalation is the process of moving a support ticket to a higher tier, a specialist, or a manager when the current agent can't resolve it or when it risks breaching an SLA..
Agent Workspace
An agent workspace is the unified interface where a support agent handles their work — tickets, live chats, customer context, and channels — in one screen, so they don't have to switch between separate tools to respond..
アイデアを実装に
Macha は既に運用中のヘルプデスク (Zendesk、Freshdesk、Front、Intercom、Gorgias) の上に載る AI エージェント層です。
トライアルを開始
Shopify
Stripe
Slack
Notion
Google Workspace
Confluence