Customer work, connected.

Help & supportMyAccount
AI assistance, CRM conversion, read receipts and attachments

Understand Mailbox Exchange AI request limits

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

This guide explains that input/output parameters.

Audience: Mailbox Exchange usersPermission: AI enabledModule v1.0.0
Jump to steps
Where to goAutomatic AI library behaviour — no separate menu route

What this guide helps you do

Know input/output parameters. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.

Follow these steps

  1. Go to the exact navigation path shown above.
  2. Select the authorised mailbox, message or configuration record.
  3. Complete the fields or action described in this guide.
  4. Save or submit once, then verify the resulting status and related record.

Fields and options

This workflow does not expose additional user-entered fields.

Rules and limits

  • Default input maximum 12000 characters.
  • Unread body maximum 3000 per message.
  • Temperature 0.4; output maximum 600 tokens.
  • Library handles max_tokens/max_completion_tokens provider variation.

Check it worked

  • The requested Mailbox Exchange record is updated through the supported controller and remains attributable to the acting staff member.

Security, audit and troubleshooting checks

  • Use the exact authorised account, role and record before saving or sending.
  • Verify the saved status and downstream record; a browser success message alone is not sufficient evidence.
  • Never expose passwords, API keys, access tokens, protected attachments or raw server paths in support tickets.
  • Do not edit module or core database records directly to bypass validation, permissions, migrations or state rules.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page