Automation
What this installation does by itself, and where it stops. The counts come from the same read as the review queue.
Per kind of mail
| Kind | What the assistant does | Conversations | Waiting now |
|---|---|---|---|
| Order | Proposal, a person sends | 2 | 1 |
| Delivery | Proposal, a person sends | 3 | 2 |
| Damage | Proposal, a person sends | 1 | 0 |
| Product question | Proposal, a person sends | 3 | 1 |
| Business | Proposal, a person sends | 1 | 0 |
| Allergens | Always a person | 1 | 1 |
| Food safety | Always a person | 1 | 1 |
| Payment | Always a person | 2 | 2 |
| Personal data | Always a person | 1 | 1 |
| No reply needed? | No reply needed? | 2 | 1 |
- Proposal, a person sends
- The assistant proposes a reply from the knowledge base; a person reviews and sends.
- Always a person
- No proposal. A person decides and replies.
- No reply needed?
- A thank-you or compliment. A person confirms nothing needs to go back.
How a mail moves through the system
- Intake and matchingAutomatic
9 recognised, 1 not unambiguous
The matcher is deterministic and follows a fixed order. On doubt it does not link (rule 7).
- Drafting a proposalAutomatic
4 ready for review
Only with grounding: every proposal cites the sources it used, and without grounding there is no text.
- Routed to a humanAlways a human
6 right now
An unknown sender, or an assistant saying itself it cannot. The reason comes from that source.
- SendingNever automatic
0 sent automatically
Outbound is simulated (rule 9) and a human confirms (rule 8). There is no switch that turns this on, not here and not in the code.
This installation sends nothing by itself. Outbound is simulated and every send takes a click from a human.