Training results

Copy as training-results-{name}-{date}.md. Keep it locally.

Meta information

• Participant:
• Start date:
• Completion date (basic level, Use Case 9):
• Completion date (advanced level, Use Case 10–11):
• Completion date (capstone, Use Case 13):
• Self-check completed (date):
• Instance (URL, optional):
• Training bot name:

Basic level

Use Case 1: FAQ bot with AI

• Status: [ ] not started · [ ] in progress · [ ] done
• Data flow (3–5 sentences):
• Checked: [ ] Runs/preview · [ ] Fast Line agent test · [ ] KB indexed · [ ] channel (optional)
• Instance Agent (optional): [ ] rebuilt UC-1 via Agent and verified in Runs

Use Case 2: Branching by choice

• Status: [ ] not started · [ ] in progress · [ ] done
• Checked: [ ] Runs · [ ] all menu branches · [ ] default · [ ] (optional) Router by user_choice
• Instance Agent (optional): [ ] rebuilt UC-2 via Agent and verified in Runs

Use Case 3: Handoff to operator

• Status: [ ] not started · [ ] in progress · [ ] done
• subject_alias:
• subject skill group:
• chat_closed_alias:
• Checked: [ ] Runs success/limit/error · [ ] message after limit · [ ] entrypoint after close
• Instance Agent (optional): [ ] rebuilt UC-3 via Agent and verified in Runs

Use Case 4: Mock CRM lookup

• Status: [ ] not started · [ ] in progress · [ ] done
• Mock URL:
• Checked: [ ] ok · [ ] not_ok/error · [ ] Router distinguishes found / new
• Instance Agent (optional): [ ] rebuilt UC-4 via Agent and verified in Runs

Use Case 5: Action Jail — phone

• Status: [ ] not started · [ ] in progress · [ ] done
• Checked: [ ] +380 / 380 / 0… · [ ] edge error

Use Case 6: Registration + return visit

• Status: [ ] not started · [ ] in progress · [ ] done
• Checked: [ ] __set · [ ] new Run + __get success

Use Case 7: Complaint in Custom Data

• Status: [ ] not started · [ ] in progress · [ ] done
• Checked: [ ] record in CD · [ ] ID in Runs

Use Case 7b: CSAT / NPS

• Status: [ ] not started · [ ] in progress · [ ] done
• Checked: [ ] buttons 1/3/5 · [ ] free-text ≠ INTEGER success · [ ] audit alias

Use Case 8: Macro section

• Status: [ ] not started · [ ] in progress · [ ] done
• Checked: [ ] section trace in Runs · [ ] OP (optional)

Use Case 9: Scenario audit

• Status: [ ] not started · [ ] in progress · [ ] done
• RE lab / audit: [ ] RE lab · [ ] capstone audit · [ ] tooling tour (Runs + trace + action test)
• Issues found:

Advanced level

Use Case 10: Ticket + categorizer

• Status: [ ] not started · [ ] in progress · [ ] done
• Checked: [ ] ticket_id in Runs · [ ] categorizer · [ ] error edge

Use Case 11: Broadcast

• Status: [ ] not started · [ ] in progress · [ ] done
• Alias entry:
• Checked: [ ] alias in Runs · [ ] delivery (optional)

Capstone project

Use Case 13: Capstone

• Status: [ ] not started · [ ] in progress · [ ] done · [ ] self-check passed
• Third menu branch: [ ] FAQ · [ ] Custom Data complaint

Self-check:

• 3 menu branches work in Runs
• Fast Line fallback is not silent
• Connect has a message on limit
• CD or ticket in Runs/constants
• Use Case 9 audit: 0 unconnected edges on critical nodes

Optional track

• Use Case 12 Copilot · [ ] Advanced Fast Line Pro · [ ] Priority segment · [ ] AI catalog · [ ] SLA alias · [ ] Ticket events

Self-assessment

• Build a scenario independently from a task description
• Explain the data flow of any scenario
• Find the root cause via Runs
• Difference between state vs registered_users

Reflection

• What was hardest: