Home Getting Started on the Platform GET STARTED: Initial and Essential Settings for Setting Up Claudia

GET STARTED: Initial and Essential Settings for Setting Up Claudia

Last updated on Jul 01, 2026

When to use

  • You just got access to the Hub and need to set up ClaudIA for the first time
  • You want a complete checklist of the minimum settings before uploading content
  • You are setting up the environment for a new ClaudIA project

Prerequisites

  • Administrator access to the ClaudIA project Hub
  • (Recommended) Having filled out the essential information form about your operation and integration
  • Knowing the identity ClaudIA will take on (name, context, tone)

About this article

This is the official step-by-step guide to configure ClaudIA for the first time. Settings were redesigned: the stacked tabs are gone and a Hub took their place — an overview with one card per section that opens a focused editor when clicked. Each block has its own Cancel and Save buttons (only active once you change something in that block), and numeric fields use a stepper (+/−). To understand the navigation, see ClaudIA Settings — the new Hub (overview).

Open ClaudIA → Settings. The screen opens on the Hub:

Follow the order below. Each step points to the exact section → block → field and links to the detailed article.

Step by step — Settings

Step 1 — Behavior → Base prompt (identity and tone)

Open the Behavior card and go to the Base prompt block (Base prompt modules). Fill in:

  • Company and ClaudIA context — what the company does and who ClaudIA is (identity)

  • Voice, tone and style — how she speaks: formality, emojis, preferred/forbidden terms

  • Project-specific rules — rules and restrictions that apply only to this project

Project-specific rule example: If the customer asks questions about brands X, Y, Z, gently redirect the conversation without mentioning those brands, indicating that you do not work with them.

Field details in Context, identity and tone of voice fields and in ClaudIA Settings — Behavior.

Step 2 — (Optional) Behavior → Automatic translation

If a large share of customers write in another language, enable Automatic translation and choose the Supported languages. ClaudIA detects the language from the first messages and starts replying in it. More details.

Step 3 — Lifecycle → Greetings → Initial greeting

Open the Lifecycle card, Greeting messages block, and fill in the Initial greeting — the message that replaces {GREETING} in the first interaction. Mention the project/company name.

Examples:

  • "It's a pleasure to receive your message! This is ClaudIA, XPTO's virtual assistant."

  • "Hi! Great to have you here 😊 I'm Claudia, support team assistant at XPTO."

  • "Hello! How are you? I'm Claudia, a support consultant here at XPTO."

Best practices:

  • Adapt the tone to the company's profile
  • Avoid overly formal or robotic language
  • Use emojis moderately
  • Personalize with the company name and ClaudIA's role

More details in Adjusting the AI name and initial greeting.

Step 4 — Transfer → N2 Transfer → Transfer message

Open the Transfer card, N2 Transfer block (Main settings), and fill in the Transfer message — sent when the transfer to a human is not content-based (attempt limits, transfer verification, message limits, clarification limits).

Step 5 — Transfer → Automatic transfer → Unanswered ticket escalator

In the Unanswered ticket escalator block, fill in the Escalation message — sent when a ticket goes unanswered or an internal error occurs. It can be the same message as Step 4. More details.

Step 6 — Transfer → Human availability

In the Human availability block, configure the Standard support hours — ClaudIA uses this to tell the customer whether someone is available at the moment of transfer. Personalize the Out-of-hours message and, if you want to close in N1 outside business hours, enable Resolve as N1 out of hours. Also register Special dates and holidays when you need exceptions.

More details in How to set up out-of-hours message for N2 (human team unavailable).

Step 7 — Lifecycle → Automatic Resolution → Problem resolved checker

Validates with the customer whether the issue was resolved before closing. It has two independent modes — you can enable one, the other, or both at the same time:

  • Scheduled — asks via a timer. Enable Scheduled mode, set the verification Question and the Minutes until the question.

  • On message (proactive) — enable Real-time mode so ClaudIA detects, on each message, whether the issue is resolved.

More details in Validate problem resolution before closing (Problem Solved Verifier).

Step 8 — Lifecycle → Automatic Resolution → Automatic closing

Define when to close tickets without a reply: enable Automatic closing, adjust the Minutes without reply, and write the closing messages with feedback and without feedback.

More details in How to set up automatic ticket closing in N1 (Ticket Resolver).

Step 9 — Other settings

Other settings (Classification and intent, Frustration detection, Controlled Flows, Media and Tags) are customized as needed after operations start, to calibrate Retention, Quality and CSAT targets.

Step by step — Content

1 — Upload initial content via Sources

In the Content section, use Sources to upload initial FAQ content, product lists, or website data. More details

2 — Build content manually

3 — Support from the Cloud Humans team

If you don't want to create content yet, are unsure, or lack a team to start: that's okay! During Onboarding, the Cloud Humans team supports you and can bulk-upload content in this format.

Final step — Test in the Playground

Open the Playground and send a message to ClaudIA. Done! Initial setup complete.

Important points

  1. If you haven't filled out the essential information form about your operation and integration yet, fill it here

  2. During Onboarding, we assess additional implementation needs to ensure the expected results

Notes