Setup and onboarding
Store connection, data sources, AI provider keys, workspace rules, and first workflow setup.
Human Support
Get unstuck faster.
Use the guided help docs first, then send a ticket with the exact facts BAAM support needs to reproduce the issue, protect your account, and route the request correctly.
Choose the right support route
Start with the path closest to the problem. This makes the ticket category and evidence clear before support receives it.
Technical issue
Broken pages, failed syncs, connector errors, missing fields, blocked automations, or unexpected output.
Account access
Login, password reset, MFA, disabled account, workspace access, or admin handoff questions.
Billing and plan
Subscription, invoices, trial access, refunds, cancellation, plan limits, or checkout questions.
Privacy, legal, security
Data access, deletion, retention, suspicious activity, policy questions, and security reporting.
Production blocker
A paid workspace cannot log in, a live connector stopped working, or a customer-impacting workflow is blocked.
Before sending a ticket
These four steps prevent back-and-forth and protect secrets.
Include the page, tab, feature, workflow, block name, provider, or account area where the issue appears.
Copy the visible readiness message, blocker, error text, last run time, or failed sync status.
Switch risky actions to draft-only, manual review, export reminder, or approval required until support confirms readiness.
Do not send passwords, unrestricted API tokens, recovery codes, card numbers, or customer-sensitive data.
Routing and response targets
Targets are operational expectations, not a separate service-level guarantee unless your plan or contract says so.
| Request type | Send this category | Include | Target first response |
|---|---|---|---|
| Paid workspace cannot access BAAM | Account Access | Account email, workspace name, login URL, exact error, MFA/reset status. | 1 business day |
| Live connector or workflow blocker | Technical Issue | Provider, workflow/block name, readiness state, last successful run, failed run time. | 1 business day |
| Billing, refund, plan, or invoice | Billing | Account email, order or invoice reference if available, plan, requested change. | 2 business days |
| Privacy, data, legal, or security | Legal / Privacy | Verified account email, request type, affected workspace, urgency, safe contact method. | 1 business day for security/privacy triage |
| How-to or implementation question | Support | Goal, current setup step, help doc section, screenshots without secrets, blocker. | 2 business days |
Send a support request
Write the message as a reproduction note. The best tickets include the exact screen, expected result, actual result, and what changed recently.
Useful ticket format
- Workspace/account email
- Feature, page, tab, workflow, block, or provider
- Readiness state, error text, or failed sync result
- Expected result and actual result
- Urgency and whether a live customer, billing, or security issue is involved