Acquire

· #271 most-used

Engage, support, and convert every website visitor with unified live chat, co-browse, and AI

CRMSalesCommunicationAnalyticsSupportAutomation

Acquire is a unified customer engagement platform that brings live chat, co-browsing, video calling, AI chatbots, and contact management into a single workspace. Support and sales teams use it to engage website visitors, resolve complex issues with no-download co-browse, and run automated chatbot flows that handle repetitive questions without a live agent. Connect Acquire to Actionist and your agents can route conversations by customer tier, sync pre-chat form data to your CRM, retrieve analytics on demand, archive compliance-sensitive transcripts, and monitor chatbot performance — all without anyone logging into the Acquire dashboard.

Try Acquire with Actionist Visit Acquire

Average time saved

10 hours

per person · per month

≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual cycle of copying chat leads into the CRM, updating helpdesk tickets after every closed chat, monitoring queue assignments, and pulling weekly analytics reports from the Acquire dashboard.

Schedule

What your Acquire agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs

7Agents at work

24/7Always on

Agents

Tue–Thu

Tue

Wed

Thu

10a

11a

12p

Multi-app workflows

Acquire × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows

7Apps spanned

~23 hrsSaved / week

5Personas served

For customer success

Featured3 apps

CRM context and smart routing on every new chat

When a visitor starts a chat, the agent looks up their email in HubSpot, retrieves their account tier and open ticket count, adds a private context note to the Acquire conversation, and routes the chat to the correct queue — all within about a minute of the chat starting, before any agent has typed a word.

~5 hrs

Time saved for your team — every week, on autopilot

The flow

Trigger·When a visitor starts a new chat in Acquire

Trigger

Step 1

Acquire

New chat started by visitor

read

Step 2

HubSpot

Look up visitor email in CRM contact records

write

Step 3

Acquire

Add private note with CRM account tier and open ticket count

write

Step 4

Acquire

Assign conversation to the correct support tier queue

write

Step 5

Slack

Notify enterprise-queue Slack channel if visitor is enterprise tier

Result

Add private note with CRM account tier and open ticket countAssign conversation to the correct support tier queueNotify enterprise-queue Slack channel if visitor is enterprise tier

The win

Saved per run

4 min

Runs / week

~80×

Every agent sees full CRM context before typing the first reply

Driven byCustomer Support Agent

ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

Sales
25 min / week
Manual lead creation from chat
Sales reps copy visitor details from the Acquire chat sidebar into HubSpot manually — 5–10 minutes of data entry per lead, usually done after the chat ends, by which time context is already fading.
Sales Agent
0 min
Agent creates CRM leads from chats automatically
When a visitor submits a pre-chat form on the pricing page, the agent creates a HubSpot contact and deal within about a minute — the rep joins the live chat already knowing the prospect's company and pipeline stage.
Marketing
20 min / week
Manual weekly chat analytics reporting
The marketing team logs into Acquire, navigates to analytics, copies the relevant figures, and pastes them into a spreadsheet every week before assembling a summary for the planning meeting.
Marketing Agent
0 min
Agent posts chat analytics digest automatically
Every Tuesday at 8 AM the agent retrieves Acquire analytics and posts a ranked engagement summary to Slack — chatbot deflection rate, top pages, and channel breakdown — before the weekly planning meeting.
Customer Support
40 min / week
Manual post-chat transcript and ticket work
After each chat ends, agents copy the transcript into Zendesk, mark the ticket resolved, and write a summary note in the CRM — 5–8 minutes of admin work per resolved chat that adds no customer value.
Customer Support Agent
0 min
Agent auto-closes tickets and archives transcripts on chat close
When a chat closes, the agent retrieves the transcript, marks the Zendesk ticket resolved, and adds a summary to the CRM — agents move to the next conversation without touching a second system.
Human Resources
15 min / week
Manual agent performance data collection
HR or team leads log into Acquire, navigate to agent reports, export the data, and manually compile it into a performance dashboard before each review cycle.
Human Resources Agent
0 min
Agent pulls agent utilization data before every 1:1
Every Thursday the agent retrieves Acquire utilization metrics for each support agent and writes them to the performance dashboard — managers walk into 1:1s with factual data, not recall.
Finance
8 min / week
Manual chatbot ROI calculation
Finance manually pulls chatbot deflection reports from Acquire, looks up average agent costs, performs the multiplication in a spreadsheet, and updates the budget dashboard — a 30-minute task done monthly.
Finance Agent
0 min
Agent calculates chatbot cost avoidance monthly
The finance agent retrieves chatbot deflection numbers from Acquire monthly, multiplies them by cost-per-live-agent-conversation, and appends the savings figure to the ROI dashboard automatically.
Operations
60 min / week
Manual queue monitoring and assignment
A queue manager monitors the Acquire unassigned conversation list throughout the day and manually assigns chats to available agents — requiring constant dashboard attention to avoid SLA breaches.
Operations Agent
0 min
Agent rebalances unassigned conversations automatically
Every Tuesday at 4 PM the operations agent lists conversations open without an assignment for more than 30 minutes and assigns each to the lowest-load available agent — SLA compliance maintained without a queue manager on standby.
Legal
30 min / week
Manual compliance keyword review
Legal or a designated compliance reviewer manually reads chat transcripts — or relies on support agents to flag sensitive conversations — before archiving to the legal document management system.
Legal Agent
0 min
Agent flags and archives compliance-sensitive transcripts automatically
The legal agent monitors Acquire conversations for compliance-flagged keywords, archives transcripts to the legal system, and alerts the legal team in Slack — all within about a minute of the keyword appearing.

+ 100s of other Acquire automations

Average time saved

20 hrs / person / month

Calculator

Calculate what your team saves

Team size

5 people

Hourly rate

$75 / hr

Hours saved / week

Hours saved / year

625

Annual ROI

$46,875

Based on Acquire's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug Acquire into Actionist

Pick the connection method that suits your environment.

Connect Actionist to Acquire using an API key generated from your Acquire dashboard. A read+write scoped key lets agents read conversations and contacts and write notes, assignments, and status updates.

Open API Keys in Acquire Settings

Copy and secure your API key

Copy the generated key immediately — Acquire does not show it again after you navigate away. Store it in a secrets manager, not in plain text.

Paste into Actionist and test

Paste the key into the API key field below and click Test connection. Actionist runs a read-only call to confirm the handshake.

Credentials you'll need

API key*

Acquire dashboard → Settings → Developer → API Keys → Generate key

Actions

16 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

5 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

FAQs

Questions about Acquire + Actionist

How do I connect Actionist to Acquire?

Go to the Apps tab, find Acquire, and click Connect. Paste your Acquire API key — found under your Acquire account Settings > Developer > API Keys. Actionist runs a test call to confirm the connection before any actions run. If your workspace uses multiple Acquire accounts, you can connect each one separately and route agent tasks to the right account.

What API permissions does the Actionist agent need in Acquire?

Most read operations — fetching conversation data, retrieving contact records, pulling analytics — require a read-scoped API key. Write operations such as creating contacts, sending chat messages, updating conversation status, or assigning agents require a full-access API key. Generate your key in Acquire under Settings > Developer > API Keys. Treat it like a password: store it in a secrets manager rather than plain text.

Can I combine Acquire with other apps in the same workflow?

Yes — Acquire integrations become most powerful when combined with your CRM, helpdesk, or analytics stack. Common combinations: sync new Acquire contacts into HubSpot or Salesforce when a chat starts; push resolved conversation summaries to Notion or Google Sheets; route co-browse session recordings to a Slack channel for quality review; trigger a follow-up sequence in an email tool when a chat closes without a resolution. Any Actionist-connected app can exchange data with Acquire in the same scheduled agent task.

What are the most common things agents do with Acquire?

The four patterns that come up most often: (1) contact enrichment — when a visitor submits a pre-chat form, the agent creates or updates a contact record in your CRM immediately; (2) conversation routing — when a new conversation comes in, the agent reads the contact record and assigns it to the right team or agent based on customer tier; (3) daily support digest — agents pull conversation and resolution analytics each morning and post a summary to Slack; (4) post-chat follow-up — when a conversation closes, the agent triggers a follow-up email or satisfaction survey through a connected email tool.

How do Acquire webhooks work with Actionist agents?

Acquire's webhook events include On Chat Start, On Chat Message, On Chat Accept, and On Chat Close. In Actionist, the agent listens for these events and can trigger downstream actions within about a minute of each event firing — for example, creating a CRM lead when a chat starts, or logging a conversation summary when a chat closes. If you need a faster integration, Acquire's JS SDK also supports real-time browser-side hooks for custom embedding.

Can agents access co-browse session data and recordings through the API?

Co-browse sessions in Acquire are recorded by default on plans that include recording. Through Acquire's REST API, the agent can retrieve co-browse session metadata — session ID, duration, participating agents, and a link to the recording. The agent can then log this data to a Google Sheet for quality assurance review, or attach it to the customer's CRM record so the account manager has context before the next call.

What support analytics can agents pull from Acquire?

Acquire's Analytics API provides conversation volume, first-response time, resolution time, agent utilization, chatbot deflection rate, and channel breakdown. Your Actionist agent can pull these metrics on a schedule — daily, weekly, or monthly — and write them to a Google Sheet or post a digest to Slack. This eliminates the need for team members to log into the Acquire dashboard just to check support health metrics.

Can Actionist agents interact with Acquire's built-in chatbot and knowledge base?

Yes. Acquire's Chatbot API lets you retrieve chatbot conversation logs, trigger chatbot flows programmatically, and query knowledge base articles. An Actionist agent can monitor chatbot deflection rates and automatically flag knowledge base articles that have low success rates for a human content review, or escalate chatbot conversations to a live agent when the bot confidence score falls below a threshold you define.