[INTERNAL] What Unify Chat can't do (yet)

This article is internal-only, used to train the agent on its own limits.

Unify Chat does a lot, and we're adding more every week. Here's what it can't do today, so you know where to set expectations.

What chat can't do (yet)

Write to your CRM

Chat can read from Salesforce and HubSpot: accounts, contacts, opportunities, owners, custom fields, pipelines. It can't write to them. Creating records, updating fields, logging activities, and moving deals through stages still happens in your CRM directly. Reads-only is by design at launch.

Assign account owners or round-robin ownership

Chat can't assign an owner to an account or run round-robin ownership logic. Account ownership still lives in your CRM and is managed there.

Set up Outlook from inside chat

If you use Gmail, you can connect your mailbox directly inside a chat conversation when chat asks for permission. Outlook works with Unify, you just need to connect it from Settings → Deliverability → Mailboxes before chat will be able to use it. We're working on bringing Outlook setup into the chat flow.

Access your LinkedIn first-degree connections

Chat can find warm introduction paths through your team's broader network (work history, shared employers, investor ties, and similar inferred connections). It can't read your personal LinkedIn first-degree connections, and it can't pull the engagement on an arbitrary LinkedIn post on demand.

Make phone calls

Chat doesn't initiate calls or interact with a dialer. Calls still happen through your normal calling tool.

Build dashboards or visualizations

Chat won't create charts, dashboards, or reports for you. It can return data, summarize it, and put structured results into a table you can save, but not graph it.

Send emails outside a sequence

Chat works with sequences, drafts copy, and can enroll contacts. It doesn't send one-off "send this exact email to this exact person right now" emails. If you need that, ask chat to create a manual one-off task with the draft, then send it yourself from your mailbox.

Apply exclusions to lists automatically

Exclusions are always applied to sequences: a contact who matches an exclusion rule won't be enrolled. But exclusions don't filter out matching contacts from lists chat builds. The contacts will still appear in the working table.

Best practice: when building a list, start the prompt with the filters you want explicitly. For example: "Build me a list of Series A SaaS companies, excluding existing customers, open opportunities, and companies anyone on my team has reached out to in the last 90 days." Chat will apply those filters at list-build time.

Remember everything across conversations

Chat persists explicit memories across all your conversations (things you ask it to remember, like your ICP, your tone preferences, or the personas you work with). It doesn't have full memory of every previous conversation's content. See Does Unify Chat remember things between conversations? for what is and isn't persistent.

Take destructive actions without confirming

By design, chat asks before doing anything destructive (deleting a List, unenrolling contacts in bulk, sending edits to a live sequence). If a quick answer matters more than confirmation, tell chat to "just do it" and skip the check.

On the roadmap

We're actively working on:

• Writes to Salesforce and HubSpot

• Outlook OAuth from inside chat

• Scheduled chat runs (recurring prompts that fire on a cadence)

• List-time exclusions and guardrails (so exclusions apply to lists, not just sequences)

• Richer cross-conversation memory

• More integrations (additional CRMs, additional mail providers)

If there's something you wish chat could do, tell us. Feedback shapes what we build next.