Skip to main content
Create an assistant in the subaccount where its calls, messages, and connected actions belong. Use a descriptive name so your team can distinguish production assistants from experiments.

​
Choose a starting point

Open Assistants → Create assistant. Follow the selected dialog to create the assistant. Generated or imported content still needs review: confirm the business name, instructions, voice, tools, and account-specific identifiers before enabling customer traffic.

​
Configure the job

  1. Write the assistant’s purpose and response limits in its prompt.
  2. Open Knowledge Base and assign the relevant business information.
  3. Open Tools & APIs and attach only the actions needed for the job.
  4. If the job includes booking, open Calendars and select the intended calendar.
  5. Configure Chat Settings or Call Settings for the channel you will use.
The standard booking assignment selects one calendar. A prompt listing several calendars does not grant routing to them; use the booking guide for that separate workflow.

​
Test the configuration

Use Chat Lab for wording and tool behavior, and Voice Lab for the spoken conversation. Test a successful request, missing information, and a failed action. Inspect any resulting booking or CRM change.

​
Publish

Wait for changes to save, then click Publish. A disabled assistant can show Enable & Publish; review its assigned channels before enabling it. If publication fails or reports a conflicting change, reload and retry the intended version. Publishing the assistant applies its configuration. Phone-number routing, active chat tags, and widget assignment still determine how customers reach it. Finish with a test through the channel you intend to use. See Quickstart, Voice Studio, and Platform Tools.

​
Assistant workspace reference

The nine toolkit entries are Chat Settings, Call Settings, Autopilot, Tools & APIs, Map Custom Fields, Knowledge Base, Calendars, Find & Replace, and Team Notes. Available panels can depend on account access and assistant type.

​
Assistant model choices

The assistant selector currently offers the following text-model labels. These are configuration choices; provider routing and fallback can affect the underlying model used. Kimi K2.5 can still appear as the label of an older saved configuration but is no longer offered for new selection. Selecting a regular model clears the flow assignment. With a GPT Live voice, the selector controls Chat & tools model and does not offer Flow assignment; change to a compatible standard voice before using a flow. Review the selected value after creation or import instead of assuming all creation methods share the same default.