Elbuz pulls Rozetka, Allegro and Prom buyer messages into tickets, the same online store helpdesk as emails and chats, and sends your reply through the marketplace API, no seller account needed.
When you need this:
- A Rozetka buyer asks in the order chat where the parcel is: it joins the shared queue with emails and messengers.
- The marketplace tracks seller response time: the ticket gets its first-reply deadline, and overdue ones show in “SLA breached”.
- Several managers reply: the ticket has an assignee, so no two people answer differently.
Where to start: “Tickets” → gear icon → “Autonomous support” → “Channels and proactive” → the “Marketplace messages” card.
What the marketplace channel does
- Pulls in buyer messages: Rozetka order chats, Allegro Message Center, company messages on Prom.
- Turns on separately for each marketplace: credentials come from an import template you've already set up.
- Sets the marketplace reply deadline if it's shorter than the support desk schedule.
- Sends your reply through the marketplace API: the buyer sees it in their conversation.
- Checks for new messages on demand with the “Check now” button, without waiting for the background check.
Which messages become tickets
| Marketplace | What the app pulls in | Channel label |
|---|---|---|
| Rozetka | buyer messages in order chats | Rozetka |
| Allegro | buyer messages in Message Center | Allegro |
| Prom | customer messages to the company; each one is a separate conversation | Prom |
The app takes only the buyer's messages. A reply a manager writes directly in the marketplace's seller account won't reach the ticket, so reply from the ticket. Reading changes nothing in the seller account: the conversation isn't marked as read.
The bot doesn't reply here: the message waits for a person right away. The ticket follows the usual chat rules: the subject is the buyer's first question, the department is “Customer service”. If the app recognizes the buyer among your contacts and they have an open ticket active in the last 3 days, the message goes there (how channels merge).
On the first check, the app takes messages from the last 24 hours only, so the whole marketplace archive doesn't turn into tickets. After that, only new ones.
How to turn on marketplace messages
You don't need to enter credentials separately: the app takes them from the marketplace import template you already use to pull products or orders. The template must be enabled.
| Marketplace | What the template needs | How to set up the template |
|---|---|---|
| Rozetka | the seller API key (gapi_…) or the seller account login and password | Import from Rozetka via API |
| Allegro | a connected Allegro account (token) | Import from Allegro via API |
| Prom | the company API token | Import orders from Prom.ua |
- Open “Tickets” → gear icon → “Autonomous support” → “Channels and proactive” tab.
- In the “Marketplace messages” card, turn on the toggle for the marketplace you need: “Rozetka”, “Allegro” or “Prom”. All three are off by default.
- Click “Apply”. The toggle doesn't take effect without it.
- Check the table under the toggles: the template should show “Polled”.
The table lists all enabled templates with credentials, in the columns “Import template”, “Channel” and “Status”. If you see “No active Rozetka, Allegro or Prom import templates with credentials.” instead, set up the template first. You don't need to turn on the main autonomous support switch for this channel: AI does nothing on its own here.
Marketplace reply deadline
Marketplaces rate sellers on how fast they reply. That's why a marketplace ticket gets a first-reply deadline in calendar hours from the buyer's message, not in working hours of the schedule.
| Card field | Default | Range |
|---|---|---|
| “Rozetka reply deadline, h” | 24 | 1–168 |
| “Allegro reply deadline, h” | 24 | 1–168 |
| “Prom reply deadline, h” | 24 | 1–168 |
The shorter deadline applies: the marketplace's or the support schedule's. Under a Mon–Fri schedule, a Friday evening message would get a reply on Monday; with the marketplace's 24 hours, it lands in “SLA breached” by Saturday evening. The same goes for the next reply when the buyer writes again. Deadlines and overdue notifications: Working hours and reply deadlines (SLA).
How to reply to a buyer
Open a ticket with the Rozetka, Allegro or Prom channel and reply as you would in a chat: type your text and click “Send”. The app sends it to the same conversation through the marketplace API, and your reply appears in the ticket feed.
1
Rozetka channel2
Buyer question3
Reply deadline chip4
Reply field- The ticket header shows that the conversation came from Rozetka.
- The buyer's question about shipping the order is the ticket subject.
- The chip shows the first-reply deadline and how far it is overdue.
- The reply field sends the answer back through Rozetka (“The reply will go out via: Rozetka”).
- Files: marketplaces don't accept files from sellers through the API, so the app sends a link to the file in the message text.
- Formatting isn't carried over: the marketplace gets plain text with line breaks.
- The reply goes out even if the marketplace check is turned off with the toggle: an enabled template with credentials is enough to send.
Internal notes, macros and the AI draft work the same as in other tickets: Replying to a customer.
How often the app checks marketplaces
The background check runs every 30 minutes. To skip the wait, click “Check now” in the “Marketplace messages” card: the app polls all enabled marketplaces and creates the tickets right away. The hint shows “New messages: N”.
If a marketplace returns an error, such as a wrong password or an expired token, a red message with the marketplace's error text appears under the hint. The other marketplaces are polled as usual.
Scenarios
A store sells on Rozetka, and buyers ask about delivery
The Rozetka template with an API key or login and password already pulls in orders. Turn on “Rozetka” in the card, click “Apply”, then “Check now”. Buyer questions appear in the queue with the “Rozetka” channel and a 24-hour deadline; a manager replies from “Tickets”, and the buyer sees the reply in the order chat.
Allegro requires a reply within a day, but support works weekdays
Set “Allegro reply deadline, h” to 24 or less. A message that arrives on Friday evening lands in “SLA breached” on Saturday, and the assignee and the manager in charge get a notification, so someone replies over the weekend.
Several managers reply on Prom
Turn on “Prom”. Each message becomes a ticket with an assignee: support distribution gives it to one manager, and the ticket shows who is already writing a reply. Two people won't tell the buyer different things.
What to do when marketplace messages don't arrive
| What you see | Why | What to do |
|---|---|---|
| “No active Rozetka, Allegro or Prom import templates with credentials.” | The marketplace template is disabled, or it has no API key or login and password (Rozetka) or token (Allegro, Prom) | Enable the template and fill in the credentials (how to turn it on) |
| The template shows “Off” | The marketplace toggle is off, or the changes weren't applied | Turn on the toggle and click “Apply” |
| After “Check now”, a red message with a marketplace error | The marketplace rejected the credentials: the password changed or the token expired | Update the credentials in the import template and check again |
| Old messages aren't in Tickets | The first check takes only the last 24 hours | Finish old conversations in the marketplace's seller account |
| A reply from the ticket wasn't sent | The marketplace template was disabled, or its credentials were removed | Restore the template and credentials, then send the reply again |
FAQ
Will a reply I write in the Rozetka seller account show up in the ticket?
No. The app pulls in only buyer messages. To keep the conversation complete and have your reply count toward the deadline, reply from the ticket.
Will messages be marked as read in the marketplace's seller account?
No, the check changes nothing in the seller account. You see the same unread messages as before.
Does the app pull in questions about Rozetka products?
No, only order chats come from Rozetka. Questions and reviews about Rozetka products are in the “Reviews, comments” window: How to review and publish product reviews.
Does AI reply to marketplace buyers on its own?
No. The bot doesn't reply in these conversations; the ticket waits for a person right away. You can ask for an AI reply draft in the ticket, and an employee sends it.
What is the “Send order status to the marketplace” toggle in the same card?
It's about orders, not tickets: when you change the status of a Rozetka, Prom, Epicentr, EVA or Kasta order in Elbuz, the new status goes to the marketplace via status mapping. It's off by default.
Where it is and who has access
The “Autonomous support” window has no menu item of its own: you open it from the “Tickets” window.
- Other ways in
- “Tickets” → gear icon → “Autonomous support” → “Channels and proactive” tab
- Access right
- the “Autonomous support” window; the gear icon in “Tickets” is visible to the “Management” department
- Prepare
- an enabled Rozetka, Allegro or Prom import template with credentials
- Reply
- in the “Tickets” window, as with any other ticket
Related topics
- To see which other channels feed into tickets: How customer emails, chats and calls become tickets.
- If a buyer left a low-rated review on Rozetka: Low-rated reviews in tickets.
- To change the support schedule and reply deadlines: Working hours and reply deadlines (SLA).
- If AI should cancel marketplace orders or send statuses on its own: AI order actions.
