AI Connection

AI add-ons

Connect an AI assistant to Sparki so it can look up approved portal information before helping your team.

The AI connection uses Sparki's remote MCP server and OAuth, so access follows the portal, user, and permissions that were authorized.

The AI connection is for teams that want to use assistants such as ChatGPT or Claude with live Sparki context. Instead of copying details from the dashboard by hand, the assistant can request approved information from Sparki and use it to answer questions, prepare follow-ups, or explain what happened recently.

What You Can Ask

Projects

Ask which projects are active, what a project is for, and where to manage the project in the dashboard.

Appointments

Ask about connected agendas, upcoming availability, appointment requests, and links for managing appointment setup.

Inbox follow-up

Ask which new messages, requests, callbacks, or appointment proposals may need urgent attention.

You can also ask about customer timelines, recent interactions, documents, bids, workflow answers, configured workflow procedures, and portal statistics when those tools are enabled for the connected AI.

Good first prompts:

Try prompts like:

"What projects do we have?"

"When can someone book this project?"

"Which inbox items need urgent follow-up?"

"What happened with this customer recently?"

"Explain the procedure in this workflow."

Set Up the Connection

Open the active portal in the dashboard, then choose Add-ons. In the MCP section, open ChatGPT or Claude.

Copy the MCP server URL shown by Sparki and paste it into the assistant's custom remote MCP connector setup. When the assistant asks how to authorize, choose OAuth. If it asks for OAuth endpoints, copy the authorization and token URLs from the same Sparki setup screen.

After authorization, test the connection by asking the assistant to use Sparki before answering. For example: "Use Sparki to find recent unread inbox items that need follow-up."

Access and Privacy

The connection is scoped to the portal and user that authorized it. The assistant can only receive data returned by the approved Sparki tools and granted scopes. Sparki logs OAuth events and MCP tool calls so admins can review connected AI usage.

Use the Connected AIs section in the setup screen to review active connections. Revoke access when a connection is no longer needed, when a teammate changes role, or when you are testing with a temporary assistant account.

What the AI Should Not Do Alone

The assistant is useful for reading context, summarizing, drafting replies, and pointing your team to the right dashboard page. Important changes should still be reviewed in Sparki. If an action needs approval, such as creating or changing an appointment, use the dashboard link the assistant provides and confirm the change there.

AI integrations are currently best treated as an alpha capability for careful pilots. Start with low-risk read-only use cases, such as looking up projects, summarizing recent interactions, or preparing a draft response. Be more cautious with write actions, because logged actions do not automatically mean every destructive change can be rolled back.

Good early use cases include answering customer questions, finding available properties, looking up recent customer history, preparing support notes, and helping a team member find the right dashboard page. Scheduling or rescheduling assistance should still be reviewed by a person before the change is trusted.

Plan and Role Notes

AI add-ons are self-serve where available for the portal. Members need admin access to set up or revoke AI connections.