Freshservice Work Next icon

Freshservice Work Next

Freshservice app

Freshservice Work Next

Installation and configuration guidance for Freshservice administrators and agents.

Coming soonIn Marketplace review

Installation availability

Work Next 0.5.1 is in Freshworks Marketplace review and is not yet available for public installation. This guide explains the submitted version so administrators can prepare. The Marketplace link will be added when the public listing is available.

Before you install

  • Use an authorised Freshservice administrator account to install and configure the app.
  • Find your Freshworks organisation domain in Freshworks Admin Center. This is different from your Freshservice account URL.
  • Confirm the native Freshservice status IDs and what they mean for your team. Work Next does not preselect or guess mappings.
  • Review the three read-only permissions, Privacy Notice and Terms.

Install and connect

  1. When the public listing is available, open Work Next for Freshservice by PezTech Software in Freshworks Marketplace. Check the listing's current price and evaluation terms, then follow Freshworks' installation prompts.
  2. When the connection asks for Freshworks organisation domain, enter only the organisation hostname, such as yourcompany.myfreshworks.com or yourcompany.freshworks.com. Do not include https://, spaces, a path or your yourcompany.freshservice.com account URL.
  3. Complete the Freshworks OAuth sign-in and consent flow for the intended organisation. The submitted app requests ticket, ticket-conversation and workspace read access. It does not require your Freshservice API key or a customer-created OAuth client.
  4. Complete the administrator configuration below and use Check settings. Finish the save or installation action provided by Freshworks.
  5. Open Work Next from Freshservice's Apps area as an agent, then select Refresh. Work Next evaluates that signed-in agent's assigned tickets.

If you are unsure which organisation hostname to use, ask your Freshworks administrator to confirm it in Admin Center. Do not guess from the Freshservice account address.

Configuration overview

An authorised Freshservice administrator manages Work Next through the app's installation settings. New installations do not guess status mappings. Follow-up recommendations start disabled, and the default Stale threshold is three calendar days.

  1. Confirm each native Freshservice status ID and its meaning in your installation.
  2. Map each status to one Work Next class.
  3. Choose whether requester or third-party follow-up recommendations are enabled and set their thresholds.
  4. Confirm the Stale threshold, validate the form and save through Freshservice.
  5. Open Work Next and refresh to evaluate the signed-in agent's assigned tickets.

Status mapping

Actionable

Open work that can enter the ranked queue and relevant Smart Views.

Waiting on requester

Work waiting for the requester; eligible for an optional closure-review recommendation.

Waiting on third party

Work waiting on an external party; eligible for an optional chase recommendation.

Other blocked/waiting

Visible in Waiting / Blocked but never promoted by a follow-up rule.

Resolved/closed

Excluded from the operational Work Next view.

Enter comma-separated positive status IDs in the matching settings fields. At least one Actionable status is required. Each ID can belong to only one group; multiple IDs can share a group. Do not copy another organisation’s IDs without checking them.

Unmapped statuses are excluded and shown as requiring administrator mapping. Work Next does not infer meaning from a label such as “Pending”, and status IDs must be confirmed for the actual Freshservice installation.

Waiting follow-up settings

Requester and third-party rules are configured separately. The settings form accepts whole calendar days from 1 to 3650. An enabled rule also requires a single-line plain-text label of 1–60 characters. Follow-ups start disabled for new installations; the suggested three-day value does not enable a rule. Calendar time includes weekends.

Changing a threshold applies to existing observed waiting periods, so some follow-ups may become due immediately. Changing only the label or threshold does not reset an observation. A newly observed waiting status or class starts a new period.

Observation wording

Work Next uses wording such as First observed waiting on requester 4d 3h ago. This is based on Work Next observations, not complete Freshservice status history. An exit and re-entry between checks may be missed.

Stale threshold

Stale is one installation-wide threshold in whole calendar days from 1 to 3650, defaulting to three days. It affects only actionable tickets and uses current attention age—not ticket update time, waiting age or Freshservice business hours.

Settings validation

  • Status IDs must be unique positive integers with a recognised Work Next class.
  • A blank initial mapping must be completed before ranking can begin.
  • Enabled follow-up rules require the corresponding waiting mapping, a valid threshold and a label of 1–60 single-line characters.
  • Zero, negative, fractional, missing or overflowing enabled thresholds are rejected.
  • Invalid settings do not silently turn tickets into actionable work.
  • Existing legacy settings remain readable until an administrator makes an explicit migration choice.

Your first use

  1. Open Work Next using the agent account whose assigned work you want to review. Check the last refresh time and any partial, stale or mapping warning.
  2. Start with All work. Read the reason beside a ranked ticket, together with its priority, active SLA and conversation information.
  3. Try SLA At Risk, Customer Replied, Unanswered, Stale and Waiting / Blocked. Empty views can be valid. Switching Smart Views uses the same evaluated workload and does not make another ticket-list request.
  4. Open a row to continue in the native Freshservice ticket. Work Next does not reply, assign, change a status or send a reminder.
  5. Return and select Refresh when you need current source data. A complete empty queue is different from an incomplete result: check the displayed status before concluding that no work is waiting.

Change settings later

An authorised administrator can reopen the installed app's settings through Freshservice. Use Check settings, then save through Freshworks. Reopen Work Next and refresh to apply the configuration. If a legacy-configuration review is shown, read every mapping and threshold before deliberately choosing migration; simply opening the page does not migrate settings.

Marketplace reviewer overview

Use an authorised non-production Freshservice review account. Complete deliberate status mappings, assign suitable test tickets to the reviewer, inspect ranking reasons, switch each Smart View, open a row in native Freshservice, return and refresh. Empty views are valid and do not prove populated-state behaviour.

Do not include credentials, private packages, customer data or internal engineering evidence in review notes hosted on this site.

Getting help

See Work Next support and troubleshooting. Do not email passwords, OAuth tokens, private conversation history, full API responses or unredacted diagnostic exports.