Support, troubleshooting, and known issues

Trial and migration known limits

Some launch-surface answers remain orientation-first, so this article makes the known limits explicit instead of letting confidence drift too far.

Who this is for: Trial users and evaluators hitting the edges of the current launch shell.

Last reviewed 2026-04-29 · Source of truth: launch shell · Languages: en, es

Before you start

Use this article when the current help surface feels too high level for a real migration, billing, or setup decision.

Article metadata

Product area: known issues and launch limits

Owner: Launch readiness

Parity reviewer: Bilingual launch review

Retrieval-ready: Yes

What to expect next

Request a guided demo if the real blocker is migration or stakeholder confidence.
Use support intake when the issue is sensitive or product-specific.

What is intentionally still thin

The current launch shell is strong on evaluation posture, pricing explanation, and escalation boundaries, but not yet a full church operations product.

Some deeper onboarding, migration, and support operations behaviors are still later tranches rather than live launch-surface workflows.

How to respond when the article is not enough

Do not over-read a thin launch article as a full implementation promise.

Move into the matching structured route when the next decision needs more precision than the current article family can safely provide.

Escalation path

If the question needs real implementation-specific certainty, escalate instead of treating the launch shell as more complete than it is.

Related next steps

Open support assistant Open structured support intake Request guided evaluation Open Spanish version Back to help center