Support & Requests

Status: Implemented / controlled release

What it does

Captures support/reception/customer-request workflows as accountable operational work.

Benefits

• reduces lost chat requests
• queue/accountability
• status/escalation

Typical usage

1. Create request
2. Queue receives request
3. Process
4. Record result/status

Roles

Customer where exposed, Staff, Manager, Owner, Platform support

API families

• /api/v1/support/*
• /api/v1/public/*requests*

Endpoint presence does not automatically make an endpoint a Partner API. See API → API Overview.

Configuration

• Request type
• Tenant context
• Workflow/queue

Current limitations / release notes

Exact request families depend on enabled vertical/workflow.

Related modules

Staff Operations, Customers, Notifications