Intents
What the agent recognises an email as. 27 shipped, 3 defined by your organization. A custom intent is a first-class citizen — it classifies, routes, holds templates, carries a policy, and appears in the metrics.
What a new intent starts as
- · New intents start collaborative: the agent drafts, a person sends. Autonomy is enabled once the intent has a track record (§70).
- · This intent requested the RATE permission. It has been created without it — financial data is granted per sender, not per intent.
This is a clamp, not a validation failure. The settings that decide whether the agent sends unsupervised all live on the intent, so an intent created with all of them open would be a way to grant autonomy without touching a security screen. The intent is created, it classifies, it drafts — it just does not send yet.
Your intents (3)
Pre-cool confirmation
collaborativeShipper asking whether the trailer was pre-cooled to setpoint before loading.
- “was the trailer pre-cooled”
- “confirm precool temp before loading”
- “did the reefer run down before we loaded”
Tarp and securement question
collaborativeFlatbed customer asking how a load is tarped, strapped or chained.
- “is this load tarped”
- “how many straps on that flatbed”
- “do we need coil racks”
Driver check call request
collaborativeCustomer asking us to have the driver call them directly on arrival.
- “can the driver call on arrival”
- “have him ring the receiver first”
Every custom intent is created with starter templates. An intent without one is not half-built, it is silent: it would classify correctly, route correctly, and reply with a generic acknowledgement that never mentions what was asked.
Shipped intents (27)
| Intent | Mode | Threshold | Permission | Replies |
|---|---|---|---|---|
| Shipment status SHIPMENT_STATUS | autonomous | 0.95 | SHIPMENT_STATUS | yes |
| ETA request ETA_REQUEST | autonomous | 0.95 | ETA | yes |
| Tracking request TRACKING_REQUEST | autonomous | 0.95 | SHIPMENT_STATUS | yes |
| Pickup status PICKUP_STATUS | autonomous | 0.95 | SHIPMENT_STATUS | yes |
| Delivery status DELIVERY_STATUS | autonomous | 0.95 | SHIPMENT_STATUS | yes |
| Appointment request APPOINTMENT_REQUEST | autonomous | 0.95 | APPOINTMENT | yes |
| POD request POD_REQUEST | autonomous | 0.98 | POD | yes |
| BOL request BOL_REQUEST | autonomous | 0.98 | BOL | yes |
| Document request DOCUMENT_REQUEST | collaborative | 0.98 | POD | yes |
| Carrier request CARRIER_REQUEST | collaborative | 0.95 | CARRIER | yes |
| Delay explanation DELAY_EXPLANATION | collaborative | 0.95 | SHIPMENT_STATUS | yes |
| Shipment not found SHIPMENT_NOT_FOUND | autonomous | 0.9 | SHIPMENT_STATUS | yes |
| Document not found DOCUMENT_NOT_FOUND | autonomous | 0.9 | POD | yes |
| Missing data MISSING_DATA | collaborative | 0.9 | SHIPMENT_STATUS | yes |
| Quote request QUOTE_REQUEST | collaborative | 0.99 | RATE | yes |
| Rate request RATE_REQUEST | collaborative | 0.99 | RATE | yes |
| Invoice request INVOICE_REQUEST | collaborative | 0.99 | INVOICE | yes |
| Claim CLAIM_REQUEST | human_required | 1 | FINANCIAL | yes |
| Request for record update RECORD_UPDATE_REQUEST | human_required | 1 | — | yes |
| Request for remittance advice REMITTANCE_ADVICE_REQUEST | collaborative | 0.95 | INVOICE | yes |
| Short pay inquiry SHORT_PAY_INQUIRY | collaborative | 0.99 | INVOICE | yes |
| Document submission DOCUMENT_SUBMISSION | autonomous | 0.9 | — | yes |
| Acknowledgement ACKNOWLEDGEMENT | autonomous | 0.8 | — | never |
| General operational GENERAL_OPERATIONAL | collaborative | 0.9 | — | yes |
| Unclear UNKNOWN | human_required | 1 | — | yes |
| Unintelligible UNINTELLIGIBLE | human_required | 1 | — | yes |
| No freight business intent NO_BUSINESS_INTENT | autonomous | 0.9 | — | never |
Creating and editing intents needs the intent table applied. The catalogue, the clamp and the starter templates are enforced today and covered by the tenancy test suite; nothing on this page writes.