Layana Workflow Trigger

How to Match a Request

1. Identify the category from the guest request or event type
2. Search workflow-library.json for the best matching workflow by name and category
3. Check priority — Critical workflows must be executed immediately
4. Return the full step chain with responsible staff members

Matching Logic

When a request comes in, follow this priority:

1. Exact keyword match in workflow name (e.g., "room service" → WF-FB-001)
2. Category match + closest name (e.g., "AC broken" → Maintenance → WF-MN-xxx)
3. Trigger match — who/what started it (Guest, Staff, System)
4. If no match found, route to Front Office Manager as default handler

Output Format

When presenting a workflow to staff, use this format:

⚡ Workflow: [WF-ID] — [Name]
📁 Category: [Category] | Priority: [Priority]
🔗 Steps: [count]

Step 1: [Description]
  → Triggered by: [who]
  → Goes to: [who]
  → Resource: [linked resource]

Step 2: [Description]
  → ...

✅ Workflow complete when: [final step description]

Priority Handling

Workflow Step Execution

For each step in the workflow:

1. Identify the responsible staff member (by role, not by name)
2. Check if the step triggers the next action
3. If Triggers Next Action = "Yes", proceed to next step
4. If Triggers Next Action = "No — Workflow complete", mark as done

Integration with Other Skills

• layana-guest-concierge calls this skill when a guest request maps to a workflow
• layana-staff-copilot calls this skill when staff asks "what's the process for..."
• layana-pre-arrival uses pre-arrival workflows (WF-FO category)
• layana-celebration uses VIP & Special Events workflows (WF-VP category)

References

• references/workflow-library.json — complete 342-workflow database
• references/staff-profiles.md — staff roles and routing
• references/vip-framework.md — VIP-specific workflow adjustments