Add and configure skills
Choose useful capabilities, distinguish silent helpers from announced lookups and limit allowed actions.
A skill adds a capability to the bot: send a message, check a calendar, query a CRM or trigger an automation.
Choose a skill
In the bot configuration, use Add a skill. The selector shows available capabilities, their descriptions and their current state. Search for a name or need, then select the required skill.
Already selected capabilities remain visible to prevent duplicates.
Least-privilege principle
For each skill:
- enable only useful actions;
- limit recipients, models or resources;
- clearly explain when the bot should use the action;
- ask the caller for confirmation when an action has an important effect;
- test one success and one failure.
Common skills
| Need | Suitable skill |
|---|---|
| Send a summary | Email or SMS |
| Book an appointment | Microsoft 365, Google or Progenda Calendar |
| Create a ticket or find a customer | Odoo, HubSpot or Zendesk |
| Call a service or schedule a callback | Outbound call or contact callback |
| Run an external scenario | Webhook automation |
Understand errors
An external action can be refused even while the bot itself works correctly. The tool result appears in the conversation. Check the connection, external account permissions and allowed settings before changing the prompt.
Create your first bot shows a minimal configuration with email, calendar and call transfer.
During a lookup
For one caller request, the bot announces the lookup once, then chains the necessary tools without repeating waiting messages. A quiet waiting sound continues between tool results and the actual resumption of spoken audio. The bot speaks again to give a verified answer, report a failure or ask for essential clarification or consent. A new request can start a new sequence. Required consent before a write still applies.
Silent system tools, such as get_time (date and time) or phone-number pronunciation formatting, do not count as an announcement and do not reset an already announced sequence. For example: silently resolve “tomorrow” → “I’ll check availability” → calendar lookup → silent complementary reads → answer. With technical tools only, the bot answers directly without a lookup announcement. A new request requiring a business lookup gets its own announcement.
This behavior is shared by bots configured through the console and API. Avoid instructions requiring an announcement before every tool or retry.