CRM › Utilities
Customer Requests
What the public and portal customers asked for — start, stop or move service, a leak or an outage, an arrangement — waiting for somebody to review it.
Where to find it
Address in the console: /crm/util-requests
Read-only list · 15 columns · 7 actions
This list is read-only: its records are written by the work that produces them. A correction, where one is possible at all, is made where the record was created.
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Request | Code | request_no |
| Received | Date and time | created_at |
| What | Status | request_type |
| Problem | Status | problem_type |
| From | Status | channel |
| Name | Text | full_name |
| Text | email | |
| Telephone | Text | phone |
| Address | Text | address_text |
| What they wrote | Text | details |
| Matched premise | Code | premise_no |
| Account | Code | account_no |
| Service order | Code | order_no |
| Status | Status | status |
| Review note | Text | review_note |
What you can do here
Raise service order primary
Asks for: Premise
Premises at this address
Match to a premise
Asks for: Premise*
Accept
Asks for: Note
Decline
Asks for: Why
Mark as spam
Done
* required
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.