# Welcome to SalesEQ (/docs)
SalesEQ records your meetings, transcribes them, and turns the result into
something your team can search, share, and act on.
## Get set up [#get-set-up]
Start with the one that describes you.
Nobody at your company uses SalesEQ yet. You set it up and your team joins you.
A teammate already set up SalesEQ and sent you an invite.
Already in? Install the desktop app and capture a meeting.
The eleven ideas the rest of the product is built on.
## Find your way around [#find-your-way-around]
* **[Capturing meetings](/docs/capturing-meetings/desktop-app)** covers every way a meeting gets into SalesEQ, including importing from other tools.
* **[Live AI](/docs/live-ai/overview)** covers the transcript, chat, and checklist you get during a meeting.
* **[Your meetings](/docs/your-meetings/viewing-a-meeting)** covers playback, Ask AI, and search.
* **[Sharing and permissions](/docs/sharing/share-a-meeting)** covers who sees what, and how to automate it.
* **[Meeting insights](/docs/insights/meeting-insights)** covers what SalesEQ generates from a meeting.
* **[Integrations](/docs/integrations/calendar)** covers calendar, email, and HubSpot.
* **[Account and organization](/docs/account/members-and-roles)** covers members, roles, security, and billing.
# Plans and billing (/docs/account/billing)
SalesEQ bills through Stripe, so your plan, payment method, and invoices are all managed there. Seats update as you invite and remove people.
Billing is admin-only.
## Manage your plan [#manage-your-plan]
Go to [Billing & invoices](https://app.saleseq.ai/settings#billing) as an admin and select
**Manage in Stripe**. Your plan, payment method, and invoices all live there.
## How seats work [#how-seats-work]
A seat is a member of your organization. Inviting someone adds a seat, and removing them frees it.
On a self-serve card plan, SalesEQ keeps your Stripe subscription matched to your active member count. You pay
for the seats you are using, rather than buying a block up front and leaving some of it empty.
Seats added partway through a billing period are prorated, and that charge lands on your next invoice rather
than straight away. Start a monthly period with four seats, add two at the halfway point, and your next
invoice covers six seats plus a half-period charge for the two you added.
If you are trimming seats before a renewal, remove members rather than only asking them to stop signing in. An inactive member still holds a seat.
## Paying by invoice [#paying-by-invoice]
Most teams pay by card and manage everything themselves from billing settings.
Larger teams can be billed by invoice instead. That is arranged by hand rather than through the app, so
[contact us](mailto:billing@saleseq.ai) to set it up. Organizations billed this way manage seats with us
rather than through billing settings, so automatic seat tracking and proration do not apply.
## Next [#next]
* [Members and roles](/docs/account/members-and-roles) covers inviting and removing people, which is what moves your seat count.
# Members and roles (/docs/account/members-and-roles)
Everyone in an organization is either an **Admin** or a **Member**.
| Role | What they can do |
| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Member | Record, upload, import, and share their own meetings. Transfer ownership of their own meetings. See what has been shared with them. |
| Admin | Everything a member can do, plus manage members, invites, groups, organization sharing defaults, and billing. Admins can also manage an organization meeting when they have its link. |
Keep at least two admins. One admin is a single point of failure the first time they are on holiday.
### What only an admin can set [#what-only-an-admin-can-set]
Several settings apply to everyone in the organization, and a member cannot override them:
* **[Require 2FA for password sign-ins](/docs/account/two-factor#require-it-across-your-organization).**
* **[Block recording](/docs/capturing-meetings/recording-rules)** for a meeting, or for every meeting
matching a rule.
* **[Require or block Live AI](/docs/live-ai/rules)**, or leave the choice to each member.
* **[Meeting deletion policy](/docs/your-meetings/delete-and-discard#who-can-delete)**, which decides
whether owners can delete their own meetings.
* **[Organization jargon](/docs/capturing-meetings/what-gets-captured#transcription-vocabulary)**, the shared vocabulary used when transcribing the organization's meetings.
Any member can share a quick action or a checklist with the organization. Those are additions to a
catalog rather than policy, so they need no admin.
## Invite someone [#invite-someone]
Two routes end in the same place. Send an invite to a specific address when you know who you are adding.
Copy a link when you are dropping it into Slack and letting people take it themselves.
### Open settings [#open-settings]
Go to [Organization members](https://app.saleseq.ai/settings#organization-members).
### Start an invite [#start-an-invite]
Select **Invite**. Choose the role the person gets when they accept.
### Send it, or copy a link [#send-it-or-copy-a-link]
Enter one or more work email addresses and select **Send Invite**. Turn on **Add message** to include a
note in the email.
Select **Copy Invite Link** instead to get a link that anyone can use to join in that role. Treat it like
a password, because it does not check who opens it.
Invite links expire after 30 days. Expired invites stay listed under **Pending invites** until you clear
them.
## Verify it worked [#verify-it-worked]
The person appears in your members list once they accept. Until then the invite is pending, and you can
re-send or withdraw it.
**Pending invites** lists everything outstanding, who created it, and when it expires. Links sent to a
named address show that address. Links you copied show as **Anyone with link**, because a copied link does
not know who will open it.
## Capping how many people can join [#capping-how-many-people-can-join]
**Member limit** sets a ceiling on how many people your organization accepts. Leave it at **No limit**
unless you have a reason.
The limit is not a billing control. Billing follows your active members either way, so a limit prevents
joins rather than capping what you pay.
## Email domain auto-join [#email-domain-auto-join]
Turn this on and anyone with your organization's verified email domain joins it instead of starting their own.
This is worth turning on early. Without it, the most common failure is a new rep signing up, creating a second organization by accident, and recording meetings nobody else can see.
## Removing someone [#removing-someone]
Remove a member from [Organization members](https://app.saleseq.ai/settings#organization-members). Their meetings stay in the organization, because meetings belong to the organization rather than to a personal account.
Their meetings do not move to anyone else. Ask them to [transfer ownership](/docs/sharing/transfer-ownership) of their meetings before you remove them, so the work lands with whoever takes it over.
Removing someone also removes the access they had through any group. SalesEQ also disconnects any [meeting imports](/docs/capturing-meetings/import-meetings) they set up. The meetings they imported stay.
An admin who has the link to one of those meetings can open, edit, share, or delete it.
## Next [#next]
* [Groups](/docs/sharing/groups) covers organizing members into teams.
* [Onboarding flow](/docs/account/onboarding-flow) covers what people see on their first sign-in.
* [Two-factor authentication](/docs/account/two-factor) covers adding a second step to signing in.
* [Plans and billing](/docs/account/billing) covers how members turn into seats.
# Onboarding flow (/docs/account/onboarding-flow)
New members are walked through setup rather than landing in an empty organization. The guided steps cover installing the desktop app, connecting a calendar, and connecting a CRM.
Admins choose which steps appear and which are required, so people join with the connections your team actually uses.
## Configure it [#configure-it]
### Open settings [#open-settings]
Go to [Onboarding flow](https://app.saleseq.ai/settings#onboarding-flow) as an admin.
### Choose which steps appear [#choose-which-steps-appear]
Turn off steps that do not apply to your team. A team that does not use a CRM should not be asked to connect one.
### Choose which steps are required [#choose-which-steps-are-required]
A required step has to be completed before someone finishes setup.
## Verify it worked [#verify-it-worked]
Select **Preview** to walk the flow exactly as a new member sees it, without inviting anyone.
Preview runs your unsaved changes, so you can check a step before you commit to it. Select **Close preview**
to come back, then **Save**.
## What to require [#what-to-require]
Requiring everything gets people stuck on their first day. Requiring nothing costs more than it looks.
Someone who skips the calendar gets generated meeting titles, no attendee list, and no reminder before a
meeting starts. Someone who skips the desktop app cannot record at all.
A reasonable middle:
* **Require the desktop app.** Without it a rep cannot record, which is the whole product.
* **Require the calendar.** It is what puts real titles and names on meetings.
* **Leave the CRM optional.** Not every rep owns CRM records, and it can be added later.
## Next [#next]
* [Members and roles](/docs/account/members-and-roles) covers inviting people.
* [Join your organization](/docs/getting-started/join-organization) is the same path, written for the person joining.
# Two-factor authentication (/docs/account/two-factor)
{/* The QR code and manual key in this screenshot are intentionally scrambled and are not usable credentials. */}
Two-factor authentication asks for a code from your authenticator app after your password. SalesEQ uses time-based one-time codes, so any standard authenticator app works.
Meeting recordings are among the most sensitive things a sales team holds. They contain pricing, roadmaps, and customer conversations. A password on its own is thin protection for that.
## If you sign in with Google [#if-you-sign-in-with-google]
This applies to accounts that sign in with an email address and a password. If you signed up through Google or another provider, SalesEQ never sees a password to add a second step to. Manage two-factor authentication in that provider's account settings instead.
Settings tells you which case you are in: the authenticator option names your provider and offers no **Enable 2FA** button when your account came from one.
This is also why an organization requiring 2FA does not reach you. See
[Require it across your organization](#require-it-across-your-organization).
## Turn it on [#turn-it-on]
### Open your security settings [#open-your-security-settings]
Go to [Security](https://app.saleseq.ai/settings#security), find **Personal two-factor authentication**, and select **Enable 2FA**.
### Confirm your password [#confirm-your-password]
Enter your current password to start setup.
### Scan the code [#scan-the-code]
Scan the QR code with your authenticator app, then enter the current code to confirm.
### Save your backup codes [#save-your-backup-codes]
SalesEQ shows a set of backup codes once setup finishes. Download or copy them before you close the dialog.
## Verify it worked [#verify-it-worked]
Sign out and sign back in. After your password, SalesEQ asks for a code from your authenticator.
## Add a second authenticator app [#add-a-second-authenticator-app]
**Set up another app** under **Authenticator app** points a second app at the same account, which is
what saves you when the first phone goes in a river.
Confirm your password and a current code, then scan the new QR code. Both apps generate valid codes
from then on, and your existing app and remaining backup codes keep working.
## Require it across your organization [#require-it-across-your-organization]
Admins can make two-factor authentication mandatory. Go to
[Organization two-factor authentication](https://app.saleseq.ai/settings#organization-two-factor) and
turn on **Require 2FA for password sign-ins**.
What the policy does:
* **Members without 2FA set it up at their next password sign-in.** They cannot reach SalesEQ until
they finish, and the enrollment screen says the organization requires it.
* **Sessions already signed in keep working.** The requirement lands the next time somebody
authenticates rather than throwing everyone out.
* **Nobody can turn their own 2FA off** while the policy is on. Settings says so instead of offering
the control.
* **Somebody joining the organization enrolls first.** The requirement is checked before membership
is granted.
**Third-party sign-ins are exempt.** The policy covers passwords, which are the thing a second step
protects. Members who sign in through Google or another provider are unaffected, and their second
step stays that provider's business. An organization where everyone uses Google gets nothing from
this setting.
Turning the policy back off leaves existing enrollments in place. It stops requiring new ones, and
members can then disable their own.
## Before you finish [#before-you-finish]
Set up your authenticator on a device you will still have next month, and keep your backup codes somewhere you can reach without that device. They are the way back in if you lose the authenticator.
## Next [#next]
* [Members and roles](/docs/account/members-and-roles) covers who can administer the organization.
# Connect ChatGPT (/docs/ai-assistants/connect-chatgpt)
SalesEQ is an official ChatGPT app, so connecting takes a few clicks with nothing to configure.
## Before you start [#before-you-start]
* A SalesEQ account you can sign in to at `https://app.saleseq.ai`
* A few meetings recorded, uploaded, or imported already, so ChatGPT has something to work with
* A ChatGPT Pro, Plus, Business, Enterprise, or Edu account
## Steps [#steps]
### Open the SalesEQ app in ChatGPT [#open-the-saleseq-app-in-chatgpt]
Go to the [SalesEQ app page](https://chatgpt.com/apps/saleseq/asdk_app_69d72da114fc8191bf725a82d6d42a9a) and select **Connect**.
### Sign in with SalesEQ [#sign-in-with-saleseq]
In the **Add SalesEQ to ChatGPT** window, select **Sign in with SalesEQ**.
### Allow access [#allow-access]
On the SalesEQ authorization page, select **Allow**. ChatGPT finishes the connection and returns you to the app page.
## Verify it worked [#verify-it-worked]
Start a chat and ask a question that needs your data:
```text
List my three most recent meetings in SalesEQ and summarize them.
```
A correct setup returns real meeting titles from your account. Mention `@SalesEQ` in your prompt if ChatGPT does not reach for it on its own.
If the app fails to connect, or connects but returns no meetings, read [Troubleshooting](/docs/ai-assistants/troubleshooting).
## Next [#next]
* [Connect custom MCP](/docs/ai-assistants/connect-custom-mcp) covers any other client.
* [Tools](/docs/ai-assistants/tools) lists everything your client can call.
* [Overview](/docs/ai-assistants/overview) covers permissions, privacy, and how to disconnect.
# Connect Claude (/docs/ai-assistants/connect-claude)
SalesEQ is available in Claude's Connectors Directory, so connecting takes a few clicks with nothing to configure.
## Before you start [#before-you-start]
* A SalesEQ account you can sign in to at `https://app.saleseq.ai`
* A few meetings recorded, uploaded, or imported already, so Claude has something to work with
* Claude on web or desktop
## Steps [#steps]
### Open the SalesEQ connector in Claude [#open-the-saleseq-connector-in-claude]
Go to the [SalesEQ Claude connector page](https://claude.ai/directory/saleseq) and select **Connect to Claude**.
An Owner or Primary Owner must add SalesEQ to a Team or Enterprise organization before members connect their own accounts.
### Sign in to SalesEQ [#sign-in-to-saleseq]
Sign in with the SalesEQ account whose meetings you want Claude to reach. If you are already signed in, Claude takes you directly to authorization.
### Allow access [#allow-access]
On the SalesEQ authorization page, select **Allow**. Claude finishes the connection and returns you to the connector page.
## Verify it worked [#verify-it-worked]
Confirm the connector page says **Connected**. Start a conversation, turn SalesEQ on from the connectors control, and test it with:
```text
List my three most recent meetings in SalesEQ and summarize them.
```
A correct setup returns real meeting titles from your account.
If the connector fails to add, or connects but returns no meetings, read [Troubleshooting](/docs/ai-assistants/troubleshooting).
## Next [#next]
* [Tools](/docs/ai-assistants/tools) lists everything Claude can call.
* [Overview](/docs/ai-assistants/overview) covers permissions, privacy, and how to disconnect.
# Connect custom MCP (/docs/ai-assistants/connect-custom-mcp)
Claude and ChatGPT have their own pages. Any other client that supports remote MCP servers also reaches SalesEQ, whether it runs in a browser, on your desktop, or inside an IDE.
Each client labels this differently, so the steps below describe what to look for rather than what to select.
## Before you start [#before-you-start]
* A SalesEQ account you can sign in to at `https://app.saleseq.ai`
* A few meetings recorded, uploaded, or imported already, so your client has something to work with
* A client that supports **remote** MCP servers
## Steps [#steps]
### Find where your client adds a remote MCP server [#find-where-your-client-adds-a-remote-mcp-server]
The wording varies: connectors, integrations, MCP servers, tools. If the only documentation you find covers
local servers, check that product's guide for remote or HTTPS MCP.
### Paste the server URL [#paste-the-server-url]
```text
https://mcp.saleseq.ai
```
Choose **streamable HTTP** if the client asks which transport to use. No client ID or secret is needed.
### Sign in to SalesEQ [#sign-in-to-saleseq]
Choose **OAuth** if the client asks how to authenticate, then sign in with the account whose meetings you want the client to reach. The connector exposes that account's access and nothing more.
## Verify it worked [#verify-it-worked]
Ask your client a question that needs your data:
```text
List my three most recent meetings in SalesEQ and summarize them.
```
A correct setup returns real meeting titles from your account.
If the client fails to connect, or connects but returns no meetings, read [Troubleshooting](/docs/ai-assistants/troubleshooting).
## Next [#next]
* [Tools](/docs/ai-assistants/tools) lists everything your client can call.
* [Overview](/docs/ai-assistants/overview) covers permissions, privacy, and how to disconnect.
# Overview (/docs/ai-assistants/overview)
The SalesEQ connector lets you query your meetings and their analysis from any AI client that speaks the Model Context Protocol (MCP). That includes Claude on web and desktop, ChatGPT, and anything else built on the standard.
Permissions are enforced exactly as they are inside the SalesEQ app.
## What you can ask [#what-you-can-ask]
Ask for your recent meetings, a transcript, or which meetings mentioned a topic, and you get them back.
The connector earns its place on the questions no single meeting can answer. It searches across meetings
you created or received through a direct or group share, pulls whole transcripts, and pulls frames from the recording. Your AI client can read dozens
of meetings and come back with one answer.
**Coach yourself against another rep.**
```text
Compare how I handle pricing objections with how Dana handles them. Search both of our meetings from the last quarter, find the moments where a customer pushed back on price, and tell me what she does that I do not.
```
**Gather customer evidence before you build something.**
```text
Go through the meetings shared with me and find every moment a customer talked about our meeting search. Quote what they said, and tell me which requests came up more than once. I am about to start rebuilding it and I want to hear what customers actually asked for before I design anything.
```
**Prepare for the next conversation with a client.**
```text
I have a call with Acme tomorrow. Go through every meeting we have had with them and tell me what they asked for, which objections came up, what we committed to, and what is still unresolved.
```
**Hand the answer to another tool.**
```text
I have a call with Acme on Thursday. Go through every meeting we have had with them, pull out what they care about and where they pushed back, then use Gamma to build a short proposal deck I can walk them through.
```
## Server details [#server-details]
| Setting | Value |
| -------------- | ------------------------------------------ |
| Endpoint | `https://mcp.saleseq.ai` |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.0 with Dynamic Client Registration |
You do not need a client ID or secret. To set the connector up, read [Connect Claude](/docs/ai-assistants/connect-claude), [Connect ChatGPT](/docs/ai-assistants/connect-chatgpt), or [Connect custom MCP](/docs/ai-assistants/connect-custom-mcp) for anything else. For what the connector exposes, read [Tools](/docs/ai-assistants/tools).
## Permissions and data access [#permissions-and-data-access]
The connector uses the same scope as **All meetings** and **Search** in the web app: meetings you own, meetings shared with you directly, and meetings shared with a group you belong to.
Meetings available only through an organization default do not appear in list or search results. Ask the owner to share one directly with you or with a group you belong to when you want the assistant to find it.
## Privacy and data handling [#privacy-and-data-handling]
When your AI client calls a tool, the server returns the requested meeting metadata, transcript, or analysis to that client. From there, the client may forward your prompt and the tool result to its own model provider, such as Anthropic for Claude or OpenAI for ChatGPT.
SalesEQ does not see or log the prompts you send to your AI client. SalesEQ sees only the tool calls the client makes back to us. For full details, read the [privacy policy](/privacypolicy).
## Disconnecting [#disconnecting]
Disconnect SalesEQ at any time from your AI client's connector or integration settings. To use it again later, reconnect and sign in to SalesEQ.
## Next [#next]
* [Connect Claude](/docs/ai-assistants/connect-claude) sets it up in Claude.
* [Connect ChatGPT](/docs/ai-assistants/connect-chatgpt) sets it up in ChatGPT.
* [Tools](/docs/ai-assistants/tools) lists the seven tools the connector exposes.
# Tools (/docs/ai-assistants/tools)
The connector exposes seven tools. All of them are read-only and non-destructive. No tool modifies SalesEQ data, sends notifications, writes to your CRM, or makes external requests on your behalf.
| Tool | What it does |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `list_meetings` | Lists meetings you own plus meetings shared directly with you or one of your groups. Returns title, participants, duration, platform, source, owner, and recorder, with filter and sort options. |
| `search_meetings` | Searches your meeting transcripts by topic, phrase, or speaker. Returns the most relevant meetings with their best-matching snippets and playback offsets. |
| `get_meeting_summary` | Fetches the generated summaries of up to 20 meetings in one call. This is a much cheaper way to answer "what was this meeting about" than reading the full transcript. |
| `get_meeting_table_of_contents` | Fetches a meeting's table of contents: each topic discussed, with a title, a short description, and start and end times. Works for up to 20 meetings in one call. |
| `get_transcript` | Fetches the transcript for a specific meeting, optionally sliced to a time range so long meetings do not blow out context. It can also mark when each word was said. |
| `get_meeting_frame` | Fetches still frames from a meeting's video at up to 8 timestamps in one call. Audio-only and transcript-only meetings have no video frames. |
| `get_org_context` | Looks up your organization and its members, so the AI resolves a teammate's name or email before searching their meetings. |
## Filters [#filters]
`list_meetings` and `search_meetings` filter by who owns a meeting, who recorded it, and who imported it. They also filter by the platform the conversation happened on, the tool that recorded it, and how it reached SalesEQ. That is how an assistant answers questions such as:
```text
Which of Jason's meetings did we import from Fathom?
Find the Zoom meetings Rory recorded last month where pricing came up.
```
Ask by name. The assistant uses `get_org_context` to turn a teammate's name into the right person before filtering.
## Access [#access]
`list_meetings` and `search_meetings` use the same scope as **All meetings** in the web app: meetings you own, meetings shared with you directly, and meetings shared with a group you belong to. Meetings available only through an organization default do not appear in these results.
Meeting-specific tools still check whether your account can open the meeting. Read [Overview](/docs/ai-assistants/overview) for more about permissions.
## Next [#next]
* [Overview](/docs/ai-assistants/overview) covers permissions, privacy, and how to disconnect.
* [Troubleshooting](/docs/ai-assistants/troubleshooting) covers what to do when a tool returns nothing.
# Troubleshooting (/docs/ai-assistants/troubleshooting)
## Adding the connector fails with an authorization or connection error [#adding-the-connector-fails-with-an-authorization-or-connection-error]
* If you added SalesEQ as a custom MCP connection, confirm the server URL is exactly `https://mcp.saleseq.ai`, with no path and no trailing characters.
* Allow pop-ups for the SalesEQ sign-in window. A pop-up blocker is the most common cause of an OAuth window that never opens.
* Verify you sign in to `https://app.saleseq.ai` in a regular browser tab. If sign-in fails there, the connector cannot authorize you either.
## The connector connected, but I do not see meetings I expect [#the-connector-connected-but-i-do-not-see-meetings-i-expect]
* Meetings available only through an organization default do not appear in list or search results. Ask the owner to share one directly with you or with a group you belong to.
* If a meeting is shared with you directly and still does not turn up, ask your assistant to look again across everything you can access rather than only the meetings you recorded.
## A get\_transcript call returns a permission error [#a-get_transcript-call-returns-a-permission-error]
* The connector enforces the same permission model as the SalesEQ app. If you cannot view the meeting at `https://app.saleseq.ai`, the tool refuses it as well.
* Ask the meeting owner to share it with you, or check the share settings inside the SalesEQ app.
## Transcript timestamps look wrong or are labeled estimated [#transcript-timestamps-look-wrong-or-are-labeled-estimated]
* Some transcript-only meetings carry no word-level timestamps.
* In those cases the tool estimates timestamps at 150 words per minute. That is good enough for slicing, and it does not match a recording exactly.
## Anything else [#anything-else]
Open the tool call in your AI client. It shows the request that went to SalesEQ and the response that came back, which tells you whether SalesEQ refused the request, returned nothing, or was never called.
Your assistant reads those errors as well. Ask it why the SalesEQ connector failed.
## Tell us [#tell-us]
Email [founders@saleseq.ai](mailto:founders@saleseq.ai). Something broken is worth hearing about, and so is what you are trying to do with the connector. That holds especially when it is something we have not built for yet.
## Next [#next]
* [Tools](/docs/ai-assistants/tools) lists what each tool returns.
* [Overview](/docs/ai-assistants/overview) covers permissions, privacy, and how to disconnect.
# Automatic imports (/docs/capturing-meetings/automatic-imports)
Automatic imports keep SalesEQ in step with another tool your team still records in. Each time that tool finishes a
meeting, SalesEQ imports it. Nobody has to remember to do it.
Turn it on per connection. Past meetings are a separate job: [Import meetings](/docs/capturing-meetings/import-meetings)
covers bringing in a backlog, and you can do both on the same connection.
## How it works [#how-it-works]
When you turn on automatic imports, SalesEQ registers a webhook with the tool through your connection. A webhook is a
notification the tool sends each time a meeting is ready. You never copy a URL or a secret, because SalesEQ creates and
removes the webhook for you.
When a notification arrives, SalesEQ imports that meeting the same way as a manual import:
* **The recorder owns it** when their email matches a verified member of your organization. Otherwise the owner of the
connection holds it until the recorder joins. [Who owns it](/docs/capturing-meetings/import-meetings#who-owns-it)
covers this in full.
* **Auto-share rules run** when the meeting goes to its recorder, the same as for a new recording.
* **Everything stays editable.** Change the owner, the sharing, the title, or the speaker names after the meeting
arrives, the same as on any other meeting.
A meeting that is already in SalesEQ, or one someone deleted, is never imported twice.
## Turn it on [#turn-it-on]
### Open the connection [#open-the-connection]
Go to [Meeting imports](https://app.saleseq.ai/settings#meeting-imports) in Settings and select **Manage imports** on
the connection. [Connect the tool](/docs/capturing-meetings/import-meetings#connect-the-tool) first if you have not.
### Choose which meetings to import [#choose-which-meetings-to-import]
Under **New meetings**, choose what the connection imports:
| Choice | What it imports |
| -------------- | -------------------------------------------------------------------------------- |
| Own meetings | Meetings recorded by the connected account. This is the default. |
| All accessible | Also meetings that teammates or outside users shared with the connected account. |
Pick **All accessible** when one account can see a whole team's recordings and you want all of them in SalesEQ.
### Turn on Automatic imports [#turn-on-automatic-imports]
Turn on **Automatic imports**. SalesEQ sets up the webhook, which takes a few seconds.
Automatic imports run only while your organization has an active plan or trial.
## Verify it worked [#verify-it-worked]
Record a short meeting in the tool you connected. Once that tool finishes processing it, open **Import history** from
**Manage imports**. The meeting appears there as an import marked **Automatic**, and then on the
[Meetings](https://app.saleseq.ai/meetings) page.
## Change which meetings import [#change-which-meetings-import]
Switch between **Own meetings** and **All accessible** while automatic imports are on. SalesEQ replaces the webhook
after a few seconds. A meeting that finishes during that switch is not imported, so bring it in from **Past meetings**.
## When something goes wrong [#when-something-goes-wrong]
**The connection shows Disconnected, or the dialog says access has expired.** The tool stopped accepting your
credentials, so nothing new imports. Select **Update API key** or **Reconnect** on the connection. Then import anything
you missed from **Past meetings**.
**SalesEQ could not confirm the webhook was removed.** This can happen after you turn automatic imports off or
disconnect. The dialog shows the webhook's address. Open the tool's API or webhook settings, delete the webhook with
that address, then confirm in SalesEQ that you removed it. Until you do, you cannot turn automatic imports back on or
replace the connection's credentials.
**Automatic imports are still being updated.** Setup or cleanup is in progress. Wait a minute and try again.
## Turn it off [#turn-it-off]
Turn off **Automatic imports** on the connection. New meetings stop importing straight away, and meetings already
imported stay in SalesEQ. Past-meeting imports keep working.
Disconnecting the connection turns off automatic imports too. Reconnecting later does not turn them back on.
When someone leaves your organization, SalesEQ disconnects their connections and removes their webhooks. The meetings
they imported stay.
## Next [#next]
* [Import meetings](/docs/capturing-meetings/import-meetings) covers past meetings, import history, and duplicates.
* [Auto-share rules](/docs/sharing/auto-share-rules) covers who sees imported meetings as they arrive.
* [Transfer ownership](/docs/sharing/transfer-ownership) covers changing who owns an imported meeting.
# Automatic recording (/docs/capturing-meetings/automatic-recording)
SalesEQ watches for meetings on the platforms listed under [Desktop app recording](/docs/capturing-meetings/desktop-app#supported-platforms). You decide what happens when it finds one, for all platforms at once or per platform.
## The four behaviors [#the-four-behaviors]
| Behavior | What happens when SalesEQ detects a meeting |
| -------------------- | ---------------------------------------------------------------------------------------- |
| Record automatically | Recording starts on its own. |
| Ask before recording | You get a notification, and the meeting appears in the desktop app with a Record button. |
| Show in SalesEQ only | The meeting appears in the desktop app. No notification. |
| Ignore | SalesEQ leaves that platform alone. You cannot record there at all. |
**Ask before recording** is the safe default while you get used to the desktop app. **Record automatically** is what most reps settle on, because the meetings you forget to record are the ones you most want back.
This page covers the floor: what SalesEQ does when nothing more specific applies. To decide per meeting, or by what is on the invitation, see [Recording rules](/docs/capturing-meetings/recording-rules).
## Set your default [#set-your-default]
### Open desktop settings [#open-desktop-settings]
Open the SalesEQ desktop app and go to **Settings**.
### Choose a default behavior [#choose-a-default-behavior]
Pick **Record automatically**, **Ask before recording**, or **Show in SalesEQ only**. This applies to every platform SalesEQ detects.
### Override individual platforms [#override-individual-platforms]
Set a different behavior for a single platform where you want one. Record your Zoom meetings automatically while ignoring Slack huddles, for example.
**Ignore** is available as a per-platform override.
## Verify it worked [#verify-it-worked]
Join a meeting on a platform set to **Record automatically**. The control bar appears on its own and shows a running timer.
## Next [#next]
* [Recording rules](/docs/capturing-meetings/recording-rules) covers departing from this default for one meeting, or for a whole category of them.
* [Recording notice](/docs/capturing-meetings/recording-notice) tells people a recording started, which matters most when it starts on its own.
* [What gets captured](/docs/capturing-meetings/what-gets-captured) covers what a recording produces.
* [Delete and discard](/docs/your-meetings/delete-and-discard) covers getting rid of a meeting you did not want.
# Desktop app recording (/docs/capturing-meetings/desktop-app)
SalesEQ records from your own machine rather than sending a bot into the meeting. Nobody sees an extra
participant, and the meeting works the same as it always does.
Recording starts only on a meeting SalesEQ detects, on one of the platforms below, and only when you start
it or you set that platform to record on its own. While it runs, SalesEQ reads the meeting window and
nothing around it.
## Telling people you are recording [#telling-people-you-are-recording]
No bot in the meeting means nobody gets the usual signal that a recording is running, so saying so is on
you. Consent rules vary by country and by state.
SalesEQ can post a notice in the meeting chat as a recording starts. See
[Recording notice](/docs/capturing-meetings/recording-notice).
## Supported platforms [#supported-platforms]
Meeting apps, recorded from their desktop app:
| App | macOS | Windows |
| --------------- | ---------- | ------- |
| Zoom | Yes | Yes |
| Microsoft Teams | Yes | Yes |
| Slack huddles | Audio only | No |
Google Meet runs in a browser, so support depends on which one:
| Browser | macOS | Windows |
| ---------------------- | ----- | -------------- |
| Chrome | Yes | Yes |
| Edge | No | Yes |
| Safari | Yes | Not applicable |
| Arc, Brave, Comet, Dia | Yes | No |
Google Meet companion mode is not supported on either platform.
SalesEQ cannot record a meeting on anything else.
## Before you start [#before-you-start]
* The desktop app installed and signed in. See [Download SalesEQ](/docs/getting-started/download).
* Screen recording and microphone permissions granted to the desktop app.
## Record a meeting [#record-a-meeting]
### Get into the meeting [#get-into-the-meeting]
Join the meeting however you normally do, from your calendar, from a link, or from the SalesEQ desktop app.
With a connected calendar, SalesEQ also lists your upcoming meetings and offers **Join and Record** shortly
before one starts. That button opens the meeting in your default browser. Detection then happens the same
way it would have if you had opened the link yourself.
### Start recording [#start-recording]
A bar appears at the bottom of the SalesEQ desktop app when it detects the meeting, and a notification
comes with it. Select **Record**.
You can also start from the menu bar or system tray without opening the main window.
### Work with the recording while it runs [#work-with-the-recording-while-it-runs]
**Pause** blanks the video and drops the audio for as long as it lasts, then picks up when you resume. The
recording stays one meeting. Use it when a customer reads out card details, when someone shares a screen
with personal data, or when the conversation turns somewhere that does not belong in a recording.
**Live AI** runs alongside, transcribing as people talk. Ask it a question, or track your objectives
against what has been said. See [Live AI](/docs/live-ai/overview).
### Finish the meeting [#finish-the-meeting]
Stop the recording, or leave the meeting and let it end on its own. Either way the file uploads and
processing starts.
If you did not mean to record the meeting, select **Discard recording** in the recording bar before you stop.
A discarded recording is never processed and never reaches your organization.
## Verify it worked [#verify-it-worked]
The meeting appears under **My meetings** on the **Meetings** page once processing finishes, and it opens.
## SalesEQ is not detecting your meeting [#saleseq-is-not-detecting-your-meeting]
No bar and no notification means SalesEQ has not detected the meeting, and it cannot record one it has not
detected. Work through these in order:
* **Check the platform against the table above.** Companion mode and an unsupported browser are the two
that catch people out.
* **Make sure you are in only one meeting.** Detection expects a single meeting at a time.
* **Quit and reopen SalesEQ.** Give it around twenty seconds after it starts before you expect detection,
because the app has to come up first.
If a supported platform still goes undetected after that, send us the platform and the browser so we can
look at it.
## Next [#next]
* [Automatic recording](/docs/capturing-meetings/automatic-recording) removes the step of pressing Record.
* [Live AI](/docs/live-ai/overview) reads and answers questions during the meeting.
* [Delete and discard](/docs/your-meetings/delete-and-discard) covers getting rid of a meeting you did not want.
# Import meetings (/docs/capturing-meetings/import-meetings)
If your team recorded meetings with another tool before SalesEQ, import them instead of downloading and uploading each
file. Imported meetings become full SalesEQ meetings. They are transcribed, analyzed, searchable, and shareable like
anything the desktop app records.
The tools you can import from are listed under [Meeting imports](https://app.saleseq.ai/settings#meeting-imports) in
Settings. A tool marked **Coming soon** is not available yet.
This page covers meetings that already happened. To bring in new meetings as they finish, turn on
[Automatic imports](/docs/capturing-meetings/automatic-imports).
## Before you start [#before-you-start]
* **An active plan or trial.** Importing is part of a paid plan.
* **An account on the tool you are importing from.** You can import any recording that account can open, including
recordings teammates shared with it.
Any member can import. You do not need to be an admin.
## Connect the tool [#connect-the-tool]
### Open Meeting imports [#open-meeting-imports]
Go to [Meeting imports](https://app.saleseq.ai/settings#meeting-imports) in Settings.
### Choose the tool [#choose-the-tool]
Select it from the grid. Depending on the tool, you either sign in to it or paste an API key you create in that tool's
settings. When a tool needs a key, the connect dialog links to the page where you create it.
SalesEQ checks your credentials with the tool before saving them.
### Confirm it connected [#confirm-it-connected]
The connection appears at the top of the section, marked **Connected**.
A connection belongs to you. Other members, admins included, cannot see its key or import through it. If you have
several accounts on the same tool, connect each one.
## Import past meetings [#import-past-meetings]
### Open the connection [#open-the-connection]
Select **Manage imports** on the connection. Under **Past meetings**, a table lists the recordings that account can
open.
### Choose the meetings [#choose-the-meetings]
Select the checkbox on each meeting you want. The checkbox in the header row selects the current page, every loaded
meeting, or every meeting matching your filters.
Filter the table to narrow a long list, such as to one person's meetings or a date range. Which filters appear depends
on what the tool lets SalesEQ search.
### Review the import [#review-the-import]
Select **Review import**. The review lists every meeting you chose and estimates how long the import takes. One import
holds up to 500 meetings, so bring a large backlog across in several imports.
### Start it [#start-it]
Select **Start import**. You can close the window straight away. The import runs in the background.
## Verify it worked [#verify-it-worked]
Select **Import history** in the same dialog. Each import shows its progress, and expanding it lists every meeting with
its own status. A finished meeting has a **View meeting** link.
Imported meetings also appear on the [Meetings](https://app.saleseq.ai/meetings) page. Each one keeps its original date,
and its source icon shows which tool it came from.
## What SalesEQ does with an imported meeting [#what-saleseq-does-with-an-imported-meeting]
SalesEQ downloads the recording and processes it like a meeting it recorded itself. It writes its own transcript, so
search, Ask AI, playback, and insights work the same way. When the original tool labels its speakers, SalesEQ uses
those labels to help name them.
### Who owns it [#who-owns-it]
The original tool records who captured each meeting. SalesEQ uses that to pick the owner:
* **The recorder is a member of your organization.** If their email matches a verified member, that member owns the
meeting.
* **The recorder is not a member yet.** You own the meeting for now. When the recorder joins your organization and
verifies their email, the meeting moves to them on its own.
Either way, you keep editor access to every meeting you import for as long as you stay a member.
[Transfer ownership](/docs/sharing/transfer-ownership) to change the owner yourself. A transfer is final. Once you
transfer a meeting, it no longer moves to its recorder when they join.
### Who can see it [#who-can-see-it]
A meeting that goes to its recorder runs their [Auto-share rules](/docs/sharing/auto-share-rules), plus any
organization rules that apply, the same way a new recording does. A meeting you hold because no recorder matched skips
Auto-share rules and the organization default sharing, so only you can see it until you share it. When it later moves
to its recorder, their rules do not run either.
Sharing on an imported meeting works like on any other meeting. Change it whenever you want.
## Meetings that are already in SalesEQ [#meetings-that-are-already-in-saleseq]
A recording is imported once per organization, whoever brings it in. The **Status** column tells you where each one
stands:
| Status | What it means |
| ------------------ | ------------------------------------------------------------------------------------------------------- |
| Not imported | Ready to import. |
| Imported | Already in SalesEQ, brought in by you or a teammate. Ask its owner to share it if you cannot open it. |
| Processing | Being imported now. |
| Needs retry | The last attempt failed. Select it to try again. |
| Cancelled | Its import was stopped before it finished. Select it to try again. |
| Previously deleted | Deleted in SalesEQ after it was imported. It never comes back on its own. Select it to import it again. |
| Unavailable | The tool reports no recording to import. |
Deleting an imported meeting in SalesEQ does not delete it from the tool it came from.
## Stop or retry an import [#stop-or-retry-an-import]
Open **Import history** and select **Stop import** on a running import. Meetings that already finished stay in
SalesEQ, and meetings that are partway through processing may still finish. The rest are not imported.
Expand an import and select **Retry** on a failed meeting to queue it again. If many meetings fail at once, the
connection has usually lost access. Select **Update API key** or **Reconnect** on the connection, then retry.
## Disconnect [#disconnect]
Select **Disconnect** on the connection. SalesEQ removes your saved credentials and stops
[Automatic imports](/docs/capturing-meetings/automatic-imports) for that account. Meetings you already imported stay.
## If someone imported your meetings for you [#if-someone-imported-your-meetings-for-you]
A teammate or the SalesEQ team sometimes imports a backlog before you join. You have nothing to set up. Meetings you
recorded appear in **My meetings** once you join with the email you recorded them under and verify it, or as soon as
someone transfers them to you.
## Next [#next]
* [Automatic imports](/docs/capturing-meetings/automatic-imports) covers bringing in new meetings as they finish.
* [Transfer ownership](/docs/sharing/transfer-ownership) covers handing imported meetings to the right people.
* [Upload a recording](/docs/capturing-meetings/upload) covers a single file from somewhere without an import.
# Recording notice (/docs/capturing-meetings/recording-notice)
SalesEQ records from your machine rather than sending a bot, so nobody in the meeting gets the usual
signal that a recording started. This setting supplies one. When you start recording, SalesEQ posts a
message in the meeting chat.
Windows is coming.
## Turn it on [#turn-it-on]
### Open desktop settings [#open-desktop-settings]
Open the SalesEQ desktop app and go to **Settings**.
### Turn on the notice [#turn-on-the-notice]
Under **Recording notice**, find **Post a notice in the meeting chat** and switch it on.
### Edit the message [#edit-the-message]
The default reads:
```text
This meeting is being recorded with SalesEQ.
```
Replace it with whatever your team says.
## Where it posts [#where-it-posts]
The notice posts in Zoom, in Microsoft Teams, and in Google Meet when you are on Chrome. Google Meet in
another browser does not get one.
The meeting also has to be in front of you. SalesEQ opens the chat panel to post, so switching to another
window or another tab as recording starts can stop the message going out.
Slack huddles have no chat to post into.
## Verify it worked [#verify-it-worked]
Start a recording with the meeting window in front of you. The message appears in the meeting chat as you
begin.
## What to put in it [#what-to-put-in-it]
Short is better than complete. People read a chat message in a second or not at all.
Teams tend to land on one of three. Swap in your own company name.
**The bare fact.** This is the default, and it is enough for most teams.
```text
This meeting is being recorded with SalesEQ.
```
**The fact plus a reason.** Useful while recording is new to your team and customers ask why.
```text
Acme is recording this meeting so we can capture notes and follow up accurately.
```
**The fact plus a link.** For teams with a recording policy written down somewhere.
```text
Acme is recording this meeting. Our recording policy: acme.com/recording
```
## What this setting is not [#what-this-setting-is-not]
The notice posts a message. It does not ask for consent, wait for a reply, or stop the recording if
somebody objects.
Recording rules vary by country and by state, and some of them require more than telling people. Work out
what applies to you and treat this setting as one part of that, not the whole of it.
## Next [#next]
* [Desktop app recording](/docs/capturing-meetings/desktop-app) covers starting a recording.
* [Automatic recording](/docs/capturing-meetings/automatic-recording) covers recordings that start on their own, where a notice matters most.
# Recording rules (/docs/capturing-meetings/recording-rules)
Your default recording behavior applies to every meeting SalesEQ detects. Recording rules are how you depart from it: for one meeting, or for every meeting that looks a certain way.
Find them in the desktop app under **Settings**, in the **Recording Rules** section. It has two tabs. **Upcoming meetings** lists what is on your calendar and lets you set any one of them. **Automatic rules** holds the rules that decide for you.
## Two separate decisions [#two-separate-decisions]
A meeting gets recorded when two things agree, and they are set by different people.
**Personal recording** is yours. It says what you want to happen when SalesEQ detects the meeting.
| Behavior | What happens when SalesEQ detects the meeting |
| -------------------- | --------------------------------------------------------------- |
| Record automatically | Recording starts on its own. |
| Ask before recording | You get a notification, and a Record button in the desktop app. |
| Show in SalesEQ only | The meeting appears in the desktop app. No notification. |
| Ignore | No recording and no prompt. |
**Organization recording policy** is the admin's, and it is a gate rather than a preference:
| Policy | What it does |
| --------------- | --------------------------------------------------------------------- |
| Allow recording | Members use their own recording behavior. |
| Block recording | Nobody in the organization records the meeting, whatever they prefer. |
A block wins. When an admin blocks a meeting, your behavior still shows in the table, and it does not run.
## Automatic rules [#automatic-rules]
An automatic rule matches meetings by what is on the calendar invitation, then applies a behavior or a policy to everything that matches.
The **Automatic rules** tab holds two lists:
**Personal behavior rules** set your behavior. They are ordered, and the first matching rule wins, so put the specific ones above the general ones. Any member can create one.
**Organization recording rules** block recording across the organization. They are admin-only, and any matching rule blocks, so order does not change the outcome.
### What a rule can match on [#what-a-rule-can-match-on]
Each condition takes a field, an operator, and a value:
| Field | Matches against | Operators |
| ------------------- | ----------------------------------------------------- | ----------------------------------------------------------------------------------- |
| Meeting title | The title on the calendar event. | contains, does not contain, equals, matches regex |
| Organizer email | Whoever organized the meeting. | contains, does not contain, equals, matches regex |
| Invitees | The email addresses invited, by address or by domain. | include anyone matching, include no one matching, all match, include anyone outside |
| Calendar connection | Which connected calendar the meeting came from. | is, is not |
Invitees work differently from the other fields, because the interesting questions are about the group rather than about one address.
**Calendar connection** is available on your own rules only. An organization rule cannot match on somebody else's connected calendar, so it has the other three fields.
**Include anyone outside** is the one worth knowing. Give it your own domain and the rule matches any meeting with someone external on it, which is the usual way to separate customer meetings from internal ones.
A rule holds up to 20 conditions and matches when **all** of them hold or when **any** of them does.
### Create a rule [#create-a-rule]
### Open the Automatic rules tab [#open-the-automatic-rules-tab]
In the desktop app, go to **Settings**, find **Recording Rules**, and select **Automatic rules**.
### Add a rule to the list you want [#add-a-rule-to-the-list-you-want]
Select **Add rule** on **Personal behavior rules** to set your own behavior, or on **Organization recording rules** to block recording for everyone. The second is available to admins.
### Name it and add conditions [#name-it-and-add-conditions]
Give the rule a name you will recognize later, such as Candidate interviews. Add conditions, and choose whether all of them or any of them has to hold.
### Choose what it does [#choose-what-it-does]
A personal rule picks one of the four behaviors. An organization rule blocks recording.
### Test it before you rely on it [#test-it-before-you-rely-on-it]
Select **Test rule**. SalesEQ runs it against your upcoming meetings and marks each one **Matches** or **Doesn't match**, so you find out the rule is broader than you meant without recording anything.
### Order matters for your rules, not the organization's [#order-matters-for-your-rules-not-the-organizations]
Move a personal rule up or down to change which one wins. A meeting that matches both an interviews rule and a customers rule takes whichever sits higher.
Organization rules do not work this way. Any matching block is a block, so there is nothing for order to decide.
## Set one meeting [#set-one-meeting]
The **Upcoming meetings** tab lists what is on your calendar, with **Personal recording** on every row and **Organization recording policy** alongside it for admins.
Change either one and it applies to that meeting alone. Recurring meetings are not covered: setting one occurrence leaves the rest of the series on whatever your rules say.
Both columns start at **Follow rules** or **Follow policy**, which shows the value your rules produced in parentheses. Picking anything else overrides them for that meeting. Returning to **Follow rules** removes the override.
**What the recorder will do** is the last column, and it is the one to read. It resolves everything above it into what actually happens, including which rule decided and whether an organization block is overriding what you chose.
## Change several meetings at once [#change-several-meetings-at-once]
Selecting meetings in the **Upcoming meetings** tab reveals a toolbar above the table.
### Select the meetings [#select-the-meetings]
Use the checkbox on each row, or the one in the header to take the whole list.
### Choose what to change [#choose-what-to-change]
The toolbar offers **Your recording behavior** and, for admins, **Organization recording policy**.
### Apply [#apply]
Pick a value and select **Apply to** the selected meetings. Meetings that cannot take the change are skipped and reported rather than failing the batch.
Up to 100 meetings go in one batch. The Live AI section has its own toolbar for checklists, quick actions, and Live AI policy, covered in [Live AI rules](/docs/live-ai/rules).
## Verify it worked [#verify-it-worked]
Open the **Upcoming meetings** tab and read **What the recorder will do** on a meeting your rule should match. It names the rule that decided.
For a rule set to **Record automatically**, join the meeting: the control bar appears on its own and shows a running timer.
## When a change takes effect [#when-a-change-takes-effect]
Rules are evaluated for each meeting as it is detected, so a change applies to meetings that have not started.
A rule you turn off or delete stops applying to upcoming meetings. It does not reach back: recordings you already have stay where they are. To get rid of one of those, see [Delete and discard](/docs/your-meetings/delete-and-discard).
A change made on the web reaches the desktop app on its next refresh rather than instantly.
## Next [#next]
* [Live AI rules](/docs/live-ai/rules) does the same thing for Live AI, checklists, and quick actions.
* [Automatic recording](/docs/capturing-meetings/automatic-recording) covers the default that rules depart from.
* [Recording notice](/docs/capturing-meetings/recording-notice) tells people a recording started.
# Upload a recording (/docs/capturing-meetings/upload)
Uploaded files become full meetings. They are transcribed, searchable, shareable, and analyzed exactly like meetings SalesEQ recorded itself.
Upload is how you bring in a single file SalesEQ did not record, such as a recording from a platform you do not run the desktop app on, or a file a teammate sent you.
If your meetings are in another meeting tool, [import them](/docs/capturing-meetings/import-meetings) instead. An import brings a whole backlog across at once and keeps each meeting's date and recorder.
## Upload a file [#upload-a-file]
### Open Manual upload [#open-manual-upload]
Go to [Meetings](https://app.saleseq.ai/meetings) and select **Manual upload**.
### Add a file [#add-a-file]
Drag a file into the dialog, or select the drop zone to browse for it.
SalesEQ accepts common audio and video formats, including MP4, MOV, MP3, M4A, WAV, and WebM.
### Follow its progress [#follow-its-progress]
The dialog closes and a temporary row appears at the top of **My meetings**. It shows the upload and processing state without blocking another upload.
Keep the tab open while the file is uploading. Once processing starts, you can leave the page. Processing usually takes a few minutes.
Select **Manual upload** again if you want to upload another recording in parallel.
## Verify it worked [#verify-it-worked]
The temporary row becomes a normal meeting under **My meetings** when processing finishes. Its generated title and thumbnail can arrive as the row updates.
## What is different about uploaded meetings [#what-is-different-about-uploaded-meetings]
An upload is a media file and nothing else. A meeting SalesEQ records arrives knowing what the meeting knew: who was in it, who spoke when, who shared a screen. An upload carries none of that, so SalesEQ works out what it can from the recording itself.
* **Speaker names are a best guess.** They come from the conversation rather than from the meeting, so they need checking more often than on a recorded meeting.
* **The title is generated from the content.** Rename it if your team calls it something else.
* **The date is the day you uploaded it.** A recording of a meeting from last month arrives dated today.
## Next [#next]
* [Viewing a meeting](/docs/your-meetings/viewing-a-meeting) covers fixing a title or a speaker name.
# What gets captured (/docs/capturing-meetings/what-gets-captured)
Every meeting produces the same set of parts, whether SalesEQ recorded it, you uploaded it, or you imported it from another tool. This page covers what each part is.
## The recording [#the-recording]
The audio and video of the meeting, captured on your machine or brought in from the tool that recorded it. This is what plays in the meeting view.
Some meetings are audio only, either because the meeting had no video or because you uploaded an audio file. Those meetings work normally, and the parts that need video are absent.
## The transcript [#the-transcript]
Every word spoken, split by speaker and timestamped against the recording. Selecting a line jumps playback to that moment.
SalesEQ names the speakers on its own. When a name is wrong, rename the speaker once and every line from them updates.
### Transcription vocabulary [#transcription-vocabulary]
Save names, acronyms, and product names under **Settings → Transcription vocabulary** in the web app to help SalesEQ recognize them in recordings.
Terms guide recognition but do not guarantee a particular spelling every time.
**Organization jargon** contains shared terms that admins manage for the organization. **Personal jargon** contains terms you manage for your own meetings.
SalesEQ combines the organization list with the meeting owner's personal list, not every attendee's list.
Add terms before your next meeting. Changing vocabulary does not update existing transcripts.
## The participants [#the-participants]
Two different lists come together here:
* **Participants** are the people who were in the meeting.
* **Detected speakers** are the distinct voices in the audio.
SalesEQ lines the two up, which is what puts real names on the transcript. This works without a calendar. What a calendar adds is everyone's email address, and anyone who was invited and did not turn up.
## The insights [#the-insights]
The summary, the scoring, and the conversation metrics, generated once processing finishes. See [Meeting insights](/docs/insights/meeting-insights) for what each one covers.
Insights read the whole recording rather than only the words. Each layer carries something the one before it cannot:
* **The words** carry what was discussed, what was asked, and what was agreed.
* **The audio** carries tone, pace, and delivery.
* **The video** carries body language, and whatever was on screen.
A meeting SalesEQ records has all three. An audio-only meeting has the first two. A file you import as a transcript has only the words, which is why that is the thinnest kind of meeting to work with.
## Next [#next]
* [Viewing a meeting](/docs/your-meetings/viewing-a-meeting) covers reading all of this.
* [Meeting insights](/docs/insights/meeting-insights) covers the generated analysis.
# Concepts (/docs/getting-started/concepts)
SalesEQ has a small vocabulary. Learn these eleven ideas and the rest of the product explains itself.
## Meeting [#meeting]
A **meeting** is the central object in SalesEQ. It holds the recording, the transcript, the participants, and everything generated on top of them.
Meetings arrive three ways:
* **Recorded by the desktop app** while you are on a meeting, either because you pressed Record or because you set that platform to auto-record. Recording happens on your own machine, so no bot joins the meeting and nobody sees an extra participant.
* **Uploaded** by hand as an existing audio or video file
* **Imported** from another meeting tool, either a backlog of past meetings or each new meeting as it finishes
However a meeting arrives, it becomes the same kind of meeting. Some meetings are audio only, and some are transcript only. Those still work, they show fewer things.
## Organization [#organization]
An **organization** is your company's account. It owns the members, the groups, the settings, and the meetings.
Every meeting belongs to exactly one organization.
## Members and roles [#members-and-roles]
Everyone in an organization is a member of it, and every member holds a role.
The word does double duty, so the casing matters. Lowercase, a member is anyone in the organization. Capitalized, **Member** is the role held by everyone who is not an **Admin**.
* **Member** records, uploads, imports, and shares their own meetings, and sees whatever has been shared with them.
* **Admin** does all of that, and also manages the organization: members, invites, groups, and organization-wide sharing rules.
People join by invitation, whichever role they get. An invite carries the role the person receives when they accept.
## Groups [#groups]
A **group** is a named set of people inside your organization, such as Sales, Customer Success, Engineering, or Leadership. Groups exist so you share with a team instead of a list of names, and so access stays correct when people join or leave.
Share a meeting with a group and everyone in it gets access, including people who join the group later.
## Access and sharing [#access-and-sharing]
Every meeting has exactly one **owner**. A meeting you record or upload is yours. An imported meeting goes to whoever recorded it in the original tool, when they are a member of your organization. Sharing never changes the owner. The owner or an admin can [transfer ownership](/docs/sharing/transfer-ownership) to another member.
A new meeting follows the organization's default sharing setting. New organizations start at **Restricted**, which means only the owner can open the meeting until someone shares it. An [Auto-share rule](#auto-share-rules) can share it the moment it finishes.
Sharing works two ways, and the share dialog separates them.
**People and groups** get a named grant:
| Share with | What it means |
| ---------- | -------------------------------------------------------- |
| A person | One specific member |
| A group | Everyone currently in that group, and anyone added later |
**General access** covers everyone at once. Set a meeting to organization access and every member can open it, without anyone being named.
Each grant carries a role:
* **Viewer** watches the recording, reads the transcript, and sees the insights.
* **Editor** does everything a viewer does, and also edits the meeting and shares it onward. Editor access with an expiration can edit the meeting but cannot share it onward.
Sharing is additive. If you have access through both a group and a direct grant, you keep the higher of the two roles.
### Access is not the same as appearing in Meetings [#access-is-not-the-same-as-appearing-in-meetings]
The [Meetings](https://app.saleseq.ai/meetings) page has two scopes. **My meetings** contains meetings you own. **All meetings** contains those meetings plus meetings shared directly with you or with a group you belong to.
Meetings available only through an organization default do not appear in **All meetings** or **Search**. If you have the link and your role allows access, you can still open the meeting.
## Auto-share rules [#auto-share-rules]
An **Auto-share rule** shares meetings the moment they finish, so nobody has to remember to do it.
Every rule points from a **source** (a person or a group) to a **target** (a person or a group), and grants viewer or editor.
Rules come in two kinds.
Every rule names whose meetings it watches, who receives them, and the role they get. What differs is when it fires.
An **Always** rule shares every meeting its source records.
A **Prompt** rule adds a condition written in plain language. SalesEQ reads each finished meeting and shares it only when the condition holds:
```text
Share this meeting if a customer reports a bug.
```
The prompt decides whether a meeting qualifies. It never names the recipient, because the rule already did.
Members write rules for their own meetings. Admins write rules for anyone's, and can lock them so the people whose meetings are shared cannot edit or remove them.
[Auto-share rules](/docs/sharing/auto-share-rules) covers writing them, and what a prompt can be evaluated against.
## Public links [#public-links]
A **public link** shares a meeting with someone outside your organization, such as a prospect, a customer, or a candidate, without making them a member.
Anyone with the link views the meeting, and nothing checks who they are. Links are managed per meeting, carry an expiry, and can be revoked at any time.
A public link opens a reduced view of the meeting: the recording, the transcript, the speakers, and the summary. Insights and Ask AI stay inside your organization. Sharing a meeting outward does not share what SalesEQ worked out about it.
## Participants and speakers [#participants-and-speakers]
These are two different things, and the difference matters.
* **Participants** are the people the meeting knows about, from the calendar invite and from the meeting platform.
* **Speakers** are the distinct voices SalesEQ detects in the audio.
SalesEQ puts names to the speakers on its own, so most transcripts read with real names from the start. Where it cannot work out who was talking, the transcript falls back to numbered speakers such as Speaker 1 and Speaker 2.
Rename a speaker once and every line from that speaker updates.
## Insights [#insights]
**Insights** are what SalesEQ generates from a meeting once it is processed. That covers the summary, the scoring, and conversation metrics such as talk ratios, monologues, filler words, speech rate, and qualification signals.
Insights are computed per meeting and stay attached to that meeting.
## Search [#search]
**Search** runs across your meetings plus meetings shared directly with you or with a group you belong to.
Search matches on meaning as well as on exact wording. Describe an objection in your own words and it finds the moment even when nobody phrased it that way. Type a product name or a competitor's name and it lands where that term came up.
## Connected assistants [#connected-assistants]
SalesEQ connects to AI assistants such as Claude and ChatGPT over MCP, so you ask questions about your meetings in the tools you already work in.
A connected assistant uses the same meeting scope as **All meetings** and **Search**. Disconnect SalesEQ from the assistant when you no longer want to use it there.
## Next [#next]
* [Record your first meeting](/docs/getting-started/record-your-first-meeting) puts a real meeting behind these ideas.
* [Share a meeting](/docs/sharing/share-a-meeting) covers access in practice.
* [Auto-share rules](/docs/sharing/auto-share-rules) covers sharing without doing it by hand.
# Create your organization (/docs/getting-started/create-organization)
Every SalesEQ account belongs to an organization. Creating one makes you its admin, which puts you in
charge of billing, members, and what new people see when they join.
If someone at your company already has a SalesEQ organization, [join theirs](/docs/getting-started/join-organization)
instead. Meetings, groups, and sharing all live inside a single organization, so being in the same one
is what lets your team see each other's meetings.
This takes about ten minutes.
## Before you start [#before-you-start]
* A work email address you can receive mail at
* A payment method, or a conversation with our team if your company pays by invoice
### Sign up [#sign-up]
Go to [app.saleseq.ai/sign-up](https://app.saleseq.ai/sign-up) and enter your name, work email, and a
password. You can also continue with Google.
Use your work email. Your domain determines which coworkers can find and join your organization later.
Landing on **Meetings** instead of the sign-up form means you are already signed in to an existing
account. Sign out first if you meant to use a different one.
### Verify your email [#verify-your-email]
SalesEQ sends a verification link to the address you signed up with. Open the message and select
**Verify Email**.
The link signs you in and takes you to organization setup. If the message has not arrived after a minute,
select **Resend verification email**.
### Name your organization [#name-your-organization]
Choose **Create a new organization**.
Enter an organization name. Your team sees this name in the app, and you can change it later.
Choose monthly or yearly billing. Yearly bills once and costs less per seat.
Decide whether coworkers can join on their own. With this turned on, anyone who signs up with an email
address on your domain lands in your organization without needing an invite. Leave it off if you want to
add every member yourself.
### Complete checkout [#complete-checkout]
Continue to checkout and pay for your first seat. Your organization activates as soon as the payment
succeeds.
Larger teams can be billed by invoice instead of card. That is set up by hand, so [contact us](mailto:billing@saleseq.ai) before you sign up and we
will arrange it.
### Finish onboarding [#finish-onboarding]
SalesEQ walks you through a short setup flow before dropping you into the web app. A new organization starts
with steps for connecting a calendar, connecting a CRM, downloading the desktop app, and connecting an AI
assistant.
Required steps have to be finished before you reach the web app. Optional steps have a **Skip for now** link.
Connecting a calendar and connecting an AI assistant are the two worth doing now rather than later.
[Calendar](/docs/integrations/calendar) covers what a connected calendar changes about your meetings, and
[AI assistants](/docs/ai-assistants/overview) covers asking questions about them from Claude or ChatGPT.
## Verify it worked [#verify-it-worked]
You land on **Meetings** with your organization name in the welcome message. The table is empty until
you record something, which is expected.
New organizations start with default sharing set to **Restricted**. New meetings stay private to their
owner until someone shares them or an auto-share rule grants access. An admin can change this under
[Organization Default Sharing](https://app.saleseq.ai/settings#organization-default-sharing).
## Invite your team [#invite-your-team]
An organization with one person in it does not do much. Inviting your team is the step that makes shared
meetings and groups worth anything.
Open [Organization members](https://app.saleseq.ai/settings#organization-members) and select **Invite**. You
can send invites to specific addresses or copy a link anyone can use, and you choose the role people land
with either way.
[Members and roles](/docs/account/members-and-roles) covers both routes in full.
## Next [#next]
* [Record your first meeting](/docs/getting-started/record-your-first-meeting) gets a real meeting into SalesEQ.
* [Members and roles](/docs/account/members-and-roles) covers inviting your team and what each role can do.
* [Onboarding flow](/docs/account/onboarding-flow) controls which steps new joiners have to finish.
# Download SalesEQ (/docs/getting-started/download)
The desktop app is what captures a meeting while it happens. It records, it transcribes live as people
talk, and it lets you ask questions about the meeting without waiting for it to finish.
Everything after a meeting works in the web app. Everything during one needs the desktop app, so install
it on whichever machine you take meetings on.
## Install [#install]
### Download the app [#download-the-app]
Open [Download](https://app.saleseq.ai/download) and choose macOS or Windows.
### On macOS, drag it to Applications [#on-macos-drag-it-to-applications]
Drag SalesEQ into your Applications folder before you open it.
Running it from your Downloads folder works at first, then stops updating. The app cannot install its own
updates from outside Applications, so it falls behind and eventually breaks. This is the most common
setup mistake.
### Approve the system permissions [#approve-the-system-permissions]
macOS asks before it lets any app reach your screen or your audio, and SalesEQ records nothing until you
approve those prompts. Accept each one as it appears. macOS sometimes wants the app quit and reopened
before a permission takes effect.
Windows asks for less. Approve whatever it prompts for and carry on.
### Sign in [#sign-in]
Sign in once the permissions are done. The app opens your browser, then hands you back. Use the same
account you use for the web app.
## Where it lives [#where-it-lives]
The app runs in your menu bar on macOS and your system tray on Windows. Start and stop a recording from
there without opening the main window.
SalesEQ can also show recording status on its Dock icon on macOS or its taskbar icon on Windows. A red dot
means recording, and an amber dot means paused. Turn the indicator on or off under **Dock icon** or
**Taskbar icon** in the desktop app's **Settings**.
## Updates [#updates]
The app installs its own updates in the background and shows the version you are running. You do not need
to download a new build to stay current.
On macOS this depends on the app living in Applications. If updates never seem to arrive, check where you
dragged it.
## Verify it worked [#verify-it-worked]
Open SalesEQ from Applications on macOS or the Start menu on Windows. The desktop app window opens and shows
that you are signed in. To test the recording path, continue to [Record your first meeting](/docs/getting-started/record-your-first-meeting).
## Next [#next]
* [Record your first meeting](/docs/getting-started/record-your-first-meeting) walks through a meeting end to end.
* [Desktop app recording](/docs/capturing-meetings/desktop-app) covers capturing a meeting.
* [Live AI](/docs/live-ai/overview) covers reading and questioning a meeting as it happens.
# Join your organization (/docs/getting-started/join-organization)
A teammate already set up SalesEQ and invited you. Joining their organization is how you see the meetings
your team shares.
You do not choose a plan or enter payment details. Your admin handles billing.
This takes about five minutes.
## Before you start [#before-you-start]
* An invite link from your admin, or a work email address on a domain your team already uses
### Open the invite link [#open-the-invite-link]
Open the link your admin sent you. It looks like this:
```
https://app.saleseq.ai/invite/33665390-c8f3-434f-b1b3-a18a53922c03
```
The page shows which organization you are joining and which role you get.
The steps below cover the most common path. The page adapts to your situation, so you might see fewer
screens than this.
### Sign in or create an account [#sign-in-or-create-an-account]
If you are signed out, select **Sign in** or **Create account**. SalesEQ returns you to the invite when
you finish. New accounts verify their email first.
If you are already signed in, SalesEQ takes you straight to the accept screen.
Check the email address on this screen before you continue. That account is the one that joins.
### Accept the invite [#accept-the-invite]
Select **Accept Invite**. SalesEQ adds you to the organization and starts setup.
### Finish onboarding [#finish-onboarding]
Your admin chooses these steps, so they differ between organizations. They can include connecting a
calendar, connecting a CRM, downloading the desktop app, and connecting an AI assistant.
You have to finish required steps before you reach the web app. Optional steps have a **Skip for now** link.
Connect a calendar and an AI assistant now rather than later.
[Calendar](/docs/integrations/calendar) covers what a connected calendar changes about your meetings.
[AI assistants](/docs/ai-assistants/overview) covers asking questions about them from Claude or ChatGPT.
## Two kinds of invite [#two-kinds-of-invite]
Invites come in two kinds. The difference is whether you can join from a different account.
An invite **sent to your email address** works only for that address. If you open it while signed in as
someone else, SalesEQ asks you to switch accounts.
An invite from a **copied link** works for anyone who opens it. The accept screen includes **Login with a
different account** if you are on the wrong one.
## Troubleshooting [#troubleshooting]
The invite page explains most problems as they happen. Three of them need action somewhere else.
* **Already in another organization.** Leave your current organization under [Organization members](https://app.saleseq.ai/settings#organization-members) first. An account
belongs to one organization at a time.
* **Organization full.** Your admin is out of seats. Select **Notify admin** to email them.
* **Expired, revoked, or already used.** Ask your admin for a new link. An invite sent to a single
address works once.
## Join from the setup screen [#join-from-the-setup-screen]
Sign up at [app.saleseq.ai/sign-up](https://app.saleseq.ai/sign-up), select **Join an existing
organization**, and paste the same invite link.
Both routes end in the same place. Opening the link directly takes fewer steps.
## Join with your work email [#join-with-your-work-email]
If your admin turned on email domain auto-join, sign up with your work email and verify it. You land in your
company's organization without an invite, because your email domain matches.
If you expected this and reached the organization setup screen instead, ask your admin for an invite link.
## Verify it worked [#verify-it-worked]
You land on **Meetings**, and a welcome message names your organization.
**My meetings** fills up when you record or upload something. **All meetings** also includes meetings a
teammate shares directly with you or with a group you belong to.
## Next [#next]
* [Record your first meeting](/docs/getting-started/record-your-first-meeting) gets a real meeting into SalesEQ.
* [Concepts](/docs/getting-started/concepts) explains meetings, sharing, and groups in eleven short sections.
* [Share a meeting](/docs/sharing/share-a-meeting) covers getting a meeting in front of your team.
# Record your first meeting (/docs/getting-started/record-your-first-meeting)
You are in an organization and looking at an empty **Meetings** page. This guide fills it.
SalesEQ records on your own machine rather than sending a bot to the meeting. Nobody sees an extra
participant.
This takes about ten minutes, most of which is the meeting itself.
## Before you start [#before-you-start]
* A SalesEQ account in an organization, from [creating one](/docs/getting-started/create-organization)
or [joining one](/docs/getting-started/join-organization)
* A Mac or Windows machine you take meetings on
* A meeting on Zoom, Google Meet, or Microsoft Teams. An empty one you start yourself is fine.
[Supported platforms](/docs/capturing-meetings/desktop-app) covers Slack huddles and which browsers work for Google Meet.
### Install the desktop app [#install-the-desktop-app]
Open [Download](https://app.saleseq.ai/download) and get the app for macOS or Windows. You may already
have done this during onboarding.
### Approve the system permissions [#approve-the-system-permissions]
macOS asks before it lets any app reach your screen or your audio, so SalesEQ cannot record until you
approve those prompts. Accept each one as it appears. macOS sometimes wants the app quit and reopened
before a permission takes effect.
Windows asks for less. Approve whatever it prompts for and carry on.
### Sign in [#sign-in]
Sign in once the permissions are done. The desktop app hands you to your browser and brings you back
afterward.
### Join a meeting [#join-a-meeting]
Join a real meeting, or start an empty one and sit in it alone if you would rather try this out first.
SalesEQ treats both the same.
SalesEQ spots the meeting and shows a bar with a **Record** button.
### Start recording [#start-recording]
Select **Record**. A control bar appears showing what you are recording and how long it has been running.
Everyone on the meeting is recorded, so tell them first if that is how your team works. SalesEQ can post
a notice in the meeting chat for you as recording starts. See
[Recording notice](/docs/capturing-meetings/recording-notice).
### Stop and wait for processing [#stop-and-wait-for-processing]
Stop the recording when the meeting ends. The file uploads and processing starts on its own, and usually
finishes inside five minutes.
Processing transcribes the meeting and runs the analysis behind everything in the meeting view.
[What gets captured](/docs/capturing-meetings/what-gets-captured) covers the parts you end up with.
### Open the meeting [#open-the-meeting]
Your meeting appears in the desktop app once processing finishes. Select it and it opens in the web app,
which is where meetings are watched, read, and shared.
## Verify it worked [#verify-it-worked]
Opening the meeting is the check. A recording that plays with its transcript beside it means the whole
path worked.
Speakers sometimes come through under the wrong name. Rename one in the web app and every line from that
speaker updates.
## Next [#next]
* [Automatic recording](/docs/capturing-meetings/automatic-recording) stops you having to press Record every time.
* [Share a meeting](/docs/sharing/share-a-meeting) covers getting a meeting in front of your team.
* [Upload a recording](/docs/capturing-meetings/upload) brings in meetings you captured somewhere else.
* [Concepts](/docs/getting-started/concepts) explains meetings, sharing, and groups in eleven short sections.
# Meeting insights (/docs/insights/meeting-insights)
Once a meeting finishes processing, SalesEQ generates a set of analyses alongside the transcript. Each one is a tab in the meeting view.
You are not meant to read all of them on every meeting. Most people live in Overview and reach for the rest when coaching or preparing.
## The tabs [#the-tabs]
**Overview** is always there. The rest appear when the meeting produced that analysis, so a short or quiet
meeting shows fewer tabs than a long one. Each tab carries a number in the strip, such as a score or a
count, so you can see where to look without opening anything.
| Tab | What it covers |
| ------------- | ------------------------------------------------------------ |
| Overview | The summary, the top moments, and the next action |
| Nonverbal | Voice and visual moments from the recording |
| Methodology | Qualification evidence, including BANT signals |
| Questions | The questions asked and what was agreed as next steps |
| Coaching | Focus areas and strengths for the person who ran the meeting |
| Speech and EQ | Pace, talk time, monologues, and how the conversation landed |
## Which to use when [#which-to-use-when]
* **Preparing for a follow-up:** Overview, then Questions for what was agreed.
* **Coaching a rep:** Coaching, with Speech and EQ for the talk ratio.
* **Qualifying a deal:** Methodology, then Questions.
* **Diagnosing a meeting that went flat:** Nonverbal, then Speech and EQ.
## Fix speaker names first [#fix-speaker-names-first]
Every insight is generated from the recording, so anything measured per person is only as good as the speaker
names. Correct them before you rely on per-person analysis rather than after. See
[Viewing a meeting](/docs/your-meetings/viewing-a-meeting).
# Calendar (/docs/integrations/calendar)
Connecting a calendar lets SalesEQ match each recording to the event it came from. Meetings arrive carrying the title you actually put on the invite, and the people you invited.
It also tells the desktop app what is ahead, so it can notify you before a meeting starts and let you join and record it in one step.
Connecting a calendar does not put a bot in your meetings. SalesEQ records on your own machine either way. The calendar supplies the context around the recording.
## Connect as many as you need [#connect-as-many-as-you-need]
Connect as many calendars as you like, from either provider. Two Google accounts and an Outlook account can sit in the same SalesEQ account.
That matters when your meetings are split across accounts: a fractional CRO working with several companies, a consultant with a client login, or anyone whose personal calendar holds real meetings. SalesEQ reads them as one schedule, so nothing depends on which account an invite happened to land in.
## Connect [#connect]
### Open settings [#open-settings]
Go to [Calendar integrations](https://app.saleseq.ai/settings#calendar-integrations) in the web app, or open **Settings** in the desktop app. Both manage the same connections, so it makes no difference which you use.
### Choose your provider [#choose-your-provider]
Connect **Google Calendar** or **Microsoft Outlook**, and repeat for each account you want.
### Authorize SalesEQ [#authorize-saleseq]
Sign in with the account holding the calendar you take meetings on.
## Verify it worked [#verify-it-worked]
The connection shows as **Connected** in settings. It may sit at **Connecting** for a while first, which is normal.
Record your next meeting. It arrives named after the calendar event, with the attendees attached.
## Knowing what is coming up [#knowing-what-is-coming-up]
The desktop app lists **Upcoming meetings** across every calendar you connected, each one showing its
platform and length. **Join and Record** opens the meeting and starts SalesEQ with it.
**Join and Record** appears about five minutes before a meeting starts and stays until the meeting ends. It
is still there once a meeting is already running and you have not started recording.
A notification arrives about a minute before the start with the same option, so you do not have to be looking
at the app to catch it.
Three settings in the desktop app control all of this:
| Setting | What it does |
| ------------------------------------------- | ------------------------------------------------------ |
| Show upcoming meetings | Shows or hides the list on My Meetings |
| Show upcoming meetings with no participants | Includes events with no participants and no video link |
| Meeting notifications | Notifies you about a minute before a meeting starts |
## What it changes [#what-it-changes]
| Without a calendar | With a calendar |
| ------------------------------------- | ------------------------------------------------------------- |
| A generated title | The title you put on the invite |
| Who spoke, and who was in the meeting | The same names plus emails, and anyone invited who never came |
A recorded meeting already knows who turned up and who said what. What a calendar adds is who was meant to be there and how to reach them.
Those emails are what tie a meeting to a person and a company across your other tools. Auto-share rules, follow-up drafts, and CRM pushes all act on them.
## Pausing and disconnecting [#pausing-and-disconnecting]
Two ways to stop a calendar, and the difference is whether you sign in again later.
**Pause sync** stops SalesEQ reading that calendar and keeps the connection. **Enable sync** turns it back on, with no authorization to repeat.
**Disconnect** removes the connection. Reconnecting means going back through sign-in.
Either way, meetings already recorded keep the titles and attendees they were matched with.
## Next [#next]
* [Automatic recording](/docs/capturing-meetings/automatic-recording) covers what happens when a meeting is detected.
* [What gets captured](/docs/capturing-meetings/what-gets-captured) covers where each part of a meeting comes from.
# Email and follow-up drafts (/docs/integrations/email)
Connect your inbox and SalesEQ writes follow-up emails as drafts in your own mailbox, where you edit them like any other draft.
Nothing is ever sent on your behalf. You review and send every email yourself.
## Connect [#connect]
### Open settings [#open-settings]
Go to [Email integrations](https://app.saleseq.ai/settings#email-integrations).
### Connect Gmail or Outlook [#connect-gmail-or-outlook]
Choose your provider and authorize SalesEQ with the mailbox you send from.
## Draft a follow-up [#draft-a-follow-up]
Two ways, and they end in the same place.
Select **Email** at the top of a meeting. It opens [Ask AI](/docs/your-meetings/ask-ai) and runs the
follow-up prompt for you.
Or ask Ask AI yourself. That is the better route when you want to say what the email is for, because a recap
and a proposal follow-up are different emails.
Either way the draft comes back with a subject line. With a connected mailbox, write it into your drafts
folder. Without one, copy it in a single click and paste it wherever you send from.
## Verify it worked [#verify-it-worked]
Open your drafts folder in Gmail or Outlook. The draft is there, unsent, and editable.
## Getting a usable draft [#getting-a-usable-draft]
The draft is a starting point, not a send-ready email. Two things improve it:
* **Correct the speaker names first.** A follow-up that attributes a commitment to the wrong person is worse than no draft at all.
* **Say what the email is for.** Asking for a recap produces something different from asking for a proposal follow-up.
## Next [#next]
* [Ask AI](/docs/your-meetings/ask-ai) covers the rest of what it drafts.
* [HubSpot](/docs/integrations/hubspot) covers pushing notes to your CRM.
# HubSpot (/docs/integrations/hubspot)
Connect HubSpot and send a meeting's summary and notes onto a contact or a deal without leaving SalesEQ.
You choose which meeting goes where, one at a time. Nothing syncs on its own.
## Connect [#connect]
### Open settings [#open-settings]
Go to [CRM integrations](https://app.saleseq.ai/settings#crm-integrations).
### Connect HubSpot [#connect-hubspot]
Authorize SalesEQ against your HubSpot account.
## Push a meeting [#push-a-meeting]
Open the meeting, select **More actions** next to **Share**, then select **Add to HubSpot**. Search for the
contact, the deal, or both, and send it. Both are optional, so you can attach a meeting to a deal without
naming a contact.
**Add to HubSpot** appears only once HubSpot is connected.
## Verify it worked [#verify-it-worked]
Open the contact or deal in HubSpot. The notes from the meeting are on the record.
## Why you push each meeting yourself [#why-you-push-each-meeting-yourself]
Every meeting is a judgment call about whether it belongs in the CRM. Internal meetings, first conversations that went nowhere, and meetings with the wrong person would all end up on customer records if this ran on its own.
Pushing per meeting keeps your CRM readable.
## Next [#next]
* [Email and follow-up drafts](/docs/integrations/email) covers the follow-up itself.
# Chat (/docs/live-ai/chat)
Chat answers questions about the meeting you are in, while you are still in it. Use it to recall
something you missed, check a claim, look something up, or work out what to say next.
## Ask a question [#ask-a-question]
Type into the box on the **Chat** tab and press Enter. Questions that work well:
```text
What number did they say for headcount?
What have they asked for that I have not answered?
Who on their side has not spoken yet?
What did they say about timing earlier?
```
Answers are short on purpose. You are reading them in the middle of a conversation, so Chat is built
and tested to stay scannable rather than thorough. Ask for more detail and it gives you more detail.
## Quick actions [#quick-actions]
The buttons in the composer send a prompt in one select, without typing. They behave like a message
you typed, so they carry the same meeting context and queue the same way.
Three are shown at a time. **Assist**, **Explain**, and **Catch me up** are the ones you start with.
**Fact check**, **Answer**, and **LinkedIn** are available to swap in, and **LinkedIn** looks up
whoever you are talking to and comes back with their profile and their recent history.
Change them under **Chat quick actions** in the desktop app's **Settings**:
1. Select **Choose actions** and pick the three you want shown, in the order you want them.
2. Write your own with a title of up to 16 characters and the prompt it sends.
3. Check the preview, which shows the composer as it will look in the meeting.
A quick action you write is worth the effort when it is specific to how you sell. A prompt that
names your competitors and asks how to position against whichever one comes up is a better use of a
button than anything generic.
### Share one with your organization [#share-one-with-your-organization]
Each quick action you write is **Mine** or **Organization**.
**Mine** keeps it yours. Nobody else in the organization sees it, and it follows you to your other
computers.
**Organization** puts it in the shared catalog, where any member can select it. Any member can share
one, not only an admin. Sharing adds the button to the catalog and changes nobody's selection, so
people opt in by choosing it.
Editing a shared action stays with whoever made it and the organization admins. An edit reaches
other people's meetings the next time their catalog refreshes, including mid-meeting, though a
prompt already sent keeps the text it was sent with.
SalesEQ blocks deleting a shared action, or making it personal again, while another member still has
it selected. It tells you how many people that is, so a button somebody relies on does not disappear
from under them.
You get 50 personal quick actions and 200 shared ones per organization, and a prompt can run to
20,000 characters. Presets and other people's shared actions do not count against your 50.
### Set the buttons for one meeting [#set-the-buttons-for-one-meeting]
Quick actions are also assignable per meeting, ahead of time, alongside the checklist. Walking into
a renewal call with the right three buttons already up is worth more than swapping them while
somebody talks. See [Live AI rules](/docs/live-ai/rules).
## What Chat can see [#what-chat-can-see]
Every question carries the meeting with it, so you never have to explain what is going on:
* **The transcript** so far, with each speaker named.
* **The meeting events**, including who joined, who left, and when a screen share started.
* **The calendar event**, when the meeting came from one. That covers the title, the scheduled
times, the invited attendees, and the organizer's description.
* **Your earlier messages** in this chat.
* **The meeting view**, when the meeting-view control is on.
Calendar details are context rather than fact. Chat treats what people actually said as the stronger
evidence when the two disagree.
## Include the meeting view [#include-the-meeting-view]
The meeting-view control in the composer attaches a picture of your meeting to each question. Use it
when the answer depends on something visible rather than something said, such as a slide on screen.
SalesEQ captures the meeting's own window. Zoom and the Microsoft Teams desktop app each give the
meeting a window of its own, so this works whatever else you have in front of you.
Google Meet is the exception, because there the meeting is a browser tab and the window belongs to
the browser. Chat gets whichever tab is in front, so leave Meet on the active tab while you ask.
You can also attach up to five images of your own with the image control.
## Searching the web [#searching-the-web]
Chat searches the web when the answer is not in the meeting, and runs several searches at once when
a question needs them. Above the answer you get a receipt showing what was searched, and the answer
cites its sources.
## While it is answering [#while-it-is-answering]
Send another message while an answer is streaming and it queues behind the current one. From there:
* **Steer** stops the current answer and takes your queued message now.
* **Edit** changes the queued message before it is sent.
* **Stop** ends the current answer where it is.
On any message you have already sent, **Edit and resend** reruns it. On any answer, you can copy the
answer on its own or the conversation through that point.
## The conversation is not saved [#the-conversation-is-not-saved]
The chat is discarded when the meeting closes, along with any images you attached. Copy what you
want to keep before you leave: each answer carries a control to copy that answer, and another to
copy the conversation through it. See
[Save anything you want to keep](/docs/live-ai/overview#save-anything-you-want-to-keep).
Once the meeting ends, use [Ask AI](/docs/your-meetings/ask-ai) on the meeting itself. It reads the
processed transcript along with the audio and video, so it knows things Chat could not.
## Next [#next]
* [Checklist](/docs/live-ai/checklist) tracks objectives instead of answering questions.
* [Live AI rules](/docs/live-ai/rules) covers choosing a meeting's buttons before it starts.
* [Ask AI](/docs/your-meetings/ask-ai) covers asking about a meeting after it ends.
* [AI assistants](/docs/ai-assistants/overview) covers questions that span more than one meeting.
# Checklist (/docs/live-ai/checklist)
Checklist tracks the objectives you need to cover before the meeting ends. It reads the meeting as
it happens and marks each objective against what has actually been said.
Checklists are saved to your organization, not to one machine. Keep as many as you need, set a
default for your meetings, and switch to a different one mid-meeting.
The tab itself carries a count of the acceptance criteria covered so far, so you can see where you
stand from Chat or Transcript without switching over.
## Build a checklist [#build-a-checklist]
Open the desktop app, go to **Settings**, and find the **Checklist** section. The checklist under
**Default checklist** is the one your meetings start with. Choose **No checklist** to record
without one.
Your default is the fallback. Any upcoming meeting can be given a checklist of its own, and a week
of them can be set in one go, under [Live AI rules](/docs/live-ai/rules).
### Start from a preset [#start-from-a-preset]
The checklist menu includes presets for common frameworks, such as **MEDDPICC**, and a few of our
own, such as **Founder Mode**. A preset arrives complete, with the title, the objectives, and the
acceptance criteria filled in.
Presets cannot be edited in place. To adapt one, select it and choose **Duplicate checklist**. The
copy is yours, and you can cut, reword, and reorder it until it matches how you run meetings.
### Or write your own [#or-write-your-own]
1. Select **New checklist** and name it. The title is your own label for it, up to 30 characters.
2. Select **Add objective** and give it a title, such as Budget or Next steps.
3. Add at least one acceptance criterion to the objective.
An acceptance criterion is what has to be true for the objective to count as covered. Write it as a
statement rather than a question:
```text
An available budget or range is confirmed.
The final decision-maker is identified.
A target decision date is confirmed.
```
An objective with no criteria does not appear in meetings, because there is nothing to evaluate it
against. A checklist holds up to 50 objectives and 50 acceptance criteria in total, with at most 8
criteria on any one objective.
### Choose who can use it [#choose-who-can-use-it]
**Visible to** on each checklist controls who sees it:
* **Only me** keeps the checklist personal.
* **My organization** shares it with everyone in your organization, so a team can run the same
checklist without rebuilding it.
Anyone in the organization can run a shared checklist. Editing or deleting it stays with the person
who made it and the organization admins, and SalesEQ confirms before a change that affects other
people already using it.
## Statuses [#statuses]
Criteria are assessed individually, and each objective takes its status from the criteria under it.
| Status | On a criterion | On an objective |
| -------------- | -------------------------------------------------- | ----------------------------- |
| **Open** | Nothing in the meeting speaks to it yet | Every criterion is still open |
| **Unclear** | Something touched on it, and it does not settle it | Shown as Partial |
| **Developing** | Partly established, not yet enough | Shown as Partial |
| **Covered** | Established by what was said | Every criterion is covered |
Expand an objective to see each criterion, its status, and why Checklist assessed it that way.
## Evidence you can check [#evidence-you-can-check]
Each criterion carries timestamped evidence: who said it, and when. Selecting a piece of evidence
takes you to that moment in the transcript, and you can come back to the checklist from there.
Evidence comes in two kinds. Most of it supports the assessment. Evidence that cuts against it is
marked as contradicting, which is what stops an objective looking settled after somebody walked it
back.
Every check reads the whole meeting rather than the last few minutes. An objective raised early and
resolved forty minutes later still connects.
## Switch or edit mid-meeting [#switch-or-edit-mid-meeting]
The checklist title on the tab is a menu. Use it to switch to another checklist, drop to **No
checklist**, start a **New checklist**, or edit the one you are running, all without leaving the
meeting.
Switching does not cost you anything. The checklist you switch to is assessed against the whole
conversation so far, not only what is said after the switch. Each checklist also keeps its own
assessment for the meeting, so switching away and back picks up where it left off.
Edits reach the meeting the same way. Save a change to the checklist you are running, from the tab
or from **Settings**, and the live assessment updates to match.
## When it rechecks [#when-it-rechecks]
Checklist reruns on its own as the conversation moves. While objectives are still outstanding it
rechecks at most once every 15 seconds. Once everything is covered it slows to between one and two
minutes, and long meetings slow down the same way.
To pull it forward, select the recheck control next to the checklist title. It runs against the
latest transcript. The control stays unavailable until the conversation has started, because there
is nothing to check against before then.
## What is not saved [#what-is-not-saved]
Checklists themselves are saved: your catalog, your default, and anything you share with the
organization all live in your account.
The results of a meeting are not. Checklist is a live instrument, not a record, and the assessment
is discarded when the meeting closes. This tab has no copy control, so a screenshot before you
leave the meeting is the only way to keep an assessment. See
[Save anything you want to keep](/docs/live-ai/overview#save-anything-you-want-to-keep).
## Next [#next]
* [Chat](/docs/live-ai/chat) answers questions instead of tracking objectives.
* [Transcript](/docs/live-ai/transcript) is where checklist evidence points.
* [Live AI rules](/docs/live-ai/rules) covers assigning a checklist to a meeting in advance.
* [Meeting insights](/docs/insights/meeting-insights) covers the analysis produced after a meeting.
# Overview (/docs/live-ai/overview)
Live AI is a window that sits over your meeting while the meeting is running. It transcribes as
people talk, answers questions about what has been said, and tracks whether you have covered what
you meant to cover.
Everything else in SalesEQ works on a meeting once it has finished. Live AI works on the meeting you
are still in.
## Turning it on and off [#turning-it-on-and-off]
Live AI is on by default. Start a recording and the window opens over your meeting.
The switch is **Start Live AI by default**, under **Live AI** in the desktop app's **Settings**.
Turn it off to record without the window, and the recording itself is unaffected either way. A
change applies to your next meeting rather than the one you are in.
That switch is the fallback. A rule, a setting on the meeting itself, or your organization's policy
can all decide instead, and [Live AI rules](/docs/live-ai/rules) covers which one wins.
Two cases are worth knowing now. Your organization can **require** Live AI, which starts it whatever
your switch says. It can also **block** Live AI, which is the one setting that stops you opening the
window by hand mid-meeting.
## The three tabs [#the-three-tabs]
Ask about the meeting, or the web.
Follow the words and the events.
Track the objectives you set.
The tabs are not exclusive. Each one opens and closes on its own, so you can run all three side by
side, or any two of them. The window widens to fit what you have open, and selecting an open tab
closes it again.
Reading the transcript while Chat answers is the case this exists for, along with watching Checklist
move while you talk.
## Moving, sizing, and minimizing [#moving-sizing-and-minimizing]
Drag the window anywhere on screen. It snaps to eight positions around the edges of your display,
and it remembers where you left it for next time. The tab strip moves to the top or the bottom of
the window depending on where you snap it, so it always sits nearest the edge.
To make the window bigger or smaller, select it and press **Cmd** with **+** or **-** (**Ctrl** on
Windows). Five steps run from 90% to 150%, **Cmd 0** returns it to 100%, and a readout shows the
scale as it changes. Everything scales together, so a larger window means larger text rather than
more content.
**Minimize** collapses the window to its tab strip. The strip still shows the checklist count, and
it still drags around. Restore it and the tabs you had open come back. Closing every tab collapses
the window the same way, and selecting any tab in the strip opens it again.
## Keeping it off a screen share [#keeping-it-off-a-screen-share]
**Hide Live AI from screen sharing** is on by default, under **Live AI** in **Settings**. It keeps
the window out of supported screen shares, so the people you are meeting with do not see what you
are asking.
Some macOS capture methods still show it. Treat the setting as a strong default rather than a
guarantee, and check your own share once if it matters to you.
## Save anything you want to keep [#save-anything-you-want-to-keep]
Live AI stops with the recording, and nothing it produced is kept. The chat, the checklist
assessments, and the live transcript are all discarded when the meeting closes. None of it attaches
to the finished meeting, and there is no way to reopen it afterward.
Copy what you need before you leave:
* **The transcript.** The copy control in the window header copies every line captured so far, with
timestamps. It works from any tab.
* **The chat.** Each answer carries a control to copy that answer, and another to copy the
conversation through it.
* **The checklist.** This tab has no copy control yet, so a screenshot is the only way to keep an
assessment. The checklist itself is saved to your account, and only the assessment of this
meeting goes.
Carrying more of this through to the finished meeting is something we intend to add, most likely
starting with the transcript. Until that ships, treat the window as leaving nothing behind.
## What you get afterward [#what-you-get-afterward]
SalesEQ processes the meeting once it ends, which is a separate pass over the recording rather than
a copy of what Live AI produced.
The transcript comes back with corrected wording and timestamps that line up with the recording, and
the insights are generated from the audio and video rather than the words alone. What Live AI showed
you in the moment was a fast draft, and this is the accurate version.
## Next [#next]
* [Chat](/docs/live-ai/chat) covers asking questions during the meeting.
* [Live AI rules](/docs/live-ai/rules) covers deciding this per meeting, and setting the window up
in advance.
* [Ask AI](/docs/your-meetings/ask-ai) covers asking questions once the meeting is over.
* [What gets captured](/docs/capturing-meetings/what-gets-captured) covers everything a recording
produces.
# Live AI rules (/docs/live-ai/rules)
Live AI starts with your recording unless something says otherwise. Live AI rules are where you say otherwise, and where you set up what the window holds before you are in the meeting.
Find them in the desktop app under **Settings**, in the **Live AI rules** section. **Upcoming meetings** lists what is on your calendar. **Automatic rules** holds the rules that decide for you.
## The default [#the-default]
**Start Live AI by default** sits under **Live AI** in **Settings**, above this section. It is on, and it decides what happens on a meeting no rule matches.
Changing it affects your next meeting rather than the one you are in. Closing or minimizing the window during a meeting is a display action and does not change this setting.
## Who decides [#who-decides]
Two settings decide whether Live AI starts, and they belong to different people.
**Personal Live AI** is yours, and it is **On by default** or **Off by default**.
**Organization Live AI policy** is the admin's, and it has three values:
| Policy | What it does |
| ---------------- | ----------------------------------------------------------------------- |
| Let users decide | Members use their own Live AI settings. This is the starting point. |
| Require Live AI | Live AI starts whenever a member records the meeting. |
| Block Live AI | Live AI does not start, and members cannot start it during the meeting. |
**Require Live AI** does not start a recording. It decides what happens once one starts.
**Block Live AI** is the only setting that takes away the manual control. With the other two, a member whose Live AI did not start can still open it mid-meeting.
SalesEQ resolves the policy when your recording begins and holds it for that meeting. A rule changed while you are talking does not reach the meeting you are in.
## What wins [#what-wins]
Working from the top, the first line that applies decides:
1. An organization setting on that meeting.
2. The first matching **Organization Live AI rule**.
3. Left to you, which resolves in the same order: a personal setting on that meeting, then the first matching **Personal Live AI rule**, then **Start Live AI by default**.
## Automatic rules [#automatic-rules]
The **Automatic rules** tab holds **Personal Live AI rules** and **Organization Live AI rules**. Both lists are ordered, and the first matching rule wins, so the specific rules belong above the general ones. Organization rules are admin-only.
Rules match on the calendar invitation, using the same fields and operators as recording rules: **Meeting title**, **Organizer email**, **Invitees**, and, on your own rules, **Calendar connection**. That includes **include anyone outside**, which separates external meetings from internal ones. See [what a rule can match on](/docs/capturing-meetings/recording-rules#what-a-rule-can-match-on).
Recording rules and Live AI rules are separate lists and do not affect each other. A meeting can record without Live AI, and a meeting blocked from recording never reaches Live AI at all, because Live AI reads the live capture.
## Set up a meeting before it starts [#set-up-a-meeting-before-it-starts]
The **Upcoming meetings** tab carries four columns you can set per meeting, and a last one, **What Live AI will do**, that resolves them into what actually happens.
**Personal Live AI** and **Organization Live AI policy** work like the recording columns. They start at **Follow rules** or **Follow policy**, showing what your rules produced. Picking anything else overrides them for that meeting alone.
**Checklist** picks which checklist the meeting opens with. Choose one from your catalog, choose **No checklist**, or leave it on your default. See [Checklist](/docs/live-ai/checklist) for building them.
**Quick actions** picks which buttons the Chat composer shows, up to three, in the order you choose. Leave it alone and the meeting uses the buttons you have selected everywhere else. See [Chat](/docs/live-ai/chat) for the catalog.
Setting a checklist or quick actions in advance is the point of the tab. Walking into a renewal call with the renewal checklist already up, and the buttons you want for it, beats setting both while somebody is talking to you.
Checklist and quick actions stay editable even when Live AI is blocked or unavailable for the meeting, so the setup survives a policy change.
## Change several meetings at once [#change-several-meetings-at-once]
Select meetings in the **Upcoming meetings** tab and a toolbar appears above the table. It offers **Personal Live AI**, **Organization Live AI policy**, **Checklist**, and **Quick actions**.
Pick a value, then select **Apply to** the selected meetings. Up to 100 go in one batch, and meetings that cannot take the change are skipped and reported rather than failing the rest.
This is the fastest way to put one checklist on a week of meetings.
## Verify it worked [#verify-it-worked]
Open the **Upcoming meetings** tab and read **What Live AI will do** on a meeting your rule should match. It names the rule that decided.
Then record the meeting. Live AI opens, or stays shut, to match.
## Next [#next]
* [Overview](/docs/live-ai/overview) covers the window and its three tabs.
* [Checklist](/docs/live-ai/checklist) covers building the checklists you assign here.
* [Recording rules](/docs/capturing-meetings/recording-rules) decides whether the meeting records at all.
# Transcript (/docs/live-ai/transcript)
The Transcript tab fills in as people talk. Read it back to catch a number, a name, or a job title
you missed, without interrupting anyone to ask again.
It is also what Chat and Checklist read. Anything the transcript captures, they can use.
## Named speakers [#named-speakers]
Lines are labelled with the participant's name rather than a generic speaker number. That makes the
transcript quicker to read back, and it lets you ask Chat about someone by name.
## A timeline, not only words [#a-timeline-not-only-words]
The transcript carries what happened in the meeting alongside what was said:
* Attendees joining and leaving
* Screen sharing starting and stopping
* Participant identity changes
* Recording pausing and resuming
Messages sent in the meeting chat appear too, marked as **Meeting chat**.
These lines are the context words alone cannot give you. Who was in the room when something was
agreed is often the thing you need, and it is the kind of detail nobody types into their notes.
## Copying it [#copying-it]
**Copy transcript**, in the window header, copies everything captured so far with timestamps. Spoken
lines carry the speaker, and event lines carry what happened. It works from any tab, so it is also
how you save a transcript while reading the Chat or Checklist tab.
Do this before the meeting ends if you want the live transcript itself. It is discarded when the
meeting closes, and the processed transcript that replaces it is a separate pass over the recording.
See [Save anything you want to keep](/docs/live-ai/overview#save-anything-you-want-to-keep).
## While recording is paused [#while-recording-is-paused]
Pausing the recording pauses transcription. The composer in Chat shows how far the transcript runs,
and Chat keeps answering from what it already has.
Resuming picks the transcript back up.
## The finished transcript is a different thing [#the-finished-transcript-is-a-different-thing]
What you read here is produced live, in the middle of the meeting. Expect the processed transcript
to differ once the meeting ends.
The finished one carries corrected wording and timestamps that line up with the recording, and you
can rename a speaker across every line at once. Read this one in the moment and that one afterward.
[Transcription vocabulary](/docs/capturing-meetings/what-gets-captured#transcription-vocabulary) applies to the finished transcript only, and does not currently influence the live transcript that Chat and Checklist use.
## Next [#next]
* [Chat](/docs/live-ai/chat) answers questions about what the transcript holds.
* [Viewing a meeting](/docs/your-meetings/viewing-a-meeting) covers the finished transcript.
* [What gets captured](/docs/capturing-meetings/what-gets-captured) covers the rest of a recording.
# Auto-share rules (/docs/sharing/auto-share-rules)
An auto-share rule shares new meetings as they arrive. Describe which meetings should be shared and with whom, and SalesEQ evaluates each new recording against your rules.
This is what stops sharing from depending on somebody remembering.
## Two kinds of rule [#two-kinds-of-rule]
An **Always** rule shares every meeting from its source. Use one when a person or a team should see everything, such as a manager who reviews their reps.
A **Prompt** rule carries a condition in plain language, and SalesEQ reads each meeting to decide whether it holds. Use one when only some meetings should travel, such as the meetings where a particular subject comes up.
**When** is where you pick, both in the rule itself and as a column in the settings list.
Both kinds grant the same roles and both apply only to new meetings. The difference is whether SalesEQ has a decision to make.
## Personal and organization rules [#personal-and-organization-rules]
Settings holds two lists of rules, and what separates them is whose meetings a rule is allowed to act on.
**Personal auto-sharing** is yours. Every rule here shares meetings **you** record, with people you choose.
Any member can create one, and the rule has no source field because the source is always you.
**Organization auto-sharing** is admin-only, and it adds **Calls created by**. An admin picks whose meetings
the rule watches, so a rule can route someone else's meetings to someone else again. This is how "every rep
shares with their manager" or "everyone on a pod shares with the pod" gets set up once, rather than asked of
each person and forgotten.
An admin can also lock a rule. A locked rule cannot be edited or removed by the people whose meetings it
shares, which is what makes it a guarantee rather than a suggestion.
## Create a rule [#create-a-rule]
### Open sharing settings [#open-sharing-settings]
Go to [Personal Auto-Sharing](https://app.saleseq.ai/settings#personal-auto-sharing). Admins can find **Organization Auto-Sharing** directly below it.
### Choose whose meetings [#choose-whose-meetings]
Organization rules only. Under **Calls created by**, pick the person or group whose meetings the rule
watches. A personal rule skips this, because it always watches yours.
### Choose who gets access [#choose-who-gets-access]
Under **People and groups with auto-share**, add the people or groups that receive the meeting. Each one gets
viewer or editor, the same roles as sharing by hand.
### Choose when it fires [#choose-when-it-fires]
**When** is either **Always** or **If prompt matches**. Choosing **If prompt matches** reveals a **Prompt**
box, and what you write there is the condition SalesEQ checks against each meeting.
### A rule, read out loud [#a-rule-read-out-loud]
That rule watches Jason's meetings and shares them with Rory as a viewer. It shares only the ones where the
prompt holds: the meeting is customer facing and worth the head of sales seeing. Jason records, Rory
receives, and neither of them does anything.
## Test a rule before you save it [#test-a-rule-before-you-save-it]
**Test rule** runs the rule against meetings you already have and shows what it would have done with each one.
{/* "disabled" is the button's state, not a person. Both rules are aimed at describing people. */}
{/* vale alex.Ablist = NO */}
{/* vale Microsoft.Accessibility = NO */}
Testing applies to Prompt rules only. An Always rule has no decision to test, so the button stays disabled
until **When** is set to **If prompt matches** and a prompt is written.
{/* vale Microsoft.Accessibility = YES */}
{/* vale alex.Ablist = YES */}
Every meeting gets **Would share** or **Would skip**, with the reasoning next to it. This is the fastest way
to find out a prompt is broader than you meant, and it costs nothing, because testing shares no meetings.
## Verify it worked [#verify-it-worked]
Record a meeting that should match. When it finishes processing, open its share settings and confirm the rule granted access.
Each rule keeps a **History** of why it shared a meeting, so you can read its reasoning rather than guessing.
## What a prompt can use [#what-a-prompt-can-use]
{/* Intentional forward-looking product language. Do not narrow this to the current transcript-only implementation. */}
A prompt is evaluated against the whole meeting: the recording, the transcript, the title, the platform, the participants and speakers, and the calendar attendees.
A prompt can therefore act on the content of a conversation, not only on who attended it.
**A founder keeping the head of sales in the loop.** The rule shares with the head of sales, and the prompt
decides which meetings are worth their attention:
```text
Share this meeting if the customer raises a pricing objection, pushes back on contract terms, or sounds at risk of leaving.
```
**A customer success team feeding product signal to the people building it.** The rule shares with the
engineering group that owns the area:
```text
Share this meeting if the customer gives feedback about meeting search.
```
Neither decision can be made from an attendee list. That is the reason prompts exist.
A prompt never names who receives the meeting. That comes from **People and groups with auto-share**, so the
prompt only has to decide whether the meeting qualifies.
## When a rule runs [#when-a-rule-runs]
A rule is evaluated once per meeting, as that meeting finishes processing. That is the only time it ever runs.
Everything else follows from that:
* **A new rule** starts from the next meeting. It cannot reach back over what you have already recorded, so
share those by hand.
* **An edited rule** takes effect the same way. Whatever it shared before the edit keeps the access it was
given.
* **A rule you turn off or delete** stops running, but takes nothing back. Those shares were granted at the
time and now stand on their own. To undo one, remove the share on the meeting.
### Imported and transferred meetings [#imported-and-transferred-meetings]
An [imported meeting](/docs/capturing-meetings/import-meetings) counts as new when it finishes processing, so rules
run on it once, as its recorder's meeting:
* **The recorder is a member.** Their personal rules run, along with any organization rules that watch them.
* **No recorder matched.** No rules run, and the meeting stays private to whoever imported it. Rules do not run later
when the meeting moves to its recorder, so share it by hand if it needs to reach anyone.
A [transferred meeting](/docs/sharing/transfer-ownership) never runs the new owner's rules. The shares it already had
stay as they were.
## Next [#next]
* [Groups](/docs/sharing/groups) covers what most rules point at.
* [Share a meeting](/docs/sharing/share-a-meeting) covers sharing a single meeting.
# Groups (/docs/sharing/groups)
A group is a named set of people in your organization: a team, a region, a pod, a department. Share a meeting with the group and everyone in it gets access, including anyone added to the group later.
That last part is the reason to use groups. Share with five people by name and a new hire sees none of it. Share with the AE group and they see all of it on their first day.
Groups are not only for the people running the meetings. Engineering, support, and product all have a
standing reason to hear certain conversations, and a group is how those meetings reach them without anyone
forwarding links.
## Create a group [#create-a-group]
### Open settings [#open-settings]
Go to [Groups](https://app.saleseq.ai/settings#groups).
### Create the group and name it [#create-the-group-and-name-it]
Name it after how your team actually talks: `AEs`, `Enterprise`, `West Pod`, `Leadership`, `Engineering`,
`Support`.
### Add members [#add-members]
Add people from your organization. Someone can belong to as many groups as you need.
## Verify it worked [#verify-it-worked]
Share a meeting with the group. The share settings show everyone who now has access through it.
## Groups worth creating [#groups-worth-creating]
* **A group per team** covers day-to-day sharing between reps who work the same deals.
* **A leadership group** is what auto-share rules usually point at.
* **A group per segment** works when reps specialize, so enterprise meetings reach enterprise people.
* **A group per function outside sales** gets the conversation to the people who act on it. Engineering hears
the meetings where a bug or an integration comes up, support hears the escalations, product hears the
feature requests.
Resist creating a group per deal. Groups are for sets of people that outlive any one meeting.
## Removing someone [#removing-someone]
Removing a person from a group removes the access they had through it. Access you granted them individually stays, because that is a separate grant.
## Next [#next]
* [Share a meeting](/docs/sharing/share-a-meeting) covers the sharing itself.
* [Auto-share rules](/docs/sharing/auto-share-rules) covers pointing rules at a group.
# Public links (/docs/sharing/public-links)
A public link lets anyone open a meeting without a SalesEQ account. Use it to send a meeting to a customer, a prospect, or a candidate.
Organization sharing is separate and unchanged. Those shares still require a SalesEQ sign-in.
A public link opens a reduced view: the recording, the transcript, the speakers, and the summary. Insights and Ask AI stay inside your organization.
## Create a link [#create-a-link]
### Open the meeting and open sharing [#open-the-meeting-and-open-sharing]
Open the meeting and open its share settings.
### Create a public link [#create-a-public-link]
Select **Create** under **Public link**, then copy it. Create a separate link for each person you are sending
the meeting to.
New links expire after 30 days and start with a label such as **Public link 1**. Select the label to rename
it for the recipient. Select the pencil beside the expiry to choose another date.
### Send it [#send-it]
Anyone with the link can watch the meeting. They need no sign-in and no account.
## Verify it worked [#verify-it-worked]
The share settings list every public link you have created on that meeting and when each one expires.
## One link per recipient [#one-link-per-recipient]
You can create as many links as you want on a meeting. Select **Add another** and you get another one, each
with its own expiry and its own revoke.
That is worth doing when you care where a link ends up. Send one link per person and label it with the
recipient's name. If a link travels further than you meant, its label tells you which copy travelled. Revoke
that one and everybody else keeps watching.
A single link shared with five people tells you nothing when it turns up somewhere else.
## Expiry and revoking [#expiry-and-revoking]
A public link is access rather than an invitation: anyone holding it can open the meeting, including someone
it was forwarded to. Nothing checks who they are.
Every link carries an expiry, and the share settings show it, so you can see what is still live. Revoke a
link at any time and anyone using it loses access at once. Deleting the meeting has the same effect, because
deleting revokes every share on it.
## Next [#next]
* [Share a meeting](/docs/sharing/share-a-meeting) covers sharing inside your organization.
* [Delete and discard](/docs/your-meetings/delete-and-discard) covers removing a meeting entirely.
# Share a meeting (/docs/sharing/share-a-meeting)
Every meeting has one owner, usually the person who recorded, uploaded, or imported it. Who else can open it depends on the organization's default sharing setting and any direct, group, or [auto-share rule](/docs/sharing/auto-share-rules) grants.
## Share a meeting [#share-a-meeting]
### Open the meeting and open sharing [#open-the-meeting-and-open-sharing]
Open the meeting and open its share settings.
### Choose who gets access [#choose-who-gets-access]
Add a person by name or email, or add a [group](/docs/sharing/groups). Sharing with a group covers everyone in it, including people who join the group later.
### Choose their role [#choose-their-role]
| Role | What they can do |
| ------ | --------------------------------------------------------------------- |
| Viewer | Watch the recording, read the transcript, see the insights |
| Editor | Everything a viewer can do, plus edit the meeting and share it onward |
Editor access with an expiration can edit the meeting but cannot share it onward.
Give **Viewer** unless someone needs to edit or reshare the meeting. Most people only ever need to watch.
Owner is not a role you can share. Changing it is a separate action, covered in
[Transfer ownership](/docs/sharing/transfer-ownership). Only the owner and an admin can delete a meeting.
## Share several meetings at once [#share-several-meetings-at-once]
Bringing a new rep up to speed, or handing an account over, means sharing a run of meetings rather
than one. Do it from the meetings list instead of opening each meeting.
### Select the meetings [#select-the-meetings]
Select the checkbox on each meeting you want. The checkbox in the header row takes the lot, and the
arrow beside it chooses how much: **Loaded meetings** takes what the page has fetched so far, and
**All matching meetings** takes everything behind your current search and filters, including
meetings you have not scrolled to. Both show a count.
Filter first, then select all matching. Searching for an account name and taking every meeting it
returns beats scrolling and selecting by hand.
### Open Actions [#open-actions]
The count of selected meetings appears above the list, next to **Actions**. Choose **Share
meetings**, or **Remove access** to take access away.
### Choose who, and their role [#choose-who-and-their-role]
Add the people and groups, then pick **Viewer** or **Editor**. The role applies to every meeting in
the selection.
**General access** is optional here and set to **Keep existing** by default, so the organization
setting on each meeting stays as it is unless you change it.
Meetings you cannot share are skipped rather than failing the whole operation. A selection that
mixes your own meetings with meetings shared with you as a viewer still works. The result tells you
how many changed and how many were skipped.
Removing access removes the direct share. Someone can still reach a meeting through a group or
through general access, which the dialog says as you remove them.
## Verify it worked [#verify-it-worked]
The share settings list everyone who can see the meeting today, and how they got access: individually, through a group, or through your organization defaults.
That third source catches people out. If someone appears there without you adding them, your organization default is granting it.
## Organization defaults [#organization-defaults]
Admins set what happens to new meetings across the whole organization:
| Default | What it means |
| --------------------- | -------------------------------------------------------------- |
| Restricted | Meetings stay private to their owner until someone shares them |
| Organization (viewer) | Every member can watch every meeting |
| Organization (editor) | Every member can watch and reshare every meeting |
**Restricted** suits teams with sensitive meetings. An organization default suits teams that want everything open by habit. Change it under [Organization Default Sharing](https://app.saleseq.ai/settings#organization-default-sharing).
New organizations start at **Restricted**. Changing the default affects meetings created afterward and does not rewrite access on existing meetings.
## Why a direct share is not the same as general access [#why-a-direct-share-is-not-the-same-as-general-access]
Both can let someone open a meeting. Only a direct or group share puts it where they will find it.
A **direct share** to a person or a group adds the meeting to **All meetings** and makes it available in **Search** for the recipient.
**General access** makes a meeting reachable by everyone in the organization when they have its link. It does not add the meeting to **All meetings** or **Search**.
The pattern that works is to leave general access at **Restricted** or **Organization (viewer)**, then use
[auto-share rules](/docs/sharing/auto-share-rules) to share each meeting directly with the people who should
see it. Access reaches the right people, and it reaches them in the place they look.
## Sharing outside your organization [#sharing-outside-your-organization]
You can add someone outside your organization by email. If they already have a SalesEQ account, the meeting
appears in their **All meetings** like any other direct share. If they do not, they get an email saying a meeting was
shared with them, and they can create an account to watch it.
That second path asks something of the recipient. To send a meeting to a customer or a candidate, a
[public link](/docs/sharing/public-links) is usually the kinder option, because it opens without an account.
## Next [#next]
* [Groups](/docs/sharing/groups) covers sharing with a team rather than a list of names.
* [Auto-share rules](/docs/sharing/auto-share-rules) covers sharing without doing it by hand.
# Transfer ownership (/docs/sharing/transfer-ownership)
Every meeting has one owner. Transfer ownership when a meeting belongs with someone else: an account changes hands, a
rep leaves, or a backlog was imported by one person on behalf of the team.
The new owner gets the meeting in **My meetings** and becomes the person the
[Meeting deletion policy](/docs/your-meetings/delete-and-discard#who-can-delete) applies to.
## Who can transfer [#who-can-transfer]
* **The owner** can transfer their own meetings.
* **Admins** can transfer any meeting in the organization.
The Meetings page lists only meetings you own or that were shared with you, admins included. An admin transfers
anyone else's meeting from the meeting itself, opened from its link.
Editor access is not enough. The new owner must be a member of your organization who has verified their email, so you
cannot transfer to a pending invite or to someone outside the organization.
## Transfer a meeting [#transfer-a-meeting]
### Start the transfer [#start-the-transfer]
Open the meeting, select **More actions** next to **Share**, then select **Transfer ownership**. The same option sits
in each row's menu on the [Meetings](https://app.saleseq.ai/meetings) page.
### Choose the new owner [#choose-the-new-owner]
Pick a member from the list.
### Decide whether the previous owner keeps access [#decide-whether-the-previous-owner-keeps-access]
**Keep previous owners as editors** is on by default. Leave it on and the previous owner keeps editor access. Turn it
off and they lose access, unless another share still covers them.
### Transfer it [#transfer-it]
Select **Transfer meeting**. The transfer finishes in the background, and SalesEQ tells you when it is done.
## Transfer several meetings at once [#transfer-several-meetings-at-once]
Select the meetings on the [Meetings](https://app.saleseq.ai/meetings) page, then choose **Transfer ownership** from
**Actions**. Filter first and select every matching meeting to move a whole account or a whole person's history in one
go. One transfer holds up to 2,000 meetings.
The dialog splits the selection into **Ready to transfer** and **Can't transfer**, with a reason for each meeting it
cannot move. Only the ready meetings transfer. The usual reasons:
* You do not have permission to transfer that meeting.
* The meeting already belongs to the person you chose.
* The meeting is still being imported, or an earlier ownership change is still finishing. Try again in a few minutes.
## Verify it worked [#verify-it-worked]
When the transfer finishes, a notification tells you how many meetings moved and how many were skipped. Open one of
the meetings and check its share settings. The new owner is listed as the owner.
## What a transfer changes [#what-a-transfer-changes]
A transfer changes the owner and nothing else:
* **Existing shares stay.** Everyone who had access keeps it.
* **Auto-share rules do not run.** The new owner's rules apply to their new meetings, not to meetings transferred to
them.
* **Who recorded or imported the meeting is kept.** That history stays attached to the meeting.
A transfer is final. An [imported meeting](/docs/capturing-meetings/import-meetings#who-owns-it) normally moves to its
recorder when they join your organization. Once you transfer it, it stays with whoever you chose.
## When someone leaves [#when-someone-leaves]
Removing a member does not move their meetings. Their meetings stay in the organization with them as the owner, and
only an admin can manage them after that.
Transfer them before you remove the person, while they can still do it themselves. Ask them to select everything in
**My meetings** and transfer it to whoever takes over the work. After they leave, an admin can still transfer each
meeting from its link, and can transfer in bulk any of their meetings that were shared with the admin.
Any editor access someone kept as a previous owner, or holds as an importer, stops working when they leave. It works
again if they rejoin the same organization.
## Next [#next]
* [Share a meeting](/docs/sharing/share-a-meeting) covers giving access without changing the owner.
* [Members and roles](/docs/account/members-and-roles) covers removing someone from your organization.
* [Import meetings](/docs/capturing-meetings/import-meetings) covers who owns a meeting when it first arrives.
# Ask AI (/docs/your-meetings/ask-ai)
Ask AI answers questions about the meeting you have open, in plain language. Answers are grounded in that meeting's recording, so you can check them.
Ask AI only reads meetings you already have access to. Your chats are yours alone: nobody else in your organization can open them, including admins.
## Asking a question [#asking-a-question]
Open a meeting and use Ask AI. Useful questions look like:
```text
What objections came up?
What did we agree the next step is?
What did they say about budget?
Who is involved in the decision?
```
A new chat also offers a row of starting points under **Try with**, covering the questions people ask most, such as next steps, objections, and buyer intent. Select one to send it.
Ask follow-up questions in the same conversation. It keeps the context of what you already asked.
## Answers that are not just text [#answers-that-are-not-just-text]
Ask AI picks the shape that fits the question, without being asked to.
* **Ask for a breakdown** and you get a chart.
* **Ask what to do next** and you get an action item list.
* **Ask for a follow-up email** and you get a draft with a subject line, ready to copy in one click.
If you have connected Gmail or Outlook, you can put that draft straight into your mailbox instead of copying it. See [Email and follow-up drafts](/docs/integrations/email).
## What Ask AI can see [#what-ask-ai-can-see]
One meeting at a time, all of it:
* **The recording**, both the audio and the video.
* **The transcript**, with timestamps and each speaker named.
* **The participants**, including anyone who never spoke.
* **The meeting title.**
* **Who you are**, and the current date and time, so it can answer questions about timing.
Speaker names come from the transcript, so a wrong name is a wrong answer when you ask about someone by name. Fix the name first, and every line from that speaker updates. See [Viewing a meeting](/docs/your-meetings/viewing-a-meeting).
For a question that spans several meetings, connect an [AI assistant](/docs/ai-assistants/overview) instead.
## Next [#next]
* [Viewing a meeting](/docs/your-meetings/viewing-a-meeting) covers playback and the transcript.
* [AI assistants](/docs/ai-assistants/overview) covers asking questions that span more than one meeting.
* [Search](/docs/your-meetings/search) finds a specific moment across your meetings.
# Delete and discard (/docs/your-meetings/delete-and-discard)
Not every recording is worth keeping. Two actions get rid of one, and which you reach for depends on
whether the meeting has already processed.
## Delete a meeting [#delete-a-meeting]
Open the meeting, select **More actions** next to **Share**, then select **Delete meeting**. Deleting removes the recording, the transcript, and the analysis, and revokes every share on that meeting. Anyone you shared it with loses access, and public links stop working.
Delete when a meeting should not have been recorded, or when a customer asks you to remove it.
Deleting is permanent. The recording, transcript, and analysis are all removed together.
### Who can delete [#who-can-delete]
Deleting is not the same as editing. Editor access lets someone rename a meeting and, unless the access has
an expiration, share it. Only the meeting's **owner** and **organization admins** can delete.
Admins can delete any meeting in the organization at any time. What an owner can do with their own meeting
depends on the **Meeting deletion policy** an admin sets, which is why **Delete meeting** does not always
appear:
| Policy | What the owner can do |
| ----------------------------------------------- | ---------------------------------------------------------------------------- |
| Owners can never delete meetings | Nothing. Ask an admin. |
| Owners can delete meetings within a time window | Delete for a set time after processing finishes, then it is an admin's call. |
| Owners can always delete meetings | Delete their own meetings whenever they want. |
New organizations start on the time window, set to 15 minutes. The clock starts when processing
finishes rather than when the recording stops, so the window is a window on the finished meeting. A
[transferred meeting](/docs/sharing/transfer-ownership) keeps its original window, so a new owner of an older meeting
may need an admin to delete it.
## Delete several meetings at once [#delete-several-meetings-at-once]
Select the meetings on the [Meetings](https://app.saleseq.ai/meetings) page, then choose **Delete meetings** from
**Actions**. One deletion holds up to 500 meetings.
The dialog tells you how many of the selected meetings you can delete, with the reason for any you cannot. Type
**confirm** and delete. Only the meetings you can delete are removed, and the rest stay selected so you can see which
ones were left.
### Imported meetings [#imported-meetings]
Deleting an [imported meeting](/docs/capturing-meetings/import-meetings) removes it from SalesEQ only. The recording
stays in the tool it came from. SalesEQ also remembers that you deleted it, so a later import never brings it back
unless someone selects it on purpose.
## Discard a recording while it runs [#discard-a-recording-while-it-runs]
While the desktop app is recording, select **Discard recording** in the recording bar and confirm. Recording
stops and nothing is kept, so the meeting is never processed and never reaches your organization.
This is the right action for a meeting you started recording by mistake, or a meeting that turned out to be
personal. Once you stop a recording normally, it processes like any other meeting, and removing it means
deleting it.
## Which one to use [#which-one-to-use]
| Situation | Action |
| ------------------------------------------- | ------- |
| Recorded by mistake, caught while recording | Discard |
| Recorded by mistake, already processed | Delete |
| Customer asks you to remove the meeting | Delete |
## Next [#next]
* [Viewing a meeting](/docs/your-meetings/viewing-a-meeting) covers renaming a meeting or a speaker.
* [Automatic recording](/docs/capturing-meetings/automatic-recording) covers stopping unwanted recordings before they start.
* [Share a meeting](/docs/sharing/share-a-meeting) covers who could see a meeting before you deleted it.
# Search (/docs/your-meetings/search)
Search runs over what was said in your meetings, not their titles. It matches on meaning as well as on exact wording, so an objection described in your own words finds the moment even when nobody phrased it that way.
Open **Search** in the web app, describe the moment you want, and run the search. Results include the matching transcript context. Select a result to open the meeting at the relevant point.
Choose **My meetings** to search only meetings you own. Choose **All meetings** to add meetings shared directly with you or with a group you belong to.
Meetings available only through an organization default do not appear in search results. You can still open a meeting from a direct link when your role allows it.
Use filters to narrow by owner, participant, speaker, date, duration, platform, or source. **Platform** is where the conversation happened, such as Zoom or Google Meet. **Source** is the tool that recorded it, which picks out meetings imported from another tool. Search history lets you return to an earlier query and its settings.
## What is worth asking [#what-is-worth-asking]
Search earns its keep on questions a meeting list cannot answer:
```text
Which meetings mentioned our pricing change?
What objections came up about security this quarter?
Where did anyone bring up migrating off Salesforce?
```
Competitor names, feature requests, and objections are the highest-value searches. They tell you what is actually coming up across your pipeline, rather than what you remember coming up.
Meaning matching covers a lot, but the closer your words are to how someone actually talks, the better the moment you land on.
You can also search from a connected [AI assistant](/docs/ai-assistants/overview). Claude, ChatGPT, and other MCP clients use the same **My meetings** and **All meetings** scope.
## Next [#next]
* [AI assistants](/docs/ai-assistants/overview) covers connecting Claude or ChatGPT.
* [Ask AI](/docs/your-meetings/ask-ai) answers questions about a single meeting.
# Viewing a meeting (/docs/your-meetings/viewing-a-meeting)
A meeting opens here once it finishes processing. Get to one from the **Meetings** page, a search result, or a link someone sent you.
## The recording and the transcript [#the-recording-and-the-transcript]
A meeting with video plays as video. An audio-only meeting plays as audio, with no picture.
The transcript sits beside the recording, and the two are connected in both directions.
**Select any line** and the recording skips to that point and plays from there. This is where the time
goes. Finding the moment somebody pushed back on price means scrubbing the recording and guessing.
Reading for it in the transcript takes seconds, and selecting the line puts you there to hear how it was
said.
**Playback highlights the line being spoken**, wherever you are scrolled to. Turn on **Follow along** in
the transcript header if you want the transcript to scroll itself and keep the current line centered.
## Where a meeting came from [#where-a-meeting-came-from]
The icons after the participant avatars, next to the meeting date, show where a meeting came from. Hover one to read it:
* **Platform** is where the conversation happened, such as Zoom or Google Meet.
* **Source** is the tool that recorded it: SalesEQ, or the tool it was [imported](/docs/capturing-meetings/import-meetings) from.
* **Added via** is how it reached SalesEQ: a desktop recording, a manual upload, or an import.
The **Source** column on the Meetings page shows the same thing, and filters on it.
## Fixing a title or a speaker name [#fixing-a-title-or-a-speaker-name]
Both need editor access on the meeting. The owner has it, and so does anyone the meeting was shared with as
an editor. Without it the fields are not editable.
### The meeting title [#the-meeting-title]
A meeting with no calendar event behind it gets a title SalesEQ generates from the conversation. That is
usually close, and sometimes it is not what your team would have called it. Rename it so people find it
later.
Select **More actions** next to **Share**, then select **Rename**. The title turns into a text field.
### A speaker name [#a-speaker-name]
A speaker sometimes comes through under the wrong name, or as **Unknown speaker 1**. Two routes fix it,
and either one updates every line from that speaker at once.
**From the transcript.** Select the name above any line that speaker said. It turns into a text field, so
type the right name.
**From the participant list.** Select the participant avatars next to the meeting date. The list shows
everyone SalesEQ knows about, marks the host, and lets you **Add participant** for anyone it missed.
Do this before you share a meeting, because the transcript is what most people read.
## The insight tabs [#the-insight-tabs]
The tab strip under the recording holds everything SalesEQ generated: the summary, the nonverbal read,
qualification evidence, questions, coaching, and the speech metrics.
[Meeting insights](/docs/insights/meeting-insights) covers what each tab holds.
## Asking about the meeting [#asking-about-the-meeting]
Rather than reading the whole transcript, ask.
**Ask AI** sits beside the transcript as its own tab. It answers questions about the meeting you have open
and cites the moments it drew from. See [Ask AI](/docs/your-meetings/ask-ai).
You can also ask from outside SalesEQ. Connect Claude or ChatGPT and put the same questions to your
meetings there. See [AI assistants](/docs/ai-assistants/overview).
## Taking a meeting somewhere else [#taking-a-meeting-somewhere-else]
**More actions** next to **Share** copies the meeting to your clipboard as Markdown, in two sizes:
| Control | What you get |
| ------------------------ | --------------------------------------------------------------------------------------------------- |
| **Copy meeting details** | Title, date, time, duration, platform, participants, the meeting ID, and a link back to the meeting |
| **Copy full context** | The same header, plus the summary and the full transcript |
**Copy full context** is for pasting a whole meeting into an AI tool that has no access to SalesEQ.
Paste it in, then ask for the follow-up email, the objections you did not answer, or a rewrite of
your next call plan.
**Copy meeting details** is the one to reach for when the tool does have access. Every copy carries
the meeting ID, and the SalesEQ connector's tools take that ID. Pasting the details into Claude or
ChatGPT points them at the meeting. They pull the transcript, the summary, or a video frame
themselves rather than working from what you pasted. See
[AI assistants](/docs/ai-assistants/overview).
To do this for several meetings at once, select them in the meetings list and choose **Copy meeting
details** from **Actions**.
## Next [#next]
* [Meeting insights](/docs/insights/meeting-insights) covers the generated analysis.
* [Share a meeting](/docs/sharing/share-a-meeting) covers getting the meeting to your team.
* [AI assistants](/docs/ai-assistants/overview) covers reaching your meetings from Claude and ChatGPT.
# SalesEQ (https://saleseq.ai/)
## Turn every video call into revenue intelligence.
SalesEQ analyzes the body language, tonality, and buyer reactions inside every video call, then turns that intelligence into faster rep ramp, higher conversion, and better forecast accuracy.
## Built from real reactions
Grounded in how buyers receive the message, not just what they say.
## Powered by nonverbal intelligence
Analyzes tone, body language, facial reactions, hesitation, and confidence shifts.
## Designed for action
Pushes intelligence into follow-up, CRM context, coaching, and AI workflows.
## 1.0 Know when a $1M yes isn’t a yes yet.
Transcripts capture the words. SalesEQ shows how the message was received through tone changes, hesitation, facial reactions, and the surrounding call context.
Call context:
- Buyer reactions
- Tone shifts
- Reception signals
- Botless capture
## 2.0 Build call intelligence around the way your team sells.
SalesEQ is a configurable analytics engine. Your organization chooses the signals that matter to its buyers, market, and sales motion.
Custom intelligence:
- Custom signals
- Deal context
- Coaching moments
- Market-specific signals
## 3.0 Move from call insight to revenue action.
SalesEQ embeds the nuance from every call into the tools reps already use, turning live conversation context into immediate follow-up and cleaner deal execution.
Revenue workflows:
- MCP workflows
- Follow-up
- CRM context
- Sharing
# Founding team (https://saleseq.ai/team)
## Trent Ballard, Co-founder
SWE at Invisible Technologies, where he worked on RLHF data infrastructure for frontier AI labs including OpenAI, Meta, Amazon, and ElevenLabs. Trent brings backend engineering, CS/ML, and product-building experience to SalesEQ.
LinkedIn: https://www.linkedin.com/in/trentballard/
## Danny Engels, Co-founder
Account Executive at Gartner and a top regional seller, reaching 153% quota attainment. Danny is also a self-taught programmer who built automations to simplify the AE workflows SalesEQ now helps teams scale.
LinkedIn: https://www.linkedin.com/in/danny-engels/
# Privacy Policy (https://saleseq.ai/privacypolicy)
This policy describes how SalesEQ handles information collected through our marketing website, waitlist and demo flows, and related services.
Last updated: August 3, 2026
## Overview
This Privacy Policy explains how SalesEQ Inc. collects, uses, and shares information when you visit our marketing website, join our waitlist, book a demo, communicate with us, or use related SalesEQ services.
We designed this page to describe our current practices in plain language. As our product evolves, we may update this policy to reflect new features, workflows, or legal requirements.
## Information We Collect
We collect information you provide directly, information collected automatically when you use the site, and information received from third-party tools you choose to use with us.
Examples include:
- Contact details such as your name, work email address, and any information you submit through forms or demo requests.
- Waitlist or lead-capture details, including the source of the submission and related campaign or page context.
- Usage and device information such as page visits, referring URLs, browser data, and basic analytics events.
- Communications you send to us, including support requests, emails, scheduling information, and feedback.
- Information associated with the SalesEQ app and services if you later create an account or use product features.
- If you choose to connect Google Calendar or Gmail, SalesEQ accesses your Google account email address and authorization credentials. Calendar access is read-only and limited to event details such as titles, times, attendees, response status, and conferencing links; Gmail access is limited to creating drafts you request, and SalesEQ does not read your mailbox or send email automatically.
## How We Use Information
We use information we collect to:
- Operate, maintain, and improve the SalesEQ website and related services.
- Respond to inquiries, schedule demos, and communicate with prospective or current customers.
- Manage our waitlist, sales pipeline, onboarding, and customer relationship workflows.
- Measure site traffic, understand interest in our product, and improve marketing performance.
- Detect abuse, secure our systems, troubleshoot issues, and enforce our terms.
- Comply with legal obligations and protect the rights, safety, and integrity of SalesEQ, our users, and others.
Connecting Google Calendar or Gmail is optional, and you can disconnect either at any time. SalesEQ and service providers acting on our behalf use and store Google user data only as needed to provide the connected features; we do not sell it, use it for advertising, or use it to train general-purpose AI models. SalesEQ's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
## Analytics, Scheduling, and Third-Party Tools
Our marketing site currently uses third-party services to help us understand usage, capture leads, and schedule meetings. For example, we may use analytics tooling, hosted infrastructure providers, database providers, and scheduling tools.
When you interact with those tools, the providers may collect information according to their own privacy policies. We encourage you to review the privacy practices of any third-party service you use through or in connection with SalesEQ.
## Artificial Intelligence and Model Providers
SalesEQ product features may use third-party artificial intelligence services to generate analysis, summaries, answers, or similar outputs. We currently use models from Google, OpenAI, Anthropic, and ElevenLabs, accessed in part through OpenRouter (an API routing layer). The specific providers and models we use may change as we improve the product.
When you use AI-powered features, content needed to fulfill your request may be transmitted to the applicable provider for processing. Each provider applies its own terms, privacy policy, and security practices.
## MCP Connector and Third-Party AI Clients
SalesEQ publishes an MCP (Model Context Protocol) connector at https://mcp.saleseq.ai that lets you query your meeting data from third-party AI clients such as Claude, ChatGPT, and any other host that speaks the MCP standard.
When you connect SalesEQ to an AI client, the client authenticates with SalesEQ using OAuth 2.0. The AI client may then call read-only tools on the connector to fetch meetings, transcripts, and analysis associated with your account, subject to the same permission model used in the SalesEQ app.
Tool results returned to your AI client may then be transmitted by that client to its own model provider for processing as part of the conversation. Each AI client and model provider operates under its own terms and privacy policy. SalesEQ does not see or log the prompts you send to the AI client, only the tool calls the client makes back to us.
You can disconnect the connector at any time from your AI client's settings. To revoke MCP access from the SalesEQ side, contact us at operations@getsaleseq.com.
## How We Share Information
We do not sell your personal information for money. We may share information with service providers and infrastructure partners that help us run the website and business, such as hosting, analytics, scheduling, database, communications, and security vendors.
We may also share information when required by law, to respond to lawful requests, in connection with a merger, acquisition, financing, or sale of assets, or when necessary to protect our rights, users, or systems.
## Data Retention
We retain information for as long as reasonably necessary to operate the site, manage business relationships, comply with legal obligations, resolve disputes, and enforce agreements.
Retention periods may vary depending on the type of information, the context in which it was collected, and whether it is needed for operational, contractual, legal, or security purposes.
## Security
We use reasonable administrative, technical, and organizational measures to help protect information. No system is perfectly secure, and we cannot guarantee absolute security.
If you believe you have discovered a security issue involving SalesEQ, please contact us promptly so we can investigate.
## Your Choices
You may choose not to provide certain information, but that may limit your ability to use some features or receive certain communications from us.
If you want to request access, correction, or deletion of information you previously submitted to us, or if you want to opt out of future marketing outreach, contact us at legal@saleseq.ai.
## Children's Privacy
SalesEQ is intended for business use and is not directed to children under 13. We do not knowingly collect personal information from children under 13 through this site.
## Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will post the revised version here and update the effective date at the top of the page.
## Contact Us
If you have questions about this Privacy Policy or our data practices, contact SalesEQ at legal@saleseq.ai.
# Terms of Service (https://saleseq.ai/termsofservice)
These terms govern access to the SalesEQ website, waitlist and demo flows, and related services made available by SalesEQ.
Last updated: April 5, 2026
## Agreement to These Terms
These Terms of Service govern your access to and use of the SalesEQ website and related services made available by SalesEQ Inc. By accessing or using the site, you agree to these Terms.
If you are using SalesEQ on behalf of a company or other organization, you represent that you have authority to bind that organization to these Terms.
## Use of the Site
You may use the site for lawful business and informational purposes only. You agree not to misuse the site, interfere with its operation, attempt unauthorized access, or use the site in a way that could harm SalesEQ, our systems, or other users.
That means, among other things, you may not:
- Use the site in violation of applicable law or regulation.
- Upload or transmit malicious code, spam, or fraudulent content.
- Attempt to probe, scan, or test the vulnerability of our systems without authorization.
- Copy, scrape, reverse engineer, or exploit the site except as permitted by law.
- Use the site to compete unfairly with SalesEQ or to build a substantially similar service from protected materials.
## Accounts, Demos, and Waitlist Submissions
Certain features may ask you to provide contact information, request a demo, join a waitlist, or later create an account for SalesEQ services. You agree to provide accurate information and keep it reasonably current.
We may contact you regarding your request, your use of the site, product updates, or business opportunities related to SalesEQ.
## Product Availability and Changes
SalesEQ may change, suspend, or discontinue any part of the website or related services at any time, with or without notice. Some features shown on the marketing site may describe current, planned, beta, or future capabilities.
We are not obligated to make any specific feature available, maintain any specific integration, or continue offering the site in its current form.
## Intellectual Property
The SalesEQ website, branding, content, design, software, and related materials are owned by SalesEQ Inc. or its licensors and are protected by intellectual property laws.
Subject to these Terms, we grant you a limited, non-exclusive, non-transferable, revocable right to access and use the site for its intended purpose. No other rights are granted.
## Third-Party Services and Links
The site may include links to third-party websites or rely on third-party providers for analytics, scheduling, hosting, embedded tools, or other functions. SalesEQ does not control and is not responsible for third-party services or content.
Your use of third-party services is governed by their own terms and policies.
## AI-Powered Product Features
SalesEQ may offer features that use third-party artificial intelligence services, including models from Google, OpenAI, Anthropic, and ElevenLabs, accessed in part through OpenRouter. The providers and models we use may change over time. Automated outputs may be incomplete or incorrect; you should review important results independently.
Processing by those providers is subject to their respective terms and privacy policies. See our Privacy Policy for more detail.
## Disclaimers
The site and related services are provided on an "as is" and "as available" basis. To the fullest extent permitted by law, SalesEQ disclaims all warranties, whether express, implied, statutory, or otherwise, including implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement.
We do not guarantee that the site will be uninterrupted, error-free, secure, or available at all times, or that any information or output will be complete, accurate, or suitable for your specific needs.
## Limitation of Liability
To the fullest extent permitted by law, SalesEQ and its officers, employees, affiliates, contractors, licensors, and service providers will not be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, goodwill, data, or business opportunities arising out of or related to your use of the site.
To the fullest extent permitted by law, SalesEQ's total liability for any claim arising out of or relating to the site or these Terms will not exceed one hundred U.S. dollars (USD $100).
## Indemnity
You agree to defend, indemnify, and hold harmless SalesEQ and its affiliates, officers, employees, and agents from and against claims, liabilities, damages, judgments, losses, costs, and expenses arising out of your misuse of the site, your violation of these Terms, or your violation of applicable law or the rights of a third party.
## Termination
We may suspend or terminate your access to the site at any time if we believe you have violated these Terms, created risk for SalesEQ or others, or if continued access is no longer commercially or operationally feasible.
## Changes to These Terms
We may revise these Terms from time to time. If we do, we will post the updated version on this page and update the effective date. Your continued use of the site after changes become effective means you accept the updated Terms.
## Contact
If you have questions about these Terms, please contact us at legal@saleseq.ai.
# Changelog (https://saleseq.ai/changelog)
## Tables of contents and batch requests for AI assistants (2026-10-04)
AI assistants connected to SalesEQ now answer questions about your meetings faster, and cite them
more precisely.
* **Tables of contents.** Each meeting has an outline of the topics discussed, with start and end
times. `get_meeting_table_of_contents` lets your assistant go straight to the discussion you asked
about and read only that part of the transcript.
* **Batch requests.** `get_meeting_summary` accepts up to 20 meetings per call, and
`get_meeting_frame` up to 8 timestamps. Questions that span many meetings or moments finish
sooner.
* **Word-level timestamps.** `get_transcript` can return when each word was spoken, so a quote links
to the exact second.
All tools stay read-only and scoped to meetings your account can already open. See
[Tools](/docs/ai-assistants/tools).
## Import meetings from other tools (2026-09-28)
Import meetings from other tools. Only Fathom is supported for now, with more tools on the way. Connect it under **Settings → Meeting imports**, then import past meetings or turn on **Automatic imports** to bring in each new one as it finishes. See [Import meetings](/docs/capturing-meetings/import-meetings).
## Transfer ownership and bulk delete (2026-09-28)
Hand meetings to another member with **Transfer ownership**, one at a time or in bulk from **Actions**. You can also delete up to 500 meetings at once, and filter by owner and source. See [Transfer ownership](/docs/sharing/transfer-ownership).
## Recording rules (2026-09-11)
Choose which meetings SalesEQ records. Set automatic rules, configure individual meetings, or apply changes to several upcoming meetings at once. Admins can exclude internal meetings or company all-hands from recording across the organization.
Find **Recording Rules** in the desktop app's **Settings**.
## Live AI rules (2026-09-11)
Choose when Live AI starts and prepare each meeting with the checklist and quick actions you want to use. Set automatic rules or configure upcoming meetings individually or in bulk. Admins can require Live AI, block it, or let members decide.
Find **Live AI rules** in the desktop app's **Settings**.
## Organization 2FA (2026-09-11)
Require two-factor authentication for password sign-ins across your organization. Admins can enable this in the web app's **Settings**. Members without 2FA must set it up at their next password sign-in and keep it enabled while required. Google and other provider sign-ins are unaffected.
## Share and copy meetings in bulk (2026-08-27)
Select meetings in the list, then choose **Share meetings** or **Remove access** from **Actions**.
The arrow next to the header checkbox takes every meeting behind your search, not only the ones
loaded.
**Copy meeting details** and **Copy full context** copy a meeting out as Markdown, for pasting into
Claude or ChatGPT.
## Quick actions and shared checklists (2026-08-27)
Live AI in the desktop app picks up quick actions, shared checklists, and a split view.
* **Quick actions** send a prompt in one select. Assist, Explain, and Catch me up are there by
default, and you can swap in others or write your own.
* **Checklists are saved to your organization.** Keep as many as you need, and share one so your
team runs it too.
* **Switch mid-meeting.** The checklist title is a menu, so you can change or edit a checklist
without leaving the call.
* **Tabs open side by side.** Open any two, or all three, and the window widens to fit.
## Live AI during the meeting (2026-08-13)
Live AI in the desktop app is rebuilt. While a meeting is still going, you can follow
along, ask questions, and see whether you have covered what you meant to.
* **Chat** answers from the live transcript, meeting events, and a snapshot of the
meeting view. It can search the web and cite sources when it needs to.
* **Transcript** streams what was said, plus events like screen sharing and people
joining or leaving.
* **Checklist** tracks whether your objectives are covered, with presets for BANT,
SPICED, MEDDPICC, and your own lists.
It is on by default. The switch is in desktop settings under **Live AI**.
## Documentation is live (2026-07-26)
SalesEQ now has real documentation at [saleseq.ai/docs](/docs): how to record your
first meeting, share a meeting, and manage your organization.
Hand any page straight to an AI assistant. Use **Copy Markdown** to copy a Markdown
version, or **Open in** to start a ChatGPT or Claude conversation with the page already
loaded. Appending `.md` to any docs URL returns a Markdown version of the page.
Four files hand over the whole site in bulk:
* [saleseq.ai/llms.txt](/llms.txt) indexes every page.
* [saleseq.ai/llms-full.txt](/llms-full.txt) is the whole site in a single file, this changelog included.
* [saleseq.ai/docs/llms.txt](/docs/llms.txt) is the same index, documentation only.
* [saleseq.ai/docs/llms-full.txt](/docs/llms-full.txt) is the documentation in a single file.
## Search and summaries in your AI assistant (2026-07-08)
The MCP connector can now search, not just list. Ask an assistant what a customer said about
pricing last quarter and it searches your meetings instead of paging through them.
* `search_meetings` runs the same full-text search as the web app.
* `get_meeting_summary` returns a meeting's summary without pulling the whole transcript.
* `get_meeting_frame` returns a still frame from a moment in a recording.
* `get_org_context` gives the assistant your organization's members, so it can resolve a
teammate's first name.
* `list_my_meetings` and `list_shared_meetings` are now one `list_meetings` tool with a
filter.
All tools stay read-only and scoped to meetings your account can already open.
## Search across every meeting (2026-06-30)
You can now search the full text of every meeting your organization has recorded, not just
meeting titles. Results link straight to the moment in the transcript.
Search only ever returns meetings you already have access to.
## Draft follow-up emails in Gmail and Outlook (2026-06-29)
Connect Gmail or Outlook and turn a meeting into a follow-up email without copying and pasting.
SalesEQ writes the draft into your own mailbox, where you can edit it like any other draft.
Nothing is ever sent on your behalf. You review and send every email yourself.
## Sign up and pick a plan without a waitlist (2026-06-09)
The waitlist is gone. Create an organization, invite your team, and start recording the same day.
* Choose a plan and pay from billing settings. Seats update as you invite and remove people.
* Turn on domain join so anyone with a company email address joins your organization instead of
starting their own.
## Auto-share rules (2026-05-23)
{/* Quoted text is a literal prompt a user types, so its punctuation stays verbatim. */}
{/* vale Microsoft.Quotes = NO */}
Describe in plain language which meetings should be shared and with whom. For example: "share
my meetings with prospects from the enterprise segment with the AE team". SalesEQ evaluates each
new recording against your rules and shares it when it matches.
{/* vale Microsoft.Quotes = YES */}
* Rules run on the meeting title, platform, participants, and calendar attendees.
* Each rule records why it shared a meeting, so you can check its reasoning.
* Rules apply to new meetings only. Turn one off and existing shares stay as they are.
## Live transcript while you record (2026-05-22)
The desktop app now transcribes as the meeting happens, in a floating window you can keep
next to it.
Collapse it to a couple of lines to stay out of the way, expand it to read back what was
said, or minimize it entirely. The full transcript is still processed after the meeting.
## Share a meeting with a group (2026-05-18)
Share a meeting with a whole group instead of naming people one at a time. Everyone in the
group gets access, and anyone added to the group later gets it too.
The share modal shows exactly who can see a meeting today: individually, through a group,
or through your organization defaults.
## Key moments from voice and video (2026-04-27)
SalesEQ now flags the moments in a meeting that tend to matter: objections, pricing, questions
from the prospect, requests for commitment, and shifts in sentiment. Each one links to its
place in the recording.
For each moment, SalesEQ also reads how something was said, not just what was said. That
means changes in pitch and volume against the speaker's own baseline, plus posture and eye
contact when the meeting has video.
## Publish a meeting to a public link (2026-04-27)
Create a link that anyone can open without a SalesEQ account, useful for sending a meeting to
a customer or a candidate.
* The share modal shows each public link you have created and when it expires.
* Revoke a link at any time. Anyone using it loses access immediately.
* Organization sharing is unchanged: those links still require a SalesEQ sign-in.
## Onboarding flow for new members (2026-04-24)
New members are now walked through setup instead of landing in an empty organization: install
the desktop app, connect a calendar, connect a CRM.
Admins choose which steps appear and which are required, so people join with the connections
your team actually uses.
## Connect SalesEQ to Claude and other AI assistants (2026-04-21)
SalesEQ now runs a Model Context Protocol (MCP) server at `https://mcp.saleseq.ai`, so an AI
assistant can work with your meetings directly. Ask Claude for the transcript of Tuesday's
demo and it fetches the real one.
* Add it as a custom connector using the server URL and sign in with your SalesEQ account.
* The assistant can list your meetings, list meetings shared with you, and fetch a
transcript, optionally a slice of one, so long meetings don't flood the conversation.
* Every tool is read-only. Nothing an assistant does can change or delete your data.
The connector sees only the meetings your account can already open.
## Transcripts now name every speaker (2026-04-01)
{/* Quoted text is a literal UI label; a period inside would change what the label says. */}
{/* vale Microsoft.Quotes = NO */}
Transcripts now show who said what by name instead of "Speaker 1" and "Speaker 2". SalesEQ
resolves names from the meeting's participants and calendar attendees.
{/* vale Microsoft.Quotes = YES */}
When a speaker is labeled incorrectly, rename them once and every line from that speaker
updates.
## Send meeting notes to HubSpot (2026-03-30)
Connect HubSpot from settings, then push a meeting's summary and notes onto
the matching contact without leaving SalesEQ.
You choose which meeting goes where. Nothing syncs automatically.
## SalesEQ for Windows (2026-03-30)
The desktop app now runs on Windows as well as macOS, with the same meeting detection,
recording controls, and system tray behavior.
Download it from the download page and sign in with your existing account.
## Connect your calendar (2026-03-25)
Connect Google Calendar or Outlook and SalesEQ matches each recording to the event it came
from. Meetings arrive with the right title and the invited attendees already attached,
instead of a generic window name.
Connect and disconnect calendars from settings at any time.
## Two-factor authentication (2026-03-09)
Turn on two-factor authentication from your security settings. SalesEQ uses time-based
one-time codes, so any standard authenticator app works.
Once enabled, signing in asks for a code from your authenticator after your password.
## Rename, delete, and discard recordings (2026-03-05)
You can now correct a meeting title after the fact, and delete a meeting you didn't mean to
keep. Deleting removes the recording, transcript, and analysis, and revokes any shares.
In the desktop app, you can also discard a recording as it ends, so a meeting you didn't mean
to keep never reaches your organization.
## Ask AI answers with charts and action items (2026-02-23)
Ask AI now replies with more than plain text. Ask for a breakdown and you get a chart. Ask
what to do next and you get an action item list.
Ask it for a follow-up email and the draft comes back as a block you can copy in one click,
subject line included.
## Organizations, invites, and groups (2026-01-29)
Meetings now live in an organization rather than under a single account. Invite teammates by
email, and organize them into groups you can share with later.
* Invite, remove, and re-invite members from settings.
* Create groups (a team, a region, a pod) and manage who belongs to each.
* Every meeting, transcript, and share respects organization membership.
## Ask AI about a meeting (2025-12-25)
Open a meeting and ask questions about it in plain language: what the objections were, what
was agreed, what the next step is. Answers are grounded in that meeting's transcript.
Ask AI only reads meetings you already have access to.
## One player for audio and video recordings (2025-12-19)
Recordings used to open in one of three separate players depending on the meeting. Now every
recording opens in the same player with the same controls, whether it captured video or audio
only.
The transcript follows playback and highlights the line currently being spoken.
## Menu bar controls and automatic updates (2025-12-02)
Start and stop a recording from the menu bar without opening the SalesEQ window. The icon
changes while a recording is in progress, so you can tell at a glance whether you are being
recorded.
The app also installs its own updates in the background and shows the version you are
running, so you no longer need to download a new build to stay current.
## Record meetings from your desktop (2025-11-28)
The SalesEQ desktop app now notices when you join a meeting and offers to record it, so you
no longer have to start a recording by hand. It detects Zoom, Google Meet, Microsoft Teams,
and Slack automatically.
* A bar appears when SalesEQ detects a meeting. Start recording from it, or ignore it.
* A control bar shows what you're recording and how long it's been running.
* When you stop, the recording uploads and begins processing on its own.