Vight documents every service call for managed service providers (MSPs) and keeps your professional services automation (PSA) tickets alongside them. The Vight connector uses the Model Context Protocol (MCP) to let Claude, ChatGPT or Microsoft Copilot search that history and answer from it, with the same access each person already has in Vight.
Sarah Chen fixed it on a call with Mark Delgado on October 7. Outlook stopped sending after Mark changed his Microsoft 365 password.
Source: ConnectWise ticket #48213 (time entry 0.1h) and the call of October 7.
Example shown with fictional sample data.
Ask in plain English. The assistant searches Vight when the answer lives in a past call or ticket.
"How did we fix Harbor Point's Outlook issue last time?"
Finds ticket #48213 and reads its notes and time entries.
"Did anyone from Acme mention upgrading their server this quarter?"
Searches Acme's calls in that date range and quotes the transcript.
"What did we promise Contoso about their renewal?"
Pulls the call where it came up and the part of the conversation that matters.
"Which open tickets for Northwind mention the VPN?"
Filters to open tickets for that client and lists what each one says.
Built for client data that cannot leak between people or clients.
Two tools: search and fetch. Nothing can create, edit or delete a call, a ticket or any other record in Vight.
People only get the calls they can already open in Vight, and tickets only with the Tickets permission.
An MCP search permission on each account type decides who can connect. Only admins have it by default.
People connect by signing in to Vight with Microsoft or Google. There is nothing to install and no key to share.
Vight hands call text to the assistant marked as source data, not as instructions to follow.
Works with
https://app.vight.ai/api/mcpConnect in minutes, with the permissions your team already has.