Ask questions about your field service work using live FSP data. Gomocha FSP connects compatible AI assistants to orders, customers, assets, materials, stock and engineer schedules. Where your organisation and assistant permit changes, you can also create records, update orders, add notes and assign work.
The connection acts with your FSP account's permissions. Your organisation controls whether AI access and write tools are enabled.
Before you connect
You need:
- An active FSP account and your organisation's approval to use the chosen AI assistant with FSP data.
- An Advanced-or-higher FSP licence and AI access enabled for your organisation. Contact your FSP representative if either is missing.
- Your environment's FSP passphrase, provided by your FSP administrator.
- An assistant account and workspace policy that permit the connection. Microsoft 365 users also need their administrator to make the FSP connector available.
Write access is a separate FSP setting. Enabling AI access alone does not enable changes. Available actions also depend on your FSP role and the assistant you use.
Connector address
Use this address when your assistant asks for the MCP server URL:
https://mcp.gomochafsp.com/mcp
The same address serves multiple FSP environments. The passphrase selects your environment; you then sign in with your own FSP account and review the requested access. The passphrase does not grant account permissions.
Connect from Claude
- Open Claude's connector settings. If Gomocha FSP appears in the directory, select it. Otherwise, add a custom remote MCP connector using the address above.
- Use OAuth sign-in and automatic client registration if Claude asks how to register. Do not paste passwords or access tokens into request headers.
- Connect. Enter the FSP passphrase on the Gomocha connection page.
- Sign in with your normal FSP account and approve the requested access.
- Start a chat and ask: "Using FSP, list my unplanned orders for this week."
Menu names and availability can vary. See Claude's connector instructions.
Connect from ChatGPT
- Open ChatGPT's app or plugin settings. If Gomocha FSP is listed, select it and connect. Otherwise, use the custom MCP connection option available to your account, with the address above. Your workspace administrator may need to enable this option.
- On the Gomocha connection page, enter the FSP passphrase.
- Sign in with your normal FSP account and approve the requested access.
- Ask: "Using FSP, show this week's unplanned orders."
If the connection option is missing, check your plan and workspace policy. See ChatGPT's connected-app instructions.
Connect from Microsoft 365 Copilot
Your Microsoft 365 administrator must first make the FSP federated connector available to your account.
- Open Copilot Chat, then Settings and Sources.
- Find FSP and choose Connect.
- Enter your FSP passphrase, sign in with your FSP account and review the requested access.
- Ask a read-only question and compare the result with the FSP portal.
Available Copilot experiences and actions depend on Microsoft's rollout and your tenant configuration. Confirm support with your administrator before relying on write actions. An administrator-enabled connector does not mean that Gomocha FSP is published in Microsoft's public gallery. See Microsoft's federated connector guide.
Try a useful question
- "Show the open orders and assets for this customer."
- "Which materials have low available stock?"
- "Show this engineer's schedule for tomorrow."
- "Draft an order note for my review. Ask me before saving it."
Review the assistant's answer against the relevant FSP records before making an operational decision. AI-generated summaries can omit context or contain errors.
Making changes
Write tools require your organisation to enable write access and your account to have the required permissions. Creating orders and accessing planners' engineer lists require a planner account.
FSP validates writes. An overridable warning requires an explicitly confirmed follow-up call; a hard validation error cannot be overridden. Your assistant's permission settings determine when it also asks for approval, so review those settings before enabling unattended actions.
Appointment proposals and timeslot booking require Ortec scheduling to be enabled, configured and licensed. Booking also requires write access. Without Ortec, permitted users can still read schedules and assign an order through normal planning validation. A submitted booking is not confirmed until its booking status shows completion.
If a write times out or returns an uncertain outcome, check the affected record in FSP before repeating it. Repeating a request can create a duplicate. Do not ask the assistant to bypass duplicate protection by using a new request key.
What happens to your data
The assistant sends tool requests to FSP and receives the results needed to answer you. Those results can contain customer, contact, location, order or engineer information. This information leaves FSP and is processed by your selected AI provider under its own agreement, privacy policy and account settings. FSP permissions restrict which records the connection can access; they do not keep returned information out of the assistant's systems.
The shared Gomocha gateway routes requests to your environment. Its MCP access log records request metadata, including the tool name, destination, outcome, timing and correlation identifier, rather than tool arguments or response bodies. FSP records operational activity and, for writes using duplicate protection, stores request hashes, status and completed results in your environment. Disconnecting does not erase these records or information already held by the AI provider.
Review the Gomocha privacy policy and your organisation's rules for AI use. Ask your administrator about the AI provider's retention, training and regional processing settings before connecting sensitive data. Do not enter passwords, passphrases or tokens in a chat.
Direct connection for your environment
If your organisation does not permit use of the shared gateway, ask your FSP administrator for your environment's direct MCP address. It is the environment's API address followed by /mcp.
Add that address as a custom connector in a compatible assistant. You sign in directly to the environment without the shared gateway's passphrase step. Your account permissions and organisation settings still apply. The assistant still receives tool results, so this option does not remove the need to approve the AI provider's data handling.
Disconnect or change environments
Remove or disconnect FSP in your assistant's connection settings. To use a different FSP environment, reconnect and select it with its passphrase. Ask your administrator to disable FSP AI access if the organisation needs to stop further use. For suspected credential exposure, contact support and request access revocation; do not rely on closing a browser tab.
Get help
Contact Gomocha support or email support@gomocha.com. Include your organisation, assistant, error message and time of the problem. Remove credentials and sensitive customer data from screenshots and logs.