Design an operator handoff that preserves context
Describe the action accurately
A human request puts a local conversation into a waiting state. An operator can inspect it and reply in text. It does not transfer a phone call or automatically join a person to an audio room. Tell the customer the request is queued, and promise a response time only when your staffing process can deliver it.
Preserve the reason
The conversation retains the customer’s words and the point where the agent stopped. Evidence profiles can optionally queue an operator on abstention. Metadata distinguishes reasons such as empty corpus and below threshold, helping triage a missing source versus an unsupported request. Runtime reports omit question/answer text; use the conversation view for the actual transcript.
Confirm local tickets
A proposed ticket has a title and description for review before confirmation persists it. Repeated confirmation is protected by idempotent handling. This creates a local record, not a ticket in an external help desk. Assign ownership and a review routine before calling it an operational integration. Decide how staff reconcile it with an existing support queue.
Exercise an interrupted journey
Request help, close the playground, reply from the operator console and reopen the same conversation. Also end a session before an operator responds. Closing a dialog and ending a session differ. Count waiting items and inspect outcomes, but do not treat a waiting count as proof that a human reached a customer or resolved an issue.
Product and guides
Explore creekX Agents · Quick start · Documentation. Written for v0.10 early access, 23 October 2026.
Frequently asked questions
Where should I start?
Read the separate Agents quick start and evaluate v0.10 in a private local workspace before a customer pilot.