Start here

Choose the path that matches what you need to accomplish. You do not need to understand the platform's containers to begin using an existing Delphi installation.

Choose your path

• Register an account: when self-service onboarding is enabled, verify email, review documents and complete setup.

• Create your first application: select a template, confirm the saved draft and configure its entry points.

• Change an existing application: save a draft, check readiness, publish deliberately and verify the conversation.

• Deploy or update an installation: prepare configuration and recovery, activate it and verify the result.

• Connect a browser application: keep credentials on the server, open a session and handle its lifecycle.

Understand the building blocks

Building block	Role in your task
Application	The team's container for flows and the customer entry points associated with them. Create or manage an application.
Flow	The graph of steps and transitions you edit, validate and publish in Flow Designer.
Agent node	A step that uses the configured model/provider to conduct part of the interaction. Use the node and inspector reference to distinguish voice, text and other node types.
Provider	The selected speech or language-model service and its configuration. It can be a flow default or a node override; check that scope before changing it.
Entry point and endpoint	The authored entry point and its reconciled runtime destination. Configure entry points before relying on a published route.
Conversation	The stored record of a call or session. Review the matching conversation to investigate its result; a record is not proof that every intended action completed.

For administration, use team and platform tasks. For deployment health, logs and recovery, use Operate. A UI control, API request and environment variable can change different scopes of the same feature; follow the owner for the scope you need. Deployment settings are listed in the environment variable reference.

Set up your first application

1. Get access and find your workspace. Follow Get access to the right team and actions. If the expected team or controls are unavailable, ask your team administrator to check your access and enabled features.
2. Create an application. Follow Create your first application to select the team and a template, then verify what was saved.
3. Build the interaction. Build and validate a flow, using the node reference to select supported steps. Choose the channel and provider configuration, then configure application entry points. Review the draft before publication.
4. Decide what to retain. Choose recording outputs. Storage setup belongs to the team administrator.
5. Publish and verify. Follow Save, test and publish, then review the matching conversation. If a call or its recording is missing, continue to Operate.

This path only helps you choose the right guides. Each linked task lists its own prerequisites and how to verify the result.

Set up or maintain an installation

Use Service roles and dependencies to locate the components, service health for checks, and release compatibility before an update.

Start with deployment prerequisites and provisioning and bootstrap, then use Administer for shared configuration and Operate for runtime checks and recovery.

Connect another system

Open Integrate for connection guides and interface references. Check the interface version before using a schema or example.

Why the same subject appears in different places

A recording task can involve app settings, a shared storage destination and runtime processing. Each instruction has one owner; Recordings and storage connects them. UI, API and environment variables are ways to perform a task, rather than separate copies of the documentation.

Related

• Screen reference — to locate a screen that a guide names
• Understand feature availability — to find out why an expected control or screen is missing
• Shared topics — to follow one subject across use, administration, operations and integration