Contact and Escalation

Tell us what happened. Keep passwords out of it.

A short expected-versus-observed description, approximate time, provider and trading-account context, and a user-visible warning are usually more useful than a long technical guess.

Article type: Task Last reviewed: October 3, 2026

What to include

  1. Your Beaverly account email.
  2. What you expected. One or two sentences.
  3. What happened instead. One or two sentences.
  4. When it happened. Approximate date and time with timezone.
  5. Relevant context. Provider and trading-account name, conversation or goal description, active-work description, or billing tier when applicable.
  6. User-visible evidence. A warning message, Report Back details, screenshot with sensitive information removed, or other visible state that helps identify the problem.

Never send these

Keep secrets private: do not send passwords, OTP/MFA codes, recovery codes, private keys, full payment-card details, banking secrets, provider authentication secrets, or identity documents unless an official Beaverly process explicitly requires a particular document through an approved secure channel.

Beaverly support does not need your broker password to troubleshoot Chilla.

Provider issue or Chilla issue?

Provider-specific

Trading-account verification, provider outages, deposit/withdrawal processing, provider fees and provider-imposed restrictions normally belong with the provider.

Chilla-specific

Conversation problems, Chilla web assistance, trading-account connection state inside Chilla, authorization, Report Back, Work Capacity, Beaverly billing and other Chilla behavior belong with Beaverly support.

How to write the report

Example: “At about 3:20 PM WAT I expected Chilla to continue after I completed the provider login myself. Chilla still says the trading account needs attention. The affected provider is [name]. I have attached a screenshot with account details hidden.”

Urgent access or security problems

If you believe your Beaverly account, connected trading-account access or device session may be compromised, secure the affected account first, pause or stop live work where appropriate, revoke provider access if needed, then contact the relevant support/security channel.

For a suspected Beaverly security vulnerability, use security@beaverlyai.com rather than publishing exploit details publicly.