Skip to main content
After creating an assistant, configure what it says, what it can look up, and how calls should behave. To open the configuration page, click Assistants in the left sidebar, then click the assistant you want to edit.

Configuration Areas

The left panel groups settings into three areas.

Prompt

Click Assistant Settings and then Prompt. The prompt is the assistant’s working script. It has three important parts.

First Message

Keep the first message short and clear.
Use @{{variable_name}} when the greeting should include a value from the calling list, such as the customer’s name. The Interruptible setting controls whether the customer can speak before the first message finishes.

Objective

Write one short paragraph that tells the assistant what to achieve.

Response Guidelines

Use bullet points for rules the assistant must follow.

Voice

Click Assistant Settings and then Voice. Use Most Used or Neutral to filter voice options. Save the voice, then run a test call before using it in a campaign.

Custom Variables

Click Assistant Settings and then Custom Variables. Custom variables are placeholders that Ringg AI fills in for each call. They usually come from a campaign CSV or from your backend. Use the same spelling in the assistant prompt and in the CSV column name. For example, @{{callee_name}} needs a CSV column named callee_name.

Knowledge Base

Click Assistant Settings and then Knowledge Base.
  1. Select an existing knowledge base.
  2. Confirm it is trained and ready.
  3. Click Save.
Use a knowledge base when the assistant needs to answer questions from approved documents, such as FAQs, pricing, policy rules, product details, or eligibility criteria. See Create a Knowledge Base if you need to create one first.

Call Settings

Click Call Settings and then Call.
For a first launch, keep settings simple. Set a reasonable maximum duration, choose the correct timezone, and test voicemail behavior before calling real contacts.

Chat Settings

Click Call Settings and then Chat. These settings apply to Webcall assistants.

Embed

Click Advanced Settings and then Embed. Use this only for a Webcall assistant.
  1. Choose the widget theme, size, feedback screen, and branding.
  2. Select the SDK version.
  3. Click Preview to check the widget.
  4. Copy the generated code.
  5. Send the code to the website owner or developer.
Website teams should add the embed code to the website, not to internal documents or email templates.

Keyword Boosting

Click Advanced Settings and then Keyword Boosting. Add words the assistant must recognize correctly, such as brand names, course names, product names, city names, acronyms, or plan names.
  1. Type one keyword.
  2. Click Add.
  3. Repeat for each important word.

Custom Analysis

Click Advanced Settings and then Custom Analysis. Custom analysis extracts structured results after each call. Use it when your team needs consistent reporting fields. Example fields: Example prompt:
Click Save, then Test Analysis before launch.

Run a Test Call

Click Test call in the top-right corner. Use a real phone number owned by your team. Check that:
  • The first message sounds right.
  • Variables such as customer name are filled correctly.
  • The assistant follows the objective.
  • The voice and language are appropriate.
  • The call ends politely.
  • The transcript and analysis are useful.

Developer Handoff

Send this information to the engineer or website owner before launch: For production integrations, ask the developer to configure webhooks after the assistant is approved. See Webhook setup.