HubSpot
Conversations
The unified messaging hub — how to configure inboxes, connect channels, build chatbots, route conversations to the right people, and connect every message to your CRM.
A unified inbox where every customer message — regardless of channel — lands, gets routed, gets answered, and gets logged in your CRM.
HubSpot Conversations is the messaging layer of HubSpot — a shared team inbox that connects all of your communication channels (email, live chat, WhatsApp, Facebook Messenger) into one place, linked directly to your CRM. Every message creates a conversation thread associated to a Contact record. Every reply is logged. Every handoff is tracked.
The problem it solves
- Support emails buried in Gmail — invisible to CRM
- Chat conversations in Intercom — no CRM link
- Sales and CS using separate inboxes — no visibility
- No way to see who is handling a customer
- No audit trail of what was promised
- Repeat questions with no automation layer
- All emails land in a shared CRM-connected inbox
- Live chat links directly to Contact records
- One shared inbox both teams can access
- Assignment and ownership visible to all teammates
- Full conversation history on every Contact timeline
- Chatbots handle common queries automatically 24/7
Four terms that define the entire Conversations architecture — understand these before anything else.
| Concept | What it is | Analogy |
|---|---|---|
| Channel | A connected communication source — an email address, website chat widget, WhatsApp account, or Facebook page. Set up once, routes messages into an inbox continuously. | The phone line that rings |
| Inbox | A named container where conversations from one or more channels are collected and managed by a team. Each inbox has its own team members, routing rules, and settings. | The shared phone at the reception desk |
| Conversation | A single thread of messages between your team and a contact. It belongs to an inbox, is assigned to an agent, has a status, and is linked to a Contact record. | One phone call from start to finish |
| Thread | The individual messages within a conversation, sorted by time — every reply from your team and every message from the contact. | The words spoken during that call |
Think of Conversations as a phone system for a company. Channels are the individual phone numbers. Inboxes are the departments those numbers route to. Conversations are individual calls that land in a department. Threads are the transcripts of those calls. Everything connects back to the CRM — so when you look up a Contact, you see every call they ever made, what was said, and who handled it.
Six types of channels you can connect to HubSpot Conversations — each with different setup requirements and use cases.
Don't connect all channels on day one. Start with the one your team uses most (usually team email or live chat). Get the routing, bot, and CRM integration right first. Add additional channels once the first is stable. Each new channel adds complexity — connection issues, new routing rules, new notifications to configure.
The four rules that govern how HubSpot handles every incoming conversation — know these before configuring any inbox.
| Rule | What it means | Admin implication |
|---|---|---|
| Every conversation links to a Contact | HubSpot matches the sender's email or phone to an existing Contact. If no match: a new Contact is created. If match: the conversation is attached to the existing record. | Always ask for email early in chat flows — anonymous visitors create orphaned contacts that don't link to your CRM data. The email is the bridge between conversation and Contact record. |
| Conversation status drives queue management | Every conversation is Open, Snoozed, or Closed. These statuses control what agents see in their queue and what appears in reporting. | Train agents to close conversations when resolved — not just stop responding. Unclosed conversations inflate your "open" count and make workload reporting meaningless. |
| Routing rules determine ownership | Auto-assignment rules run when a conversation is created. Round-robin, contact owner, specific agent, or unassigned queue. | Always configure routing. Unassigned conversations with no rule default to unassigned — nobody feels responsible, nobody responds. This is the #1 cause of missed conversations. |
| Conversations can create Tickets | An incoming conversation can automatically create a Ticket record for pipeline-style support tracking. This is configurable per inbox. | Enable for support inboxes — gives you SLA reporting, pipeline visibility, and ticket-based automation. Don't enable for sales inboxes where conversations are not support issues. |
Processing sequence — what happens when a message arrives
- Message received on channel — email hits the inbox address, visitor sends a chat, WhatsApp message arrives.
- Email/phone lookup — HubSpot checks the sender against existing Contacts. Match found → link to existing Contact. No match → create new Contact.
- Conversation created in inbox — a new conversation thread is opened in the correct inbox, showing the full message.
- Routing rules applied — the conversation is auto-assigned to an agent or placed in the unassigned queue per your routing configuration.
- Notifications sent — configured notifications fire: email to assigned agent, in-app notification, Slack notification if integrated.
- Ticket created (if enabled) — a Ticket record is created and linked to the conversation and the Contact.
- Conversation logged on Contact timeline — the full thread becomes visible on the Contact's CRM record for any team member to see.
- Workflows triggered (if applicable) — any workflow using "Conversation is created" or "Conversation property changed" as a trigger fires.
Every conversation has one of three statuses — these drive agent queues, reporting, and SLA tracking.
| Status | What it means | When to use | Admin note |
|---|---|---|---|
| Open | The conversation is active and needs a response or action from the team. | Default status for all new conversations. Stays open until someone closes or snoozes it. | Open count = your workload metric. If this number is always high, you have a capacity or routing problem, not a tools problem. |
| Snoozed | Temporarily hidden from the queue until a set date and time, when it automatically reopens. | When you've responded and are waiting for the customer to reply. "Snooze for 3 days" — if no reply by then, it pops back to Open as a reminder. | Snoozed conversations are hidden from the main view but not resolved. Build a practice: agents snooze waiting conversations instead of leaving them cluttering Open. |
| Closed | The conversation is resolved. It moves out of the active queue into the closed archive. | When the customer's issue is resolved or the conversation is complete. Closing triggers "time to close" metric and CSAT surveys if configured. | Train agents to close promptly. Conversations that should be closed but stay Open inflate workload metrics and make prioritisation harder. Build a workflow: conversation closed → send CSAT survey 1 hour later. |
Every inbox you configure has these components — understand each before building.
How incoming conversations get assigned to agents — the most operationally important configuration in any inbox.
The most common Conversations failure mode: no routing rule configured, conversations land unassigned, nobody feels responsible, response time degrades. Always configure routing before going live. If you're unsure which rule to use, "rotate among team members" is the safest default — it ensures ownership without requiring anyone to self-assign.
Routing + contact owner = the RevOps approach
For mature CRM setups, "assign to contact owner" is the most powerful routing option. When a Customer emails support, they route to their dedicated CSM. When an SQL chats on the website, they route to their assigned AE. The routing becomes personalised without any manual intervention. This requires: every Contact in your CRM must have an owner assigned. Build that as a prerequisite with lifecycle stage workflows before enabling this routing option.
HubSpot's no-code chatbot builder — how to design, configure, and connect bots that qualify leads and handle common questions 24/7.
A HubSpot chatbot is a conversation flow — a pre-built decision tree that responds to visitors automatically. It can ask questions, collect answers and write them to Contact properties, branch based on conditions, route to a human agent, or book a meeting — all without any live agent involvement.
The two bot types
| Bot type | What it does | Best for |
|---|---|---|
| Live chat bot | A conversational flow on your website. Asks questions, qualifies leads, answers FAQs, and hands off to a human when needed. | Lead generation, support deflection, 24/7 availability, visitor qualification |
| Meetings bot | A specialised bot that focuses on booking meetings. Asks for name and email, shows available calendar slots, and books directly without a human in the loop. | Demo booking pages, pricing pages, inbound-heavy sales motions |
Bot action types — what each step can do
Every branch in your bot flow must conclude with one of: route to human agent, book a meeting, send a resource link, or collect email and enrol in a workflow. A bot that asks three questions and then goes silent is a broken bot. Visitors will leave frustrated. Map your bot flow completely before building it in HubSpot — draw the decision tree on paper first.
Bot path for a demo request flow
- 01Bot opens: "Hi! I can help you explore our product. What's your name?"
- 02Visitor types name → Set Contact property: First Name
- 03Bot: "What's your work email?" → Set Contact property: Email → Contact now linked to CRM
- 04Bot: "How large is your team?" [Buttons: 1–10, 11–50, 51–200, 200+] → Set Company Size property
- 05Branch: if 50+ → "Great! Our team would love to show you a personalised demo." → Book a meeting action
- 06Branch: if under 50 → "We have some great self-serve resources." → Send Knowledge Base article + enrol in nurture workflow
- 07Both paths end. Conversation is closed automatically after booking or article is sent.
Settings → Inbox → Create inbox
- Choose inbox type — Email (shared address), Live chat (website), Facebook Messenger, WhatsApp. The type determines which connection steps follow.
- Connect your channel — For email: OAuth connect Google/Microsoft, set up email forwarding, or use HubSpot-hosted email. For live chat: no email needed — the widget is the channel. For social: authenticate via your account credentials.
- Name the inbox — Use team function: "Customer Support," "Sales Team," "General Enquiries." This appears in every agent's view and in reporting.
- Add team members — Select which HubSpot users get access. Only add people who will genuinely manage conversations here. Each member can be set as an agent or an admin of the inbox.
- Configure routing rules — Choose how new conversations are assigned. Default recommendation: "Rotate among team members" unless you have a specific case for contact-owner routing.
- Set availability hours — For live chat: define operating hours. Configure the offline behaviour: show offline message, show an offline contact form, or show the bot instead.
- Configure notifications — Set when team members are alerted. New unassigned conversation should always notify. Tune other notifications to avoid alert fatigue.
- Enable auto-ticket creation — For support inboxes only: toggle "Automatically create tickets for new conversations." This creates a Ticket and links it to the conversation and Contact.
- For live chat: install the widget — HubSpot generates a JS embed code. Paste into your website's
<head>tag. For HubSpot CMS: the widget is available as a drag-and-drop module. - Create your chatbot (if needed) — Settings → Chatflows → Create chatflow → connect to your inbox → build the bot flow using actions.
- Test thoroughly — Send a test email to your inbox address, open the chat widget in a browser, or send a test WhatsApp message. Verify: conversation created in correct inbox, Contact record created/linked, routing fired correctly, notifications sent, ticket created if enabled.
The two-layer system for support teams — conversations for the communication, tickets for the operational tracking.
A conversation is the message thread — the literal back-and-forth between a customer and an agent. A ticket is the operational issue — it has a priority, a pipeline stage, a category, a due date, and an SLA. One conversation creates one ticket. But a ticket can span multiple conversations if the same issue resurfaces. They are complementary, not redundant.
| Conversation | Ticket | |
|---|---|---|
| What it stores | The message thread — every word sent and received | The issue metadata — priority, category, stage, SLA, due date |
| What agents do here | Read messages, write replies, handoff to colleagues | Set priority, move through pipeline stages, log resolution |
| What admins report on | First response time, message volume, channel distribution | Resolution time, open tickets by category, SLA compliance |
| Linked to | Contact record | Contact record, Conversation record, Company record |
| Enable for | All inboxes automatically | Support inboxes only — configure in inbox settings |
How auto-ticket creation works
- Customer emails support@company.com (channel: support email inbox).
- Conversation created in the Support inbox. Contact matched or created.
- Auto-ticket creation fires: a new Ticket record is created. Status = New. Priority = Medium (default).
- Ticket is linked to the conversation and the Contact. Visible from both records.
- Agent responds in the conversation thread. Ticket status updates as they work the issue.
- Agent closes the conversation. Ticket moves to Closed stage. Time-to-close is recorded.
- If configured: CSAT survey sent to customer 1 hour after ticket is closed.
The data fields on every conversation — used in workflows, reports, and routing.
| Property | What it stores | Used for |
|---|---|---|
hs_conversation_status | Open, Snoozed, Closed | Workflow trigger: "conversation closed" → send CSAT survey |
hubspot_owner_id | Assigned agent | Report on agent workload and conversation ownership |
hs_inbox | Which inbox it belongs to | Filter reports by team/channel; build inbox-specific workflows |
hs_channel | Email, chat, WhatsApp, etc. | Report on which channels generate most conversations |
hs_time_to_first_reply_ms | First agent response time (ms) | SLA reporting — measure against response time targets |
hs_time_to_close_ms | Open to closed duration (ms) | Resolution time reporting |
hs_conversation_closed_date | When conversation was closed | Time-based reports, CSAT survey timing |
hs_source_url | Page URL where chat was initiated | Report which pages generate most conversations |
hs_assigned_agent | Agent currently assigned | Routing and reassignment logic in workflows |
The hs_time_to_first_reply_ms property is one of the highest-value metrics in a sales-oriented Conversations setup. Studies consistently show that responding to an inbound lead within 5 minutes is 20× more likely to result in a conversion than responding in 30 minutes. Track this property in a real-time dashboard for your sales team. It is a direct revenue driver that Conversations data makes measurable.
A complete Conversations architecture for a B2B SaaS company with a sales team and a customer success team.
A B2B SaaS company has 8 people in sales and 6 people in customer success. Currently they use Gmail for all email, Intercom for live chat, and a personal WhatsApp for some customer messages. None of these are connected. A new customer might be talking to 3 different people across 3 different tools — none of whom can see each other's conversations.
The admin builds two inboxes
- ChLive chat widget on website (pricing and features pages only)
- Team3 SDRs added as agents
- Bot"Sales Qualifier Bot" — collects name, email, company size, role. Routes 50+ employees with VP+ title to live agent. Routes smaller companies to self-serve resources.
- RouteRotate among SDRs (round-robin)
- HoursMon–Fri 9am–6pm EST. Outside hours: bot active, collects email, creates Lead in CRM.
- TicketsDisabled — these are sales conversations, not support issues.
- ChTeam email (support@company.com) + WhatsApp Business
- Team6 CS agents added
- BotNone — all messages go directly to agents
- RouteAssign to contact owner — existing customers route to their dedicated CSM automatically
- Hours24/7 (support emails never "close" — after-hours messages queue for morning)
- TicketsEnabled — every new conversation creates a Support Ticket with priority Medium by default
What changes for the company
- 🎯The sales team's bot qualifies 60% of website visitors automatically — agents only see conversations from qualified leads. Response time for qualified leads drops from 3+ hours to under 5 minutes during business hours.
- 📋Every customer support email now creates a Ticket. The CS manager can see a live pipeline: 12 Open, 4 Snoozed, 89 Closed this week. Resolution time tracked for the first time: average 4.2 hours.
- 🔗Every conversation — sales and support — is visible on the Contact record. When a Customer calls the AE, the AE can see the last support ticket before picking up the phone.
- 📊First response time is now a reportable metric. The sales manager builds a dashboard: average first response time by SDR. Immediately identifies one SDR averaging 47 minutes vs team average of 8 minutes.
A B2B SaaS company set up HubSpot Conversations with a live chat widget but left routing as "allow agents to self-assign." Chat conversations would arrive and sit unassigned. Agents assumed someone else would pick them up. Average first response time: 47 minutes. The sales team had a 4% chat-to-demo conversion rate and couldn't understand why. The company was spending $40k/month on paid ads driving traffic to a website where chat inquiries were dying unanswered.
- ⚙️Changed routing to "Rotate among team members" — every new chat immediately assigned to the next SDR in the rotation. No conversation lands unassigned.
- 🔔Added a real-time notification: whenever a conversation is assigned to an SDR, they receive an immediate browser notification and a Slack alert via integration.
- 📊Built a "First Response Time" dashboard widget — visible to the full sales team. Updated live. Each SDR's average response time visible to everyone. Social accountability kicks in.
- ⚡Added a SLA workflow: if a conversation is Open and assigned but no response logged within 10 minutes → notify the SDR manager immediately.
Average first response time dropped from 47 minutes to 4.2 minutes within 30 days. Chat-to-demo conversion rate jumped from 4% to 18%. The $40k/month ad spend was suddenly generating 4.5× more pipeline from the same traffic. The admin change took 2 hours to configure. ROI was immediate and measurable.
An e-commerce SaaS company had 40% of their website traffic arriving between 6pm and 9am — outside business hours. During those hours, the live chat showed "We're offline. Leave a message." Visitors left. No lead was captured. The sales team came in each morning to zero overnight leads despite strong overnight traffic analytics showing 200–400 unique visitors during those hours.
- 🤖Built a "Lead Capture Bot" to run during off-hours. Flow: greeting → ask for name → ask for email → ask "What brings you here today?" (5 fixed options mapped to Contact properties) → ask "What's your company's annual online revenue?" (4 ranges) → set lifecycle = Lead → enrol in overnight nurture sequence → "We'll be in touch during business hours. Here's a guide to get started."
- ⏰Configured availability hours: live agents Mon–Fri 9am–6pm. Bot automatically activates outside those hours — no manual switching needed.
- ⚙️Built a workflow: every contact captured by the bot overnight → Lead Status = New → create task for assigned SDR: "Overnight lead — follow up first thing." Task due at 9:05am.
First month: 180 overnight leads captured that would have been zero. 34 (19%) booked a demo from the overnight nurture sequence. 11 became customers within 90 days. Revenue from overnight leads in month 1: $88,000. The bot cost 6 hours to build and configure. The sales team loved the morning task queue — structured follow-up on warm, already-partially-qualified leads.
A B2B tech company's CS team handled 200+ support emails per week. All managed in a shared Gmail inbox. No tracking of resolution time, no way to see what was open vs closed, no reporting on common issue categories, no SLA. The Head of CS had to manually count open emails every Friday to report to the CEO. When a customer asked "what's the status of my issue?" the agent had no structured answer beyond digging through Gmail threads.
- 📧Connected support@company.com to a new HubSpot Support inbox. Enabled auto-ticket creation. Every email now creates a Ticket automatically.
- 📋Built a ticket pipeline: New → In Progress → Waiting on Customer → Resolved → Closed. Each agent moves tickets through stages as they work issues.
- 🏷️Added a required "Ticket Category" property: Billing, Technical, Account, Feature Request, Other. Agents must categorise before closing.
- ⚙️Built SLA workflow: if Ticket priority = High AND no agent reply in 2 hours → escalate to CS manager with notification and create urgent task.
- 📊Built CS dashboard: open tickets by category, average resolution time by agent, SLA breaches this week, tickets closed vs opened (net flow). Shared with CEO every Monday via scheduled report.
Week 1: 147 open tickets identified that had been sitting unresolved in Gmail (some for 3+ weeks). All resolved within 10 days with the new process. Ongoing: average resolution time dropped from "unknown" to a tracked 5.8 hours for standard tickets. Billing issues identified as taking 2× longer — finance process changed to fix root cause. The CEO's Friday report went from "I think we have about 30 open issues" to a live dashboard showing exactly 12 open, 4 SLA at risk, 89 closed this week. CS team morale improved — they could see their work quantified and celebrated weekly.
- 01 — Creating too many inboxesOne inbox per team is almost always enough. Per-agent inboxes, per-product inboxes, per-region inboxes — all defeat the purpose of a shared inbox. More inboxes = more routing complexity, more notification confusion, and more places for conversations to fall through the cracks. Start with three maximum: Sales, Support, General.
- 02 — No routing rules configuredLeaving conversations unassigned with no rule is the single most common Conversations failure. Nobody feels responsible, response times balloon, leads go cold. Always configure routing before any inbox goes live — even "allow agents to self-assign" is better than nothing.
- 03 — Not setting availability hours for live chatIf live chat runs 24/7 with no bot or offline form, visitors chat at 2am and get silence. They bounce and never come back. Always configure availability hours and define clearly what happens outside those hours: offline message, offline form, or bot takeover.
- 04 — Building a bot that dead-endsEvery bot path must end with an action: route to human, book a meeting, or send a resource. A bot that asks three questions and then goes quiet is worse than no bot — it actively frustrates visitors who engaged expecting help. Map your entire bot decision tree before building it in HubSpot.
- 05 — Not asking for email early in the bot flowWithout an email, anonymous visitors create contacts that can't be linked to existing CRM data. The bot collects great qualification answers but they're attached to an orphaned "unknown" contact rather than an existing Lead. Always ask for email as one of the first two bot questions.
- 06 — Enabling auto-ticket creation on sales inboxesEvery chat from a sales prospect shouldn't create a support ticket — that pollutes your ticket pipeline with non-support conversations. Enable auto-ticket creation on support inboxes only. Sales conversations are conversations, not issues to be tracked in a support pipeline.
- 07 — Not training agents to close conversationsAgents who respond and then leave conversations Open create a permanently inflated "open" count. Workload reporting becomes meaningless. Build a daily "close stale conversations" practice — conversations with no activity in 48 hours should be reviewed and closed or snoozed.
- 🗂️One inbox per team function. Sales inbox for sales conversations. Support inbox for CS. General inbox for everything else. Never per-agent — shared inboxes exist for a reason.
- ⚙️Configure routing before going live. Routing is the first thing you configure and the last thing you want to be debugging while live conversations are coming in. Test routing with yourself before adding the team.
- 🤖Always have a bot or offline form for off-hours. No inbox should show visitors a dead end. Outside business hours: collect email and qualify with a bot, or at minimum show an offline form that creates a Lead in the CRM.
- 📧Ask for email early in every bot flow. Without email, conversations create orphaned contacts. With email, every bot interaction enriches an existing Contact record. This is the difference between conversations being useful data and being noise.
- 📊Build a first response time dashboard from day one. This is your primary metric for conversations effectiveness. Target under 5 minutes for sales chat. Make it visible to the team — social accountability drives behaviour change faster than any policy.
- 🎫Enable auto-ticket creation for every support inbox. Without tickets, support is invisible. With tickets, you have a pipeline, SLA tracking, category reporting, and resolution time measurement. This is a 2-minute toggle that unlocks an entirely new reporting layer.
- 🔒Use snippets and templates for common replies. Build a library of pre-written responses to common questions. Agents use them in one click. Consistent answers, faster responses, less typing. Create under Settings → Snippets.
Do this in your free HubSpot sandbox — approximately 50 minutes.
Part A — Create an inbox (20 min)
- Go to Settings → Inbox → Create inbox. Choose "Live chat."
- Name it "Practice Support Inbox." Add yourself as the only team member.
- Set routing to "Rotate among team members" (even with just yourself).
- Set availability hours: Mon–Fri 9am–5pm. Configure offline message: "We're offline right now. Leave your email and we'll get back to you."
- Enable auto-ticket creation. Save.
- Go to your Conversations view (top navigation) and verify the inbox appears.
Part B — Build a simple bot (20 min)
- Go to Settings → Chatflows → Create chatflow → Website → Bot.
- Connect it to your Practice Support Inbox.
- Build a 4-step bot: (1) "Hi! What's your name?" → save to First Name property. (2) "What's your email?" → save to Email. (3) "How can we help?" with 3 quick-reply buttons: Product question / Billing / Something else. (4) Each path ends with "Thanks! We'll be in touch shortly." and closes the conversation.
- Publish the bot. Use the preview tool to test it yourself.
Part C — Send a test conversation (10 min)
- Get your live chat share link from the inbox settings. Open it in a private browser window.
- Interact with your bot using a fake name and email. Complete the full flow.
- Go to HubSpot Contacts — verify a new Contact was created with the name and email you entered.
- Go to the Conversations inbox — verify the conversation appears, is assigned to you, and has a status of Open.
- Go to the Tickets view — verify a ticket was automatically created and linked to the conversation.
- Reply to the conversation from inside HubSpot. Close it. Check the ticket — did it close too?
| Concept | Key point |
|---|---|
| What is it | A unified team inbox where all channels (email, chat, WhatsApp, FB) route messages — connected to your CRM |
| Channel | A connected source: email address, chat widget, WhatsApp account, Facebook page |
| Inbox | A named container — has team members, routing rules, availability hours, and settings |
| Conversation | A single thread between team and contact — linked to a Contact record, has a status |
| Contact matching | Email/phone matched to CRM → existing Contact linked. No match → new Contact created. |
| Statuses | Open (needs action) · Snoozed (follow up later) · Closed (resolved) |
| Routing options | Rotate (round-robin) · Contact owner · Specific agent · Self-assign (unassigned queue) |
| Routing rule #1 | Always configure routing. Never leave conversations landing unassigned with no rule. |
| Live chat + bot | Bot responds first, qualifies visitor, hands off to human. Bot must always end with an action. |
| Bot: always collect email | First 2 steps of any bot: name + email. Without email, conversations create orphaned contacts. |
| Auto-ticket creation | Enable for support inboxes only. Creates a Ticket record linked to conversation and Contact. |
| Inbox vs Ticket | Conversation = the message thread. Ticket = the operational issue with pipeline stage and SLA. |
| Key metric | First response time (hs_time_to_first_reply_ms) — direct revenue driver for sales inboxes |
| Multiple inboxes | One per team function: Sales, Support, General. Never per-agent. |
| Off-hours rule | Always configure: offline form, offline message, or bot for when agents are unavailable |
| RevOps superpower | Route to contact owner → existing customers reach their CSM automatically with no manual assignment |
| Admin interview gold | "I measure first response time from day one — it's a direct revenue driver for sales inboxes and a direct retention driver for support inboxes." |
Conversations is simultaneously a communications tool and a revenue infrastructure component. For sales teams, it's the mechanism that determines whether warm inbound leads get a response in 4 minutes or 47 minutes — and that difference is worth tens of thousands in pipeline monthly. For CS teams, it's the operational backbone that turns support from invisible email chaos into a measurable, pipeline-style function with SLAs, categories, and resolution time reporting. A well-built Conversations setup — right channels, right routing, right bots, right ticket integration — is one of the highest-ROI admin projects you can deliver for any organisation. Build it deliberately and you'll see the impact immediately in the numbers.