پایگاه دانش GetMyBot

Chats and Operators

Reply to customers in the dashboard, hand a conversation to a teammate, leave private notes and manage the support queue.

در این صفحه

In Chats, your team answers customers and continues conversations after the bot. The shared queue, also called the inbox, is on the left, the conversation is in the center, and the customer card is on the right. Select a conversation, reply and close it when the question is resolved.

The bot can hand a conversation to a person with the Transfer to operator action. A teammate can also take it manually. This article covers your customer conversations; GetMyBot support handles questions about the platform itself.

Operator inbox

The left-hand list has search and All / Open / Closed filters with counts. Each row shows the customer's name, transferred or closed status, the start of the latest message, its time and the unread count. The conversation appears in the center and the customer card on the right.

Working with a conversation

At the top of a conversation, you can see the VIP label and the Transfer (take the conversation) and Close buttons. Quick-reply buttons help with common phrases. As in People, you can type a reply, attach a file or send a reaction.

Handing off from a reaction

The Transfer to operator action (to_operator) moves the conversation into the shared queue. The customer's message is forwarded to an operator's chat; you can add a prefix if needed. The operator replies to that forwarded message, and the reply goes back to the customer. The bot can handle the first part of a conversation and pass harder cases to a person.

Approval by a teammate

Use Request approval (approval) when a person must make a decision, such as checking a request before granting access. The bot sends them a card with Approve and Reject buttons. Each button has its own reaction. Technical settings may call the person making the decision an approver.

Priority conversations

The Priority reaction (color) action marks a conversation with a color so operators can find important requests faster.

Live chat and history

New customer messages and operator replies appear in the open conversation without reloading. They arrive over a WebSocket connection, so several operators see updates at the same time.

Older messages load as you scroll up. This lets even a long conversation open without waiting for its full history. Technically, cursor pagination uses a “load before” marker and a flag showing whether more messages remain.

Managing the queue

Filter the shared queue by channel, group, status, label, assignee, first-reply deadline, unread messages or a search term. Clear the filters to see everything again. A conversation can be open, pending, closed or snoozed. Assign it to yourself, another available operator or a group. To snooze it, choose a future return time. A new customer message or that time arriving returns it to the active queue.

Use a quick reply or channel template for consistent answers. Quoting, attachments, voice messages, transcription, typing indicators, editing and templates are available only when the customer's channel supports them. Emails stay in the same conversation and keep the message thread. If a channel cannot quote a message or show typing, the control is unavailable; the message is not silently changed.

For information meant only for teammates, add a private note. It is not sent to the customer. History records assignments, statuses, sent messages, delivery outcomes and references to notes. The private note's text is not included in general conversation updates.

Working together without losing changes

When two operators edit one conversation, the system compares its current version, or revision. If someone else saved first, you see the new state instead of overwriting it with an older one. The presence indicator shows who else is viewing the conversation but does not lock it. History retains changes, and the queue and open conversation update immediately.

Availability, routing and reports

In Settings, an administrator sets the schedule, timezone, breaks, holidays and automatic replies. A backup group (overflow group) can receive requests when the main operators are unavailable.

Assignment excludes unavailable operators and chooses the least-loaded suitable one. If none is available, the request goes to the backup group or remains unassigned. Before an automatic reply enters the sending queue (outbox), the system checks channel capabilities, customer consent, the allowed reply window and limits. It does not repeat the reply within the configured conversation interval.

Reports show workload, handoffs, response and resolution times, whether the first-reply deadline (SLA) was met, and customer ratings (CSAT). For example, the 90th percentile response time is the time within which 90% of measured replies were sent.

Exports require permission and a timezone in IANA format, such as Europe/Belgrade. They are recorded in the audit log and include permitted metrics, without message or private-note text. Values are protected from running as spreadsheet formulas.

Requests to GetMyBot support

Use GetMyBot support to contact the platform team. Give the issue a short subject, describe what you expected and what happened, and include the project ID if relevant. Replies and status appear in the request thread; a new reply continues the same request. Do not include passwords, tokens or authenticator recovery codes. This queue is separate from your customers' inbox.

Shared read status

Read-status settings determine whether read marks stay personal or are shared with teammates. A member can enable personal sharing. A bot-wide setting enabled by someone with the required permission makes read status shared for everyone and takes priority over personal preferences.

Reading support metrics

P50 means half of measured conversations were answered or resolved within that time; P95 means 95% were. Before comparing results, check the number of conversations, reporting period and operator or group filters. Customer satisfaction (CSAT) includes only customers who submitted a rating. Look at both the response count and the rating distribution. No ratings means satisfaction has not been measured yet.

What's next