Visitor
Troubleshooting and FAQ
Resolve common account, practitioner, connection, PocketFSM, advice and PEMF issues.
Last updated: 10 October 2026
Objective
Provide a first response to common problems before contacting support.
Requirements
- Note the account email.
- Identify the affected page and action.
- Never send patient or banking data to support.
Steps
- Check spam for missing email.
- Use password reset when needed.
- If practitioner tools are missing, check the active Pro subscription and saved practitioner declaration separately.
- If FSMPro is missing, also check the saved FSM-training attestation and purchase state.
- If an FSMPro payment remains pending, wait for Stripe confirmation and review the payment history before starting another purchase.
- Renew security-code verification only when a protected practitioner workflow requests it.
- Refresh and check Dashboard > Subscription for locked content. If the subscription is suspended, restore it there; practitioner connections and advice remain unavailable until it is active again.
- For an expired invitation or unavailable connection, use Connections and have the practitioner resend it when needed.
- For a PocketFSM device-limit error, revoke an unused installation from Subscription.
- For advice missing from fsm.care, verify that advice and connection are active, then synchronize PocketFSM again.
- For a blocked PEMF export, fix the first validation error and check every enabled pair.
Tip
A screenshot without sensitive data helps support.
Caution
Never send card numbers or patient text to support.
Common issues
- Include the page, approximate time, browser and displayed message.
- For catalog content, include the exact title.
- For the Repertorizer, state whether the issue affects Kent rubrics, materia medica or infoceutic linking.
- For Connections, include the displayed state without forwarding the private invitation link.
- For PocketFSM, include the device label, platform and application version but never the installation secret.
- For the PEMF editor, keep a JSON copy and include the first validation message.