Skip to content
Hypamoon

For teams that run on Freshdesk

Freshdesk follow up business days, not hours

When you wait on a customer, you want a reminder after a few working days and a polite close after a few more. Freshdesk time triggers count in hours, so a Saturday counts the same as a Tuesday.

How it goes today

  1. Set the time trigger in hours and accept that weekends count.
  2. Pick longer waits so Monday reminders do not go out too early.
  3. Check the pending tickets by hand on Monday morning.
  4. Send the reminder and the closing message yourself.

How it can go

Nudge customers who go quiet, counted in your working days.

Each working morning the tickets waiting on the customer are checked against the business hours you set in Freshdesk and the holidays you list. After the number of working days you choose, the customer gets your reminder as a reply on the ticket. After a second wait without an answer, your closing message goes out and the ticket is set to resolved. A reply from the customer stops the count.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Freshdesk key in the portal, never in the chat.

Your request

With Hypamoon, every working morning, look at our Freshdesk tickets that are pending, waiting on the customer. Count working days since our last reply using our Freshdesk business hours and this list of holidays. After three working days, reply on the ticket with our reminder text. After three more without an answer from the customer, send our closing text and set the ticket to resolved.

Each Freshdesk agent finds a personal API key under Profile settings, and it sees what that agent may see. For some requests an admin also sets up a rule in Freshdesk that passes ticket updates on. It stays yours.