Fast help for setup, access, reporting, and data issues

Help Center for Lotus Beta Analytics

Get answers quickly with step-by-step guides and proven troubleshooting. If you’re blocked, submit a ticket and our support team will work with you to restore access and keep your analytics running smoothly.

  • Account access & role permissions
  • Dashboards, reports & filters
  • Data sources & integrations
  • Security, SSO & API access
Help Center

Guides organized by what you’re trying to do

Start with the category that matches your issue. Each section includes the most common fixes and the details support will ask for if the issue needs escalation.

Login & Access

Reset passwords, resolve “access denied”, verify roles, and troubleshoot SSO sign-in.

Password reset Invite users SSO

Dashboards & Reports

Fix loading issues, align filters, validate calculations, and resolve report mismatches.

Filters Permissions Export

Data & Refresh

Understand refresh schedules, investigate missing rows, and confirm expected vs actual results.

Refresh schedule Data latency Schema changes

Integrations & API

Connector setup, API tokens, webhook verification, and troubleshooting authentication errors.

API auth Webhooks Connectors

Security & Compliance

Access policies, audit trails, IP allowlists, and recommended security configurations.

MFA Audit Policies

Billing & Workspace Admin

Manage workspaces, ownership, seats, invoices, and admin-level settings responsibly.

Workspace Seats Invoices
Support Ticket

Submit a ticket and we’ll take it from there

The fastest resolutions come from clear context. Include what you expected, what happened instead, and any steps that reproduce the issue.

Create a ticket

This button opens your email client and sends the ticket to support@lotusbetaanalytics.com. You can replace this with your own ticket API anytime.

What we need to diagnose quickly

  • Where: workspace, project, report/dashboard name, dataset name
  • What: expected result vs actual result
  • How: steps to reproduce (click-by-click if possible)
  • When: timezone + timestamps of the last known good state
  • Evidence: screenshots, error IDs, sample request/response for API issues
Email: support@lotusbetaanalytics.com Response updates by email
Response Times

Clear expectations for support and resolution

We prioritize tickets by severity and business impact. When you submit a ticket, you’ll receive confirmation and updates by email.

Typical first response targets

  • Critical: as soon as possible during active coverage
  • High: same business day when received early
  • Normal: within 1–2 business days
  • Low: best effort based on queue

If your issue is time-sensitive, include “Critical” and provide a direct reproduction path to reduce back-and-forth.

Common quick fixes

  • Sign out and sign back in to refresh permissions and sessions
  • Confirm you’re in the correct workspace and have the required role
  • Validate dataset refresh time and whether upstream schema changed
  • For API issues, re-check token scope and token expiration

If you suspect an outage, submit a ticket with and include timestamps and impacted features.

FAQ

Common questions

Answers to the most frequent support questions for Lotus Beta Analytics.

How do I create a support ticket?

Use the ticket form above. Provide the workspace/project, what you expected vs what happened, and any error messages. You’ll receive a confirmation email and ongoing updates until the issue is resolved.

What should I do if I can’t log in?

Confirm your email address, try a password reset, and check whether SSO is required for your organization. If you receive “access denied,” request the correct role or workspace access from an admin, then try again.

My report numbers don’t match—what details help?

Share the report name, filters applied, the metric definition, the timeframe, and the source data reference. Include screenshots showing the discrepancy and a sample record if available.

Can support help with connectors, APIs, or webhooks?

Yes. Include the endpoint, authentication method, token scope, and a sample request/response. If it’s a webhook issue, include the verification method and the payload you receive.