Model & Context

Open in CMS

The Model & Context page contains settings that influence which AI model the agent uses for conversation, what users may attach to their messages, and how much conversation history it "remembers."

For Atlas, Kirana Group's operations assistant, the defaults are a good start: the organization default model, attachments on so people can send a quotation or a site photo, and the last 10 messages carried over. You come back here when real conversations show a specific problem, for example answers that arrive too slowly during a site visit, or a follow-up question about a purchase request that Atlas cannot connect to the request it just looked up.

Navigate to Conversation β†’ Model & Context in the left sidebar. The CMS lists this page under Conversation; in these docs it belongs to the Fine-Tune Answer Quality stage, because the defaults work for most agents and you usually change them only to solve a specific problem.


Before you start

  • Finish the basics first: Give Your Agent an Identity, Teach Your Agent, and Shape the Conversation.
  • Write down the problem you want to solve (for example "answers are too slow", "site supervisors need to send photos", or "the agent forgets what was said earlier") and a few test questions that show it, such as "What do I need to attach to a USD 400,000 capex request?".

Model

The Model card holds the conversation model and the two switches next to it.

Model card: Conversation AI Model set to Organization default (β†’ Smart) with its description, estimated credit ratio 3x and the chips Image in and Document in, the Enable User to Change AI Model switch off, and the Enforce Thinking switch off

Conversation AI Model

The primary AI model used for all user-facing conversation. This model handles every message the user sends and generates the visible response.

The first option, Organization default (β†’ Smart), follows the default model your organization has chosen; the arrow shows which model that currently is. Under the picker you see the selected model's description, its estimated credit ratio, and chips such as Image in and Document in that show which inputs it accepts. Atlas uses the organization default.

It is also the model that answers during Natural conversation voice calls, unless the Voice page picks a different Answering AI model.

Choose based on the trade-off between response quality, speed, and cost:

ConsiderationGuidance
High accuracy requiredUse the most capable model available
High volume / cost-sensitiveUse a smaller, faster model
Mixed needsEnable User to Change AI Model below

Model levels and + models

Qlar's built-in models come in six levels, from fastest and cheapest to deepest-thinking. The picker shows each model's description and its estimated credit ratio: how much it costs relative to the others.

ModelCredit ratioBest for
Light1.5xFAQ bots, auto-replies, simple formatting; answers without reasoning first
Smart3xEveryday chat: customer service, appointment booking, routine questions
Analyst35xStructured workflows: forms, API orchestration, rule-based automation
Insight45xKnowledge-base Q&A and support that needs context
Thinker90xComplex, multi-step reasoning: data analysis, compliance checks
Sage230xStrategic, high-stakes decisions

Every level also has a + version: Light+, Smart+, Analyst+, Insight+, Thinker+, Sage+. A + model is the same model, thinking exactly the same way, running on Fast mode: its answers come about 1.5–2x faster, at twice the credit ratio (Light+ 3x, Smart+ 6x, Analyst+ 70x, Insight+ 90x, Thinker+ 180x, Sage+ 460x). Choose a + model when waiting matters (busy chats, voice calls), not for better answers. Under heavy load an answer can occasionally run at normal speed; it is then billed at the normal rate. Background work such as summaries and knowledge-base training never uses Fast mode, so it costs the same with either version.

Enable User to Change AI Model

Allows end users to switch between different AI models during their conversation. When enabled, a model picker appears in the chat interface. Off by default.

Allowed Conversation AI Models

Visible only when Enable User to Change AI Model is on. Select which models users are allowed to choose from. Users cannot pick a model outside this list. If Allow Image Upload is on, include at least one model that accepts images.

The first model in the list becomes the default. It is the model the agent uses at the start of every conversation before the user makes a selection.

Enforce Thinking

When enabled, the AI is required to reason through its approach before generating the final response. This improves the quality of answers to complex or multi-step questions.

Use this for agents dealing with analysis, troubleshooting, or any task requiring careful reasoning. Off by default.

Trade-off: Thinking adds latency. Responses take slightly longer to appear.


Attachments

These settings decide what users can attach, in text chat and during an immersive voice call. They sit on this page because whether an image can be read depends on the model chosen above.

Attachments card with Allow Image Upload and Allow Document/File Upload both switched on, and an empty Document Upload Restrictions text box showing an example restriction as placeholder

Allow Image Upload

Lets users attach images (JPG, PNG, WEBP) to their messages. In text chat, the Conversation AI Model must accept image input; if it doesn't (or, with model switching on, if none of the allowed models do), the page shows a warning and users won't be able to send images in chat. Turn-by-turn voice calls are not affected: that style always reads images. In Natural conversation, images go to the Voice page's Answering AI model, so whether they can be sent in a call depends on that model. See Voice β†’ Attachments.

Allow Document/File Upload

Lets users attach documents (PDF, TXT, MD). The document's text is extracted independently of the AI model (scanned PDFs go through OCR), so this isn't affected by model capability.

Both switches apply to chat and to immersive voice calls alike. Turn both off and neither the chat input nor the voice call offers an attach option.

Document Upload Restrictions

A free-text field where you describe what users must not upload. Every attached file (image or document, in chat or in a voice call) is checked against this text when it is uploaded, and a file that violates it is refused with the reason, before it ever reaches the conversation.

Example restriction for Atlas:

Block salary slips, employee ID card or passport scans, and files with bank account or credit card details. Vendor quotations, purchase requests, and site photos are allowed.

Leave this field blank to allow all supported files.


Context Window

These settings control how much of the conversation history the agent "remembers" when composing each response.

Context Window card: Summarize Previous Answer off, Keep Function Tools Answer on, User Message to Carry Over 10, Max Response Token 0, and an info box saying that Personalization, whether the agent remembers users and the model it uses to do that, now has its own Personalization page

Summarize Previous Answer

When enabled, the agent summarizes its own previous responses before including them in the context window. This reduces the number of tokens used to represent prior turns, allowing longer conversations to fit within the model's context limit.

Use this for agents that handle extended multi-turn conversations.

Trade-off: Summaries may lose fine-grained detail from earlier answers. If precision in referencing past responses is important, keep this off.

Keep Function Tools Answer

When enabled, the output of any external tools or function calls (e.g., API responses, database query results) is retained in the conversation context for follow-up turns.

Use this when users are likely to ask follow-up questions about data retrieved by a tool. For example, Atlas looks up the status of project KG-2041 with a tool, and the user then asks "Who has to approve the next stage?". With this on, Atlas still has the status it just fetched.

User Message to Carry Over

The number of recent user messages to include in the context window when starting a new conversation segment or after thread separation.

ValueBehaviour
0No history is carried into the new segment
10 (default)The last 10 user messages and their responses are included
Higher valuesMore continuity but higher token usage

Set this based on how much conversational continuity matters for your agent and how long typical conversations are.

Max Response Token

The longest answer the agent may write, in tokens. 0 (the default) follows the model's own maximum. A positive value hard-stops the response at that many tokens. That is useful to cap cost, at the risk of cutting a long answer short.

Looking for memory about each person? The info box at the bottom of the card points there: Personalization, whether the agent remembers users and the model it uses to do that, now has its own page. See Remember Each User.


Saving Changes

Click Save after adjusting any setting. Publish your agent to propagate the changes to end users.


Check the result

After you save, click the reload button in the preview panel on the right side of the page to start a fresh conversation, then repeat the test questions you wrote down. Compare speed and answer quality with before. If you allowed attachments, try sending an image or document (for Atlas, a vendor quotation PDF) and check that the agent can read it.

The preview runs your draft. End users get the new model and context settings only after you publish. See Preview and Publish Changes.


Next steps

  • Retrieval: tune how the agent searches your knowledge (next step).
  • Chat: language, dictation, formatting, and other text-conversation settings.
  • Talk by Voice: the voice call, including attachments during an immersive call.

Looking for the default timezone? It is set in Profile.