Chat Session
Definition
Chat Session
A chat session is a real-time, text-based conversation between a customer and an agent — human or bot — carried over a website widget, mobile app, or messaging channel. It runs from the first message to a defined close event, and it is the atomic unit contact centres use to measure digital service quality.
Every live chat, WhatsApp thread, and Facebook Messenger dialogue a brand handles is counted as one session. Sessions carry their own timestamp, transcript, queue history, and outcome tag, which becomes the raw material for reporting on volume, handle time, and customer satisfaction.
Digital-first buyers have pushed chat past email in most Western markets. Salesforce’s State of the Connected Customer research reports that 57% of consumers now prefer messaging channels for routine service, and 71% expect a response within five minutes.
Because sessions can be human, bot-assisted, or fully automated, they sit at the intersection of the contact center, CRM, and workflow automation stacks.
Key takeaways
- A chat session is one complete text conversation between a customer and an agent or bot, opened by the first message and closed by inactivity, resolution, or manual end.
- Sessions are the base unit for chat KPIs: concurrency, average handle time, first-contact resolution, and CSAT.
- A trained agent typically handles two to four concurrent chat sessions, versus one voice call at a time.
- Chatbots now deflect the majority of tier-0 sessions; humans take over on escalation via warm handoff.
- Offshore BPO providers in the Philippines, India, and Colombia staff chat around the clock at 40–60% of onshore cost.
How it works
A chat session opens when a customer clicks the widget, sends a message to a business number, or triggers a proactive prompt. The platform assigns a session ID, routes the request through queue logic, and drops it into the next available agent’s console.
The session closes on one of three events: the customer confirms resolution, the agent clicks “end chat,” or an inactivity timer expires (usually 5–10 minutes with no reply). Everything between open and close belongs to that session, including bot handoffs and transfers.
Concurrency is what separates chat from voice. One agent runs several sessions in parallel — the industry norm is 2–4, though skilled agents on simple queues push past six. That multiplier is why chat costs less per contact than a phone call, and why workforce management formulas for chat differ from voice.
Two core formulas govern chat capacity planning:
| KPI | Formula | Healthy benchmark |
|---|---|---|
| Chat handle time | Session open → session close, agent time only | 6:00–10:00 min |
| Concurrency | Active sessions ÷ logged-in agents | 2.0–4.0 |
| Chat abandonment | Sessions ended before agent reply ÷ total offered | Under 5% |
| First-contact resolution | Sessions closed without transfer or re-open ÷ total | 70–80% |
| CSAT (post-chat) | Positive responses ÷ surveys returned | 85%+ |
Benchmarks are drawn from ContactBabel’s *US Contact Center Decision-Makers’ Guide* 2024 edition and ICMI operational surveys. Anything below the healthy band usually points to routing, staffing, or knowledge-base gaps rather than agent skill.
Modern chat platforms like Zendesk, Intercom, Salesforce Service Cloud, and LivePerson also log intent, sentiment, and bot-vs-human minutes inside the session record. That metadata feeds quality scoring, coaching, and forecasting.
Examples
Concentrix runs 24/7 chat pods for a US telco out of Manila and Bogotá. Agents handle three concurrent sessions on average, and the bot deflects roughly 45% of tier-0 password-reset traffic before a human ever sees the queue.
Teleperformance staffs Shopify’s post-purchase chat channel from Lisbon and Cairo. Session volumes triple during the November–December peak, so the client relies on forecasting models that treat chat, email, and voice as separate backlogs with different service-level agreements.
TTEC’s Digital business unit combines chatbots with human escalation for a US health-plan client. In their 2024 case study, average session length dropped from 12 minutes to 7 minutes after routing bots to authenticate members before the human joined.
Foundever (formerly Sitel + Sykes) has published that its Colombia and Philippines chat teams average 3.2 concurrent sessions per agent, with a 78% first-contact resolution rate for retail clients — inside the ContactBabel healthy band.
Alorica and Genpact both operate hybrid pods where a single agent handles two chat sessions and one back-office ticket during quiet minutes, blurring the line between contact-centre and back-office workflow.
Related terms
- Contact center: The multi-channel operation that houses chat, voice, email, and social service in one queue system.
- Live chat: The synchronous, text-based service channel that produces most chat sessions.
- Chatbot: The automated agent that handles tier-0 sessions before human handoff.
- Average handle time: The per-session duration metric — a core chat KPI.
- First-call resolution: The chat-adapted version measures sessions closed without transfer or re-open.
- Customer satisfaction: The post-chat survey score that gates coaching cycles.
- Interactive voice response: The voice-channel equivalent of the pre-chat bot greeting.
FAQ
What counts as one chat session?
One session runs from the customer’s first message to a defined close event: resolution, agent-ended chat, or an inactivity timeout. Bot minutes and warm handoffs to a human agent stay inside the same session record.
How many chat sessions can one agent handle at once?
The contact-centre norm is 2 to 4 concurrent sessions per trained agent. Simple, scripted queues push past six, while complex technical or regulated queues drop back to one or two.
How is chat handle time different from call handle time?
Chat handle time counts only the minutes a specific agent is active on the session, not the wall-clock duration. Because agents run sessions in parallel, the same 15 wall-clock minutes may log as 5 minutes of handle time per session.
What is a good chat abandonment rate?
Under 5% is the ContactBabel healthy benchmark. Above 8% usually signals under-staffing at peak, weak proactive routing, or a broken pre-chat form.
Do chatbots count as chat sessions?
Yes. Bot-only sessions log the full transcript, intent tags, and outcome (deflected, escalated, or abandoned). They typically report separately from human-handled sessions in the CSAT and KPI dashboards.
Where do offshore BPOs sit in the chat stack?
Philippines, India, and Colombia providers deliver 24/7 chat coverage at 40–60% of onshore cost. Concentrix, Teleperformance, Foundever, TTEC, Genpact, and Alorica all publish chat-specific pods for global clients.
Compare vetted BPO chat providers on the Outsource Accelerator directory or get a free quote to price a 24/7 offshore chat team.
Independent
