Customer support: requests, team and routing
Project support is the team's shared work on visitor requests. This article covers the rules for the queue, assigning an agent, AI participation, handing off to colleagues and closing a conversation. It's important to distinguish viewing, provisional assignment and actually taking a request: responsibility and automatic answers depend on it.
Viewing a request doesn't mean taking it
You can open an available conversation, read the virtual assistant's answers and leave. Viewing by itself registers the viewer's presence but doesn't make them the assignee. At the same time, an open app keeps the agent's presence online, so regular auto-assignment can still kick in regardless of viewing.
An agent's first reply or an explicit assignment ties the request to that agent. A provisional automatic reservation keeps the "New" status, while taking the request moves it to "In progress". Read access and the right to reply depend on project membership and permissions.
How automatic routing works
The project's routing settings offer manual mode, least-busy agent and round-robin. By default, the least busy eligible agent is chosen. When the load is equal, the time of the previous assignment is taken into account.
A candidate must be an active project member, have read and send permissions, be online and not have reached their limit of active requests. If a department has specific staff assigned, routing takes that staff into account. When conditions allow, the system prefers an agent who has already replied in this request.
If no eligible agents are available, the request stays in the shared queue. In manual mode there's no automatic choice: the team assigns someone themselves.
When a request is handed to another agent
If the customer is waiting for a reply, the assignment is checked against the response deadline and the agent's availability. After a long time without a reply or a loss of availability, the reservation is released, and another eligible agent can get the request. A brief network drop doesn't mean an immediate handoff.
By default, the wait time for the assigned agent's reply is 5 minutes, and the grace period for unavailability is 3 minutes. You can change these parameters in the project settings. A handoff doesn't delete the history or the customer's messages.
How AI and agents work together
While an enabled virtual assistant is still waiting for the first message, preparing a reply or has already answered the customer's latest message, auto-assignment doesn't reserve the request for a person. The assistant keeps handling the next question. An agent viewing the conversation doesn't interrupt this mode.
Taking a request pauses the assistant in it: an explicit assignment, auto-assignment, a transfer or the agent's first reply. The agent doesn't have to leave the chat to bring the assistant back: the ⏸ / ▶ AI button in the request header switches it on again, and the assistant keeps helping while the request stays with the agent. When the request goes back to the queue, the assistant is on again by itself.
If the assistant is turned off, failed to process the latest request or received an unsupported message type, regular routing applies again. An earlier successful reply doesn't hide a later unprocessed question.
An assistant reply doesn't count as the first human reply for SLA purposes. So the wait time for an agent and the fact that the AI replied are different metrics.
Pausing and resuming the assistant in a request
The button is shown when the project has an assistant and AI is allowed in the request's channel. Anyone who can reply in the request can press it: the assignee, a participant, the owner or an admin.
Open the request. In the header, next to Status and Take chat, there is the assistant button.
▶ AI means the assistant is paused in this request. Click it, and the assistant answers the customer's next messages again, while the request stays with you.
⏸ AI means the assistant is working here. Click it to pause it and answer yourself.
Colleagues see the change at once. Requests that were already taken when this button appeared start paused.
Statuses, handoff and closing
A request has four statuses: "New", "In progress", "Closed" and "Spam". In the request info, you can transfer it to a colleague or department and change its priority. Closing keeps the conversation; a new reply from the customer brings a closed request back into work. Spam isn't reopened automatically by a new message.
A separate indicator shows who is currently awaited: the agent or the customer. This isn't an additional status. If automatic closing on customer inactivity is turned on, the timer counts from the corresponding wait. There are no snoozed requests or a separate "remind me later" mode in this process.
Working with requests
To the left of the conversation is a narrow list with search and filters at the top. On the right is the chat: the other person's name in the header, messages in the middle and the input field at the bottom. Only the messages scroll; when you open a conversation, you see the latest ones. If you're reading earlier history, new messages don't jump you back to the bottom.
Open "Requests" and select the project you need at the top.
Choose a status: "Open", "All" or "Closed". If needed, choose a department or a channel.
Click a request in the list. Its history appears on the right.
Type your reply in the bottom field and click the send button. The customer sees the message on behalf of the project.
When the issue is resolved, click "Close". The conversation stays in the history; you can find it under "Closed" and open it again.
Internal notes open from the info button ⓘ in the request header. These are comments for the team. The customer doesn't see them. For example: "Check the delivery date with the warehouse".
The top block of the request info shows how the messenger knows the customer: the WhatsApp number, the name in their profile and, for Telegram, Instagram and MAX, their @username. Telegram and Instagram usernames link to the profile. The name and username are refreshed with every message the customer sends.
The new-messages banner disappears once you've read them. This doesn't delete the conversation itself.
Agents and departments
The owner or an administrator opens the project and finds the employee in the "Add agent" block. The employee must first sign in to Chat with their Sensever account. Once added, they can work with the project's requests.
In the project's "Team" tile, in the "Team and departments" card, create departments, for example "Tech support" and "Sales", and mark who works in each. An active department can be shown to the visitor before the conversation starts.
To transfer a request to another department, open it, click the info button ⓘ in the header, choose the department and click "Transfer". Notifications about a department's requests go to the assigned employees.
A department helps route requests and notifications. A department that is on and has staff shows its requests only to its staff, the owner and admins; a department that is off or empty doesn't limit who sees its requests. The owner and admins see the requests of every department.
You can also choose who handles each contact channel (a messenger, the website widget, the contact page) in "Channel access" of the "Team" tile, and turn the AI off for a single channel. Details: Channel access: who handles requests from each channel.
Which page the visitor wrote from
In the request header, click the info button ⓘ. In the window that opens, find "Visitor and page history". It shows the page of the first message, subsequent navigation on the site and the country, if it could be determined.
Visit history starts being recorded after the first message. It covers the site where the widget is installed — it isn't a history of every site the person opens in their browser.
Extra URL parameters and the part after the # sign aren't stored. The country is determined approximately; if there's no data, you'll see "Unknown".
Example: a customer asks "Is this in stock?". The history shows which product page they wrote from, so it's easier to tell which product they mean.
Why chat and request counters differ
Reads by the visitor and reads by the project team are counted separately. If the owner writes to their own widget, they are both a visitor and an employee: the conversation may be read by their account, while their incoming messages remain unread on the project side in "Requests".
What the widget marks
An open, visible widget marks messages as read on the visitor's side when they're at the latest messages. This doesn't mean a project agent has read the question.
What "Requests" means
It's the project team's work queue. To handle a question as an employee, open the corresponding request on the project side. Don't confuse this counter with the visitor's personal unread messages.
How to turn off notifications from a widget or request channel
Open the filter next to "Create" → "Feed settings". Turn on "Quiet" for the website widget or messenger connection you need, for example Telegram, and click "Save". To cover all projects at once, turn on "Quiet" for "All project requests". This is a personal mute: sound and message notifications are turned off only for you, including new conversations from that source. Unread counters are kept.
The "On home" toggle controls visibility independently of quiet mode. Hidden requests are available in their own tab. The setting doesn't change agent assignment, routing, the request status or your colleagues' work. A website widget and Telegram of the same project are separate sources with separate settings.
More details: Chats, contacts and messaging in Sensever — feed settings
Where did the conversation with a customer go?
Open "Requests", check the selected project, set the status to "All" and the department to "All departments". Click "Refresh". Closed conversations stay in the history. If the conversation is missing only from home, check the filter next to "Create" → "Feed settings": the source may be hidden. No notification doesn't mean the message was read: quiet mode may be on for the category, the source or the conversation.
Why doesn't the widget appear on the site?
Check that the code installed is for the selected site, that "Show widget" is turned on and that the domain matches, including www. Refresh the page. If the widget opens automatically, wait for the set delay.
Why can't I find an employee in search?
Ask them to sign in to Chat with Sensever at least once. Then search by name again in the project team settings.
A message didn't send. What should I do?
Check your connection and resend the same message. If the first attempt already reached the server, clicking the send button again won't create a duplicate. If you see a message saying your session has ended, sign in again.
Why is there no visit history or country?
History isn't collected before the first message. Navigation is visible only on a site with a working widget. The country can't always be determined — missing data doesn't affect the conversation.
How do I find a user and start a conversation?
In "Chats", type at least two characters of a name or an @username in the search above the list. Find the person in the global results and open a direct chat. Another way is "Chats, contacts and messaging in Sensever" → "Add contact". If the person isn't there, check the spelling and ask them to open Chat with their account at least once.
Can I just see what the AI replied?
Yes. Opening a request doesn't make you the assignee. While the AI is working, auto-assignment doesn't take the conversation for an agent. Taking the request pauses the assistant; the ▶ AI button in the header lets it help again.
How do I ask a live agent for help?
Write in the widget at sensever.com/help that you need help from an agent and describe the problem. The conversation stays in the team's request. The assistant doesn't promise that a person will join immediately and must not report a handoff it didn't perform.
Why did the AI call an ordinary question off-topic?
The topic check sometimes makes mistakes on short phrases. Questions about finding people, conversations and navigation are about Sensever even without the service name. Say exactly what you need to find or open. For an ambiguous "How do I find a person?", the assistant asks whether you mean a user or a support agent.
Comentários