Skip to main content
A useful prompt describes what the assistant should accomplish and how to recognize completion. Give it a small, testable job before adding more instructions.

Write the prompt

Open the assistant’s prompt in the builder. Organize your instructions around:
  • Identity: the business and role the assistant represents.
  • Task: the steps needed to help the customer.
  • Response style: language, tone, length, and how many questions to ask at once.
  • Limits and recovery: what to do when information is missing or an action fails.
These headings are a writing pattern, not a requirement to find four separate settings screens.

Example: appointment enquiry

Use booking instructions only after configuring the calendar and tools. A prompt does not create the integration or permission to perform the action.

Use known variables

A supported variable such as {{contact.first_name}} can personalize the conversation when contact data is available. Include a natural fallback for missing values and test on the actual channel. Avoid inserting unverified account IDs or assuming a standalone test has every CRM field.

Improve one behavior at a time

  1. Write several representative customer messages, including a missing-information and failure case.
  2. Run them in Chat Lab.
  3. Compare each response with the intended outcome.
  4. Change the smallest relevant instruction.
  5. Repeat the same cases.
  6. Publish the version you intend to use and verify the customer channel.
If you use a flow, put shared rules in its Global Prompt and the immediate task in each Conversation node. See flow conversation nodes.

Prompt editing controls

Generate Prompt and Enhance Prompt offer these language choices: Auto (default), English, Spanish, French, German, Portuguese, Italian, Dutch, Polish, Arabic, Hindi, Chinese, Japanese, and Korean. Auto keeps the existing language for enhancement; generation uses its default language behavior unless the description requests another language. This selector changes the written prompt, not the voice’s transcription language or available voice catalogue. Enhancement saves check whether the stored prompt changed while you were reviewing. If the editor reports a conflict, reload the current prompt and reconcile your edits before saving again. A generated prompt still needs real tool, knowledge, and channel tests.