TL;DR

In Eloqra, whoever replies first to a conversation becomes its assigned operator, so there is no queue or routing engine to configure.

Key Points

✓

Eloqra uses a simple first-responder model: the first [[support-operator]] to reply via Telegram is stored as the assignment for that [[conversation]].

✓

There is no round-robin, load-based, or rules-driven assignment yet, unlike larger help desks that auto-route to the least-busy or most-relevant agent [1][3].

✓

Because new visitor messages are forwarded to the project owner over [[telegram-integration|Telegram]], assignment happens by replying-to-message rather than clicking an "Assign" button [4].

✓

Assignment is distinct from [[chat-routing]] (deciding where a conversation goes) and from a formal [[ticketing-system]] queue, neither of which Eloqra implements.

✓

Eloqra has no multi-seat teams, tags, or [[escalation]] paths, so assignment stays a single recorded fact per conversation rather than a configurable workflow [2].

How assignment works in Eloqra

When a Website Visitor sends their first Chat Message, Eloqra stores the message and forwards it to the project owner on Telegram. The owner answers either by using reply-to-message in the chat or from the Telegram Mini App inbox, and that reply travels back to the widget through a Webhook. The moment that first reply is sent, Eloqra records the responding Support Operator as the conversation's assigned agent. This is the same plain-English idea other tools call manual assignment, where a teammate simply claims a chat and becomes responsible for it ^[1]^[4] - except Eloqra makes it automatic and invisible: there is no "Assign to me" action to click, no queue to pull from.

First responder vs. automatic routing

Mature platforms layer routing strategies on top of assignment: round-robin rotates chats sequentially, balanced (load-based) assignment sends each new Conversation to the agent with the fewest open chats, and rules can route by intent or attributes ^[1]^[2]^[3]. Crisp, LiveChat, and Intercom all expose these as configurable settings ^[2]^[3]^[4]. Eloqra deliberately ships none of this. With a single project owner answering from Telegram, first-responder assignment is enough and keeps setup near-zero. Founders who later need Chat Routing, a Shared Inbox, or per-agent Chat Concurrency limits would be describing features beyond Eloqra's current scope.

What assignment does not include

Assignment in Eloqra is one recorded fact, not a workflow. There is no Ticketing System, no SLA timers, no tags, and no Escalation from one operator to another, because Eloqra is single-seat today. A Conversation still carries an Open or Closed status and unread counters, and on first contact Eloqra captures context such as page URL, device, and IP Geolocation - but none of that drives who gets assigned. If you grow into a multi-agent team and want metrics like First Response Time (FRT) tied to specific assignees, that is the point where a dedicated Help Desk becomes relevant ^[2].

Sources & References

Chat Distribution Features - LiveAgent ↗

Balanced assignment deep dive - Intercom Help ↗

Inbox Routing Rules: Assign Conversations Automatically - Crisp ↗

Understanding chat assignment - LiveChat Help Center ↗

Last updated: June 25, 2026

Related Terms

Chat Routing

Chat routing is the logic a live-chat or support platform uses to direct each incoming conversation to the right operator, team, or queue. It applies rules based on agent availability, capacity, skills, and customer attributes so that visitors reach a qualified responder quickly.

Support Operator

A support operator is the human on your side of a live chat who reads visitor messages and replies to them. In Eloqra the operator is whoever has access to the project's Telegram chat or Mini App inbox and answers incoming conversations from there.

Conversation

A conversation is the threaded exchange of messages between a single website visitor and a project's operators, grouped as one unit with a status and unread counters. In Eloqra it is the container that holds every message, the visitor's captured context, and the assigned operator.

Ticketing System

A ticketing system is software that turns customer requests into trackable tickets, then helps a support team categorize, prioritize, assign, and resolve them through a defined lifecycle. It centralizes inquiries from many channels into one queue with status, ownership, and reporting.

Telegram Integration

Telegram Integration is the mechanism by which Eloqra routes every website chat into the project owner's Telegram, forwarding visitor messages to a Telegram bot and flowing operator replies back to the widget. It turns Telegram into the operator inbox, so there is no separate agent console to keep open.

Escalation

Escalation is the process of moving a customer issue from a first-line agent to someone with more seniority, authority, or specialized expertise when it cannot be resolved at the current level. It routes the conversation to the person best equipped to solve it, rather than leaving it stuck.

More in Conversational Support & Help Desk

← Previous

Chat Routing

Conversation Tag

Collect testimonials that build trust

Eloqra gives you a lightweight live chat widget that routes every visitor message to your Telegram — free while in early access.

Get Started Free

More in Conversational Support & Help Desk

Business Hours

Canned Response

Chat Routing

Conversation Tag

Conversational Support

Customer Service

Customer Support

Escalation

First Contact Resolution (FCR)

Help Desk

View all in Conversational Support & Help Desk →

Conversation Assignment

Key Points

How assignment works in Eloqra

First responder vs. automatic routing

What assignment does not include

Related Terms

Collect testimonials that build trust