Guide
Article Markdown

ConnectiveOne implementer training

Track version: v2.4 — Instance Agent, Router/switch, connect parameters, debug tooling.

Who this is for

This track is for a technical person on the client side (integrator, analyst, scenario developer) who works in ConnectiveOne only through the instance UI — without support from an internal ConnectiveOne team.

What you will get

After completing the track, you will be able to:

  • build a bot scenario for a typical business task;
  • test the logic with Runs and Chat preview;
  • find and fix common configuration mistakes (edges, alias, variables).

Before you start

  1. Read Prerequisites.
  2. Review the Implementer overview.
  3. Copy the progress template and results template.
  4. Create a training bot (for example, “Training Bot”) — complete all Use Cases in it.

How to follow the track

Pace is not fixed. What matters is the stage sequence and a self-check before moving on.

Stage Use Case File
0. Preparation Prerequisites prerequisites.md
1. Basic Use Case 1 → 2 → 3 from Use Case 1
2. Basic Use Case 4 → 5 from Use Case 4
3. Basic Use Case 6 → 7 → 7b → 8 from Use Case 6 · concepts
4. Basic Use Case 9 + RE lab Use Case 9
5. Advanced Use Case 10 → 11 from Use Case 10
6. Capstone Use Case 13 capstone/use-case-13-integrated-bot.md

Basic level

Use Case Name
Use Case 1 FAQ bot with AI
Use Case 2 Branching by choice
Use Case 3 Handoff to operator
Use Case 4 Mock CRM lookup
Use Case 5 Phone normalization
Use Case 6 Registration + return visit
Use Case 7 Complaint in Custom Data
Use Case 7b Post-dialog rating (CSAT/NPS)
Use Case 8 Macro section
Use Case 9 Scenario audit

Advanced level {#advanced-level}

Use Case Name
Use Case 10 Ticket from bot + categorizer
Use Case 11 Broadcast

Capstone project

Use Case Name
Use Case 13 Integrated bot (capstone)

Optional (by task type)

Use Case Name
Use Case 12 Copilot + CD lookup
Advanced Fast Line Pro Streaming / completion
Priority segment Different branches by segment
AI catalog Search in Custom Data
SLA alias Escalation via alias
Ticket events Ticket events

Reference

Document Purpose
Key concepts Edges, Router/switch, Instance Agent, mock API, categorizer, broadcast
Actions glossary Actions reference
Testing matrix What to check in Runs
FAQ Common problems
When it is not the scenario Scope limits and self-debug

Something is not working?

  1. Runs — which edge fired, which variables.
  2. Alias / subject_alias — match with Settings.
  3. Channel — preview vs real Telegram/widget.
  4. FAQ for the relevant Use Case.
  5. When it is not the scenario.
  6. If the scenario is correct but platform behavior is inconsistent — ConnectiveOne support.

Concepts by hint

Using your own AI agent?Install the open skill so your AI agent can work with current official ConnectiveOne documentation.Get the skillNeed support?Couldn’t find the answer or need help from the ConnectiveOne team? Create a request in Client Portal.Create a request