For teams that run on Zendesk
Zendesk marketplace messages as tickets
Sellers on marketplaces such as eBay, Mercado Libre, Allegro or Kaufland answer buyer questions inside each seller portal, often with a deadline that counts for their rating. Those messages are not in Zendesk, so they are answered in another place, by other people or late.
How it goes today
- Log in to each seller portal several times a day.
- Answer there, without the history from Zendesk.
- Forward some messages to the support inbox.
- Miss the response time when it is busy.
How it can go
Answer marketplace buyers from the same queue as everyone else.
New buyer messages from the marketplaces you connect become tickets, with the order and the marketplace in fields, and tickets near their response deadline go to the top. When an agent replies on the ticket, the reply is posted to the buyer on the marketplace.
Say this in ChatGPT, Claude or Copilot
Your chat gets connected to Hypamoon first, with this request filled in. You paste your Zendesk key in the portal, never in the chat.
With Hypamoon, turn new buyer messages from our marketplaces into Zendesk tickets, with the order and the marketplace in fields. Put tickets that are close to the response deadline at the top. When an agent replies on the ticket, send that reply to the buyer on the marketplace.
An administrator creates an OAuth client in Zendesk Admin Center, under Apps and integrations, APIs, OAuth clients, and limits what it may read and change. It stays yours.
More for teams on Zendesk
- I want a customer contact added as CC when a ticket matches a rule.
- Real emails end up in suspended and nobody looks in time.
- I want to see which macros are used and which are not.
- We only see the comment on a low rating if we open the ticket events.
- Customers want an overview of their company's tickets.
- I want to know what customers ask about, beyond how many tickets.
- I want help center articles as a PDF to print or send.
- A customer says thanks and the solved ticket is open again.
- When someone changes a trigger, I can't go back to how it was.
- I want the time we spent per client each month, so we can bill it.
- Tickets stay with an agent who is on leave.
- Every year I enter the holidays in each schedule again.
- I copy every order number into the shop to see what is going on.
- I want to send one message to a list of customers from Zendesk.
- I log in to each review site to read and answer reviews.
- Our contracts allow a number of tickets per month and nobody keeps count.
- We pay for agents who have not logged in for months.
- I want a message when a queue goes over a number.
- People without report access ask me for an export every week.
- I want a ticket to come back on the date I agreed with the customer.
- For every billing question I open another system to see what they pay.
- The same customer opens three tickets about one question.
- The same customer has two or three profiles in Zendesk.
- I look up every tracking number on the site of the carrier.
- We want NPS again and the score next to the customer in Zendesk.
- A customer asks for their data and I search ticket by ticket.
- Customers send ID numbers and we remove them by hand.
- I want to see which customers keep opening new tickets.
- The account details in our CRM do not reach Zendesk.
- IT hears about a new colleague when they are already at the door.
- I print tickets one by one to build a case file.
- I download attachments from each ticket to collect the documents.
- Everything for Zendesk