Solutions · Sales

Everything around the conversation, so you can have the conversation.

The research, the pre-call brief, the notes typed back into the CRM, the follow-up drafted from what was actually said. An agent picks up the work that sits either side of a call — and nothing leaves the building without your approval.

Drafts, not sends · every action logged · your CRM, your rules

Reaches
Your CRM, your inbox, your sheets
Credentials
Brokered server-side, never in the machine
Sending
Set it to Ask and the run pauses
Every call
Written to an audit record
The handoff

The half of the job that is not selling.

Nobody joined a sales team to update a CRM. But the pipeline is only as good as the data in it, and the data is only as good as the last hour someone was willing to spend on admin. That hour is the handoff.

  1. 01

    The pre-call brief

    Before a meeting it assembles what you would have skimmed anyway: the account history in the CRM, the open threads in the inbox, what the company has said publicly since you last spoke, and the two things that changed. One page, in your inbox, before the call.

  2. 02

    Call notes into the CRM, in your fields

    You paste the notes or drop the transcript in a thread; it writes them back into the right record, updates the stage, sets the next step, and flags what it could not confidently place rather than guessing at a picklist value.

  3. 03

    The hygiene pass nobody runs

    Duplicate accounts, opportunities with a close date in the past, contacts with no owner, deals that have not moved in six weeks. It produces the list with a proposed action per row — not a dashboard telling you the list exists.

  4. 04

    Account research that is actually current

    It reads what the company has published, matches it against your own qualifying criteria, and says whether the account fits and why. When it does not fit, it says that too, which is the more useful half.

  5. 05

    The follow-up, drafted from what was said

    Written against the notes and the account record rather than a template with a merge field. It lands in the CRM or your inbox as a draft. Sending is an action you can require approval on.

  6. 06

    Renewal and expansion watch

    A scheduled session reads which contracts come up, which accounts have gone quiet, and which have grown — and opens a thread with the shortlist and a first draft per account.

The output

A worklist with a proposed action on every row.

A report tells you what is wrong. A sales session hands you the rows and the specific thing it wants to do to each one, already drafted, waiting for a yes. The difference between those two is the whole product.

pipeline/2026-07-31-gone-quiet.mdReport
AccountStageLast touchDrafted action
Northwind LogisticsProposal31 daysFollow-up on the pricing question
Acme RoboticsDiscovery19 daysRe-book — champion changed role
Globex HealthNegotiation12 daysSend the security review pack
Initech RetailProposal44 daysClose-lost: no reply to three touches
Illustration. Northwind, Acme, Globex and Initech are placeholders — Kortix never names a customer.

Drafted is not sent

Every message it writes lands as a draft in the CRM or the inbox. If you want a hard stop before anything goes out, set the send action to Ask and the run pauses at the call and waits for you.

It shows what it read

Each row carries the record and the thread it drew from. A claim about an account that you cannot trace back to a source is a claim you should not act on, so it does not make one.

It arrives where you already are

Connect Slack and the shortlist lands in a thread you can argue with. Reply in the same thread and you are talking to the same session, not starting a new one.

Where it reaches

Your CRM and your inbox — without handing over the keys.

A sales agent is only useful if it can reach the systems the pipeline actually lives in. Connect each one once for the whole project. The raw credential is decrypted on our side and attached to the outbound call; it never lands in the machine the model is driving.

Salesforce, HubSpot
In the Easy connect catalogue: click through the OAuth screen and the connection belongs to the project. Read accounts, opportunities and activity; write back the fields you allow it to write.
Gmail and Outlook
Read the threads on an account and draft the reply. Reading and sending are separate actions with separate answers, so "may read the thread" never silently means "may send as me".
Google Sheets and Drive
The forecast that lives in a spreadsheet, the pricing sheet, the account plan. It reads them as source and writes the worklist back where the team already looks.
Slack
The one live channel. A mention in a thread starts a session and the answer comes back into the same thread. Microsoft Teams is shipped but stays off until your deployment turns it on.
Whose account it acts as
Choose one project-managed connection the whole team shares, or a personal authorization where every member acts as themselves — and an automated principal cannot act at all.

Easy connect covers 3,000+ apps through their own OAuth screens. If your sales stack includes something that is not in that catalogue — an internal quoting service, a regional CRM — it is still reachable through OpenAPI, GraphQL, raw HTTP or a remote MCP server.

How it runs

Before the call, during the week, and at 07:00 on a Monday.

The same session machinery started three different ways. What changes is when it runs, not what it is allowed to do.

  1. 01On demand

    "Brief me on Northwind before eleven"

    Ask in a Slack thread or from the web app. The session starts, does the reading, and answers in the thread with the brief attached as a file.

  2. 02Human-assisted

    It stops at the send

    Set the send action to Ask and the run holds at the call, showing you the message and who it is addressed to. Approve and the same call completes. Deny and the session carries on without it.

  3. 03Automated

    The Monday list, written overnight

    A cron trigger runs the hygiene pass and the gone-quiet sweep before anyone is at a desk, and posts the worklist into the channel. Triggers name the agent they run as, so the overnight session gets no more reach than the daytime one.

Control

Nothing goes to a customer without a yes.

Sales is the function where an autonomous mistake is a customer-visible mistake. So be precise about the defaults rather than reassuring about them.

Approval gates are off until you set them
The shipped default is permissive — an action runs unless you have said otherwise. For a sales project the first thing to do is set the outbound actions to Ask and the destructive ones to Block. We are telling you this rather than letting you assume the safer default was chosen for you.
An approval pauses the run, it does not fail it
A gate that errors out teaches an agent to route around it. A Kortix gate holds the call open, so you answer while the session is still mid-task and it resumes from exactly where it stopped.
The rule can read the arguments
"May the agent send email?" is rarely the question. Conditions match on the values in the call, so a rule can allow sending inside your own domain and stop at everything else. Anything the rule cannot decide resolves toward less access.
Connector credentials never enter the machine
The sandbox carries one project-scoped Kortix token and no third-party keys. Your CRM credential is decrypted server-side and attached to the outbound request. Turning a connector off takes effect on the next call — there is nothing in the sandbox to rotate.
Every call it made, and who let it
The record carries the connector and exact action, the agent, the person or trigger behind the session, the outcome, and who released a held call. There is no path to a connected tool that skips the thing writing the record.

The same platform, the other teams

One project, one set of connectors, one memory that compounds. Each team writes the skills for its own work; nobody stands up a second system.

All solutions →
Sales

Give it the admin. Keep the conversations.

Open source and self-hostable. Any model, your keys. Kortix Cloud, your own VPC, or your own on-prem network.

Kortix for sales teams