Outbound Messaging Controls
Personal Assistants can initiate conversations with contacts across multiple channels using the send_to tool. Administrators control which contacts each PA is allowed to message through Outbound Channel Access settings, and configure organization-wide rate limits to prevent runaway send behavior.
Per-Channel Access Settings
Each PA has an independent access level for every outbound channel. These settings live on the PA's configuration and default to internal for all channels when a PA is provisioned.
| Value | Who the PA can message |
|---|---|
none | Nobody — outbound sends on this channel are blocked entirely |
bo_only | Only the employee (Business Owner) the PA serves |
internal | Contacts classified as Employee, Colleague, Business Owner, or with a direct relationship to the BO — external and vendor contacts are blocked |
any | All contacts, including external and vendor contacts |
Channels with configurable access
| Channel | Setting name | Default |
|---|---|---|
| Outbound Email Access | Varies (existing PAs retain their prior setting) | |
| Microsoft Teams | Outbound Teams Access | internal |
| Slack | Outbound Slack Access | internal |
| Boardroom | Outbound Boardroom Access | internal |
| PA Hub | Outbound PA Hub Access | internal |
When the cross-channel messaging feature is enabled, existing PAs inherit their current Outbound Email Access value for all new channels. For example, a PA already permitted to send emails to any contact will also start with any access for Teams, Slack, Boardroom, and PA Hub.
How "internal" is evaluated
A contact is considered internal — and therefore permitted under the internal setting — if any of the following is true:
- The contact's
relationshipToBoisself,internal, orkey_contact - The contact has at least one classification label of
Employee,Colleague, orBusiness Owner
A contact with no classification labels and no relationship record is treated as external and blocked under internal. This fail-closed behavior prevents newly imported or unclassified contacts from bypassing access controls.
Classification is evaluated at send time against the current contact record. If you reclassify a contact (for example, from External to Employee), the change takes effect immediately — the PA's next send_to call to that contact will use the updated classification.
Configuring access
- Navigate to Manage > Team > Users
- Open the employee whose PA you want to configure
- Select the Personal Assistant tab
- Under Outbound Channel Access, set the access level for each channel
- Click Save
Rate Limits
Organization-wide rate limits protect against runaway agent behavior. These settings apply to all agents (AICOS and PAs) and are configured at the account level.
| Setting | Default | Description |
|---|---|---|
| Max Send-To Per Execution | 5 | Maximum number of send_to calls an agent can make in a single execution. Resets with each new inbound message or wake-up trigger. |
| Max Outbound Per Agent Per Hour | 50 | Sliding-window hourly cap on outbound messages per agent, across all channels and tools. |
| Max Outbound Per Contact Per Hour | 10 | Sliding-window hourly cap on outbound messages to any single contact, across all agents. |
Rate limits use a sliding window — not a fixed hourly bucket — to prevent bursts at hour boundaries. If a send fails due to a platform error (such as a Teams delivery failure), the per-execution counter is decremented so the agent can retry within the same execution without paying the cap twice.
When a rate limit is reached, the agent receives a rate_limit_exceeded response and will typically report the situation to the Business Owner before stopping the current execution.
Configuring rate limits
- Navigate to Manage > Account > Settings
- Scroll to the Agent Outbound Rate Limits section
- Adjust the values as needed
- Click Save
The defaults (5 per execution, 50/hour per agent, 10/hour per contact) are appropriate for most organizations. Increase limits only if your agents are regularly hitting caps on legitimate outreach tasks. Monitor outbound activity in Monitor > Activity > Agent Activity to identify patterns before raising limits.
Related Topics
- Admin Setup Wizard - Provisioning a PA, including tool assignment
- Privacy & Governance - Admin-level controls and audit logging
- AICOS Tools Reference -
send_toand other communication tools