Elbuz sends a wholesale customer's tickets to their manager, puts top customers first and shows their invoices, orders and waybills alongside.
When you need this:
- A customer expects “their” manager — emails, chats and calls go to that manager.
- The manager is on vacation — an unanswered ticket goes to a colleague on shift.
- A buyer, accountant and warehouse clerk write from one customer — Elbuz sees one company.
- The answer depends on the warehouse or accounting — call in a colleague with a note the customer can't see.
Where to start: add customer contacts to their cards, then enable “First — to the customer's account manager”.
What wholesale support can do
- Recognizes the company by any email address or phone number in its card.
- Sends tickets to the account manager, or to a colleague on shift when the manager is away.
- Puts VIP customers first — “High” priority and a shorter deadline.
- Counts deadlines by your business hours, with separate time for claims.
- Limits visibility — a manager sees their own customers and unassigned tickets.
- Brings the warehouse and accounting into a ticket with a note or an email.
- Follows your rules — a tag, a note, a different assignee for a key account.
How to make Elbuz recognize the customer
The account manager, VIP, documents in the right panel and customer-based flows only work when the ticket knows the contact. A ticket recognizes the contact by the sender's email address or phone number.
- An email is matched against the “Email”, “Email #2” and “Email #3” fields of the card.
- A call or chat is also matched against the “Phone”, “Phone #1” and “Phone #2” fields.
- Contact details that appear in two cards can link to the wrong card or to none: keep each email or phone in one card only.
Add the email addresses and phone numbers of everyone who writes on behalf of a key customer to that customer's card. You can link a ticket without a customer in the right panel by searching, but the address isn't added to the card. Learn more: how to link a customer.
Different people write on behalf of a company, and with the “One customer — one open ticket” checkbox (selected by default) everything goes into one open ticket. If your managers handle invoices and shipments separately, clear the checkbox. Learn more: one ticket per customer.
How to send a customer's tickets to their manager
Turn on “First — to the customer's account manager” on the “Assignment” tab. A new ticket from a customer with an assigned manager goes straight to that manager — whatever distribution option you use, and even above the limit. Tickets from customers without a manager follow the usual distribution.
It goes to someone else if Elbuz didn't recognize the customer, the manager can't open the “Tickets” window, or isn't on shift while “Only to people on shift (online in chats)” is on. New customers get an account manager automatically: whoever answered the call, and for chats and email — the least loaded sales manager.
Manager on vacation. With “Only to people on shift”, tickets of a manager who isn't online in chats go to a department colleague. A new ticket the manager left unanswered moves to whoever is on shift. Without it, the ticket waits for the manager until handed over manually. Learn more: how to avoid assigning tickets to people who have left.
How to let your largest customers skip the queue
The “VIP customers — High priority” checkbox is selected by default. A customer that Elbuz classified as VIP based on their orders gets tickets with at least “High” priority and the vip tag. A VIP is a regular customer whose total purchases are at least twice the company average; the segment is calculated automatically.
Together with an assigned manager, this gives a simple rule: a large customer's ticket goes to “their” manager and sits above small requests in that manager's queue. Learn more: VIP without the queue.
What deadlines to set for a wholesale company
Wholesale needs a fast first reply but more time to resolve: an invoice waits for accounting, a shipment for the warehouse, a claim for the batch to be checked. The default resolution targets are designed for retail. For business hours Mon–Fri 09:00–18:00 (540 business minutes a day), we suggest:
| Priority | First reply | Next reply | Resolution | What goes here |
|---|---|---|---|---|
| Urgent | 30 | 60 | 540 (1 day) | a failed shipment; set manually or by a flow |
| High | 60 | 120 | 1620 (3 days) | VIP customer, missed call, wholesale request |
| Normal | 240 | 480 | 2700 (5 days) | invoices, documents, stock questions |
| Low | 480 | 960 | 5400 (10 days) | claims, reconciliations |
While you wait for payment or the customer's reply, set “Pending”: the resolution clock stops. While you wait for the warehouse, set “On hold”: the ticket stays in your queue and the clock keeps running. Learn more: support desk SLA.
Who sees tickets
Visibility is set by the department's “Data scope” — the same switch that limits contacts and documents. For tickets, it works by the ticket's assignee, not by the customer's account manager.
| Department's “Data scope” | What a manager sees |
|---|---|
| All | all tickets |
| Own and subordinates | their own, their subordinates' in the org structure, and unassigned ones |
| Own only | their own and unassigned ones |
While a ticket has no assignee, every manager sees it. As soon as one takes it, colleagues with “Own only” stop seeing it — both in the queue and in reports. A sales lead with “Own and subordinates” sees the tickets of managers below them in the org structure. Learn more: who sees tickets.
How to involve the warehouse and accounting
- A colleague who signs in to Elbuz — an internal note with
@login: they get a notification with an “Open” button. Their department needs access to the “Tickets” window and a “Data scope” that shows the manager's tickets. Learn more: how to bring in a colleague with a note. - Someone without an Elbuz sign-in — “⋯” → “Write to a supplier / warehouse”: the email goes from your mailbox, and a reply in the same thread arrives in the ticket. This suits a logistics company or an outsourced accountant. Learn more: how to ask a supplier or the warehouse.
The customer sees neither the notes nor this correspondence. A colleague's reply doesn't change the ticket's status or deadline: the manager writes the answer to the customer.
1
Internal note in the feed2
Internal note switch3
Hint with @username- An internal note with an @username mention of a warehouse colleague, visually distinct from customer messages.
- The “Internal note” switch turns the reply field into a note field.
- The hint says the customer will not see the note and that @username notifies a colleague.
What to leave to AI and what to people
The manager's AI assistant works right away: it reads the email, sets the reason (“Payment”, “Wholesale request”, “Complaint”) and writes a draft from the customer's data. The manager sends it. Learn more: AI reply draft.
Autonomous support is off by default. For a wholesale company, we recommend:
- Don't turn on money actions — returns, reshipments, compensation promo codes, canceling paid orders. A claim on a batch is handled by the manager.
- Canceling unpaid orders — only with a small “Order total up to, UAH”, so large orders stay with people. Learn more: how to limit what AI does on its own.
- “AI questions to staff” — AI asks the warehouse about stock and lead times and tells the customer when to expect an answer. Learn more: how AI asks an employee.
- Chat auto-replies — start in “Test” to see what AI would write. Learn more: chat auto-replies.
Which flows to add
A flow is a “when X happens, do Y” rule triggered by a ticket event. It changes the status, priority, assignee, department and tags and writes an internal note; it doesn't send anything to the customer. How to build a flow: flows on ticket events.
| Purpose | Condition | “Ticket: update” |
|---|---|---|
| Key account — to the team lead, with an explanation | ticket_event = created and contractor_id = card number | assignee, tag key-account, note with @login |
| Wholesale request from email — to sales | ticket_event = created and intent = wholesale_request | department 9, “High” priority |
| Claim resolved — check quality | ticket_event = status, status = solved, tags contain claim | tag quality-check, note to the team lead |
| A customer who hasn't bought for a long time wrote in | ticket_event = created and segment = sleeping | “High” priority, note asking the manager to offer terms |
The reason is known at creation only for emails with automatic AI email analysis turned on; for chats and calls it's still empty. A customer-based flow won't fire on an email from an address that isn't in the card.
Scenarios
The customer's accountant asks for an invoice
What the manager does. Opens the order in the right panel's “Recent documents”, creates an invoice from it and sends it as usual. Replies “Invoice sent” with “Send as” → “Pending”. Result. While the customer pays, the resolution clock stops; a reply reopens the ticket. An invoice can't be created from the ticket — only in the document.
1
Document number2
Next pipeline step3
Other tickets of the customer- Document number in “Recent documents” — a click opens the document.
- The “Next: …” button moves the document to the next pipeline stage.
- “Other tickets of the customer” — the customer's earlier and open tickets.
A buyer asks whether the batch ships today
What the manager does. Shipped — “Add tracking to reply” by the document. Packed, but the status is unchanged — “Next: …” by the document. Still being packed — a note to the warehouse and “On hold”. Result. The customer gets an answer in a minute without opening other windows. Shipping in batches: wholesale: request, quote, contract, shipment.
Claim: short delivery and defects in a batch
What the manager does. Takes the ticket, adds the claim tag, writes a note to the warehouse. For defects, clicks “Create a return for …” and keeps only defective items in the unposted document. Result. Claims form a separate queue by tag. A short delivery isn't a return — it's a follow-up delivery or a document correction.
A key account's manager is on vacation
What to set up. “First — to the customer's account manager” and “Only to people on shift (online in chats)”. Result. While the manager isn't online, their customers' tickets go to a colleague from the department, and once the manager is back — to them again.
FAQ
Why did an email from a customer arrive without the customer, although the card exists?
The sender's address isn't in any of the card's three email fields. Link the ticket in the right panel and add the address to the card so future emails are recognized automatically.
A manager doesn't see their customer's tickets. Why?
Another employee took the ticket, and the manager's department has “Data scope” set to “Own only” or “Own and subordinates”. Tickets are visible by assignee, not by the customer's account manager.
How can an accountant reply without getting access to all of support?
There's no separate “mentions only” permission. Email the accountant via “Write to a supplier / warehouse”: their reply arrives in the ticket, and they don't need access.
A macro shows ТОВ (LLC) instead of the customer's name. What should I do?
The name variable takes the first word of the sender's name, or of the contact's name if the sender has none. For companies, write macros without addressing the customer by name.
Can I build a queue of one customer's tickets?
The queue has no customer filter. Tag the key account with a flow and build a queue by that tag, or search by the contact's name. Learn more: your own queues.
Can AI process a return for a wholesale customer on its own?
It can, if you turn on the “Return” action, but we don't recommend it for wholesale: a claim on a batch needs a warehouse check. Keep money actions turned off.
Where to find it and who has access
- Menu
- Directories → Contacts → Tickets; Organizer → Tickets
- Support settings
- window gear icon → “Support desk settings”
- Access right
- “Tickets” — “Management”, “Sales”, “Customer service”; settings and flows — “Management”
- Prepare
- customer cards with all email addresses and phone numbers, account managers, the org structure
Related topics
- For the big picture of Tickets — customer tickets: where to start.
- If you're setting up distribution between managers — ticket distribution.
- If a manager doesn't see other people's tickets but should — org structure.
- If you manage deals and ship in batches — wholesale: request, quote, contract, shipment.
