CRM › Automation
Technician Skills
Who can be dispatched to what, where, and how many visits a day. Field dispatch picks the least busy available technician with the skill in the customer's country.
Where to find it
- Module: CRM
- Group: Service & Engagement
- Section: Automation
- Screen: Technician Skills
Address in the console: /crm/technician-skills
List · 6 columns · 5 fields on its form · 2 of them required
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 |
|---|---|---|
| Employee | Code | employee_no |
| Technician | Text | technician_name |
| Skill | Text | skill |
| Countries | Text | territory |
| Visits a day | Number | max_jobs_per_day |
| Available | Yes or no | is_available |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Technician required | Choice | Looked up from existing records | |
| Skill required | Text | The same word a work order names as its required skill. | |
| Countries | Text | Country codes, comma-separated. Blank is anywhere. | |
| Visits a day | Number | ||
| Available | Yes or no |
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.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.