Practical scenarios

This section brings together the concepts, skills, events, and integrations covered across the developer documentation into complete, buildable examples. Each scenario walks through a realistic business use case from first event to final response — including flow YAML configuration, full NSL skill code, and annotated comments that explain every architectural decision.

Who these scenarios are for

These walkthroughs are for developers who have read the Core Concepts and Building with the Platform sections and are ready to see everything working together. Each scenario is intentionally fictitious but realistic: the businesses, problems, and solutions mirror what Newo partners actually build.

Prerequisites

Before working through these scenarios, you should be familiar with:

Agents, flows, and skills — the agent execution model and how flows orchestrate skills
Events and the event system — how event subscriptions trigger skills and how interrupt_mode affects concurrency
NSL syntax — Jinja2-based scripting, {% set %}, {{ }}, {% if %}, {# #} comments
Core actions — GenStream, Gen, Set, GetState, SetState, GetPersonaAttribute, SetPersonaAttribute, GetCustomerAttribute, GetTriggeredAct, SendCommand, Do

Scenarios in this section

Scenario	Business	Key patterns demonstrated
1. HVAC lead capture and booking	Comfort Air HVAC	State machine routing, service area validation, async HTTP availability check, SMS confirmation
2. Restaurant reservation with Magic Browser	Bella Vista restaurant	Intent classification, AKB-powered menu Q&A, Magic Browser availability check, multi-step browser confirmation
3. E-commerce returns and order lookup	ShopNow	HTTP order lookup, return ticket creation, webhook-based escalation, branching on state
4. Real estate lead qualification and follow-up	Keystone Realty	Voice channel, multi-stage qualification, post-call actions, 48-hour follow-up timer, outbound call
5. SaaS support with ticket creation and escalation	Nexus Software	AKB deflection, Zendesk ticket creation, timer-driven escalation, ticket lifecycle state machine

How to read the code

Every skill in these scenarios contains {# ... #} comment blocks that explain what each section does and why it was designed that way. Read the comments as teaching material — they are as important as the code itself.

Code in these scenarios uses realistic values and identifiers, but you should replace connector names, attribute keys, and URLs with the values specific to your implementation.

Changelog

Practical scenarios: initial publication

Published section overview for the Practical Scenarios developer walkthrough series, covering five end-to-end business scenario articles that combine flows, skills, events, state, and integrations.