How routing works
- The AI agent identifies the caller’s issue during the conversation
- It matches the issue to a slot via the
casesfield - The agent tries the Priority 1 contact first
- If unavailable, falls back to Priority 2, then Priority 3
- If all contacts fail, the agent handles the call based on its configuration
Data model
| Field | Type | Description |
|---|---|---|
id | uuid | Slot identifier |
slotnummer | string | Two-digit slot number ("01", "02", etc.) |
cases | string | Comma-separated case types (e.g., "Billing, Payments") |
slot_belegung | string | Name of the person assigned to this slot |
prioritaet_1 | string | Primary contact (phone number or name) |
prioritaet_2 | string | Secondary fallback contact |
prioritaet_3 | string | Tertiary fallback contact |
agent_id | uuid | Parent agent |
Endpoints
List forwarding slots
forwarding:read | Pagination: no (returns all, ordered by slot number)
Create forwarding slot
forwarding:write
Required fields: slotnummer, cases
Update forwarding slot
forwarding:write
Delete forwarding slot
forwarding:write | Returns 204 No Content
Replace all forwarding slots (bulk)
forwarding:write
Replaces all existing slots with the provided list in a single operation. Existing slots are deleted first. Use this for bulk synchronization from external systems.
replaced_count — the number of previous slots that were removed:
Best practices
- Use
PUTfor full sync from external systems,POST/PATCH/DELETEfor individual changes - Slot numbers should be sequential two-digit strings:
"01","02","03" - Keep
casesdescriptive — the AI uses this text to match caller issues
Related resources
- Agents — Parent resource
- Employees — People referenced in slot priorities
- Forwarding Slots — Dashboard UI guide