Telecom story
Two customer tasks, handled end to end on the shared runtime.
A Telecom customer checks service status and opens a support case, or checks availability at an address and books an installation. Both tasks ran through Widget and Hosted Chat on the same knowledge, Flows, and handoff the platform pages describe. Demonstration data and actions are simulated; no provider system is connected.
- Service status and support
- Availability and installation
- Need
- Knowledge
- Capture
- Action
- Simulated
- Record
- Handoff
Widget and Hosted Chat.
- Kept in your Nexus workspace
- Simulated external facts and effects
- Handled by people
From customer need to durable result.
Each task runs as a deterministic Flow with approved knowledge, structured capture, governed actions, and a human handoff at the end. Demonstration data and actions are simulated; no provider system is connected.
Service status and support
- Need
A customer's service is not working and they want to know why and what happens next.
- Knowledge
Approved documents describe service states, diagnostic guidance, and when to involve a person.
- Capture
The customer provides a service reference and describes the issue in structured steps.
- Action
The Flow reads the service status, walks through diagnostics, and creates one support case with a receipt.
- Simulated
The service status and the support case are demonstration data and simulated effects.
- Record
The session, the structured submission, and the case receipt are kept in the workspace.
- Handoff
If the issue remains unresolved, or the customer asks, the conversation is handed to a person with the collected context.
Availability and installation
- Need
A customer wants to know whether service is available at an address and to book installation.
- Knowledge
Approved documents describe plans, prerequisites, and appointment rules.
- Capture
The customer provides a location code, chooses a plan and slot, and confirms contact details and consent.
- Action
The Flow checks coverage, lists installation slots, and books one slot with a receipt.
- Simulated
Coverage, plans, slots, and the booking are demonstration data and simulated effects. A slot no longer available is shown plainly as a conflict.
- Record
The session, the structured submission, and the booking receipt are kept in the workspace.
- Handoff
If nothing is available, or the customer asks, the conversation is handed to a person with the collected context.
Nexus records, simulated effects, and people.
Kept in your Nexus workspace
- Sessions
- Submissions
- Receipts
- Handoff records
Simulated external facts and effects
- Status
- Coverage
- Plans
- Slots
- Cases
- Bookings
Service status, coverage, plans, installation slots, support cases, and bookings are deterministic demonstration data, and the actions that read or change them are simulated. Demonstration data and actions are simulated; no provider system is connected.
Handled by people
- Unresolved issues
- No availability
- Any request for a person
Handoff carries the transcript and the captured fields into the configured external support inbox, so the person does not start from zero.
Widget and Hosted Chat.
Customers reach both tasks through the embeddable Widget or the Hosted Chat page. The conversation runs on the shared runtime and its records stay in the workspace. Demonstration data and actions are simulated; no provider system is connected.
Run both tasks in your own workspace.
Create a workspace and follow the guided Telecom setup to run both tasks yourself, or explore how the platform pieces fit. Demonstration data and actions are simulated; no provider system is connected.
- Create an account
Opens account registration.
- Explore the platform
Opens the platform overview.
- Email the team
Opens your mail client; the page sends nothing.