Support guidance for Pairnt's launch-stage shell
Pairnt is meant to reduce stress, not create it. This page explains how to think about support in the current launch release, especially around sign-in, case access, durable records, and workflows that are intentionally not fully automated yet.
Launch posture
Support expectations at launch
This support page sets expectations for an early premium product: Pairnt should feel calm and well-considered, but support operations are still launch-stage and not positioned as emergency coverage.
- There is no public promise of 24/7 support, live emergency triage, or legal guidance in this repo.
- If you cannot sign in, start with your email inbox and magic-link flow before assuming the case data is unavailable.
- If a workflow logs a request rather than delivering an artifact immediately, treat that as current product behavior, not a one-off outage.
Launch model
Best-effort support
Fastest self-check
Email + session
Emergency response
Outside Pairnt
Common issues
Most early issues in the current shell fall into a few predictable buckets.
- Magic-link sign-in problems, including using the wrong email address or opening the link on a different device.
- Access confusion caused by missing case membership, invite timing, or a role that does not expose every module.
- Expectation gaps where a page records an export request, call log, or other durable event without immediately producing a final artifact.
What to include when asking for help
Clear issue reports make launch support much faster and reduce the risk of misreading sensitive case activity.
- The page or workflow involved, such as sign-in, messages, calendar, expenses, records, calls, exports, or trust.
- The rough time of the issue and what you expected to happen compared with what actually happened.
- Whether the issue affects access, data visibility, or a workflow that already created a durable timestamped record.
What support does not cover
Pairnt support can help explain product behavior. It is not a substitute for emergency, legal, or clinical help.
- Urgent safety concerns, welfare checks, or time-sensitive emergencies.
- Legal strategy, interpretation of court orders, or advice about what you should say to another party.
- Guarantees that every early-release workflow can be reversed or hidden after it has created a durable shared record.
If you are deciding whether something is broken or simply not automated yet, compare the page language in the product with the explanations on this site. Several flows in Pairnt are intentionally honest about recording requests or operational facts before a richer delivery layer exists.
If you are already signed in, the most useful operational explanation lives on the in-app trust surface, which is tailored to current authenticated behavior rather than generic marketing copy.
Keep reading Pairnt honestly
Use this page to calibrate what help should look like
Support works best when the issue report matches the product's real behaviors: what page you were on, which case workflow you were using, and whether you were expecting a durable record, a queued request, or a fully automated result.