> ## Documentation Index
> Fetch the complete documentation index at: https://hopsdocs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Client request inbox

> Turn client emails into tracked requests with owners.

Client asks hide in long email threads and get missed. Hops reads them from your inbox, logs each request with an owner and a due date, and flags anything outside the SOW scope.

<Info>
  **How it runs:** Scheduled. An automation runs every weekday at 5:00 PM, posts new requests and saves them to the request table. You can also ask Hops any time.
</Info>

## What it does

* **Pulls every ask out of client emails.** Hops reads new threads from Gmail or Outlook and extracts each request, even when it is buried mid-thread.
* **Assigns an owner and a due date.** Owners come from the engagement team in Space context. Due dates come from the email, or a default you set.
* **Checks scope.** Each request is compared with the SOW pinned in the Space. Anything outside scope is flagged for the partner rather than logged as normal work.
* **Avoids duplicates.** A request that already has a row is updated, not added again.
* **Highlights what is due soon.** New requests due this week are listed first.

<Frame>
  <img src="https://mintcdn.com/hopsdocs/E03FYifT87c9QmFJ/images/use-cases/ps-client-requests.gif?s=badda0087b897c06c199805def8b1d94" alt="Gmail connection, Hops read 17 Acme threads in Gmail and logged new client requests" width="1440" height="810" data-path="images/use-cases/ps-client-requests.gif" />
</Frame>

## Ask Hops

Copy a prompt into any chat with Hops, or mention `@Hops` in a Space.

```text theme={null}
Log new requests from Acme's emails.
```

```text theme={null}
Which Acme requests are due this week, and who owns them?
```

```text theme={null}
Is the request in the latest Globex email inside the SOW scope?
```

```text theme={null}
List every open request from Northwind that has no owner.
```

```text theme={null}
Draft a reply to Acme confirming which requests we accepted and which need a change order.
```

Example reply:

> 5 new requests logged from 17 Acme threads:
>
> * 2 are due this week, owners Sam Cole and Priya Nair.
> * 1 is outside scope (a second market analysis); flagged for the partner.
> * Owners assigned for the rest.

## What you get

* **A daily post.** Every weekday at 5:00 PM Hops posts the new requests, what is due soon and what is out of scope to the Space chat.
* **An updated Table.** The request log lives in **Tables** in the Space, with one row per request: source email, owner, due date and scope status.
* **Answers on demand.** Ask in chat any time and get the answer in the same thread.

## Connections needed

Connect these apps. Each card opens Connections in the app.

<CardGroup cols={3}>
  <Card title="Gmail" icon="envelope" href="https://app.hops.ai/my-hops/connections">
    Client email threads (or Outlook).
  </Card>

  <Card title="Slack" icon="slack" href="https://app.hops.ai/my-hops/connections">
    Where the daily request post goes.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Connect your apps">
    Connect Gmail or Outlook, and Slack, in **Connections**.

    See [Connections](/docs/connections/overview).
  </Step>

  <Step title="Create the Space">
    Create a **client-acme** Space. Pin the SOW scope in Space context.

    See [Spaces](/docs/spaces/overview) and [Space context](/docs/spaces/space-context).
  </Step>

  <Step title="Add the skill">
    Give Hops these instructions:

    ```text theme={null}
    You log client requests. Pull every ask from client emails, assign an owner, set a due date and flag anything outside the SOW scope for the partner.
    ```

    See [Build a skill](/docs/agents/build-a-skill).
  </Step>

  <Step title="Schedule it">
    Run it every weekday at 5:00 PM. Hops posts new requests and updates the request table.

    See [Automation](/docs/spaces/automation).
  </Step>
</Steps>


## Related topics

- [Agencies & consulting](/teams/professional-services.md)
- [Client onboarding and kickoff](/teams/professional-services/use-cases/engagement-kickoff.md)
- [Client status and dashboard](/teams/professional-services/use-cases/client-status-report.md)
- [Client relationship pulse](/teams/professional-services/use-cases/client-relationships.md)
- [Client feedback to tasks](/teams/professional-services/use-cases/feedback-to-tasks.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.