83 lines
3.2 KiB
Markdown
83 lines
3.2 KiB
Markdown
---
|
||
id: create-employee-role
|
||
name: Create Employee Role
|
||
description: Record what a worker does — their role, experience, pay and availability — by answering a few questions in the chat.
|
||
pages:
|
||
- talent-pool
|
||
- positions
|
||
status: active
|
||
version: 1
|
||
prompt: Create an employee role
|
||
flow: employee-role
|
||
triggers:
|
||
- create an employee role
|
||
- create employee role
|
||
- create employee roles
|
||
- add an employee role
|
||
- add employee role
|
||
- new employee role
|
||
- create a worker role
|
||
- create worker role
|
||
- record a role for
|
||
- add a worker role
|
||
actions:
|
||
- create_employee_role
|
||
---
|
||
|
||
# Create Employee Role
|
||
|
||
## Purpose
|
||
|
||
Record a worker's declared professional role without leaving the page. Owliver
|
||
asks one question at a time, offers the answers as chips, and reads the whole
|
||
thing back before anything is written.
|
||
|
||
**This is not Create Position, and the difference is the point.** A position is
|
||
what the ORGANIZATION needs filled — a company, a title, a pay range it will
|
||
pay. An employee role is what a WORKER says they do — the role they present
|
||
themselves as, the experience they have, and the pay they are looking for. The
|
||
two share a vocabulary and nothing else: "3 years" on a position is a minimum an
|
||
applicant must clear, and the same words here are what this person has.
|
||
|
||
They are never joined by a column. Supply and demand meet through applications,
|
||
which already carry the funnel, the interview and the outcome.
|
||
|
||
## Capabilities
|
||
|
||
- Understand requests to record what a worker does.
|
||
- Ask who the role is for, and resolve the answer to a real worker profile.
|
||
- Read the role, experience, English level, certifications, desired pay and
|
||
availability out of a single sentence.
|
||
- Ask only for what the request did not already answer.
|
||
- Offer each answer as a suggestion, so the whole flow can be clicked.
|
||
- Read the role back for confirmation before recording it.
|
||
|
||
## Conversation
|
||
|
||
Each line is `field | question | suggestions | required?`. Suggestions beginning
|
||
with `@` come from the application's own data.
|
||
|
||
This creates a NEW employee. The name is not looked up — an organization may
|
||
employ several people who share one, so a name selects nobody — and the email is
|
||
asked for outright and never derived from the name, from the operator's account
|
||
or from an earlier conversation. The email is the identity: `worker_profiles`
|
||
carries UNIQUE (org_id, email), so the database decides whether this person
|
||
already exists.
|
||
|
||
Recording another role for somebody who is already on file is a different
|
||
request and is not this flow.
|
||
|
||
- worker_name | What is the new employee’s full name? | | required
|
||
- worker_email | What is their email address? | | required
|
||
- role_category | What role do they work as? | @roles | required
|
||
- experience_years | How much experience do they have? | No experience; 1 year; 2 years; 3+ years | optional
|
||
- english_level | What is their English level? | @english | optional
|
||
- certifications | Any certifications they hold? | @certifications; None | optional
|
||
- desired_pay | What pay are they looking for? | $18–$28/hr; $25–$35/hr; $30–$40/hr; Custom | optional
|
||
- availability | When are they available? | @availability | optional
|
||
- notes | Anything else worth recording? | | optional
|
||
|
||
## Actions
|
||
|
||
- create_employee_role
|