Incoming requests
Repair requests in one working inbox
New, active and completed requests stay separate. Open a request, see the customer and object context, reply in the conversation and move the job to its next state.
Connect a service centerStatus shows what needs attention
The workspace groups requests by working state. New enquiries stay separate from jobs that are already underway or complete.
- New requests
- Work in progress
- Completed jobs
- Workspace counters
Every request has its own conversation
Messages and attachments remain inside the request. The working context is not scattered across a shared messenger, calls and separate staff notes.
- Message history
- Request attachments
- Service center notifications
- Owner replies in the same thread
Object context follows access rules
The center sees information needed for the specific request. Server-side access checks keep the owner’s wider inventory from becoming an open record.
- Connection to the customer object
- Request ownership checks
- Details before work begins
- Path to a completed service record
FAQ
Common questions
Can requests be filtered by status?
Yes. The workspace separates new, active and completed requests.
Is there one shared chat for every customer?
No. Each conversation belongs to a specific service request.
Can a center see the customer’s full inventory?
No. Access to object context is checked within the selected request.