Configure your assistant and skills
Choose the assistant’s identity, tone and reply mode, then review its skills.
Wasel’s voice · English subtitles Open the video directly
Jump to a chapter
Written walkthrough
Follow the video, then use the written steps below while you work in your dashboard.
The walkthrough uses a demo workspace and synthetic customer details. Channel availability depends on your account and provider configuration.
Assistant settings
In this lesson, we will review assistant settings and skills. Open Assistant and start with Identity. Set the customer-facing name, presentation, company name, and description. Describe your business clearly and save the assistant profile.
Tone and language
Open Tone and choose friendly, professional, or casual to suit your company. Review language settings next. Automatic detection suits Arabic and English conversations. Choose a default language for cases where the customer’s language is unclear.
Reply mode
Review reply operation before serving customers. This demo account uses Copilot, where the assistant prepares a draft for team review. The interface offers switching to automatic replies. Also review AI ticket completion, which depends on the operating mode.
Advanced instructions
Use Advanced for specific style instructions, such as concise answers and prices in EGP. Keep instructions simple to review. Store business facts, prices, and policies in Knowledge Center. Save the assistant profile after editing.
Available skills
Now open Skills. Explore the built-in lead capture and topic detection settings, plus custom skills. Start with a clear team need and review when the skill is used and what it should achieve.
Lead capture
In Lead capture, choose the contact methods your team uses, such as phone, WhatsApp, or email. Review interest signals, including a callback request or accepted handoff. Enable what fits your follow-up process and review before saving.
Supported topics
Open Topic detection. Start with suggestions or create a topic for your business. Use clear names such as delivery, returns, or complaint. Review rules and examples so the team understands each conversation label.
Custom HTTP tools
For a custom skill, enter its name and description, when to use or avoid it, and example customer messages. Create the skill before managing tools. Remember that testing an API executes a real request.