# 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.
* **[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.
* **[Insights and reporting](/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 [Settings](https://app.saleseq.ai/settings) as an admin, find **Billing & invoices**, 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, and share 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. |
Keep at least two admins. One admin is a single point of failure the first time they are on holiday.
## 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 [Settings](https://app.saleseq.ai/settings) and find **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 settings. Their meetings stay in the organization, because meetings belong to the organization rather than to a personal account.
Removing someone also removes the access they had through any group.
## 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 [Settings](https://app.saleseq.ai/settings) 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** button when your account came from one.
## Turn it on [#turn-it-on]
### Open your security settings [#open-your-security-settings]
Go to [Settings](https://app.saleseq.ai/settings), find **Two-factor authentication**, and select **Enable**.
### 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.
## 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 or uploaded 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 last three meetings in SalesEQ.
```
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)
Connect your SalesEQ account to Claude so you ask about your meetings without leaving the conversation.
## Before you start [#before-you-start]
* A SalesEQ account you can sign in to at `https://app.saleseq.ai`
* A few meetings recorded or uploaded already, so Claude has something to work with
* Claude on web or desktop
## Steps [#steps]
### Open the connector settings [#open-the-connector-settings]
In Claude, go to **Settings**, then **Connectors**, then **Add custom connector**.
### Enter the connector details [#enter-the-connector-details]
Name it `SalesEQ`, and use this endpoint exactly as written, with no path and no trailing characters:
```text
https://mcp.saleseq.ai
```
Leave the optional OAuth client fields empty.
### Add it, then connect [#add-it-then-connect]
Select **Add** to create the connector, then **Connect** to authorize it. Claude opens a browser window for
SalesEQ sign-in.
### Sign in to SalesEQ [#sign-in-to-saleseq]
Sign in with the account whose meetings you want Claude to reach. The connector exposes that account's access and nothing more.
## Verify it worked [#verify-it-worked]
Start a conversation and turn SalesEQ on with the connectors control in the composer. Then ask Claude a
question that needs your data:
```text
List my last three meetings in SalesEQ.
```
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 or uploaded 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 last three meetings in SalesEQ.
```
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 every meeting
you can reach, 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 reporting dashboard. 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 enforces the same permission model as the SalesEQ app. You see meetings you own, meetings shared with you directly, and meetings shared with a group you belong to.
Meetings shared organization-wide do not appear through the connector. If you need one available to your AI client, ask the owner to share it with you directly or with a group you belong to.
## 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 six tools the connector exposes.
# Tools (/docs/ai-assistants/tools)
The connector exposes six 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 can access, with title, participants, duration, and platform. Filters to only meetings you recorded or uploaded, plus participant, duration, 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 summary of a meeting. This is a much cheaper way to answer "what was this meeting about" than reading the full transcript. |
| `get_transcript` | Fetches the transcript for a specific meeting, optionally sliced to a time range so long meetings do not blow out context. |
| `get_meeting_frame` | Fetches a still frame from a meeting's video around a specific timestamp. 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. |
## Access [#access]
Tools return only what your account can reach: meetings you own, meetings shared with you directly, and meetings shared with a group you belong to. Read [Overview](/docs/ai-assistants/overview) for the full permission model.
## 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]
* 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 shared organization-wide are not exposed through the connector. If you need one, ask the owner to share it with you directly 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 meetings, typically transcript-only imports or backfills from other providers, 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 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 |
| -------------------- | ---------------------------------------------------------------------------------------- |
| Auto-record | 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. **Auto-record** is what most reps settle on, because the meetings you forget to record are the ones you most want back.
## 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 **Auto-record**, **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. Auto-record your Zoom meetings 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 **Auto-record**. The control bar appears on its own and shows a running timer.
## Next [#next]
* [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 and it answers from the meeting
so far. See [Live AI](/docs/capturing-meetings/live-ai).
### 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** 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/capturing-meetings/live-ai) 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.
# Live AI (/docs/capturing-meetings/live-ai)
Live AI runs in the SalesEQ desktop app while a meeting is going on. It transcribes as people talk. Ask it
a question and it answers from what has been said so far.
The point is the second half. Everything else in SalesEQ works on a meeting once it has finished. Live AI
works on the meeting you are still in.
## Turn it on [#turn-it-on]
Live AI is off until you switch it on. Open the SalesEQ desktop app, go to **Settings**, and turn on
**Show Live AI in meetings** under **Live AI**.
## Reading along [#reading-along]
Start a recording and the Live AI window opens over your meeting. It has two halves: **Ask AI** on the
left, and **Live Transcript** on the right, filling in as people talk.
Use the transcript to catch a number, a name, or a job title you missed, without interrupting the person
speaking to ask again.
**Collapse transcript** narrows the window to the asking side. **Minimize** puts it away entirely.
## Asking during the meeting [#asking-during-the-meeting]
Type into the box on the **Ask AI** side and select **Ask**. Live AI answers from the transcript so far:
```text
What number did they say for headcount?
What have they asked for that I have not answered?
What did they say about timing?
```
This is what makes it more than a transcript window. Reading back means finding the line yourself. Asking
means getting the answer while the conversation is still live.
Live AI only knows the meeting in progress. For questions across meetings, use
[Search](/docs/your-meetings/search) or a [connected assistant](/docs/ai-assistants/overview) afterward.
## What you get afterward [#what-you-get-afterward]
Live AI is a fast draft, produced while the meeting is still running. The transcript SalesEQ processes
after the meeting ends is the accurate one.
Expect the finished transcript to differ. It carries speaker names, corrected wording, and timestamps that
line up with the recording. Read Live AI in the moment, and the processed version afterward.
## Next [#next]
* [Viewing a meeting](/docs/your-meetings/viewing-a-meeting) covers the finished transcript.
* [Ask AI](/docs/your-meetings/ask-ai) covers asking questions once a meeting is done.
* [What gets captured](/docs/capturing-meetings/what-gets-captured) covers everything a recording produces.
# 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.
# 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 meeting SalesEQ did not record. That covers meetings from before you had SalesEQ, recordings from a platform you do not run the desktop app on, and files a teammate sent you.
## Upload a file [#upload-a-file]
### Open Upload [#open-upload]
Go to **Upload** in [the web app](https://app.saleseq.ai/upload).
### Add your files [#add-your-files]
Drag a file onto the page, or browse for it.
SalesEQ accepts common audio and video formats, including MP4, MOV, MP3, M4A, WAV, and WebM.
### Wait for processing [#wait-for-processing]
Uploading a large file over a slow connection takes a while, so leave the tab open until it finishes.
Processing runs after that, and it usually takes a few minutes.
## Verify it worked [#verify-it-worked]
The meeting appears under **My Meetings** once processing finishes, and it opens.
## 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 or you uploaded it. This page covers what each part is.
## The recording [#the-recording]
The audio and video of the meeting, captured on your machine. 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.
## 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
* **Pulled in by an integration** from a connected tool that already holds your meetings
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, 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**, the person who recorded or uploaded it. Ownership stays put. Everyone else reaches a meeting through sharing.
A new meeting starts with only its owner. Anyone else who can see it got there because someone shared it, or because an [Auto-share rule](#auto-share-rules) shared it the moment it finished.
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 Shared Meetings [#access-is-not-the-same-as-appearing-in-shared-meetings]
The [Shared Meetings](https://app.saleseq.ai/shared-meetings) page collects meetings other people have given you access to. A meeting lands there when someone names you directly, or names a group you belong to.
Organization access does not. You can open the meeting if someone sends you to it, and search reaches it, but it never shows up in Shared Meetings. That is why a meeting can be open to your whole organization and still look missing.
## 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, reporting, 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. They roll up across meetings in **Reporting**, which is where trends over a rep, a team, or a time range live.
## Search [#search]
**Search** runs across the meetings you have access to, not only yours, and never more than your permissions allow.
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 never sees more than you do. It reaches meetings you own, meetings shared with you directly, and meetings shared with a group you belong to. Meetings shared organization-wide stay out. 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 **My 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 **My Meetings** with your organization name in the welcome message. The table is empty until
you record something, which is expected.
## 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, groups, and Reporting worth anything.
Open [Settings](https://app.saleseq.ai/settings) and select **Invite** under **Organization members**. 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.
The icon changes while a recording is running, so you can tell at a glance whether you are being recorded.
## 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/capturing-meetings/live-ai) 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 in Settings 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 **My Meetings**, and a welcome message names your organization.
Both meeting lists start empty. **My Meetings** fills up when you record something. **Shared Meetings**
fills up when a teammate shares a meeting with you, which they can do now that you are in the
organization.
## 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 **My Meetings**. 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).
## Next [#next]
* [Reporting](/docs/insights/reporting) covers trends across many meetings.
# Reporting (/docs/insights/reporting)
Reporting covers every meeting in the organization rather than one meeting at a time. It answers questions about volume and participation: who is recording, how much, and how that is changing.
Open **Reporting** in [the web app](https://app.saleseq.ai/reporting). Every member can, not only admins, and everyone sees the same numbers.
## What it shows [#what-it-shows]
Four totals across the top: **total meetings**, **total minutes processed**, **average BANT score**, and **average EQ score**.
Below them, each of the four charted month by month, then meetings and minutes broken down by rep.
**Export to PDF** saves the current view.
## Next [#next]
* [Meeting insights](/docs/insights/meeting-insights) covers per-meeting analysis.
* [AI assistants](/docs/ai-assistants/overview) answer questions that span many meetings.
# 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 [Settings](https://app.saleseq.ai/settings) 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 [Settings](https://app.saleseq.ai/settings).
### 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 [Settings](https://app.saleseq.ai/settings).
### 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.
# 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 [Settings](https://app.saleseq.ai/settings) and find auto-sharing.
### 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 the reporting dashboard.
```
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.
## 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 [Settings](https://app.saleseq.ai/settings) and find 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, reporting, 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)
A meeting starts with only its owner, the person who recorded or uploaded it. Everyone else reaches it through sharing, whether you shared it by hand or an [auto-share rule](/docs/sharing/auto-share-rules) did it for you.
## 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 hand out. It stays with the person who recorded or uploaded the meeting, and only
they and an admin can delete it.
## 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 in [Settings](https://app.saleseq.ai/settings).
## Why a direct share is not the same as general access [#why-a-direct-share-is-not-the-same-as-general-access]
Both let someone open a meeting. Only one puts it where they will find it.
A **direct share** to a person or a group lands under **Shared Meetings**, in the **Shared With Me** tab.
That is the list people check for work sent to them.
**General access** makes a meeting reachable by everyone in the organization, but it does not put the meeting
in anyone's **Shared With Me** tab. Those meetings sit in the **Organization** tab instead, which people go
looking through rather than watch.
The result is a meeting reachable by everybody and surfaced to nobody.
The pattern that works: 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 Shared Meetings like any other 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.
# 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 |
| ---------------------------------------- | --------------------------------------------------------------- |
| Creators can never delete | Nothing. Ask an admin. |
| Creators can delete within a time window | Delete for a set time after upload, then it is an admin's call. |
| Creators can always delete | Delete their own meetings whenever they want. |
The setting says "creators" for what the rest of SalesEQ calls the owner.
## 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.
You reach it through a connected [AI assistant](/docs/ai-assistants/overview). Ask Claude or ChatGPT about your meetings and it searches on your behalf, then opens the ones worth reading.
Search only ever covers meetings you already have access to: your own, meetings shared with you directly, and meetings shared with a group you belong to.
## 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.
## 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 **My Meetings** or **Shared Meetings**.
## 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.
## 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).
## 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.