Skip to guide

See Distill in action

Request Demo

Tell us a little about yourself and we’ll follow up to schedule time.

Browse guides
Read Markdown

Using an assistant

On this page 13 sections

Distill connects research, audience selection, contact lists, personalized messages, and outreach. An AI assistant can use Distill's supported tools to work with those capabilities in a connected account.

These public pages explain Distill's capabilities and fit. Connecting a Distill account also lets the assistant read private account information and carry out supported actions with that user's permissions.

How the connection works#

MCP, short for Model Context Protocol, is the standard a compatible assistant uses to connect to Distill's tools. Distill supplies the account information and supported actions; the assistant interprets the customer's request and uses the actions available to it.

The assistant setup page has instructions for supported apps, including ChatGPT and Claude. It includes the server address and sign-in steps. Settings and workspace policies in the assistant app can affect which connections a person can add. The Distill MCP page summarizes what the server does; it is available to both Agent and Managed customers.

You approve the connection in the browser. A new user can sign up there; an existing user signs in to the Distill account they intend to connect. The approval screen identifies the app requesting access. The assistant then uses Distill as that signed-in user.

The assistant's access follows that user's organization, project, and list permissions. Its available tools determine which actions it can perform.

What a connected assistant can help with#

The supported actions include several parts of the same outreach workflow.

AreaExamples of supported workImportant boundary
ResearchFind people or companies, read profiles, resolve an email to a profile, request profile researchA pending lookup is not a completed or verified profile
ProjectsRead project settings; create and update supported project details; archive projects with owner accessAccess and setup requirements still apply; archiving is separate from billing and connection management
ReportingRead project and campaign results and supported weekly performance summariesDate windows, the people counted, and missing calendar data affect interpretation; see Reporting and results
TargetingRead targeting groups and searches; create groups; update supported criteria, traits, and starting poolsThe app has search options that the current connector cannot set
ListsCreate lists, add people, import CSV data, review matches, edit supported columns, and remove entriesImports can run in the background; some columns need the app
CampaignsCreate supported campaigns, adjust supported settings, work on message templates, preview and publish messages, launch, pause, resume, or finish eligible campaignsA saved campaign or published template is not evidence that outreach was sent
Account setupRead organizations, relevant billing, LinkedIn, extension, or HubSpot setup information and obtain setup links; create an organization where supportedPayment, installation, and connection consent happen in the browser; creating an organization is an account change
SupportSubmit feedback, a bug report, or a support question through the supported support toolIt sends an email associated with the account; success means accepted for delivery, not read or resolved

The current tool descriptions and Distill's workflow guidance give the supported inputs and restrictions. Some app features are not available through MCP.

The product pages provide the fuller explanations: Research and Enrichment, Company search and People search, Lists, Campaigns and personalization, Reporting and results, and Integrations.

Changes can take effect immediately#

Some tools call their changes “proposals.” When an assistant uses them through MCP, supported changes can apply immediately as the signed-in user. There may be no separate card waiting for someone to click Apply in Distill.

This includes creating a project, importing a file, updating a list, changing a campaign's source lists, and pausing or resuming outreach. The tool's result says whether the change applied or was refused.

The assistant app may ask for confirmation first. Once allowed, the Distill action still takes effect as described by the tool.

Creating an organization can also place the creator's existing, unassigned projects into that organization, so its billing applies to them.

Drafting copy in a conversation is different from saving that copy to a campaign. Previewing a message is different from publishing the template. Publishing does not itself activate a campaign, but it can affect unsent messaging in a campaign that already exists. Launching or resuming is a separate action with its own consequences.

Campaign readiness still matters#

The current connected tools support launching eligible campaigns as well as pausing and resuming them.

Launch checks still apply. A campaign needs its required messages set up, a sender who can send, and an account that meets the launch requirements. Available sending allowance and billing status can also affect whether it can run. The tool can report what is blocking the campaign instead of launching it. On Agent, a failed automatic outreach-pack payment blocks launch or resume until payment succeeds.

Creating a campaign does not launch it or enable automatic sending. Launching or resuming preserves the campaign's existing sending mode. Manual mode requires approval to start new outreach, while eligible continuations and follow-ups can still send. A resumed automatic campaign can resume its sending.

The current campaign tools do not cover every control in the app. They cannot edit automatic-send settings, daily caps, or send windows, or provide a general way to handle and send individual replies. Some changes affecting the sender or seats can require confirmation in the app.

An eligible sender can launch without active billing while within the free sending allowance reported by the tools. The billing section below explains how that differs from the paid plan's allowance.

An email-capable campaign also needs a usable sending mailbox. A new campaign can exist before that setup is complete. LinkedIn-only outreach has different channel requirements. These distinctions are covered in Campaigns and personalization.

What needs to be connected?#

There is no single connection that enables every part of Distill. Each connection has a different purpose.

Connection or settingWhat it enablesWhat it does not establish
Distill sign-in and assistant consentThe assistant can act as that Distill user through supported toolsAccess to another user's account or every company project
Organization and billingThe organization's plan, subscription, and applicable seatsA connected sender mailbox or LinkedIn session
Sender's LinkedIn connectionLinkedIn work through that sender's authenticated sessionEmail sending or calendar access
Gmail connectionAuthorized email sending and reading needed for campaign email workA calendar connection or permission to use any address typed into a campaign
Google Calendar and ContactsCalendar information, meeting context, and imported contact relationshipsGmail sending permission or proof that every meeting was attributed to outreach
Campaign booking linkA route for a recipient to book a meetingA completed booking, calendar sync, or supported booking confirmation for every scheduling provider
CRM connection and project settingsThe CRM data and behavior configured for the relevant projectA completed import or automatic application of every CRM field; see Integrations

A setup link starts the connection process in the browser. Requesting setup, installing an extension, saving a connection, passing a connection check, completing an import, and having a campaign ready to send are separate steps. For example, Gmail can be connected while the LinkedIn session has expired. A campaign can also have a booking link while calendar reporting is incomplete.

Email, dedicated mailboxes, and calendars#

The standard in-product email connection is Connect Gmail. The current Gmail consent requests both sending and read access. Calendar and Contacts have a separate connection, even when they use the same Google account. Older email connections can have narrower permissions and may need an upgrade for current campaign features.

The connection belongs to the Distill user who completes the browser flow. Completing setup while signed in to a teammate's Distill account does not grant the intended sender their own connection. Selecting a different Google mailbox also does not change which Distill user receives the connection.

A campaign's sending address must be available to its configured sender through a usable connection. Distill supports connected Gmail mailboxes and Gmail-authorized Send as addresses. A Send as alias still uses the underlying connected mailbox; entering an arbitrary address does not create sending permission. The app can refresh available Send as addresses after they are configured in Gmail.

Distill can also arrange dedicated cold outreach mailboxes. On Agent, customers can use their own mailboxes or request the paid mailbox add-on. Managed includes mailbox setup and warm-up. The current price and setup timing are on Pricing.

The in-app mailbox request sends the request to Distill's team and records it on the project. The assistant's general support tool can send a question or request to the team, but it is not a dedicated mailbox-provisioning action. In either case, a submitted request is separate from a mailbox being created, connected, warmed up, and selected for a campaign.

Use the connection options and sending addresses available in the account. The documented Gmail setup does not establish support for arbitrary Outlook or SMTP connections.

A connected calendar and a booking link also serve different purposes. Calendar access supports meeting information and context. A booking link lets the recipient choose a time. Supported booking integrations and calendar matching can supply evidence of a meeting, but merely saving or clicking a link is not a booked meeting. The effect on results is covered in Reporting and results.

LinkedIn is a separate connection#

Connecting an assistant to Distill is separate from connecting the sender's LinkedIn account.

The Distill Chrome extension normally supplies the LinkedIn session to Distill through the signed-in browser setup. A session cookie represents an authenticated LinkedIn session. It is sensitive account access, not an ordinary public profile link.

The supported connection flow keeps setup in Distill and the browser. Raw LinkedIn cookies do not belong in an assistant conversation, email, or shared document.

Distill can report whether a usable LinkedIn session is on file and whether the extension has been detected. Those are different checks. Past detection does not prove that the extension is still installed or running now.

If the saved session expires or LinkedIn ends it, Distill may require reconnection. The settings page also distinguishes an unverified session status from a confirmed session failure. An unavailable status check does not necessarily mean the user needs to reconnect.

The settings page provides Disconnect LinkedIn and reconnect controls. Disconnect removes the saved LinkedIn cookies and clears the restriction that requires reconnecting with the same LinkedIn profile. It does not delete all existing Distill data. Email outreach has its own connection and campaign controls, so disconnecting LinkedIn does not by itself establish whether email has stopped. Removing the extension from Chrome is also separate from removing the session already stored by Distill.

LinkedIn still controls account limits and restrictions. Pause other LinkedIn outreach automation on the same sender account before Distill starts. FAQ covers personal use, travel, and account-access questions.

Permissions and account context#

Distill separates the individual user, the organization, the project, and the outreach sender. They are related, but they are not interchangeable.

  • User: the person signed in to Distill. Their assistant connection and personal integrations belong to that user.
  • Organization: groups a company's members, billing, and projects. A user can belong to more than one organization.
  • Project: the workspace for a particular outreach effort, with its own people, lists, targeting, campaigns, and settings.
  • Sender: the person a campaign sends as. That identity can differ from the teammate operating the app or assistant.

Organization roles and project roles are separate:

RoleMain scope
Organization AdminManages organization settings, members, and billing, and can attach eligible unassigned projects they own. Some project views recognize organization-admin access, but project editing and owner-only actions still require the relevant project membership.
Organization BillingCan manage the subscription and sender seats, alongside ordinary organization membership. It does not grant organization-admin powers or project ownership.
Organization MemberHas ordinary organization access. It does not automatically grant access to every project or its sending accounts.
Project OwnerCan work with project resources and manage its members and roles. Owner access is also required for archiving and other owner-only actions.
Project MemberCan work with the project's ordinary resources, including supported edits. This is not a read-only project role. Members cannot manage existing users or grant owner access.

Project members can create member invitations. Project owners can create owner or member invitations and manage pending invitations. For normal customer invitations, acceptance is required before access is granted. An invitation awaiting acceptance is not a project membership or consent to send as that person. An invitation addressed to an email must be accepted by the matching account; forwarding it does not transfer that access.

When someone accepts a customer project invitation sent to their email address, they also join the project's organization if they are not already a member. Distill staff have a separate direct-enrollment flow, so access can start immediately when they grant it.

Lists also have their own access rules. A shared list can be readable without granting every edit or owner-only operation. Project access does not automatically make someone the owner of a list. Lists explains those boundaries.

The sender must be eligible to send, with the necessary account connections and access. A person appearing in the project's sender roster is not proof that their mailbox is connected or usable. Adding or removing a project member also does not automatically replace the sender selected on an existing campaign.

Seats and permission roles are separate. Assigned roles determine what each person can access. An Organization Admin can manage billing. Assigning a seat does not connect LinkedIn or grant mailbox access. See Pricing for the current seat rules.

Some assistant actions require project edit access even when related information is readable elsewhere in the app.

Billing, project lifecycle, and offboarding#

These controls affect different things:

ChangeWhat it changesWhat remains separate
Pause or finish a campaignIts outreach state, with the distinctions described in Campaigns and personalizationSubscription cancellation, mailbox setup or shutdown, and disconnection of integrations
Archive a projectThe project's status and its presence in active project lists; its record is retainedA billing cancellation or a completed account offboarding
Remove a project memberThat project membershipOrganization membership, directly shared lists, stored integrations, and the campaign's selected sender
Disconnect GmailDistill's stored access for that connection, including sending and email tracking through itCancelling the Google mailbox itself or its subscription
Disconnect Google Calendar and ContactsCalendar/contact access and the associated imported calendar/contact data in DistillDeleting the original calendar or contacts in Google
Disconnect LinkedInThe saved LinkedIn session in DistillCancelling Distill, disconnecting email, or ending every session on LinkedIn
Cancel a Distill subscriptionRenewal and the subscription's effective end dateConfirmation that campaigns, connected accounts, and separately provided infrastructure have all been closed

Archiving is not an account-deletion or data-erasure request. Removing a person from one project is not complete offboarding either: another membership or directly shared resource may still provide access. The project also needs a remaining owner; the member-removal action refuses to remove its last owner. Organization member controls similarly prevent removing or demoting the last organization admin.

The published Terms of Service describe cancellation as taking effect at the end of the current subscription period. The applicable plan or signed agreement and confirmed service end date determine the customer's arrangement.

The assistant's billing setup view shows the selected organization's stored subscription information. It may not yet reflect a recent change made through the billing page.

When billing is inactive, the setup tools can report a free sending allowance, including its limit, used amount, and remaining amount. This is cumulative for the sender across campaigns and organizations, not a monthly allowance. A person contacted in more than one campaign can count more than once in that report. Eligibility and launch behavior come from the account's returned allowance and readiness checks.

That free allowance is separate from the paid Agent plan's monthly allowance pooled across seats. The billing setup tool reports Agent's included usage and allowance, remaining purchased credits, purchased-pack count, and any failed pack payment when those apply. These values can lag recent sending or billing changes. The free allowance is not a substitute for the paid Agent pool. Published paid-plan terms are on Pricing; billing questions go through the organization's billing page or Distill support.

On Agent, once the included pool and purchased credits are exhausted, the next chargeable outreach automatically buys a pack of 200 for $200. A failed payment pauses the organization's live campaigns and prevents launch or resume. The billing page provides payment-method management and Retry payment. Once the payment succeeds, campaigns can be resumed; they do not resume automatically. Plans and usage explains the six-month counting window.

Customer-provided mailboxes and domains remain separate services at their provider when disconnected from Distill. Distill-provided outreach mailboxes and domains are managed as part of the service. Distill handles their shutdown during offboarding. Coordinate the service end date, stopping outreach, and disconnecting sending accounts with the team. Distill support can confirm the shutdown steps for your setup.

Offboarding includes the agreed service end, stopping relevant outreach, handling open conversations and meetings, removing access and connections, and shutting down Distill-provided sending infrastructure. A request to delete or transfer customer data is separate.

Current guidance and changing tools#

Distill's assistant capabilities evolve. The connection provides current guidance for projects, targeting, campaigns, and list importing. That guidance explains how to use the tools; these product pages explain what they do and their limits.

An assistant app can retain an older tool list after Distill updates its connection. If an action is missing or the connection asks for a refresh, refreshing can update that list. The available tools and their returned results establish what the connection supports.

Who does the ongoing work?#

On Agent, the customer owns strategy, replies, and scheduling. The assistant can help with the supported preparation, account changes, and analysis; connecting it does not turn the plan into a managed service.

On Managed, Distill's team and account strategist operate the program, keep the outreach strategy aligned with the customer's goals, and retain the context of what was tried and learned to guide the next changes. Current responsibilities and terms are on Pricing.

Common questions#

Can an assistant explain Distill without signing in?

Yes, it can read the public product pages. Private account data and actions require a connected account with appropriate access.

The assistant called it a proposal. Has it already changed my account?

It may have. Through MCP, supported proposed changes can apply immediately. The tool's reported result determines whether the change happened.

Can my assistant launch a campaign?

Current tools support eligible launches, pauses, and resumes. Readiness checks and account permissions still apply. Creating a campaign or publishing a message is not the same as launching it.

Will the assistant handle all my replies and meetings?

Not automatically. The current tools cannot handle the full process of reviewing and sending individual replies. On Agent, replies and scheduling remain the customer's responsibility.

Can I use the app and my assistant together?

Yes. They work with the same account resources, within the access and capabilities of each. Changes made through one can affect what the other reads, including campaign lists and unsent messages.

Does connecting Gmail also connect my calendar?

No. Gmail and Google Calendar/Contacts have separate connections and permissions, even if they use the same Google account.

Can an organization admin automatically edit every project?

No. Organization administration and project membership are separate. Some views recognize the admin role, while project edits and owner-only actions still require the appropriate project access.

If someone leaves the team, is removing them from one project enough?

No. That changes one project membership. Organization roles, other projects, shared lists, sending identities, and account connections may need separate attention.

What happens to sending accounts when service ends?

Your own mailboxes and domains remain separate services with their providers. Distill handles the shutdown of outreach mailboxes and domains it set up as part of the service. Coordinate the service end date and shutdown steps with your Account Strategist or Distill support.

All guidesBack to top
Distill product guidesAll pages as text