Create and Configure an AI Call Assistant
Create an AI Call Assistant with a greeting, call direction, instructions, hours, closing behavior and transfer rules.
What this guide helps you do
Create an AI Call Assistant with a greeting, call direction, instructions, hours, closing behavior and transfer rules.
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 |
|---|---|
| Assistant Name | Internal identity. |
| Greeting | Opening message. |
| Direction | Incoming, outgoing or both. |
| Business Hours | Approved call times in PKT. |
| Exit Keywords | Words that close or transfer the call. |
| Closing Message | Final caller message. |
Step-by-step instructions
- Open AI Call Assistant.
- Choose Create Assistant.
- Enter a clear internal name.
- Set call direction.
- Write the greeting and AI disclosure where required.
- Add instructions and knowledge.
- Set PKT business hours and outbound rules.
- Add exit keywords and closing message.
- Configure transfer/callback.
- Save as draft and test.
Test and verification
- Call from +92 300 1234567 fictional example.
- Check greeting and disclosure.
- Check business hours.
- Check exit keywords.
- Check transfer.
Common issues and solutions
| Issue | What to Check |
|---|---|
| Assistant unavailable | Active status, provider and call connectivity. |
| Wrong greeting | Selected assistant and saved version. |
| Calls outside hours | Timezone and schedule. |
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:

