# What is Keeping?

**Keeping** is a customer support tool that works on top of Gmail.  After you install Keeping's [Chrome Extension](https://chrome.google.com/webstore/detail/keeping-the-original-help/mhmcjokmjcnjmlmmbaopcgkbomfdlpcn) or [Safari Extension](https://apps.apple.com/us/app/keeping-for-safari/id1666996817), you can assign, track, and prioritize customer support email right inside your Gmail inbox.

Keeping is **built for teams that do more than just customer support**. It comes with everything you need to get a handle on your shared inbox without all the clutter and confusion of a tool like Zendesk.

Our mission is to make customer support **fast and simple**, right inside Gmail.  Because who wants another inbox to manage?

## A Quick Overview

**Got 3 minutes?** Check out a video overview of Keeping.

{% embed url="<https://katsuventures.wistia.com/medias/u6qqgu3nef?embedType=iframe&videoFoam=true&videoWidth=640>" %}

{% hint style="info" %}
**Good to know:** Keeping requires that you have a Google Workspace, Gmail, or GSuite account and our Gmail integration works exclusively with Safari or Chrome browsers.
{% endhint %}

## How Keeping Works

When you connect a shared mailbox to Keeping, every message sent by your customers is sync'ed to the work or personal Gmail of your team members. And when a team member replies, that message is sent via your shared inbox back to your customer and it is also sync'ed with the entire team.  This keeps everyone in the loop without messy cc:s or forwarding around email.

Of course, every Keeping ticket can be assigned, prioritized, or discussed right inside Gmail.  All of Keeping's features are meant to be **powerful & simple** so you can stay on top of your shared mailbox.

### Guides: Jump right in

Follow our handy guides to get started on the basics as quickly as possible:

{% content-ref url="getting-started/quick-start-for-admins" %}
[quick-start-for-admins](https://docs.keeping.com/help/getting-started/quick-start-for-admins)
{% endcontent-ref %}

{% content-ref url="getting-started/quick-start-for-agents" %}
[quick-start-for-agents](https://docs.keeping.com/help/getting-started/quick-start-for-agents)
{% endcontent-ref %}

{% content-ref url="getting-started/using-keeping-in-gmail" %}
[using-keeping-in-gmail](https://docs.keeping.com/help/getting-started/using-keeping-in-gmail)
{% endcontent-ref %}

### Fundamentals: Dive a little deeper

Learn the fundamentals of Keeping to get a deeper understanding of our main features:

{% content-ref url="fundamentals/mobile-and-web-access" %}
[mobile-and-web-access](https://docs.keeping.com/help/fundamentals/mobile-and-web-access)
{% endcontent-ref %}

{% content-ref url="fundamentals/assigning-a-ticket" %}
[assigning-a-ticket](https://docs.keeping.com/help/fundamentals/assigning-a-ticket)
{% endcontent-ref %}

{% content-ref url="fundamentals/using-templates" %}
[using-templates](https://docs.keeping.com/help/fundamentals/using-templates)
{% endcontent-ref %}

{% content-ref url="fundamentals/changing-ticket-status" %}
[changing-ticket-status](https://docs.keeping.com/help/fundamentals/changing-ticket-status)
{% endcontent-ref %}

{% hint style="info" %}
**Good to know:** Splitting your product into fundamental concepts, objects, or areas can be a great way to let readers deep dive into the concepts that matter most to them. Combine guides with this approach to 'fundamentals' and you're well on your way to great documentation!
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.keeping.com/help/what-is-keeping.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.