Help center Chat and messaging Run effective B2B support conversations in Chat Updated Thursday, November 5, 2026 · Marcel Gravelle Chat helps customers get an immediate conversation while Supportbench keeps the work connected to customer context, knowledge, and cases. For a B2B team, a useful chat is more than a fast reply: it identifies the organization and issue, assigns the next action, and preserves enough history for a specialist to continue. At a glanceFor: chat agents, queue owners, supervisors, and knowledge authors. Applies to: Supportbench Core.Start here: Chat in the application navigation opens the Chat Console Before the shift · Choose the right conversation · Read Company and Contact details while replying · Reply with a clear next step · Confirm whether the customer received or viewed your reply · Keep private work separate from customer messages · Transfer with context and ownership · Continue longer work as a case · Handle an AI-to-agent handoff thoughtfully · Close deliberately and understand transcripts · Work a customer chat through triage, handoff and follow-up · Make the inbox manageable across a support shift · Troubleshoot common chat problems Before the shift Your administrator configures the widget, queues, working behavior, AI assistance, case creation, and transcript options. Your role and team access determine which conversations and transfer targets you can use. A visible All view does not mean unrestricted access to every customer conversation.Confirm your availability using the agent status controls your team uses. Follow the configured routing policy rather than assuming a widget is always staffed.Know which queue owns unassigned conversations and who monitors AI handoffs.Review the knowledge articles and escalation path for the products you support.Agree when a conversation should become a tracked case and who sends the next customer update after a handoff. Choose the right conversation Open Chat. Use My chats for your conversations and Unassigned for work awaiting an owner. Other available views include All, AI Bot, and Sessions, subject to access.Check the Open or Closed scope before interpreting the list. Open the conversation you intend to handle.Read the timeline, including any AI exchange or previous agent messages. Use Load earlier messages when the visible history is incomplete.Review the available customer details and related case context. Confirm identity and the organization before relying on an association or sharing account-specific information. In Tabbed mode, click a company or contact name, or a related case link, to open that record in an application tab. If the record is already open, its existing tab is selected. Return to the Chat tab to continue your conversation and unsent reply. Standard mode retains normal browser navigation; Ctrl-click, Command-click and middle-click retain browser-tab behavior.Take or confirm ownership using the actions available to your role. Coordinate with another agent already working the conversation before sending a competing reply.Example: a customer’s second contact joinsA company’s operations manager opens a chat about an issue an engineer already reported. Review the customer and related case context before repeating the troubleshooting. Confirm which issue they mean, summarize the known state, and explain who owns the next update. Never disclose another organization’s information simply because a name or email looks similar.Choose the inbox scope before interpreting an empty conversation list. My chats shows your assigned conversations; review Unassigned and the Open or Closed filter when finding work. Counts and available controls depend on current activity and access. Check the selected inbox view and Open or Closed status before concluding that work is missing. Here My chats > Open is empty, while other views have counts. ALL beside Inbox controls whether chats outside assigned queues are included; it is separate from the All conversation view. Counts are demonstration values, not recommended settings or targets.Read Company and Contact details while replying Your account’s Chat policy can show selected Company and Contact fields automatically when you open a conversation. This lets you verify a customer identifier, support level or contact detail without leaving your reply. The policy is shared across all chats in the account, with separate Company and Contact groups. Your record and field permissions still determine what you can read. Use the configured detailsOpen the conversation and check which Company and Contact are linked in the customer area. A missing association cannot supply customer field values.Read the expanded Company and Contact detail groups. Your administrator chooses their fields and ordering; collapse a group when you need more room.Check custom identifiers against the customer’s request. For example, Acme Manufacturing’s Company License number might display ACME-2026-0042 directly below its name. A Contact license field is a separate value, even if its label is similar.To inspect or correct customer data, follow an available Company or Contact name link. In Tabbed mode the record opens in an application tab; in Standard mode the existing browser-tab behavior remains. Editing still requires the record’s normal permissions.Continue your reply in Chat. Viewing details does not send a message or change the customer record. Understand blanks, hidden details and errorsAn em dash (—) means the displayed field has no value. A numeric zero or a false/No value is information, not a blank. When no customer is linked, the group shows its unassigned state. If a selected field is hidden by your effective Customer Policy or is no longer available, it is omitted rather than revealed by the Chat layout. A user with the Manage Chat policy role permission uses the Chat policy visibility toggles to show or hide individual fields or the configured customer details while retaining the saved layout. Existing conversation and case history remains accessible. Accounts without a saved Chat policy continue using their existing expandable details. The policy contains Company and Contact fields, not a list of linked Asset records. If customer details cannot load, use Retry. The console clears the failed details instead of showing a different default layout, and your reply remains available. After a Company or Contact is reassigned, wait for its refreshed details and verify the record name before using a license number from it. If a value still appears incorrect, open the linked record and ask an authorized administrator to check that field and your access. Administrators can follow Configure case forms and chat customer details with policies for the exact configuration steps, hiding controls and license-number example. Agents do not need Manage Chat policy merely to read permitted customer details in a conversation. That permission controls the shared layout and its audit history; it does not grant access to customer records or otherwise hidden fields. Agents do not have separate personal policy layouts. Reply with a clear next step Read the latest message and confirm that you are composing for the intended conversation.Write a direct answer or a focused diagnostic question. Keep one important request per message when the customer needs to act.Use Templates for a reusable starting point, Attach for appropriate files, and Knowledge to find relevant guidance. Check any inserted text and links before sending.If available, use an AI reply suggestion as a draft. Verify the advice, customer context, and promised actions before using it.Choose Reply to continue the conversation. Use Reply and close only when the message and the conversation outcome are ready.Check that the message appears in the timeline. If delivery is uncertain, inspect the conversation state before repeating the message. Confirm whether the customer received or viewed your reply Use the status beside each public agent message to decide whether to wait for a response or use an agreed follow-up channel. A receipt describes the customer widget, not email delivery or a guarantee that the customer understood your message. You need access to the conversation in Chat; receipts do not grant access to another agent's restricted conversation or case. StatusMeaningWhat to doOne check: SentThe reply was saved successfully. The customer's widget has not confirmed delivery.Leave the saved reply in place. Check connectivity before sending the same reply again.Two neutral checks: DeliveredThe customer's widget acknowledged the complete message, including completion of a multipart reply.Allow time for the customer to open the conversation. Delivered does not mean viewed.Two accent-colored checks: SeenThe message appeared in the visible conversation area while the widget was open on that conversation and the browser tab was visible.Use the customer's response and your service commitments to decide when to follow up. Check a reply and its timestampOpen Chat and select the authorized conversation. Confirm the customer and linked case before replying.Send a public reply. Keep any sending or failure indicator in view until the message is saved; a failed send does not become Sent.Read the checkmarks and their text label beside the message. Hover over the status for the available time: while Sent, this is the message time; after Delivered or Seen, it is the stored receipt time. Text labels accompany the colors for accessibility.Keep working in the conversation. Receipt updates arrive without replacing your draft or moving the transcript. Reopening the conversation restores recorded Delivered and Seen times. Example: follow up on installation instructionsYou send “Open Settings and choose the production workspace” at 10:00. Sent confirms that Supportbench saved the reply. The customer reconnects at 10:02, so it becomes Delivered. They have the case form open and have not viewed the conversation; it remains Delivered. At 10:04 they open the conversation and scroll that message into view, so it becomes Seen. A newer reply farther down the transcript can remain Delivered until it enters view. Understand missing or delayed receiptsA closed widget, hidden browser tab or message outside the visible transcript cannot establish Seen. An offline customer can reconnect later; acknowledgements are retried and never downgrade Seen to Delivered. Multiple authorized agent windows receive the same saved timestamps. Private notes, customer messages and bot replies do not display customer receipt states. Existing historical read flags are not converted into receipts.If a reply remains Sent, confirm that the customer can open the intended widget and conversation. Older widget or API packages, or accounts without receipt storage enabled, cannot confirm Delivered or Seen. Do not interpret missing receipts as proof that the customer did not receive the message. Ask your administrator to check the coordinated widget/API/Core release if newly sent replies never progress. Use Configure a chat widget to review availability, identity and continuation settings. Keep private work separate from customer messages Use the private-note or internal collaboration option offered by the console for working hypotheses, specialist coordination, and internal handoff detail. Confirm the selected mode before submitting. A customer reply should contain the information the customer needs to act, not the team’s internal discussion.Private chat rows and their files are excluded from the customer transcript email. This does not make every file or case automatically private: case visibility, public attachments, article audiences, and other sharing paths have their own rules. Review each destination before sharing a link. Transfer with context and ownership Use Show conversation details and the available ownership/queue controls to inspect the current assignment and eligible targets.Choose an appropriate active agent or queue. Available targets follow the configured team and permission scope.Record the handoff: customer impact, steps already tried, evidence, open question, and the next promised update.Complete the transfer and verify the resulting owner or queue. A queue transfer clears the individual owner so the receiving queue can own the work. Where a case is linked, check its assignment as well.Tell the customer what happens next when the handoff changes their expectation. An internal transfer does not explain the change to the customer on its own. Continue longer work as a case Use the available case action when the issue needs an accountable investigation beyond the live conversation. Depending on widget and workflow configuration, a case may already have been created. Check for the existing linked case before creating another.Confirm the company and contact association, the issue summary, and the relevant history.Open or create the case using the console’s available action. Complete required fields and assignment.Verify that the conversation is associated with the intended case and that the next action has an owner.Continue formal updates in the agreed channel. Tell the customer whether to expect a case email, another chat, or another documented follow-up.A case is especially useful for intermittent defects, a recurring asset problem, multi-team investigation, or an escalation that needs service deadlines and a durable resolution. Handle an AI-to-agent handoff thoughtfully AI assistance can help with initial questions and reusable knowledge, but the configured widget and routing rules determine the actual handoff. Do not promise that every bot is always available, has unlimited capability, or automatically learns every correction.Read what the customer already asked and what the AI answered before asking them to repeat it.Check the cited or suggested knowledge against the actual environment. Correct a mistaken answer clearly and move the customer forward.If the answer exposed a knowledge gap, use an available create-article action or the knowledge improvement process. Remove customer-specific information from reusable content.Use Knowledge Quality where enabled to assess the captured answer, identify the failure reason, assign an improvement, and retest. Close deliberately and understand transcripts Summarize the result and any remaining customer action. If work continues in a case, state who owns it and when an update is expected.Choose Reply and close when sending the final message, or Close conversation when no further reply is needed. Verify the closed state.Transcript email is queued after an actual close transition for a non-bot conversation when transcript email is enabled, the contact has an email address, an agent has replied, and a usable From address is configured. Bot-only or anonymous conversations do not meet those conditions. Queueing a message is not confirmation of delivery.Review a representative transcript through an approved test conversation when changing its branding or delivery settings. Check links, attachments, customer-visible content, and private-note exclusion.Branded transcript emailsAdministrators can enable Use a custom branded email in Chat Widgets → Transcript email. The custom body must contain {{chat_transcript}} exactly once, on its own line or in its own paragraph or table cell. Insert transcript adds the placeholder. Turning custom branding off restores the standard email. See the Chat Widgets configuration guide before editing production templates. Finish a chat with automatic case details Decide only whether the linked case is resolved. Choose Close chat to end the conversation and leave the case status unchanged. Choose Resolve case and close chat when the linked case is ready for closure. Eligible transcripts automatically include the customer-accessible linked case reference and its customer portal link when available. There is no case-details checkbox. Release availability: This simplified flow requires the updated Core release. If your console still shows a case-details checkbox or a third follow-up option, it is using an earlier interface. Ask your administrator about the matching release; the automatic-details behavior described here does not enable transcript email by itself. The only decision when a case is linked Choose whether to resolve the linked caseActionChatCaseUse when Close chatEnds the conversation.Leaves its status unchanged. Required case-closure fields do not block this action.This exchange is finished, but the case remains open for investigation or other work. Resolve case and close chatEnds the conversation after closure requirements pass.Uses the existing case-close modal inside Chat Console. Now closes immediately; a future time schedules case closure while ending the chat now.The issue is resolved and no outstanding work prevents case closure. When there is no linked case There is nothing to choose about case status. Close conversation closes the chat directly, and Reply and close sends the final reply and closes it. The extra finish-choice dialog is skipped. An eligible transcript contains the conversation without a case-details block. These actions do not create a case. What is included automatically? For either close action, the transcript can include the linked case reference, such as c-23670, and its customer-facing portal link. The reference is included only when the case is customer-accessible, belongs to the same customer as the chat, and is not merged or in trash. A case being resolved, already closed, or pending closure can still have a safe reference. The wording identifies the linked case without promising further work. Private, missing, unavailable or mismatched case details are omitted. That does not prevent an otherwise eligible ordinary transcript or make Close chat require case-edit or case-close permission. If the case association changes after closing, its details are omitted; if the customer association changes, the transcript is withheld rather than redirected to a different customer. Normal case access still applies when an agent opens the case, and normal portal sign-in and audience rules apply to the customer link. Transcript email still follows widget settings. It requires an enabled transcript setting, a customer email address, at least one live-agent reply and a usable sender. Bot-only and anonymous conversations do not qualify. Without a valid customer portal, the safe case reference can appear without a link. Queueing is not proof of delivery. See Chat Widget transcript-email settings. Automatic case details do not create a second email, task, assignment or reminder. Existing ownership and workflow behavior remains in effect. Confirm the next owner and promised update separately when investigation continues. Inspect the case without leaving your chat Open the finish dialog for a chat with a linked case.Select the underlined ID in the Linked case card. It opens in a new browser tab; keyboard users can focus the link with Tab and press Enter.Review the case status and remaining work.Return to the Chat tab. The dialog and unsent reply remain available. Opening the link does not send, resolve or close anything. End the chat while case work continues Read the latest messages and verify the customer and linked case.Explain the next step and agreed update time if work remains.Use Reply and close when sending a final reply, or Close conversation when no further message is needed.Choose Close chat. There is no separate email-content option.Verify that the conversation is closed and the case has the intended unchanged status. If you sent a reply, confirm it appears in the timeline. Resolve the case and end the chat Confirm that the customer’s issue is resolved and the case is ready to close. You need permission to close that case.Use Reply and close or Close conversation, then choose Resolve case and close chat.Complete the existing case-close modal’s required fields, such as Issue, Outcome, Summary or custom fields.Select Now for immediate case closure, or the appropriate future closing time. Submit Resolve and close in the modal.Verify the conversation and case status, including any scheduled closing time. Existing case-resolution survey rules still apply. Cancel or recover without losing work Cancel or Escape: does not submit a close action. Your unsent reply, staged attachments and entered case-close fields remain available while working on the same conversation.Required field or Article confirmation: the case-close modal keeps your values and displays the validation result. Complete the required fields or respond to the existing explicit Article confirmation; automatic email details do not bypass closure policy.Reply sent but finishing failed: the successful reply is acknowledged and cleared from the composer. Inspect the timeline, then retry finishing without typing and sending that reply again.Attachment failure: the chat remains open. Address the failed file; already successful content is retained.Case or customer changed: review the refreshed association before retrying resolution. A saved case-close draft cannot resolve a different newly linked case.Result uncertain: use the case modal’s Retry refresh to read current state without repeating the previous command. Check the timeline before any new send.Transcript or case link missing: check transcript eligibility, the customer email, the case’s customer visibility and matching customer, and portal configuration. Do not expose a private case just to obtain a link, or repeatedly reopen and close the chat to test delivery. Examples A quick chat with no case: answer the question and use Reply and close. No finish-choice dialog or case reference is needed.Investigation continues: confirm the owner and next update, then choose Close chat. The case status stays unchanged and its safe reference is automatically included in an eligible transcript.A confirmed fix: choose Resolve case and close chat, complete the closure form and select Now. The eligible transcript includes the resolved case’s safe reference automatically. Case-created and case-closed workflows may independently send mail. Check workflow notification conditions and actions when investigating additional notifications. Work a customer chat through triage, handoff and follow-up A customer’s warehouse supervisor starts a chat because order processing has stopped. The first agent does not need to solve the entire incident in the chat, but must establish the customer context, immediate impact and next responsibility.Identify the contact/company and ask for the affected operation, when it stopped, and whether work is blocked or degraded. Read the existing conversation before asking the customer to repeat it. If AI handed over the chat, use that context as a starting point and verify uncertain facts.Acknowledge what is known in a customer-visible message and ask for one useful next piece of evidence. Avoid pasting a long generic checklist before understanding the reported task.Use a private note for internal diagnostic context or a specialist question. Confirm the reply mode before sending; a private note is not the customer acknowledgement and should not be treated as a public first reply.If another agent or queue must take over, record the impact, evidence, attempted checks, unresolved question and promised update before transferring. Inspect the resulting assignment so the conversation has a clear next owner.If the work will continue beyond the live exchange, use the supported case linkage/follow-up workflow and verify the resulting case. Tell the customer how the investigation will continue and who owns the next update.Before closing, confirm the outcome or follow-up plan. Check the relevant transcript behavior and recipient details; an internal note should not be repeated in a customer transcript.Two messages with different jobsInternal handoff: “Warehouse orders blocked. Two failed request timestamps attached. Retrying did not recover service. Specialist needs to compare the mapping; current cause unconfirmed. Customer expects next update at the agreed time.”Customer update: “We have captured the failed examples and are bringing in the integration team. We will continue on the linked case and update you at the agreed time.”Replace the example with verified facts and a real agreed time. A transfer is not the moment to invent a cause or promise a fix date. If the customer disconnects, preserve the work in the permitted case/follow-up path rather than treating disconnection as resolution. Make the inbox manageable across a support shift Use the console’s available views to distinguish your conversations, queued work and historical context. Check availability and queue coverage before assuming someone else will pick up an unanswered chat. Team conventions should make clear who monitors waiting work and who verifies that a transferred conversation is accepted.Review attachments before relying on them, and request only the evidence needed. When a conversation is slow to load, use the available earlier-message control to inspect history instead of assuming the visible portion is complete. After an uncertain send, inspect the message list before repeating it so the customer does not receive duplicate instructions. Troubleshoot common chat problems ProblemChecks and actionI cannot see a conversation or transfer targetCheck Open/Closed scope, selected view, team/role access, and the target’s active state.The conversation is unassigned after a transferA queue transfer clears individual ownership. Confirm the destination queue and the team’s pickup process.A customer repeats information after an AI handoffRead the captured timeline and earlier messages first; summarize what is already known.A transcript did not arriveCheck widget transcript settings, recipient availability, close event, and delivery evidence. Do not equate configured with delivered.A reply suggestion contains the wrong adviceEdit or discard it, verify the underlying knowledge, and use the improvement workflow for a repeatable correction.Two cases appear to cover the same conversationCheck existing chat-to-case linkage before creating another. Follow your case consolidation process after comparing the records. Continue learning Configure Chat Widgets and transcript behaviorConfigure queues and assignmentImprove knowledge through KCSContinue the investigation in a caseManage escalations and handoffsConfigure case forms and Chat customer details with policiesConfigure agent roles and permissions Compare widget searches with AI answers Use this check when a visitor can find an article manually but the chat assistant gives a different answer or asks for clarification. The widget searches the public articles available through its configured knowledge scope. Agent-only drafts and internal articles are not customer answer sources. Open your public widget as the intended visitor. If the Knowledge Base panel is enabled, enter a specific question and open the matching article to confirm it is available.Ask the same question in the AI conversation, if your widget has an AI responder enabled. Include the product, action and error or limitation. A follow-up can use conversation context, so compare a fresh conversation when you need the same starting conditions.Compare the answer with the article. Shared relevance does not require identical lists: the assistant also needs usable, current content that is permitted for AI. It can use fewer sources or ask for missing details.For configured equivalent wording such as drop-in, drop in and dropin, compare the core matches. Adding an action such as offer or schedule can appropriately change their order. The manual Knowledge Base panel and the AI responder have separate availability controls. Hiding the manual panel does not by itself disable the responder. Where configured, independent Intercom knowledge can remain available when Supportbench article retrieval fails. The responder’s existing knowledge-source language remains English; an answer-language setting does not select translated source articles. If a result is missing, check the article’s publication, public topic placement, visitor restrictions and whether AI use is excluded. Then verify the widget’s configured community and Divisions. Do not make an internal article public just to improve a match. Compare the exact query, article ID and intended visitor access with Test article search in AI Terms; that administrator test uses the agent’s access and does not impersonate the visitor. Was this article helpful? Yes No Thank you for your feedback.