---
title: "The Best Simple Ticketing Systems for Small Teams (2026)"
description: "Compare 12 simple ticketing systems for small teams, from Gmail-based tools to free open source options, with prices and free-plan limits."
author: "Cody Duval"
url: https://www.keeping.com/content/simple-ticketing-system/
datePublished: 2025-01-18
dateModified: 2026-09-27
---

# The Best Simple Ticketing Systems for Small Teams (2026)

> **The short answer:** A simple ticketing system turns requests into tickets with an owner, a status, and a history. Gmail teams can add Keeping or Hiver to their inbox; teams wanting a separate app can use Help Scout, Freshdesk, or Zoho Desk. Teams with technical support can self-host osTicket, Zammad, FreeScout, or Request Tracker, with hosting and maintenance costs.

A simple ticketing system turns customer or employee requests into a shared queue with an owner, a status, and a conversation history. For a small team, the best choice usually comes down to three options: add ticketing to Gmail, use a separate help desk, or run open source software on your own server.

Start with where your team already answers requests. Keeping and [Hiver](https://www.keeping.com/hiver-alternative/) work inside Gmail; Help Scout, Freshdesk, and Zoho Desk provide a dedicated support workspace; osTicket, Zammad, FreeScout, and Request Tracker give technical teams more control through self-hosting.

We make Keeping, so it is included in this comparison. The recommendations below draw on vendor documentation and community discussions, rather than a hands-on test of every product. Prices and free-plan limits were checked in September 2026; screenshots are vendor-published examples, and may show features outside the entry plan.

## Is there a simple ticketing system that works inside Gmail?

Yes. Keeping is a simple ticketing system that works inside Gmail: email sent to a shared address such as support@ becomes a ticket your team can assign, track, and close from the Gmail inbox instead of a separate help desk app. Each conversation gets one owner, a status (Open, Pending, or Closed), and internal notes, and customers still get replies from the shared address. Hiver in Gmail takes a similar approach, and Google Groups Collaborative Inbox is the free, more manual option.

Here is how it works:

1. **Connect the shared mailbox.** Sign in with Google if support@ is its own Google Workspace or Gmail account, or use Gmail forwarding if it is a Google Group or an alias.
2. **Install the extension.** Each teammate adds the Chrome or Safari extension, and the shared mailbox’s conversations appear in their own Gmail.
3. **Assign and reply.** Pick an owner from the sidebar, leave a note for a teammate, and reply as usual. Collision detection shows when someone else is already working on the same email.
4. **Set the status as you send.** Send & close, Send & pending, or Send & open moves the ticket, so the open queue only shows work that still needs an answer.

Essentials costs $14 per user per month billed annually ($19 monthly), with a 2-user minimum and a 14-day free trial. See the [Gmail ticketing system](https://www.keeping.com/try/gmail-support-ticket-system/) page for the full workflow, or read on to compare it with separate and self-hosted help desks.

## What is a simple ticketing system?

A simple ticketing system records each support request as a ticket your team can assign, prioritize, answer, and close. It keeps the request, replies, and internal history together so another teammate can take over. The goal is to make outstanding work visible without making routine support harder to manage.

Look for these basic components:

- **Submission channel:** email, a web form, chat, or a manually recorded phone request. You only need the channels your team uses.
- **Unique identifier:** a ticket number or stable record that separates one request from another.
- **Status:** open, in progress, waiting, or resolved, with names that make sense to your team.
- **Priority:** a way to distinguish an urgent outage from a routine question.
- **Assignment:** one person responsible for the next action.
- **History:** previous replies, notes, and changes available to the next agent.

Our guide to [what a support ticket is](https://www.keeping.com/content/support-ticket/) explains the underlying record. A basic ticketing system adds a process around it: incoming work gets an owner, waiting work stays visible, and completed work leaves the active queue.

“Simple” should describe the work your agents do every day. During a trial, have a teammate answer, hand off, and reopen a request without coaching. Also check what the administrator must maintain: a clean agent screen can still hide a complicated setup.

## Simple ticketing systems at a glance

These 12 tools cover three common workflows. Annual prices below are monthly equivalents paid on an annual contract; monthly billing is identified separately. Setup effort describes the work involved, not a measured deployment time.

| Tool | Workspace / best fit | Free option | Starting price in USD | Setup effort |
| --- | --- | --- | --- | --- |
| Keeping | Gmail / shared email teams | 14-day trial | $14/user/month annually; minimum 2 | Connect mailbox and install extension |
| Hiver in Gmail | Gmail / email collaboration | 7-day trial | $25/user/month annually; minimum 2 | Connect Gmail and configure inboxes |
| Help Scout | Separate app / support conversations | 5 users; 100 contacts/month | $0; Standard $25/user/month, monthly | Connect inbox and invite teammates |
| Freshdesk | Separate app / portal and email support | 2 agents for 6 months | $19/agent/month annually after free program | Configure channels and ticket rules |
| Zoho Desk | Separate app / small support teams | 3 agents | $0; Express $7/user/month annually | Configure department and email |
| HubSpot | Separate app / CRM-linked tickets | Free tools for 2 users | $0 | Configure CRM records and pipeline |
| Jitbit | Separate app / focused ticket queue | Trial | $29/month, monthly, for 1 agent | Connect support email and categories |
| Desk365 | App plus Teams / Microsoft users | 50 tickets/month | $0; Standard $12/agent/month annually | Configure portal and Teams connection |
| osTicket | Self-hosted / traditional help desk | Open source | $0 license; hosting extra | Server, email, backups, and updates |
| Zammad | Self-hosted / configurable service desk | Open source | $0 license; hosting extra | Server and channel administration |
| FreeScout | Self-hosted / shared mailbox | Open source core | $0 core license; modules may cost extra | PHP hosting and mailbox configuration |
| Request Tracker | Self-hosted / custom request queues | Open source | $0 license; hosting extra | Server and workflow administration |

Pricing sources and limits appear in the relevant entries and the free-plan table below. Gmail labels and Google Groups are an additional starting point if you need a manual process before adopting one of these tools.

## If your team already works in Gmail

Choose an inbox-based tool when the people answering requests also spend their day in Gmail. The benefit is a familiar place to work, with ownership and status attached to shared conversations.

### 1\. Keeping: a simple help desk in Gmail

Keeping adds assignment, statuses, internal notes, templates, and collision detection to shared email in Gmail. Agents use a Chrome or Safari extension to handle conversations, while customers receive replies from the shared mailbox address.

![A customer email in Gmail with Keeping mailbox folders and assignment, priority, and status controls.](https://www.keeping.com/_astro/keeping.D_1XquFY_95l1T.webp)

*Source: [Keeping](https://www.keeping.com/).*

This fits teams whose main problem is “who is handling this?” You can give a billing question an owner, leave a note for a teammate, and keep the conversation pending while waiting for an answer. See how a [simple help desk in Gmail](https://www.keeping.com/features/simple-streamlined/) handles that workflow.

Essentials starts at **$19 per user per month with monthly billing, or $14 with annual billing**, with a 2-user minimum. It includes 2 mailboxes and supports up to 10 agents; the trial lasts 14 days and requires no credit card. These terms come from [Keeping’s pricing](https://www.keeping.com/pricing/).

The limitation: Keeping is built around shared email. If phone or social support is central to your operation, test a platform built for those channels. Teams specifically evaluating a [Gmail ticketing system](https://www.keeping.com/try/gmail-support-ticket-system/) can start with that narrower workflow.

### 2\. Hiver in Gmail

Hiver in Gmail also adds shared inbox management, assignment, and collaboration to Gmail through a Chrome extension. Make sure you evaluate this edition: Hiver Omni is a separate workspace.

![Hiver inside Gmail showing shared inbox folders, a billing email, assignee, status, tags, and internal notes.](https://www.keeping.com/_astro/hiver.sqs2lTO7_Zf4wtO.webp)

*Source: [Hiver in Gmail](https://hiverhq.com/hiver-in-gmail).*

[Growth costs $25 per user per month annually or $35 monthly](https://hiverhq.com/pricing/hiver-in-gmail), with a seven-day trial. Hiver starts at two seats, then grows to five and in increments of five after that. Those seat blocks are the main budgeting trade-off: calculate the bill for your actual headcount, not just the headline rate.

### The free option: Gmail labels and Google Groups

Labels such as “needs reply” and “waiting” can organize one person’s work. They become harder to coordinate when several people maintain separate inbox copies and cannot see a single shared owner.

Google Groups has a stronger baseline: its [Collaborative Inbox supports taking and assigning conversations](https://support.google.com/groups/answer/2467048?hl=en), plus completion tracking. The collaboration workflow lives in Google Groups; receiving group messages in Gmail does not reproduce all those controls there.

Start with our guide to [Google Groups for customer support](https://www.keeping.com/content/google-groups-collaborative-inbox/). If coordinating ownership across those surfaces becomes cumbersome, consider a [Google Groups alternative](https://www.keeping.com/solutions/google-groups/) or the other ways to [turn Gmail into a help desk](https://www.keeping.com/content/gmail-as-help-desk/).

For small businesses that want easy email ticket management in Gmail, Keeping gives each request an owner and a visible status. [Try Keeping free for 14 days](https://app.keeping.com/signup), with no credit card required.

## Simple help desk software that runs as its own app

A separate help desk makes sense when support needs its own workspace, customer portal, or CRM context. For a wider selection beyond this shortlist, compare the [best help desk software](https://www.keeping.com/content/best-help-desk-software/) by the channels and workflows you need.

### 3\. Help Scout

Help Scout organizes customer conversations in a dedicated shared inbox, with a knowledge base alongside it. It suits teams that want a conversation-focused workspace and are comfortable answering outside Gmail.

![Help Scout conversation view with a billing inquiry, reply controls, and customer details.](https://www.keeping.com/_astro/helpscout.DL7RmpNI_1op386.webp)

*Source: [Help Scout](https://www.helpscout.com/shared-inbox/).*

Its [Free plan includes five users, one inbox, and 100 contacts per month](https://www.helpscout.com/pricing/); Standard is $25 per user per month on monthly billing. That contact limit matters more than the generous user allowance: a small team can still serve many distinct customers. If the main requirement is keeping agents in Gmail, our [Help Scout comparison](https://www.keeping.com/helpscout-alternative/) explains that workflow difference.

### 4\. Freshdesk

Freshdesk combines ticket handling with a customer portal, knowledge base, and reporting. It is a useful shortlist option when you want customers to submit and follow requests through a dedicated support site.

![Freshdesk ticket details showing a customer conversation, ticket properties, and contact information.](https://www.keeping.com/_astro/freshdesk.CCEHf5iz_ZFOTW9.webp)

*Source: [Freshdesk ticket details documentation](https://support.freshdesk.com/support/solutions/articles/37588-understand-the-ticket-details-view).*

[Growth starts at $19 per agent per month annually](https://www.freshworks.com/freshdesk/pricing/). The [Free Program covers one or two agents for six months](https://support.freshdesk.com/support/solutions/articles/50000010099-explore-freshdesk-free-plan), so budget for the paid plan from the outset. There are more settings to decide on than a shared inbox alone; our [Freshdesk comparison](https://www.keeping.com/freshdesk-alternative/) is useful if those extra workflows feel too complex for your email queue.

### 5\. Zoho Desk

Zoho Desk is worth considering when you want conventional ticket management with a permanent free starting point. Its [free edition supports three agents](https://www.zoho.com/desk/pricing.html), while [Express starts at $7 per user per month annually](https://www.zoho.com/desk/express/).

![Zoho Desk billing ticket with customer information, ticket properties, and an actions menu.](https://www.keeping.com/_astro/zoho-desk.M2lhLt5S_ZD4bTP.webp)

*Source: [Zoho Desk ticket documentation](https://help.zoho.com/portal/en/kb/desk/ticket-management/actions-in-tickets/articles/user-actions-in-the-ticket-detail-page).*

The low starting price is attractive, but the plan must include your actual workflow. Check agent limits, automation, and reporting before choosing; our [Zoho Desk comparison](https://www.keeping.com/zoho-desk-alternative/) helps weigh a separate support app against working in Gmail.

### 6\. HubSpot Service Hub

HubSpot’s [free ticketing tools](https://www.hubspot.com/products/service/ticketing-system) connect requests with CRM contact records. That is particularly useful when the support conversation belongs alongside an existing sales or customer relationship.

![HubSpot ticket board with new, working, waiting, and closed columns and ticket owners.](https://www.keeping.com/_astro/hubspot.CZn72Zvv_2aEgXJ.webp)

*Source: [HubSpot ticketing](https://www.hubspot.com/products/service/ticketing-system).*

The current [free tools package supports up to two users](https://www.hubspot.com/pricing/crm?product=marketing). Do not assume free ticket records include every paid Service Hub workflow: confirm the plan needed for your routing, automation, and reporting. The trade-off is the wider CRM setup if all you wanted was a small email queue.

### 7\. Jitbit

Jitbit centers the agent’s work on a ticket list, conversation history, and automation rules. It offers both hosted and self-hosted editions, making it a candidate when you want a focused queue with deployment options.

![Jitbit ticket queue with assignees, statuses, priorities, and category filters.](https://www.keeping.com/_astro/jitbit.CUcV7iKK_ZkvTrf.webp)

*Source: [Jitbit](https://www.jitbit.com/helpdesk/).*

[Hosted pricing starts at $29 per month for one agent](https://www.jitbit.com/saas-helpdesk/purchase/) on monthly billing; the four-agent Startup plan is $69 per month. A trial is available. The entry rate is for a single agent, so a team should compare the whole plan price with per-agent competitors rather than treating $29 as a team-wide rate.

### 8\. Desk365

Desk365 is an independent help desk with Microsoft Teams integration, suited to teams receiving employee requests there. It also provides a web workspace, so evaluate the agent experience as well as the requester’s Teams experience.

![Desk365 Support Bot inside Microsoft Teams with Create Ticket and Check Status controls.](https://www.keeping.com/_astro/desk365.CmqG3HPI_1eoGnO.webp)

*Source: [Desk365](https://www.desk365.io/).*

[Standard starts at $12 per agent per month annually](https://www.desk365.io/pricing/), and a free plan allows 50 tickets per month. That is useful for a light queue, but it can be a small allowance even for one busy technician. Desk365 is a third-party product; it is not a ticketing feature included automatically with Microsoft Teams. Microsoft’s own [Lists Issue tracker template](https://support.microsoft.com/en-us/sharepoint/lists/data-and-lists/list-templates-in-microsoft-365) is a separate, manual starting point.

## Simple open source and self-hosted ticketing systems

An open source ticketing system lets you run and modify the software without buying a proprietary license for its core edition. Self-hosting gives you control over deployment, but your team takes responsibility for updates, backups, uptime, and email delivery. A free license therefore does not mean a cost-free service.

### 9\. osTicket

osTicket is our pick for the best simple open source ticketing system for teams wanting traditional ticket queues. It is a free, self-hosted solution offering email-to-ticket conversion and basic workflow management.

![osTicket support queue with ticket numbers, priorities, assignees, and departments.](https://www.keeping.com/_astro/osticket.C0ElOStU_ZEF9qW.webp)

*Source: [osTicket features](https://osticket.com/features/).*

Its [documented features](https://osticket.com/features/) include ticket filters, assignment, custom queues, and collision avoidance. It suits a small IT department that has someone to maintain the installation. The interface is more traditional than many newer help desks, so ask the people handling tickets to try the daily workflow before committing.

### 10\. Zammad

Zammad offers an open source service desk with ticket ownership, priorities, conversation history, and internal notes. Its [ticket workflow](https://user-docs.zammad.org/en/latest/basics/work-with-tickets.html) also shows when other agents are viewing or editing the same ticket.

![Zammad ticket detail view with conversation history, owner, priority, state, and internal note editor.](https://www.keeping.com/_astro/zammad.SviDAx3H_pR8rs.webp)

*Source: [Zammad UI documentation](https://user-docs.zammad.org/en/latest/basics/zammad-ui.html).*

The [self-hosted software is free](https://zammad.org/); hosting and administration are your responsibility. Choose it when you want room to configure a service desk and can support the installation. The trade-off is the operational work behind that flexibility: plan the upgrade and recovery process before routing customer email into it.

### 11\. FreeScout

FreeScout is a shared mailbox application built with PHP, with assignment, internal notes, and conversation history. Its [open source core supports unlimited agents and mailboxes](https://github.com/freescout-help-desk/freescout), making it appealing to technically capable teams that prefer a mailbox-style interface.

![FreeScout conversation with an assigned agent, active status, customer information, and mailbox folders.](https://www.keeping.com/_astro/freescout.D97SYv8q_Z1TdFmw.webp)

*Source: [FreeScout project screenshots](https://github.com/freescout-help-desk/freescout#screenshots).*

The core license is free, while optional modules can add cost. Check the modules required for your workflow before comparing it with a hosted subscription, and include the time needed to maintain the server and email connection.

### 12\. Request Tracker

[Request Tracker](https://requesttracker.com/request-tracker/) organizes requests into queues with ownership, status, and configurable workflows. Its open source edition fits teams that need to adapt ticket handling to an established process.

![Request Tracker RT 5 dashboard showing owned and unowned tickets, priorities, and queues.](https://www.keeping.com/_astro/request-tracker.BiU3bdUY_11Xk12.webp)

*Source: [Request Tracker](https://requesttracker.com/request-tracker/).*

The software license is free; hosting, implementation, and support are separate considerations. Its flexibility is also the reason to be selective: a team needing only “assign, reply, close” may have little use for extensive configuration. The vendor screenshot shows its RT 5 interface; assess the current release in your own trial.

GLPI and Peppermint are additional open source projects to investigate if this deployment model is a requirement. Keep the shortlist manageable: compare two candidates against the same real request instead of installing every option.

### Hosted help desk vs self-hosted help desk

With hosted help desk software, the vendor runs the application infrastructure and ships updates. Your team still configures access, routing, and the support process. With a self-hosted help desk, you also own the server, security patches, backups, and recovery plan.

Ask who will restore service when email stops becoming tickets. If nobody owns that job, a modest hosted subscription can be simpler than a free installation. If you already have the skills and need deployment control, self-hosting can be a reasonable choice.

## What is a simple IT ticketing system?

A simple IT ticketing system gives employee requests a queue, an owner, a priority, and a resolution history. Start with those requirements, then add asset tracking or approval workflows only when the team actually needs them.

An employee asking for printer access should be able to submit the request without learning your internal categories. The technician needs enough context to act, a way to ask a follow-up question, and a visible waiting state.

Jitbit and osTicket above are candidates for this workflow. Other IT-focused products to investigate include Spiceworks, Jira Service Management, and BOSSDesk; compare their current editions and administration needs before adding them to your shortlist. These are additional research leads, not part of the 12-tool comparison.

If employees already email an IT mailbox and agents work in Gmail, [Keeping for IT and tech support](https://www.keeping.com/solutions/it-tech-support/) can add ownership to that existing process. For asset inventories, change approvals, or a broader service catalog, evaluate a dedicated IT service management product.

## What is the best ticketing system for small businesses?

The best ticketing system for a small business is the one that matches its request channels, staffing, and budget. Choose a Gmail-based tool for shared email, a standalone help desk for a dedicated support workspace, or self-hosted software when deployment control justifies the maintenance. Test the same requests in your finalists.

Use three questions to narrow the choice:

1. **Where do requests arrive?** If almost everything comes through support@, an [email ticketing system](https://www.keeping.com/content/email-ticketing-system/) may cover the job. A mix of email, chat, and phone needs a different evaluation.
2. **Who answers them?** Dedicated support agents can settle into a separate workspace. People who handle requests between operations, finance, or office duties may prefer their existing inbox.
3. **What does the budget include?** Count required seats, channel add-ons, usage caps, and administration. A free plan that cannot handle your normal month is a trial in practice.

Then run a small workflow test. Submit a request, assign it, add an internal note, hand it to someone else, wait for a reply, and close it. Reopen it with a follow-up email and check that the history survives.

Your must-have checklist should include email-to-ticket capture, assignment, clear statuses, searchable history, and basic reporting. Add collision detection when multiple agents work the same queue, and simple automation when a repeated routing decision is easy to define.

Agree on what “waiting” means and who reviews unassigned work. These [help desk best practices](https://www.keeping.com/content/help-desk-best-practices/) matter regardless of the tool: software cannot rescue a queue that nobody owns.

## How much does a simple, low-cost ticketing system cost?

The options here range from free capped plans and open source licenses to paid subscriptions. Compare the total for the team: 2 Keeping Essentials users cost $38 per month on monthly billing, or $28 per month equivalent billed annually. A self-hosted product adds hosting and staff time even when the license costs nothing.

Free-plan limits checked in September 2026:

| Product | Free allowance | What to budget for |
| --- | --- | --- |
| [Freshdesk](https://support.freshdesk.com/support/solutions/articles/50000010099-explore-freshdesk-free-plan) | Up to 2 agents for 6 months | Paid subscription after the program |
| [Zoho Desk](https://www.zoho.com/desk/pricing.html) | Up to 3 agents | More agents or required paid features |
| [Help Scout](https://www.helpscout.com/pricing/) | 5 users, 1 inbox, 100 contacts/month | Contact volume and plan features |
| [HubSpot](https://www.hubspot.com/pricing/crm?product=marketing) | Free tools for up to 2 users | Additional seats and paid service workflows |
| [Desk365](https://www.desk365.io/pricing/) | 50 tickets/month | Higher ticket volume; confirm user allowance |

A contact cap and a ticket cap measure different things. Help Scout counts a person receiving a reply or an AI resolution as a contact; multiple conversations with that person count once in the month. Model your own workload before calling one free plan more generous.

For a cheap ticketing system, prioritize the least expensive plan that covers a normal busy month. Check [Keeping’s current plans](https://www.keeping.com/pricing/) and each vendor’s billing terms before purchasing an annual subscription.

## What Reddit recommends

Reddit discussions are useful for finding practical objections and products to test. They are not a representative customer survey, and older comments are a poor source for current pricing.

These threads ask concrete questions that help sharpen a shortlist:

- [Recommendations for a very simple ticketing system](https://www.reddit.com/r/sysadmin/comments/89ql98/need_recommendation_for_very_simple_ticketing/).
- [Jitbit vs Freshdesk vs osTicket](https://www.reddit.com/r/sysadmin/comments/sz4iaq/jitbit_vs_freshdesk_vs_osticket/).
- [Help desk software where users only use email](https://www.reddit.com/r/sysadmin/comments/1c4ny7s/help_desk_software_where_users_only_use_email/).
- [A family-friendly simple ticketing system](https://www.reddit.com/r/selfhosted/comments/1856y1q/is_there_any_family_friendly_simple_ticketing/).

Read for the context behind a recommendation: team size, hosting skills, request channels, and time spent administering the system. Someone running a home server and someone answering a shared business mailbox can reasonably choose different tools.

## Frequently asked questions about simple ticketing systems

### Is there a free ticketing system available?

Yes. Zoho Desk and Help Scout offer capped free plans, while osTicket and FreeScout offer free open source software. Freshdesk limits its Free Program to two agents for six months. Check user and usage limits, and remember that self-hosted software still requires hosting, backups, and maintenance.

### What are the top 5 ticketing systems?

Five useful starting points are Keeping for Gmail, Help Scout for a separate shared inbox, Freshdesk for a support portal, Zoho Desk for a small free team, and osTicket for self-hosting. This is a shortlist by workflow, not a universal ranking.

### What is the easiest ticketing system to use?

The easiest option is usually the one that fits how your team already handles requests. For Gmail teams, Keeping adds assignment and status in a familiar inbox; test a real handoff before choosing any tool.

### How do I create my own ticketing system?

You can connect a request form to a spreadsheet and add columns for owner, status, priority, and follow-up date. Our [Google Workspace ticketing system](https://www.keeping.com/content/google-ticketing-tool/) guide covers the Forms and Sheets approach, including the coordination work you must handle yourself.

### Does Microsoft offer a ticketing system?

Microsoft offers an Issue tracker template in Microsoft Lists for tracking issues, priorities, and progress. It is a starting point for a manual process; automatic email intake and help desk workflows require additional configuration or software.

### What is the best self-hosted help desk software?

Choose osTicket for traditional ticket queues, FreeScout for a shared mailbox, Zammad for a configurable service desk, or Request Tracker for custom request workflows. The best fit also depends on which installation your team can maintain.

### Can Gmail/Outlook become an email ticketing system with statuses (open/pending/closed) without moving tools?

Yes, compatible add-ons can add ticket ownership and statuses to an existing email interface. Keeping supports Gmail; see how to [turn Gmail into a help desk](https://www.keeping.com/content/gmail-as-help-desk/), and evaluate Outlook-specific tools separately.

## Give your shared email a clear owner

If your team works in Gmail, Keeping can give shared email an owner, a status, and a clear next action. [Start a 14-day free trial](https://app.keeping.com/signup), with no credit card required, or explore the [simple Gmail help desk workflow](https://www.keeping.com/features/simple-streamlined/).