Skip to main content

AI tools, connectors and knowledge

These pages give AI agents things to know and things to do. They are all company settings; every change is audited. Secrets you enter (tokens, client secrets) are stored sealed and never shown again.

PageMenu pathPermission to see itPermission to change
AI toolsAdmin > AI tools (/admin/ai-tools)settings:readsettings:write
AI connectorsAdmin > AI connectors (/admin/ai-connectors)settings:readsettings:write
Product catalogueAdmin > Product catalogue (/admin/ai-catalogue)settings:readsettings:write
Knowledge baseAdmin > Knowledge base (/admin/ai-knowledge)settings:readsettings:write
MCP accessAdmin > MCP access (/admin/mcp-access)api_keys:read, api_keys:write or settings:readsettings:write for new-client rules, api_keys:write to revoke

AI tools​

A tool is a web service the agent may call during a call (book a table, open a ticket). You describe it; no code is needed.

  1. Open Admin > AI tools and choose Add tool.
  2. Set the name (3 to 48 lowercase letters, digits or underscores, starting with a letter) and the description for the model (1 to 500 characters: it decides when the agent uses the tool).
  3. Set the URL (an https address without a user name or password), the method, the parameters as a JSON object with at most 12 properties, and optionally the authentication header name, value prefix and secret.
  4. Set the limits: calls per minute (1 to 600) and timeout (500 to 15,000 ms). Add the arguments to hide in the audit.
  5. Leave The caller must say yes before the tool is called on unless the tool is harmless. The agent then reads the action back and waits for a spoken yes.
  6. Save. Up to 50 tools can exist.

To give an agent a tool, use Tools per agent on the same page: choose which tools an agent may call (up to 12 each). A disabled tool stays assigned but is not offered.

Every call, including refusals and dry runs, is recorded. Calls shows the latest 100 with outcome, status, duration and redacted arguments. In the agent test consoles a tool is never called; the console shows the request it would send.

The URL is checked when you save it and on every call: private and internal addresses are refused unless they are on the private hosts list below (or the operator allowed them for the install).

Private hosts​

If a tool must call a host inside your network, the company owner can list it under Private hosts: one name or address per line, with an optional port, at most 20. This needs the owner-only permission ai_tools:private_hosts, and the list has an effect only if the operator enabled company lists on the install (the page says so when it is not enabled). Cloud metadata and multicast addresses and URL credentials stay blocked.

Offer a tool to MCP clients​

By default a tool is for the voice agent only. The owner can tick Offer this tool to MCP clients (owner only) (needs ai_tools:private_hosts). Then an MCP client that holds ai_tools:invoke can list and call that tool. The call runs the same checks as a voice call: argument check, confirmation, rate limit, the address check and the audit entry. For a tool that needs confirmation the first call returns the read-back and a one-time confirmation_token, and nothing is sent; after the user agrees, the client repeats the exact call with that confirmation_token (valid 10 minutes, once, for the same connection and arguments). Without a valid token the tool is not run.

AI connectors​

Admin > AI connectors has two parts.

Calendar​

One connection per company, Google Calendar or Microsoft 365, so agents can find free slots, book, reschedule and cancel.

  1. Choose the provider and enter the calendar id, time zone, working hours, slot length (5 to 480 minutes), minimum notice and how many days ahead agents may book (1 to 365).

  2. Google Calendar: sign in with the Connect button. Your PBX does not ship a Google application, so you create one in your own Google account first (about five minutes, free):

    1. Open the Google Cloud console, create a project (or pick one) and, under APIs and services > Library, enable Google Calendar API (and Google Sheets API if you will also load products from a Google Sheet).
    2. Under APIs and services > OAuth consent screen, set up the consent screen. For use inside your own company choose Internal (Google Workspace) or External and add yourself as a test user. Keep it in Testing if only your own staff sign in; Google then asks you to renew the permission every seven days, so for lasting use publish the app.
    3. Under Credentials, choose Create credentials > OAuth client ID, type Web application.
    4. In this console page copy the Redirect address for your Google client (it looks like https://pbx.example.com/admin/ai/calendar/oauth/callback). Paste it, unchanged, under Authorized redirect URIs in Google and create the client. A different address (even http instead of https, or a trailing slash) makes Google refuse the sign-in.
    5. Google shows a client id and a client secret. Enter both here, choose Google as provider, set the calendar, time zone and hours, and Save. The secret is stored encrypted and never shown again.
    6. Choose Connect Google Calendar. Google asks you to sign in with the calendar's account and to allow two permissions: manage events on your calendars, and view your calendars. Tick both and continue. You return to this page and the status turns to Connection active.

    Tick Also allow reading Google Sheets before connecting if you want the product catalogue to load from a Google Sheet without pasting a token (see Product catalogue). The connection then also asks for read-only access to your spreadsheets.

    Microsoft 365 and the advanced fallback. For Microsoft 365 enter your own application's client id, client secret and tenant, and a refresh token you obtained for the calendar's account; there is no sign-in button for Microsoft. For Google you can also open Advanced: paste a refresh token instead and paste a token you obtained yourself.

  3. Save, then Test connection. The test refreshes the token and reads the next 24 hours of busy time; it writes nothing.

If Connect Google Calendar is grey, save the client id and secret first. If Google reports redirect_uri_mismatch, the address in Google differs from the one shown here. If you land back with a message that the sign-in expired, start it again: a sign-in must be finished within ten minutes, can be used once, and only by the person who started it. If you did not tick every permission, connect again and tick them all.

Agents book only inside the working hours and can change or cancel only what agents booked. If the provider revokes access the status shows that; connect Google again (or save a new refresh token) to make it active again. Disconnect asks Google to revoke the access, then removes the stored token, the connection and its booking references (if Google cannot be reached the token is still deleted here; you can also remove the app under your Google account's security settings); events stay in the calendar but agents can no longer change them or offer bookings.

Business tools​

Switch on only what you need; everything is off until you do. You can limit each group to listed agents.

GroupWhat the agent can do
CRMLook up and create leads and notes, through your CRM integration
E-mailSend e-mail, through your e-mail provider; limit per day
CatalogueSearch the product catalogue
ConfirmationsSend confirmations by SMS or WhatsApp, through the SMS service with its opt-outs; limits per day and per person and day
QuotesSend a quote of catalogue products by SMS or WhatsApp (needs Catalogue and Confirmations): the agent names the products and quantities, and the prices and the total always come from your catalogue, never from the AI. Mixed currencies and products without a price are refused

WhatsApp confirmations go out as an approved message template of your channel's WhatsApp Business account: a body-only template with exactly one placeholder ({{1}} takes the message text). Choose the channel, the template name (default mpbx_confirmation) and, optionally, its language on Admin > AI connectors. When you save, the template is looked up in your account and the save is refused with MPBX-AI-WHATSAPP-NO-TEMPLATE if no approved template of that name (and language) with one placeholder and no header or buttons exists. If your WhatsApp account cannot be reached at that moment the settings are saved, and the check happens again when a confirmation is sent.

Writes by agents need the caller's read-back confirmation and the recipient's consent.

Agents can also take payments (see Payment links), book and move appointments (see Calendar above), open helpdesk tickets and create leads through your connectors. Admin > AI analytics shows what each agent finished.

Product catalogue​

Admin > Product catalogue holds the products agents search with the catalogue tool.

  1. Choose Import and pick the source: CSV text or a Google Sheet (spreadsheet id and range; an access token for that one import, never stored, and none for a public sheet).
  2. The header row needs name (required) and may have price, stock, description and branch.
  3. Optionally tick Replace the catalogue; it applies only when the file has no errors.
  4. The result shows how many items were created, updated, skipped and removed, and lists each rejected row by line and field.

Use Search to test and Clear catalogue to remove everything.

Knowledge base​

Admin > Knowledge base holds the documents agents quote from. Attach sources to an agent in the agent editor.

  1. Choose Add a source and pick the kind: PDF file, DOCX file, web page, text or FAQ (one "question | answer" pair per line, at most 500).
  2. A web page is fetched once, now, over https only (no private addresses, no redirects). To refresh it, choose Re-index.
  3. Search test shows the best passages with their citation (source title, address and passage number).

Limits​

By default a company may keep 200 sources, 100 MiB in total and 5 MiB per document. Under Limits on the same page you see what is used now and can set your own limits, up to the server's maximum (1,000 sources, 2,048 MiB in total and 25 MiB per document). The page refuses a document larger than the total.

Beyond a limit the PBX refuses the new source with a quota error and deletes nothing. Lowering a limit below what you already store deletes nothing either: new sources are refused until you are under it again. The limits apply everywhere sources are added: this page, the AI receptionist, the daily re-read of web pages and the Notion and Confluence syncs.

Web pages, PDF and DOCX files added by address are read again once a day; a changed page replaces its text and keeps its place in every agent.

MCP access​

How to connect an assistant, what it may do and the full list of tools are on MCP: connect AI assistants and MCP tool reference.

Admin > MCP access lists the AI assistants (MCP clients) that people in your company authorized to act for them: client, user, access, when authorized and last used. Revoke stops the assistant for that user at once.

Under New clients, Let MCP clients register themselves controls self-registration, and Allowed redirect hosts (one host name per line; empty means any host) limits where they may redirect. Clients already registered keep working.

Working with the lists​

The tool, knowledge source, catalogue item and MCP grant lists work like the Users list: the ... menu at the end of a row (Calls, Edit and Remove on a tool; Re-index and Remove on a knowledge source; Revoke on an MCP grant), a search box on the catalogue, and Show more for the next page. Below 640 pixels wide the table turns into cards with no sideways scrolling. A list that cannot be loaded shows the reason and Try again.