Need help connecting Claude, ChatGPT or Microsoft 365 Copilot to FSP? Contact Gomocha support or email support@gomocha.com.
For AI-provider account, subscription or billing questions, contact the provider. Your organisation's AI or Microsoft 365 administrator controls which connections are available to you.
Check these first
- Confirm you can sign in to the FSP portal with the same account.
- Ask your FSP administrator whether AI access is enabled and the organisation has an Advanced-or-higher licence.
- For the shared connector, use exactly
https://mcp.gomochafsp.com/mcp. Enter your environment's passphrase on the connection page, then sign in with your own FSP account. - Confirm your assistant's plan and workspace policy allow the connection. For Microsoft 365, ask your administrator whether FSP is available to your account.
Common problems
| Problem | What to do |
|---|---|
FEATURE_DISABLED | Ask your FSP representative to enable AI access for the organisation. |
LICENSE_REQUIRED | Ask your FSP representative to check the organisation's licence. |
| Passphrase not recognised | Check the code with your FSP administrator. Do not send it in a support email or chat prompt. |
| FSP is missing from the assistant | Check directory availability and workspace policy. A custom connection may be available even when there is no public listing. |
| Microsoft 365 Copilot has no FSP source | Ask your Microsoft 365 administrator to check connector enablement for your account. |
| The assistant reads data but cannot change it | Check FSP write access, your role and the assistant's supported actions. |
| Appointment search or booking is unavailable | Ask your FSP representative to check Ortec enablement, configuration and licensing. Booking also needs write access. |
| A booking was submitted but no appointment appears | Check booking status. Submission alone does not confirm an appointment. |
| A write timed out or its outcome is uncertain | Check the affected FSP record before retrying. Do not bypass duplicate protection or use a new request key. |
429 or too many requests | Pause before trying again. Avoid rapid repeated requests. |
| The assistant shows unexpected information | Confirm the connected FSP environment and account, then compare the result with the portal. |
What to include in a support request
- Organisation name and FSP environment address.
- Assistant name, account type and whether you used a directory entry or a custom connection.
- Date, time and time zone of the failure.
- Exact error message and correlation identifier, if shown.
- Steps to reproduce the problem and a redacted screenshot.
- For an uncertain write, the affected record identifier and whether a change already appears in FSP.
Do not send passwords, passphrases, tokens, client secrets, unredacted conversation histories or unnecessary customer data. Support can arrange an appropriate channel if more information is needed.
Suspected unauthorised access
Stop using the connection and contact your FSP administrator and Gomocha support promptly. Ask for access revocation or organisation-level disablement. Removing a connection does not erase information already held by the AI provider or reverse completed FSP changes.
Questions about personal data can be sent to privacy@gomocha.com. See the Gomocha privacy policy.