Elbuz gathers today's work for you from different windows — unanswered chats, tickets, customer follow-ups, failed price lists — into the first desktop card.
When you need this:
- A customer wrote, nobody replied — the chat stays in “Unanswered chats” until an operator replies.
- A ticket, follow-up or deal is past due — the record gets an “Overdue” badge.
- AI suggested a customer reply — accept or reject it here, seeing the email first.
- A supplier price list failed to load — everyone with “Price lists” access sees the error.
Where to start: click “Open “My Day”” at the bottom of the card to open the to-do list.
What “My Day” can do
- A card on the desktop — counters for the queues that have work for you.
- A window with the to-do list — up to the first ten records of each queue; a row opens the record itself.
- Decisions on AI proposals — “Accept” or “Reject” without going to “Pulse”, with a check of everything the customer will receive.
- Overdue items flagged — an “Overdue” badge on follow-ups, deals, tickets, AI questions, price lists with an error or a blocked import, and trigger emails.
What work “My Day” collects
The first card in the column collects what needs doing today from different windows. Each row is a counter for one queue, and you see the row only if you have access to that queue's window and the queue is not empty:
- “AI proposals” — “Pulse” proposals awaiting a decision where you or nobody is assigned. You can accept or reject them right in the “My Day” window. Requires access to the “Pulse” window.
- “Tickets: new to me and overdue” — open tickets assigned to you with an unread customer message or a missed response or resolution deadline. Statuses “New”, “Open” and “On hold” count; “Pending” does not: the ball is in the customer's court. Unassigned and colleagues' tickets are not in your counter — see the “Tickets” window queue. A ticket leaves the row once you or a colleague opens it in “Tickets” before the deadline, or it moves to “Pending” or “Solved”. Requires access to the “Tickets” window.
- “Unanswered chats: mine and unassigned” — customer chats where the customer wrote again after the operator's last reply, where no operator has replied yet, or that were manually marked unread. A closed chat does not count until the customer writes again. Chats assigned to you or to no one count; a colleague's chat does not. A chat leaves the counter as soon as any operator replies. Requires access to the “Manage Chats” window.
- “Follow-ups due today” — your open calendar events linked to a contact: those scheduled for today and all overdue ones from previous days. Requires access to “Contacts”.
- “Deals past close date” — deals in progress where you are responsible and the expected close date has passed. Requires access to “Deals”, and the row appears only if your company works with deals (business format).
- “AI asks you” — questions AI asked you or your department when it was replying to a customer in a ticket and found no answer (how AI asks a staff member). The row opens the ticket; the “Overdue” badge means the time AI promised the customer an answer by has passed. Requires access to the “Tickets” window.
- “Price lists with import problems” — price lists whose last run in the past seven days ended with an error, was blocked by a stop rule, or went through but with data anomalies (test runs do not count). Below the price list name you see the supplier and what happened: “import error”, “import blocked” or “data anomalies”. A price list has no responsible person, so this is a shared queue for everyone with access to “Price lists”.
- “Abnormally low supplier prices ignored” — price lists where batch processing discarded suspiciously low prices; the row shows how many. Also a shared queue for everyone with access to “Price lists”.
- “Trigger emails are not being sent” — trigger rules whose email failed to go out in the last 24 hours, or that have failed to send three times and are paused. Requires access to the “Triggers (system events, conditions and actions)” window.
An empty queue has no row; when all are empty, there is no card at all. Numbers update once a minute. A row opens its queue's window — “Pulse”, “Tickets”, “Manage Chats”, “Contacts”, “Deals”, “Price lists” or “Triggers”; the “Open “My Day”” row at the bottom opens the window of the same name with the tasks themselves.
1
My Day card, first in the column2
AI proposals row with a count3
Open “My Day”- My Day card — it is the first widget in the column.
- AI proposals row — the number on the right is how many proposals are waiting for you.
- Open “My Day” — opens the full window with the list of tasks.
1
Block title with count2
Overdue badge3
Ticket not overdue- Your open tickets: unread or past their deadline.
- The reply or resolution deadline has passed.
- The customer wrote and you have not opened it yet — a click opens the Tickets window on it.
How to work with the to-do list
At the top of the window is the total “In queue: N” with a red “overdue: M” mark and today's date. Below it are queue tiles: the number, the name and, if any, “N overdue”. Clicking a tile scrolls the window to that queue's block.
Next, each non-empty queue is a separate card block. Blocks fill as many columns as the window width allows. The color of a block's top edge shows how urgent the work is:
| Edge | Meaning | Queues |
|---|---|---|
| Purple | routine work | “AI proposals”, “Unanswered chats” |
| Yellow | someone is waiting for you | “Tickets”, “AI asks you”, “Follow-ups due today”, “Abnormally low prices” |
| Red | a failure or the deadline has passed | “Deals past close date”, “Price lists with import problems”, “Trigger emails are not being sent” |
A block's header shows the number of records and a “Show all (N)” button if there are more than the ten shown, or “Open window” if all are shown. Both open the queue's window.
Each row in a block is one task:
- on the left, the customer's initial (chats, follow-ups, deals) or an icon for the type of task;
- the name and two lines of text — the last message, the ticket subject, the gist of the proposal;
- on the right, the time: “5 d ago” for what has already happened, “in 2 h” for what is scheduled; hover to see the full date;
- badges: the chat channel (“Website”, a messenger or marketplace name), the AI employee the proposal comes from, “To customer”, “Public”, “Overdue”;
- an action button — “Reply”, “Reply with AI”, “Review”, “Open” or “Fix”.
The action button and clicking the row do the same thing — open the record itself, not a list: a chat opens straight on the conversation in the “Chat dialogs” window, a ticket opens the “Tickets” window on that ticket, a follow-up opens the contact card, a deal opens its document.
A price list has no card of its own, so its row opens “Price lists”: from the import problems queue, straight on the “Overview” tab. A trigger email row opens the mailbox settings or, if the email is missing a subject, text or recipient, the email templates.
Tickets in a block are sorted by deadline: the one that went overdue earliest comes first, those without a deadline come last. When there is no work, the window says “All done for today”.
1
Total items in the queue2
AI proposals block3
Accept, Reject, Review- In queue — the total number of items waiting for you across all modules.
- AI proposals — drafts prepared by AI employees that need your decision.
- Accept, Reject and Review — decide on a proposal right from the list.
The window is a snapshot, not a feed: once open, it does not refresh itself (except for decisions on AI proposals). Replied to a chat or closed a follow-up? Close “My Day” and open it again.
This window has no desktop shortcut or menu item; the only way in is the “Open “My Day”” row on the card. Access to the “My Day” window is open to all departments, including ones you create later: a new department gets it turned on, even though its other work windows are closed.
How to accept an AI proposal without opening “Pulse”
In the “AI proposals” block, each row has three buttons: “Accept”, “Reject” and “Review”. “Review” opens “Pulse”, where you see the details and can edit the proposal. The access rights are the same as in “Pulse”, and every decision is written to its log.
“Reject”, and “Accept” for internal actions (create a follow-up, a task or a deal, add a phone number to a card), take effect immediately. If the action goes to the customer or will be public, “Accept” first opens the “Check before running” dialog. Such rows are marked “To customer” or “Public”:
- a reply to a customer's email, an email or a chat message to a customer;
- hiding a buyer's comment;
- autonomous support actions under the store policy — cancellation, return, reshipment, promo code, change of pickup point;
- AI agent requests from processes.
The dialog shows the action and who it goes to, and for an email or message — the subject and text, which you can edit. The email goes out only after “Confirm and run”; “Cancel” keeps the proposal in the list.
1
Action and recipient2
Email subject3
Message text4
Confirm and run5
Cancel- Action and recipient — what will be done and to whom.
- Email subject — can be edited before sending.
- Message text — the draft reply written by the AI, editable.
- Confirm and run — sends the email immediately and cannot be undone.
- Cancel — closes the dialog without sending anything.
The “Accept safe ones (N)” button appears in the block header when there are at least two such proposals. It accepts at once only those that send nothing to the customer and are not public; the rest stay in the list to check one by one. After you confirm, a summary “Accepted: N, failed: M” appears and the list refreshes.
An accepted or rejected row disappears, and the numbers in the block header, on the tile and in the total go down immediately. If the action fails, a message with the reason appears and the row stays — you can try again or open “Pulse”.
Scenarios
A chat operator wants to start the day with a to-do list instead of going through windows
What to do. Click “Open “My Day”” at the bottom of the “My Day” card on the desktop.
Result. A window opens with blocks by queue: unanswered chats, tickets, follow-ups due today. A row opens the record itself — a chat straight on the conversation, a follow-up on the contact card.
The company has a new department — will its people see “My Day”?
What to do. Nothing special: a new department gets access to the “My Day” window turned on. Give the department access to the windows of the queues it should handle — Access rights.
Result. The card shows only rows for queues whose windows the department has access to and that are not empty.
What to do when the “My Day” card is missing
| What you see | Why | What to do |
|---|---|---|
| A colleague has the “My Day” card at the top of the column, but you don't | The card appears only when at least one of your queues is not empty, and queues depend on access to windows | Nothing: you have no work for today. Once an unanswered chat, a ticket past its deadline or an overdue follow-up appears, the card shows up on its own within a minute (“My Day”) |
| There is definitely work, but the widget column is not on the desktop at all | desktop widgets are turned off, “My Day” was removed from the widget set, or the screen is narrow — then the column is hidden behind the “Widgets” tab at the right edge | Open the “Widgets” tab, or turn widgets on and add the card back to the set (desktop widgets) |
FAQ
Whose chats count in “My Day”?
Chats assigned to you and those with no one assigned yet. A chat assigned to a colleague does not appear in your counter. A chat leaves the counter as soon as any operator replies.
I replied to a chat, but it is still in the “My Day” window. Why?
The window is a snapshot, not a feed: once open, it does not refresh itself. Close “My Day” and open it again. The card on the desktop updates itself once a minute.
Why can't I see a colleague's ticket in my “My Day”?
Only tickets assigned to you count. Unassigned tickets and your colleagues' tickets are in the “Tickets” window queue.
A ticket with the “Pending” status does not count. Is this a bug?
No: the ball is in the customer's court. Statuses “New”, “Open” and “On hold” count (the “Tickets” row).
If I click “Accept” on a reply to a customer, does the email go out right away?
No. First the “Check before running” dialog opens with the recipient and the email text, and you can edit the text. The email goes out only after “Confirm and run” (AI proposals).
Where it is and who has access
- Card
- the first one in the widget column on the desktop
- “My Day” window
- the “Open “My Day”” row at the bottom of the card; there is no shortcut or menu item
- Access rights
- the “My Day” window is open to all departments; each row depends on access to that queue's window
Related topics
- For the big picture of your first day — First login: where to start.
- To understand widgets and windows on the desktop — Desktop, windows and search.
- If there are many tickets in the queue and you need to set deadlines — Tickets.
- If a colleague's card has different rows — Access rights.
