Configure Wemblo AI Behavior
Define instructions, tone, response length, creativity, language, prohibited claims and escalation rules for Wemblo AI.
What this guide helps you do
Define instructions, tone, response length, creativity, language, prohibited claims and escalation rules for Wemblo AI.
Who should use it
Workspace owners, managers, automation users and authorized technical users responsible for AI configuration or customer workflows.
Before you begin
- Use the correct workspace and minimum required role.
- Use a business-controlled provider account where applicable.
- Understand provider billing, usage and data settings.
- Use fictional Pakistan test data.
- Define human handover before enabling automatic replies or calls.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Instructions | Top-level behavior. |
| Tone | Formal, friendly or business-specific style. |
| Temperature / Creativity | How freely the model drafts where available. |
| Maximum Length | Response-size control. |
| Prohibited Claim | Information AI must not state. |
| Handover Phrase | Customer wording requesting a person. |
Step-by-step instructions
- Open AI behavior settings.
- Write the business role and purpose.
- Set supported languages and tone.
- Add answer boundaries and prohibited claims.
- Set response-length and creativity controls where available.
- Add escalation and handover rules.
- Save.
- Run a controlled test set.
Test and verification
- Test short and long questions.
- Test mixed Urdu-English.
- Test a request outside knowledge.
- Test escalation.
Common issues and solutions
| Issue | What to Check |
|---|---|
| Too verbose | Reduce maximum length and prompt verbosity. |
| Too creative | Lower creativity and strengthen factual boundaries. |
| Does not hand over | Review triggers, queue and automation pause. |
Security, privacy, consent, cost and provider notes
- AI-provider charges and Wemblo AI-action usage are separate controls.
- Do not expose provider keys or customer data in screenshots, tickets or client-side code.
- Use human review or handover for sensitive, private, regulated, urgent, high-value or final decisions.
- Do not promise perfect accuracy or guaranteed business outcomes.
Last reviewed: