Connected AI

Connect your AI to your companies, contacts and helpdesk.

Concorbit has no assistant of its own. It speaks the Model Context Protocol, so you point a compatible client at your workspace with an endpoint and a token. Each connection carries the permissions of the person who made it, writing is off until you grant it, and you can revoke it from the page you made it on.

Why there is no assistant in here

Concorbit ships no model of its own and no chat box. There is no AI provider in the codebase at all.

That is deliberate, because the model is the part you already have and the part you are most likely to change. What is hard to bolt on afterwards is the rest of it: reaching the real records under the permissions you have already set, seeing in the workspace what was asked for, and being able to take the access away. So Concorbit provides the server, and your client connects to it.

How a connection is made

  1. 01

    Switch it on

    An administrator turns Connected AI on for the workspace. It is off until they do.

  2. 02

    Add a connection

    Name it, and choose whether it may add internal notes or create drafts. Both start off.

  3. 03

    Paste the token

    Concorbit shows the token once. It goes into that client's own configuration, alongside the endpoint.

  4. 04

    Watch what it asks for

    The workspace activity list shows what the connection asked for, with the outcome and how long it took.

What it can do

Read the records

Search companies and contacts. Open one company with a capped summary of its contacts and its open tickets. List the helpdesk queue by status, company or assignee, and open one ticket with a capped slice of its conversation. Attachments are listed by name and cannot be downloaded through the server. A search or list returns up to fifty rows with a cursor for the next page; the summaries nested inside a company are capped at ten and say when they were capped.

Draft a proposal

A proposal draft for a contact or a deal. Staff only, not emailed to the customer, not signable. It cannot set prices, though a proposal attached to a deal shows that deal's existing quote. A person reviews it and sends it.

Price a draft quote

Quote lines on a deal whose quote is still a draft. This sets what the customer would be charged, and it replaces the whole quote: a line the AI does not send is a line removed. A quote already sent, accepted or declined cannot be changed.

Add an internal note

An internal note on a contact, company or ticket. This one is live rather than a draft: it is written straight away and your staff can see it. It is never emailed to the customer and never pushed to a connected PSA. A note on a ticket also emails the assignee and the watchers, who are your own staff.

Each of these is enforced on the server, not asked of the client.

8

tools in the whole server

3

of them write, none to a customer

50

rows a search or list returns

1,000

recent calls kept per workspace

How a connection is fenced

Off by default

A workspace switches it on.

One person, one workspace

It carries their permissions.

Writing is granted

Two permissions, both off at first.

Revocable

Revoke it and later calls are refused.

Permissions, and what a connection cannot reach

A connection belongs to one person in one workspace, and it carries that person's permissions rather than the workspace's. It is pinned to that workspace when it is made, and refused if that person is no longer a member of it.

A record the connection may not read and a record that does not exist come back as the same refusal, so an agent cannot work out what a workspace holds by comparing failures.

Writing is granted separately from reading, and separately per connection. Two permissions cover the three write tools: one for internal notes, one for drafts. Both start off, and each is shown with its own consequence, because they are not the same decision: a note is written straight away and your staff see it, while a draft can set what a customer would be charged.

A successful revocation refuses everything that connection asks afterwards. A write already running may finish first. Switching Connected AI off for the workspace refuses the calls that follow, from every connection.

Current limits

No hosted connector

You connect a compatible client with an endpoint and a token, from that client's own configuration. There is no sign-in flow to Concorbit.

No ticket creation

There is no tool that creates a ticket. A new ticket is visible to the customer in the portal straight away, so it is not a draft.

Companies, contacts and tickets

Invoices, services and compliance registers are not readable through the server.

A workspace list, capped

The activity list shows the workspace's recent calls, not one connection's history, and it keeps the most recent thousand. A call refused before it is authenticated leaves no entry.

Switch it on in a trial workspace and ask your own AI what is in the helpdesk queue.

It reads and nothing else until you grant a write permission, and you revoke it from the page you made it on.