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

# Self-driving

> Glimps opens its own cases, asks the right person, and settles the outcome. One rung at a time.

A blocked invoice used to need a person to notice it, work out who to ask, ask them, wait, and then do something with the answer. Self-driving does those five things itself.

Open **Self-driving** in the sidebar. It is switched on per administration, and only administrators see it.

<Note>
  The page has two sides on purpose. **What is happening** is computed from what really occurred. **How it is set up** is where you change things. Looking at your numbers never changes a setting.
</Note>

## Kinds of case

A case is one thing that needs settling. Glimps knows these kinds:

| Kind of case | What it is about |
| - | - |
| Difference with the purchase order | Price, quantity, or a line that exists on one side only |
| Unknown bank account | The IBAN differs from the one on file |
| Lines with no ledger account | Coding that could not be decided |
| Unknown supplier | The sender does not resolve to a relation |
| Doubt about the supplier | The identity of the sender is not certain |
| Expected contract invoice missing | A period passed without the invoice that was due |

## The four rungs

Each kind of case sits on its own rung, because the risk differs per kind.

<Steps>
  <Step title="Off" icon="power">
    Nothing happens. The case is not opened.
  </Step>

  <Step title="Watch" icon="eye">
    Glimps works the case out and records what it would do. Nobody notices anything. This is where you find out whether the reasoning is any good, at no risk.
  </Step>

  <Step title="Ask" icon="message-circle">
    Glimps really asks a real person. What should happen next stays a proposal that a person carries out.
  </Step>

  <Step title="Handle itself" icon="check-check">
    Glimps asks and carries out the outcome itself. This is the rung where money moves.
  </Step>
</Steps>

You move up one rung at a time. Down is always possible. The rung below is where you learn whether the questions are any good.

## What is happening

Three numbers over the last 30 days:

* **Handled without a question**: the share of closed cases where nobody was asked anything.
* **Done after one question**: the cases where one answer was enough.
* **Median answer time**: how fast answers come back, and how many questions were answered.

Below them:

* **You need to act**: the cases that only move on once you act.
* **Runs by itself**: questions that are out, and cases that are with someone outside Glimps. Nothing for you to do.
* **A rule is missing here**: the cases that came past without a rule to route them.

## Why it waits

| Group | What it means | What you do |
| - | - | - |
| No owner | No rule matched, so Glimps is asking who owns it | Click **Choose who decides**. Glimps starts the rule for you |
| Stuck | Attempts used up, an error, or nobody to escalate to | Click **Review and solve**. This one needs you |
| Question is out | The question is with the right person or group | Wait |
| With someone outside Glimps | A rule sent this to a department or to the supplier | Nothing. Glimps follows it up |

## The steps

On **How it is set up**, the list **Still to do to let everything run** shows what a working setup needs. It is recomputed rather than ticked off, so a step can open back up:

1. At least one kind of case really runs.
2. Every running kind of case has a default recipient.
3. Ledger accounts are grouped into categories.
4. Routing rules exist.
5. Answers come back.

<Tip>
  Start with one kind of case on **Watch** for two weeks. Read what it would have done. Then move that one kind to **Ask**, and leave the rest where they are.
</Tip>


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