---
title: "Customer requests — Orygent"
description: "Own the incoming request, answer it and record the outcome."
source: https://www.orygent.com/en/use-cases/customer-requests
---

[Orygent](https://www.orygent.com/en/)[Use cases](https://www.orygent.com/en/use-cases) Customer requests

# Customer requests

Every customer request gets an owner and a due date. If the reply commits the company, it goes to approval first.

Updated: 2026-11-13

## What is the problem?

Requests are scattered across e-mail, calls and messages; nobody is sure who is on it.

## What does Orygent do?

Each request becomes work from one line or an incoming e-mail; its owner, status and reason for waiting are visible.

## Steps

### Record the request

  Who asked, for what, by when.

### Prepare the reply

  You can get a draft suggestion; you write the text.

### Approve and send the reply

  After approval if it commits the company.

### Write the outcome and close

  One sentence: what happened.

## Which step needs approval?

Any outside commitment in the company name needs approval.

[Start with this flow](https://app.orygent.com/)[Use cases](https://www.orygent.com/en/use-cases)