Skip to content
Hypamoon

For teams that run on Zendesk

Zendesk bulk email to many customers as tickets

Zendesk has no way of its own to send one message to a list of customers. For an outage, a recall or a change in terms, teams use a separate mail tool, where the replies do not end up in Zendesk, or they open tickets one by one.

How it goes today

  1. Export the list of customers from Zendesk.
  2. Send the message from a separate mail tool.
  3. Forward the replies into Zendesk by hand.
  4. Or open a ticket per customer, one at a time.

How it can go

Reach every affected customer at once and keep their replies in Zendesk.

You give a list, or a rule such as the customers of a product or a region, and the message. You see who will get it before anything goes out. After you approve, a ticket is opened for each person with your message, tagged so you can follow the replies in one view.

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.

Your request

With Hypamoon, open a Zendesk ticket for each customer on a list I give you, or that matches a rule I set, with my message as the first reply. Show me the list and the text before anything is sent. Tag the tickets so we can follow the replies together.

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