New
Heralder
Bulk proactive tickets: one personal ticket per customer from a CSV or Zendesk search, with undo.
호환:
Support
개발자
Great Work LLC
About this app
Tell many customers something at once, one personal ticket each, from inside Zendesk Support. A delayed shipment, a maintenance window, a recall, a renewal reminder: build the list, write the message once with merge fields, check the dry run, and Heralder creates one ticket per person. Replies come back to the same ticket, so your team handles them like any other conversation.
Zendesk's own Proactive Tickets app was retired on October 21, 2026, and Zendesk does not include bulk ticketing. Heralder is an independent replacement built by Great Work LLC; it is not made or endorsed by Zendesk.
Who gets a ticket
- A CSV file from your store, warehouse or billing system. Every column becomes a merge field, so
{{order_id}},{{tracking_url}}or{{renewal_date}}go straight into the message. - Zendesk users matching a search, members of organizations, or the requesters of tickets matching a search (everyone affected by an incident, once each).
People are skipped before anything is sent, each with a reason you can see: agents, suspended users, an opt-out tag, domains you exclude, people Heralder contacted in the last N days, duplicates, bad emails and blank merge fields with no fallback.
Write once, personal for everyone
- Merge fields with fallbacks (
{{first_name|there}}), user fields, organization name, bold and clickable links. Language versions picked by each person's locale.
Start from one of your macros, then set status, priority, type, group, assignee, brand, form, the support address it comes from, and tags.
Check everything before it goes out
- Dry run: how many tickets, who is skipped and why, how many batches, how long it takes, and the first tickets rendered exactly as Zendesk will receive them. Nothing is written.
- Delivery check: Heralder reads your active triggers and tells you which one will email these tickets, or warns you that none will (or that two will).
- Test ticket to any address, and a typed confirmation for anything over 50 recipients.
Sends safely, recovers cleanly
Batches of up to 100 at the pace you choose; Heralder slows down when your API budget runs low, so agents and other integrations keep working.
Pause, stop, and resume after a closed tab or a failed batch: Heralder reads the campaign back from Zendesk and sends only to people without a ticket yet, so there are no duplicates.
Per-row results: which rows failed and Zendesk's exact reason.
- Undo per batch: withdraw (solve, tag
heralder_withdrawn, internal note) or delete (restorable by an admin for 30 days). - Audit trail in Zendesk: each campaign keeps a log ticket with who sent what, when, to how many, every resume and every undo.
Plans (per Zendesk account, billed monthly by Zendesk)
Every feature is on every plan. Plans differ by campaign size and by how many agents send.
- Team, $120/month: up to 1,000 tickets per campaign, 5 senders.
- Professional, $199/month: up to 5,000 tickets per campaign, 10 senders.
- Enterprise, $349/month: up to 15,000 tickets per campaign, 20 senders.
Unlimited campaigns. 14-day trial; Zendesk asks for a card at install and billing starts when the trial ends unless you uninstall. "Senders" are agents who started a campaign in the last 30 days.
Your data
Heralder runs entirely in your browser inside Zendesk. There is no Great Work server, no account to create and no API token to paste. Every call is made as the signed-in agent, with their permissions. Your CSV is read in the browser and never uploaded anywhere except as the tickets you ask Zendesk to create. Heralder keeps no copy of your customers, tickets or files, does no background collection and sends nothing to Great Work or any third party. Details are in our privacy policy.
Support
Email hello@greatwork.company. We reply within one business day and help with your first campaign.
앱 세부 정보
설치 방법
Install Heralder from the Zendesk Marketplace and pick a plan. The 14-day trial starts now; Zendesk asks for a card and starts billing when the trial ends unless you uninstall.
- Under Role restrictions, limit the app to the people who will send campaigns (for example admins and team leads). Each plan counts senders: agents who started a campaign in the last 30 days.
- Optional settings: the opt-out tag (default
heralder_opt_out; users with this tag are never contacted) and the default send rate (tickets per minute, default 300). - Open Heralder from the left navigation bar (the megaphone icon) and choose New campaign.
- Email delivery: most accounts already email new agent-created tickets through the standard "Notify requester of new proactive ticket" trigger, and the review step confirms it. If yours does not, an admin opens a campaign's Ticket and delivery step, chooses "emailed by the Heralder trigger" and clicks Turn on the Heralder trigger once.
Send a test ticket to yourself (an address that is not your agent login), then send.
Heralder adds one inactive trigger at install ("Heralder: email the requester of a new campaign ticket") and removes it when you uninstall. Campaign tickets keep their heralder tags and each campaign's log ticket stays in Zendesk as your record.
리뷰 남기기
Zendesk 커뮤니티에 나의 경험을 공유해 보세요
플랜 및 가격
Team
Free 14-day trial, then $120.00 per month
Up to 1,000 tickets per campaign, 5 senders. Every feature: CSV and Zendesk audiences, merge fields, language versions, dry run, delivery check, test tickets, rate-limit-safe sending, resume, undo per batch, campaign log. Email support, reply within 1 business day.
무료 평가판Professional
Free 14-day trial, then $199.00 per month
Up to 5,000 tickets per campaign, 10 senders. Every feature, as in Team. Email support, reply within 1 business day.
무료 평가판Enterprise
Free 14-day trial, then $349.00 per month
Up to 15,000 tickets per campaign, 20 senders. Every feature, as in Team. Email support, reply within 1 business day.
무료 평가판