Assistly for Enterprise

Your team’s calls, one shared memory

Every call anyone takes becomes context the whole team can ask — grounded in your own docs and tickets, and readable from Claude, ChatGPT, or Cursor without leaving them.

The essentials

What everyone asks first

01

Nothing joins the call

No bot in the participant list, no meeting integration for IT to approve, and no change to how anyone runs a call. Assistly works from the computer's audio, alongside Zoom, Meet, Teams, Webex, or a phone call.

02

Your conversations stay yours

Never used to train shared or foundational AI models, never sold. Your workspace sets how long anything is kept, and any session or recap can be deleted outright.

03

Live in days, not quarters

People download the app and sign in — that's the deployment. We set up the workspace, single sign-on, and retention with you, then help you bring in the first team.

Shared context

Everything your team knows, one thing to ask

A team space is the shared half of Assistly: every call, recap, action item, and project the team touches, plus the docs and tickets you connect to it — one context, in one place, instead of nine laptops with nine sets of notes.

  • Everyone in, nothing to relearn. Invite the team and the app is the app they already know — same overlay, same calls, same hotkeys. What changes is where the work lands.
  • Shared projects, not personal folders. An account belongs to the team, not to whoever happened to take the call. Anyone working it opens the same thread of history.
  • Ask the whole team's history. “What did Acme say about the renewal?” — answered from your team's calls, with the meeting it came from cited, whoever was on it.
  • Your own tools are part of the context. Connect Notion, Linear, or any MCP server to the workspace and the shared context carries your real specs, tickets, and pricing — so live guidance is built on them, not on a model's guess at them.
  • New people start from real calls. Context that used to live in someone's head is in the workspace: the last five calls with the account, what was decided, and what's still open.

Nobody writes a handover doc. The shared context is the handover.

Revenue team12 people · 4 projectsDRKMAO+9
  • Acme Corp · Renewal call · Dana

    Legal sign-off by Fri

  • Globex · Technical review · Kim

    Send SSO docs

  • Initech · Discovery · Alex

    Pricing follow-up

Acme pushed the renewal to Q1 — pricing was agreed, legal is the blocker.

From 3 calls across the team · Jul 14 – Aug 19

Pulling from

Team callsNotionLinearGoogle Calendar

Projects

Every account, one thread

A project is a client, a deal, or a workstream — and in a team space it belongs to the team. Calls land in it from the calendar, and every answer about that account comes from its own history.

  • Calls file themselves. Tell a project its meetings, its people, its company. From then on the calendar decides where a call belongs, and a single dismissable notice offers the switch when it's a different account.
  • Answers stay inside the account. Ask a project a question and it draws on that project's calls, cited — never another client's. Nothing crosses between accounts.
  • Handoffs stop being meetings. Someone picks up an account they've never touched and the history is already there — every call, every decision, every open item with an owner.

Acme Corp

Shared · 5 teammates · 23 calls

Open items

  • Send staging credentialsDana
  • Security questionnaireKim
  • Confirm Q1 start dateAlex

This call matches Globex

SwitchDismiss

MCP, both directions

Fits the AI stack you already run

Assistly speaks MCP in both directions — your team’s tools feed the shared context, and the shared context feeds your team’s tools. So the calls never sit stranded in another notes app, and the guidance on the call is built on your own documents. Nothing has to be replaced to make either one true.

Into Assistly

Your docs, live on the call

Connect the tools your team already runs and the shared context grows to include them — so live guidance is built on your real specs, tickets, and pricing, not on a general model's guess at them. Nothing moves, nothing gets re-hosted.

NotionLinearGoogle CalendarAny MCP server
Out of Assistly

Your calls, in every other tool

Assistly runs its own MCP server, so the team's shared context is readable from inside whatever they already work in — no export, no copy-paste, no second place to check. One URL, no API key: sign in, click Allow.

ClaudeClaude CodeChatGPTCursorCodex

What a connected app can read

Five capabilities, eight tools, every one of them read-only.

Search what was saidsearch_meetings
Ask by meaning, not keywordask_meetings
Browse by date, client, or projectlist_meetings · list_projects
Read a call in fullget_meeting · get_meeting_transcript
Round up follow-ups, with ownerslist_action_items

What it can’t do

Access is one person signing in against one URL — no API key to issue, rotate, or leak, and no standing credential to inherit.

Server URL
https://api.tryassistly.com/mcp
  • Read-only. A connected app can read recaps, transcripts, and action items. It cannot change or delete anything.
  • Scoped to the person. Each connection is that person's own sign-in, and it reaches exactly what they can already see in the workspace — no more.
  • Revocable. Disconnect a client at any time, from the workspace. Admins decide who can connect one in the first place.

What the team ends up asking, from wherever they work

  • What did we promise Acme on security?
  • Pull the objections from this quarter's lost deals.
  • Draft the follow-up from this morning's call.
How the MCP server works

Admin & control

The answers procurement asks for

A tool people use on customer calls has to survive a security review. These are the controls that get it through one — and we’ll take the rest of the questionnaire on the call.

Your domain, your workspace

Everyone signing up on your domain lands in your workspace instead of starting a personal account nobody can see.

Single sign-on

Sign in through the identity provider you already run. Joiners and leavers are handled where you handle them today.

Roles and permissions

Admins decide who can see a project, who can invite, who can connect an outside tool, and who can change workspace settings.

Retention you set

Choose how long transcripts and recaps are kept. Anything can be deleted outright, by the person who recorded it or by an admin.

No model training

Your team's conversations are never used to train shared or foundational AI models, and never sold or passed to data brokers.

Nothing in the room

No bot in the participant list, and the overlay is excluded from screen capture at the OS level — so it never lands in a customer's recording.

Rollout

Good tools spread on their own

Assistly gets adopted the way useful software always does — one person, then their team. Enterprise is the part that lets you say yes to that instead of finding out about it later.

01

One person

Someone on the team installs it before a call they're nervous about, and walks out of it with the recap already written. Nobody had to approve anything.

02

Their team

Their calls start showing up in a shared space, so the rest of the team stops asking what happened on them. Projects appear per account, and filing quietly stops being anyone's job.

03

The org

Enterprise puts the workspace, sign-on, and retention under your control — without changing the thing that made people pick it up in the first place.

Nothing in that required a meeting-stack change, a bot in anyone’s calendar, or a new habit. The controls arrive without touching the experience.

Questions

Before you book the call

What's included in Enterprise?+

Everything in Pro — unlimited sessions, no time cap, the full toolkit — plus the parts a team needs: a shared context every member can ask (calls, recaps, action items, and projects in one workspace), shared projects, MCP connections in both directions, roles and permissions, single sign-on, workspace-wide retention settings, and a rollout we run with you. Pricing is per seat and annual; the shape of it depends on how many people and which teams, which is what the first call is for.

How is this different from a meeting notetaker?+

Two things, and both are about context rather than transcription. First, Assistly helps while the call is happening — and the help is drawn from your team's shared context, so it can answer with what a colleague said on a call six weeks ago or what your own Notion doc says, not just what's been said in the last five minutes. Second, that context doesn't stay locked in our app: Assistly runs an MCP server, so Claude, Claude Code, ChatGPT, Cursor, and Codex read your team's calls from inside the tools people already work in. A notetaker gives you a transcript in another place to check; this gives your team one shared memory, reachable from everywhere they already are.

What exactly can a connected AI tool see?+

Recaps, transcripts, action items, and the projects they belong to — through five read-only capabilities (search, semantic ask, browse by date or project, read a call in full, and round up action items). It can't change or delete anything. Each connection is that person's own sign-in and is scoped to what they can already see in the workspace, admins control who can create one, and any connection can be revoked at any time.

How does Enterprise pricing work?+

Per seat, billed annually, with the rate set by team size. Free and Pro are self-serve and published — Enterprise isn't, because the number depends on seats and rollout scope. Tell us how many people and we'll come back with a figure, not a discovery process.

Do you train AI models on our conversations?+

No. Your calls are never used to train shared or foundational AI models, and they're never sold or handed to data brokers. Transcription and inference run in the cloud on our providers (Soniox for transcription, AWS Bedrock running Claude models for inference); Bedrock does not retain that content or make it available to model providers. Sessions and notes can be deleted at any time, and a workspace can set how long anything is kept at all.

Does a bot join our calls?+

No. Assistly is a desktop app that works from your computer's audio, so nothing joins the meeting, nothing appears in the participant list, and there's no integration to approve in Zoom, Meet, or Teams. The overlay is also excluded from screen capture at the OS level, so it never shows up in a screen share or a recording — which is what makes it usable on a customer call.

Can we connect our own tools?+

Yes, in both directions, over MCP. Connect Notion, Linear, Google Calendar, or any MCP server to Assistly and the shared context grows to include them — so live guidance draws on your team's real specs, tickets, and pricing. And Assistly runs its own MCP server at https://api.tryassistly.com/mcp, so Claude, Claude Code, ChatGPT, Cursor, and Codex can read your meetings from inside the tools your team already works in. Setup is one URL with no API key, access is read-only, and every connection is scoped to the person who made it.

How long does a rollout take?+

Days, not quarters. There's no bot to install in your meeting stack, no calendar integration for IT to approve, and no change to how anyone runs a call — people download the app and sign in. We set up the workspace, single sign-on, and your retention settings with you, then help you bring in the first team.

Talk to us

Tell us about your team

How many people, which teams, and whatever security or procurement needs from us. We’ll come back with a number and a plan.

  • A reply from a person within one business day.
  • A 30-minute call: your teams, your stack, your security questions.
  • A per-seat number and a rollout plan — not a discovery process.

Goes straight to our team as a support ticket — you’ll get a reply thread, not an autoresponder.