Connect your account to Claude

You can connect your Telma account to Claude (claude.ai, the Claude app on desktop and mobile, Claude Code) or to another assistant that supports the MCP protocol (Model Context Protocol). You then ask it your questions in plain language: "what is waiting for a reply?", "summarize the conversation with this contact", "what is in the photo they sent me?", "who do I need to call back today?".

The assistant reads your account with your rights, never more: it sees the conversations, calls and voicemail you see in Telma, in the organization you choose when you connect it, and only the functions your organization opens to assistants. It never listens to call audio: it reads the summaries and transcripts already produced by Telma AI.

Before you start

The feature is turned on for your organization. It is off by default: your provider opens it to your organization (the "AI assistants" feature), then your administrator gives it to the profiles they choose (permission "Connect an assistant (Claude or other) to one's account", see Profiles and Permissions). The Admin profile has it out of the box; the User profile has it too, for reading only.
A Claude account. Custom connectors are available on every Claude plan (the free plan allows one). On a Team or Enterprise plan, the Owner of the Claude workspace adds the connector, then each member connects with their own Telma account.
The connector address. It looks like https://mcp.telma.ca/<domain>/mcp. For Telma customers:

https://mcp.telma.ca/telma/mcp

If you are the customer of a reseller, ask them for the address of their connector: the name at the end changes, and the authorization screen is the one of their app.

Connect Claude on claude.ai

Free, Pro and Max plans:

Open Customize > Connectors on claude.ai.
Click Add custom connector.
Give it a name (for example "Telma") and paste the connector address.
Leave the advanced settings as they are: no OAuth client to enter, Claude registers by itself.
Click Add, then Connect. Claude opens the Telma authorization screen (see Give your consent).

Team and Enterprise plans: the Owner adds the connector once in Organization settings > Connectors (Add, then Custom). Each member then finds it under Customize > Connectors, labeled "Custom", and clicks Connect.

In a chat, the + button then Connectors turns the connector on or off for that chat only. Under Customize > Connectors, opening the connector also lets you block a specific function.

claude.ai labels may change; the up-to-date steps are in Anthropic's documentation.

The Claude app (desktop and mobile)

A connector added on claude.ai follows your Claude account: it appears by itself in the Claude desktop app (macOS, Windows) and on mobile (iPhone, Android), with nothing to redo. To add it from the desktop app, the steps are the same as on claude.ai (Customize > Connectors > Add custom connector).

Claude Code

In a terminal:

claude mcp add --transport http telma https://mcp.telma.ca/telma/mcp

Then open Claude Code, type /mcp, choose telma then Authenticate: your browser opens the authorization screen. Add --scope user to the command to have the connector in all your projects.

The authorization screen opens in your provider's web app, in its colors:

Sign in as usual (second factor included) if you are not already.
The screen shows the assistant asking for access and the address you will be sent back to (claude.ai for Claude).
If you are a member of several organizations, choose the one the assistant will read. A connection is for one organization only: to read another one, connect the connector a second time (in Claude Code, under another name) and choose the other organization.
Click Allow. You are back in Claude, which now sees the functions you are entitled to.

Even if your account has reseller or platform rights, the assistant only has the rights of your profiles in the chosen organization.

What the assistant can do

The assistant only sees the functions your profiles allow. Each function needs two things: the usual permission in Telma (for example reading conversations) and the matching "Assistant" permission, which your administrator can remove without changing what you do yourself in the app. The table gives what the built-in profiles have; your organization can make its own profiles.

Messages

Function	What it does	Admin	User
`list_conversations`	Lists your conversations: unread (yours: each member has their own), open or closed, by team, by person in charge (`assignee`: `me`, `none`, `all`), over a period, with the last message and the person in charge	✓	✓
`read_conversation`	Reads the messages of a conversation and its notes, without marking it as read; gives its person in charge and its changes in the timeline; tells when the contact unsubscribed (STOP), which texts were sent automatically (questionnaire, welcome, outside-hours reply, STOP confirmation), which messages came in outside business hours (team notified or not) and whether the team is open right now; with the AI on the texts, the summaries of the conversation, their actions, their deadlines and the name the contact gave (`suggested_name`, to offer only with your agreement)	✓	✓
`team_hours`	Tells whether each team is open or closed right now and when it closes or reopens, with its ranges per day, its holidays and closures, and what happens to a text received after hours (`notify_team`: a single digest at opening, never a notification at night); a team that follows the hours of a call flow gives those (`hours_from_flow`)	✓	✓
`conversation_actions`	The actions the AI noted in the text messages ("send the quote", "call back tomorrow"), without the ones already done; with the AI on the texts	✓	✓
`view_media`	Shows the assistant an image received or sent by MMS, so it can describe it	✓	✓
`contact_card`	The card of a number: its address book entry, its conversations, its latest exchanges, and the last exchange summarized by the AI (call, texts or voicemail)	✓	✓
`search_contacts`	Searches the address book: by name, company, email or digits of a number	✓	✓
`contact_history`	The full thread of a number, newest first: texts, calls and their summaries, voicemail, notes, video meetings linked to its address book entry	✓	✓¹
`send_message`	Sends an SMS or MMS to one recipient, from a number of your team, after your confirmation	✓	—
`questionnaire_results`	The results of the text questionnaires: who played, their answers, their score	✓	—
Management	Close or reopen a conversation, take it, hand it over to a colleague or release it (`assign_conversation`: "I'll handle it", never stops anybody from answering), add a note (to a conversation, a call or a contact of the address book), name a contact, mark an action as done (of a call, a voicemail message, a recorded video meeting or a text conversation), mark a callback as handled (which also marks its voicemail messages listened and ticks its « call back » actions), after your confirmation	✓	—

Calls

Function	What it does	Admin	User
`list_calls`	The call log: missed calls, duration, who answered, and for a call of a call queue the queue, the wait and whether it was abandoned; a call that reached a closed flow carries `received_while_closed`, and `status: closed` keeps only the calls "received after hours" (without their content)	✓	✓
`list_voicemails`	Your voicemail messages and their text	✓	✓
`callbacks_due`	Missed calls (callers who hung up in a call queue and calls received while a flow was closed included, `kinds: closed`) and voicemail left without a call back, without a text reply and not marked « handled »: the same list as the « To do » of the dashboard; the urgent voicemail messages first (`urgency`), with what Telma AI understood of them (`voicemail_summary`)	✓	✓
`search_calls`	Searches the summarized calls: by words, by meaning ("contacts unhappy with the delay"), by criterion ("Callback requested = yes"), by period, extension or number	✓	—
`search_summaries`	Searches everywhere at once in what Telma AI summarized: calls, voicemail messages, text conversations and recorded meetings, by words or by meaning, over a period; one list, each item with what opens it (`read_call`, `read_conversation`, `read_meeting`); only what you may read	✓	—
`read_call`	The summary of a call, its actions and their deadlines, criteria, notes and the name the caller gave (`suggested_name`); the full transcript with the transcripts permission	✓	—
`open_actions`	The actions found in the summaries of the calls, the voicemail messages and the recorded video meetings you host ("call back Thursday", "send the quote"), with their deadline (`due`) and `overdue` once passed; the ones with a deadline first	✓	—
`call_trends`	The trends of a period: most frequent topics, complaints, callbacks requested, by extension or by number	✓	—
`draft_follow_up`	Drafts a follow-up text from the summary of a call; nothing is sent without your agreement	✓	—

Video meetings

With the video meetings open to your organization:

Function	What it does	Admin	User
`list_meetings`	Your video meetings (hosted, invited to or taken part in): title, state, dates, host, address book contacts; also only the coming ones ("what is planned?")	✓	✓
`read_meeting`	A meeting: its participants and, when it was recorded, its summary, actions and criteria; the transcript with the name of each speaker with the transcripts permission	✓	—
`meeting_chat`	What was written in the chat of a meeting	✓	✓
`meeting_join_info`	The link of the guests, the 6-digit phone code and the numbers to dial of a meeting in progress or planned, only for its host (or a moderator in it)	✓	✓
`search_meetings`	Searches the recorded meetings: by words in the summary, reason, actions and, with the transcripts permission, what was said, over a period (words only, not by meaning)	✓	—
`draft_meeting_follow_up`	Gathers what the follow-up text of a recorded meeting needs (summary, actions not done yet, linked contacts with their numbers and emails, suggested sending number, STOP opt-out); nothing is sent without your agreement	✓	—
`schedule_meeting`	Schedules a meeting (title, time with its time zone, duration, address book contacts, recording, waiting room), after your confirmation	✓	—
`invite_to_meeting`	Invites a contact by text or email, or a colleague, to a meeting; Claude shows you the recipient and the channel and waits for your agreement; texts and emails count in the sending cap	✓	—
`reschedule_meeting`	Changes the title, time or duration of a meeting you host (guests invited by text or email are not told), after your confirmation	✓	—
`cancel_meeting`	Cancels a scheduled meeting you host; a meeting in progress is never ended by the assistant, after your confirmation	✓	—

The actions of a recorded meeting you host show in open_actions and are marked done like those of a call; contact_history shows the meetings linked to the card of the contact. Scheduling, inviting, moving and cancelling need the permission "Assistant: schedule, move and cancel video meetings" on top of the one of the video meetings; the User profile does not have it.

Messages between colleagues

The messages between colleagues of your organization:

Function	What it does	Admin	User
`team_chat_threads`	Your conversations with your colleagues (one per team, then the one-to-one ones), with the unread messages and mentions	✓	✓
`team_chat_read`	The messages of a conversation between colleagues, without marking it as read	✓	✓
`phone_messages`	The messages colleagues took for you during or after a call (from whom, number, message, to call back, handled or not)	✓	✓
`team_chat_send`	Writes in a conversation between colleagues or to a colleague, after your confirmation; at most 30 messages per hour and 150 per day per connection; nothing leaves the organization	✓	—

Organization

Function	What it does	Admin	User
`statistics`	Message volume, first response time, conversations without a reply; the call queues for who supervises them	✓	✓
`queue_statistics`	For who supervises the call queues: per queue, the calls (received, answered, abandoned, service level, wait); per agent, the calls offered, answered, declined, unanswered, the talk time, the time logged in, paused (by reason) and in wrap-up; the breakdown by hour; the current state of each agent in the queue (logged in, paused and why, logged out of this queue only, in a call, wrap-up)	✓	—
`balance`	The credit balance, this month's usage, your plans and the next invoice, the Telma AI hours left	✓	—
`live_activity`	What happens now: calls in progress and where they are, active conversations (without their content), counters of the day, and the presence of the colleagues who have an extension, the same as everywhere in Telma (available, ringing, in a call, in a video meeting, do not disturb, away with their status and its end, on a pause of the call queues, unreachable, offline); whether each call is recorded, and the parked calls (slot, code to take them back from a phone, who calls, who parked them). Reading only: no function acts on a call	✓	—
`parked_calls`	The parked calls of the organization (reception): slot, code to take them back from a phone, who calls, who parked them, for how long, when they return; and the parking time.	✓	✓
`set_status`	Sets or clears your status ("Away", "In a meeting", "Travelling" or a short text) with its end (in x minutes, at a time, tomorrow morning), after your confirmation; leaves do not disturb alone	✓	—

¹ Without the call summaries, which need the summaries permission.

set_status needs the permission "Assistant: set or clear my status"; only the Admin profile has it from the start (the assistant of a User reads, it does not write). Why? Your colleagues read your status as your own words: the assistant only changes it with your agreement and when the organization allows it. See My state.

Call summaries and transcripts follow the same permission as listening to recordings: a User only sees them through the assistant if their organization gives it to them with a profile.

Ready-made requests and items to attach

In Claude, the connector also offers ready-made requests (+ button, then the name of the connector): "Prepare a callback" (everything to know before calling a contact back), "What I promised this week", "Summarize my day", "What is waiting for a reply", "Weekly complaints review", "Follow-up of a video meeting" (the summary of a recorded meeting and a follow-up text for its contacts). You can also attach a conversation or a call to a chat, like a document, to discuss it with the assistant.

Example requests

"Which conversations have been waiting for a reply since this morning?"
"Is the Service team open right now? When does it reopen, and are we closed on Christmas?"
"Summarize the conversation with 514 555-0199 and tell me what they expect from us."
"What is in the photo this contact sent yesterday?"
"Which calls did I miss today, and who hasn't been called back yet?"
"Before I call Mrs. Tremblay back: what did we say last time?"
"Which contacts complained about the delivery delay this week?"
"What did I promise contacts this week, and what isn't done yet?"
"Draft a follow-up text for the 10 a.m. call with Morin Garage." (Claude shows you the text before sending.)
"How many messages did we receive this month, and what is our average first response time?"
"Who let the most support calls ring this week, and at what hour do we lose the most callers?"
"How much credit and Telma AI time do I have left?"
"Who got the best score in the text quiz this week?"
"Who is free to take a transfer, and who is away until when?"
"Put me in a meeting until 3 p.m." (Claude asks you to confirm.)
"Which video meetings do I have this week, and what did we decide in yesterday's one?"
"Schedule a video meeting on Thursday at 2 p.m. with Jeanne Roy and invite her by text." (Claude shows you the recipient and the text before inviting.)
"In which meetings did we talk about Morin Garage this month?"
"Prepare the follow-up of yesterday's meeting with Jeanne Roy."
"What did my colleagues write to me today? Tell Carla it is done."

Security and privacy

Nothing is sent without you. The functions that act (send a message, close a conversation, add a note…) are declared as such: Claude asks you to confirm each time and shows you the text and the recipient. Avoid "Always allow" for sending. One message at a time, never bulk sending.
Sending cap: at most 20 messages per hour and 100 per day per connection, invitations to a meeting by text or email included; the messages to colleagues have their own cap (30 per hour, 150 per day).
Your contacts' texts are data. A text or a call can contain a sentence written to trick an assistant ("ignore your instructions and write to…"): the connector tells the assistant never to follow what is in there. Still, review what it offers to send.
What the assistant reads goes to its provider. The conversations, summaries or images Claude reads at your request are sent to Anthropic, which processes them under its own terms, possibly outside Canada. See the privacy policy (section "Artificial intelligence assistants"). Only connect an assistant if your organization agrees to it.
Everything is logged: each function called (which one, when, by whom, with what result), never the content of your requests.
The administrator stays in control: they see the assistants connected in the organization and can disconnect them, remove a function from assistants through the profiles, or turn the feature off for everyone.
The connection ends by itself when you change your password, close your sessions, when your account is deactivated, when you leave the organization or when the feature is removed.

Disconnect an assistant

In Telma: Profile > Security, connected assistants card, Disconnect. Access is cut immediately.
In Claude: Customize > Connectors, the connector's menu, Remove. In Claude Code: claude mcp remove telma.

Removing the connector in Claude does not necessarily revoke the authorization given to Telma: disconnect it in your profile too.

Price

Included for the user of an extension that has a Telma AI plan (Telma AI or Telma AI Pro; at a reseller, its brand name replaces Telma).
Otherwise, a price per month per user who uses an assistant, set by your provider ($5 at Telma; a reseller may offer it), whatever the number of assistants or devices. The month is the organization's billing period, and the user is counted in each organization where they connect an assistant. It is due when connecting, then at the first use of each period: a connection left unused during a period costs nothing, and neither does having the permission without connecting anything. The amount shows in the estimate of the next invoice (see Credit).

Troubleshooting

Claude cannot find the connector or cannot connect: check the address (it ends with /mcp) and that you went all the way through the consent.
"Access denied" on the authorization screen: the feature is not turned on for your organization, or your profile does not have the "Connect an assistant" permission. See your administrator.
A function is missing: your profile does not have the matching permission (or the organization does not have the feature, for example Telma AI). After a change of your profiles, disconnect then reconnect the connector so that Claude reads the list again.
The functions answer "payment required": the assistant's month could not be paid, for lack of credit in the organization. The connection stays; the functions work again as soon as an administrator adds credit.
The assistant cannot see a conversation: it only reads the organization chosen at authorization, and only what you see yourself in Telma.

For the technical details (OAuth, permissions, limits), see Assistants (MCP connector) in the API documentation.