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

# Customer Feedback

> Collecting post-purchase feedback against a receipt, and reading the reports.

Customer Feedback captures what a customer thought of a shopping trip. Every entry is tied to a **receipt**, which is what links the rating back to a store, a chain and a moment in time.

## What an entry contains

| Part               | Detail                                                                               |
| ------------------ | ------------------------------------------------------------------------------------ |
| Rating             | A score from 1 to 10.                                                                |
| Predefined options | Structured choices configured per chain, so responses stay comparable across stores. |
| Message            | Free-text comment for detail the options cannot capture.                             |
| Store and chain    | Resolved automatically — see below.                                                  |

<Info>
  You can identify a store either **by ID or by name**, and the service resolves the chain for you. That matters when feedback arrives from a channel that only knows the store's display name.
</Info>

## Lifecycle

```mermaid theme={"system"}
flowchart LR
    C["Created"] --> E["Store and chain<br/>resolved"]
    E --> M["Updated<br/>optional"]
    M --> F["Completed"]
    E --> F
    F --> R["Available in reports"]
```

Feedback is a draft until it is completed. A customer can create an entry, change their mind, and finalise it later; only completed feedback is meaningful for analysis. Entries can also be deleted where a customer or a support process requires it.

Use the feedback **state** (`Open` or `Closed`) when you need to know whether an entry is still editable without pulling the whole record.

## Reporting

Two report shapes are available, and the service picks the granularity from the period you request.

| Report    | Contains                                 | Use it for                                          |
| --------- | ---------------------------------------- | --------------------------------------------------- |
| Daily     | Transaction-level rows for a date range. | Investigating specific visits, feeding a warehouse. |
| Aggregate | Averages and counts grouped by store.    | Trend lines, store-vs-store comparison.             |

Pre-generated reports can also be uploaded to blob storage when an external system needs to collect them rather than call the API.

## Predefined options

Options are configured per chain, and each can be tied to a rating range — so a low score can offer different choices than a high one. Fetch the options for the customer's chain before rendering the form; do not hard-code them.

## API reference

Endpoint documentation for this service: [Customer Feedback](/api-reference/communication/customer-feedback).