Freshworks · Freshservice and Freshdesk
Renewal Tickets
Opens a Freshservice or Freshdesk ticket 90, 60 and 30 days before a contract ends.
- Works with Freshservice and Freshdesk
- Marketplace Freshworks Marketplace
Coming soon
Under review by Freshworks Marketplace
Renewal Tickets was resubmitted to the Freshworks Marketplace after the requested changes and is under review again. It has not been approved or listed, and cannot be installed by the public today.
Coming soon toFreshworks Marketplace
What it does
Renewal Tickets is an application for Freshservice and Freshdesk that turns end dates into work in your own queue. In Freshservice it reads your contracts and creates an Incident or a Change before each one ends. In Freshdesk it watches the company Renewal date, or any company or contact date field you choose, and creates a ticket ahead of it. A dry-run preview shows exactly what would be created, a daily scan does the rest, and a record never gets two tickets for the same threshold and date.
Capabilities
Freshservice contracts
Reads the contracts of all workspaces and filters them by contract type, vendor, status and auto-renew. Contracts that already have an approved renewal are skipped. It creates an Incident, or a Change with impact, risk, change type and a planned start a set number of days before the end date; for a Change, the contract's assets are listed in the description and attached where Freshservice accepts them.
Freshdesk renewal dates
Up to five date fields: the built-in company Renewal date, or your own company and contact date fields. Each can repeat every year, so an anniversary date opens a ticket again the following year.
One ticket per record, threshold and date
Thresholds default to 90, 60 and 30 days and can be any whole number of days from 1 to 730. Only the closest threshold already reached is due, so an app installed 20 days before an end date opens one ticket, not three. Every ticket is recorded before it is created, so running the scan again never creates a duplicate.
Safe to start
The application is switched off after installation. A dry-run preview lists every ticket it would create, with the subject filled in, and creates nothing. Run now asks you to type CREATE. While the application is switched on, a daily scan creates the due tickets, and a CSV run log lists record IDs, thresholds, dates, ticket numbers and result codes.
Questions
Where does Renewal Tickets run?
The application runs inside Freshservice or Freshdesk on the Freshworks Developer Platform: its admin page runs in your browser, and its scans run on Freshworks-hosted serverless infrastructure. Atesen Software does not operate a server or a database for it.
How do I get help with Renewal Tickets?
Support for Renewal Tickets is provided by email in English and Turkish.
Email support@atesensoftware.com. We aim to acknowledge every support email within two business days (Europe/Istanbul).
What we do not claim
- It has been submitted to Freshworks Marketplace and requires changes before approval. It is not approved, listed or publicly installable. Public installation, customer and review counts are not verified.
- It does not renew, extend or create contracts, and it does not email your customers. It creates tickets and changes in your own account; your own Freshdesk or Freshservice notification settings decide who is emailed about them.
- Attaching a contract's assets to a Change depends on what the Freshservice API accepts in your account. When it refuses them, the change is created without the attachment and the assets stay listed in its description.
- It is not affiliated with or endorsed by Freshworks.
- It holds no security certification and has not undergone a third-party audit.
Marketplace
Freshworks Marketplace: Resubmitted to the Freshworks Marketplace and under review; not listed and not installable by the public.
Coming soon toFreshworks Marketplace