Contact and Escalation

How to contact Beaverly support effectively

Clear reports reduce back-and-forth and speed up resolution. This page gives a support-ready checklist.

Article type: Task Last reviewed: March 12, 2026

What to include in every support request

  1. Account identifier: email used for sign-in.
  2. Issue type: login, connection, instruction, status, billing, or usage.
  3. What you expected: one sentence.
  4. What happened: one sentence.
  5. When it happened: date and timestamp with timezone.
  6. Flow context: event types or warning labels.

Issue-specific details

Billing question

  • Plan name at time of issue.
  • Billing date and amount.
  • Expected billing behavior.

Environment issue

  • Environment provider name.
  • Connection state shown in app.
  • Last successful connected timestamp.

Instruction issue

  • Instruction name or ID.
  • Current status label.
  • Last observed lifecycle event.

No-activity issue

  • Expected activity window.
  • Current status and capacity state.
  • Most recent relevant Flow event.

How to ask clearly

Use this format:

Template: "I expected [outcome], but I saw [observed behavior] at [timestamp]. Instruction [name/ID] in environment [name] is now [status]."

Escalation guidance

  • If issue blocks activation or account access, label your request as "Access blocking".
  • If issue affects billing, include "Billing" in subject line.
  • If issue affects organization workflows, include "Enterprise" in subject line.