PageSourceSearch

https://app.gpfleet.pt/assets/partner-service-requests-Chbk2vNq.js

js gpfleet.pt collected 2026-10-02 02:06:45 UTC 1,237 bytes, 32 lines download raw bytes

1const e=`---
2title: Service Requests
3kb_url: /help/services/requests
4---
5
6# Service Requests
7
8Service requests are trip reports submitted by drivers through their app. When a driver completes a job outside the automated import flow, they submit a request for you to review. Approving a request automatically creates a service record.
9
10### Status Flow
11
12- **Created** — Submitted by the driver and awaiting your review.
13- **Approved** — You accepted the request; a service record was created automatically.
14- **Rejected** — You declined the request; no service was created.
15
16### Reviewing Requests
17
18From the list, use the inline action buttons on any **Created** request:
19- **Accept (✓)** — Approve the request and generate a service.
20- **Reject (✗)** — Decline the request. A confirmation step is required.
21
22A confirmation dialog appears before each action. Once actioned, the status is final.
23
24### Filters
25
26Filter by expense date, created date, vehicle, status, and to-invoice flag. This helps you focus on pending items or search historical decisions.
27
28### Quick Actions
29
30- Click any row to open the full request details.
31- Use the **Status** filter to show only pending requests requiring action.
32`;export{e as default};

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.