HubSpot

Your assistant can search deals by stage, amount, close date or owner, read the stage definitions for the pipeline they sit in, and put the whole thing in front of you as one list. The stage names come from your account, not from a template, so the answer matches what your team calls things.

What you end up with. A pipeline view filtered the way you asked, with owner and stage on every deal.

Start with it bringing you the information and you deciding.

Never without. Ask what filter it used. A pipeline total is only meaningful once you know which deals were left out of it.

Built on: Search deals / List deals / Retrieve pipeline stages / Retrieve owners

It reads the contact and the company, then goes after the words people actually wrote. Listing a contact's notes returns note IDs rather than note bodies, so the assistant reads those IDs back in a batch to get the text. Deal activities come back with their content directly. Reading changes nothing in the account.

What you end up with. A short brief on who they are, what was last said, and what is open, ready before you dial.

Start with it bringing you the information and you deciding.

Never without. Skim the source notes yourself for anything sensitive that a summary would flatten, such as a complaint or a pricing concession.

Built on: Read contact / Search contacts by criteria / Get company / List contact notes / Read batch of crm objects by id or property values / List deal activities

It can search tickets by stage, priority and owner, read the stages your ticket pipeline actually uses, and resolve owner IDs to real names. The result is the standing question at every support check-in, answered before the check-in.

What you end up with. A list of open tickets grouped by owner and stage, with the oldest surfaced first.

Start with it bringing you the information and you deciding.

Never without. Do not turn a per-person ticket count into a comment on a person. It measures where work landed, not how anyone is doing.

Built on: Search tickets / List tickets / Retrieve pipeline stages / Retrieve owners

It can create the meeting record with your notes on it, attach a separate note where a note belongs, link both to the right contact and deal, and update the deal fields you name. The associations are the part people skip by hand, and they are the reason the record is findable later.

What you end up with. The meeting logged on the timeline of every record it touches, with the deal updated to match.

Start with it doing the work and checking with you.

Never without. Read what it wrote before you approve. Anything on a CRM timeline is visible to your team, and in some situations it is discoverable.

Built on: Create meeting / Create note / Create object association / Search contacts by criteria / Update deal

It can. HubSpot exposes creation from a plain description, so the assistant reads your property schema at the time it runs and fills in the fields your account actually has, including custom ones. Have it search for an existing match first, because the fast path to a duplicate is creating without looking.

What you end up with. A contact and a deal created with your own fields populated, plus the association between them.

Start with it doing the work and checking with you.

Never without. Require a duplicate search before every create, and check the deal amount and close date, which are the two fields a description-to-record step guesses at most freely.

Built on: Create Contact From Natural Language / Create Deal From Natural Language / Search contacts by criteria / Create object association

It searches a pipeline you name for deals with no activity in a window you set, then creates a follow-up task for the deal owner and links it to the record. It does the whole pass in one go and hands you the list of tasks it created, so you see the result of every run rather than approving them one at a time. It only ever creates tasks, which are cheap to delete if it gets one wrong.

What you end up with. Follow-up tasks sitting on the right owners' lists, tied to the deals they belong to, with the list of what it created waiting for you.

Start with it doing the work and showing you when it is done.

Never without. Bound it to a named pipeline and a fixed quiet window, and keep it creating tasks only. A version that also moves deal stages is a different task and starts again lower.

Built on: Search deals / List deal activities / Create task / Create object association / Retrieve owners

Support requests that arrive as email or as a form notification can be filed as tickets in a batch, each with its own properties and its association to the contact or company it came from. The assistant reads your ticket pipeline stages first so a new ticket lands in a stage your team already uses, and searches for the contact so the ticket is attached to a person rather than floating.

What you end up with. The backlog of intake messages sitting in your ticket pipeline as real tickets, each attached to the right contact.

Start with it doing the work and checking with you.

Never without. Read the summaries and the stage it picked before it files a batch. A ticket created in an active stage lands on somebody's queue and fires your own routing and notification rules, so a run of fifty is fifty interruptions if the stage is wrong.

Built on: Create tickets / Create ticket / Search tickets / Retrieve pipeline stages / Search contacts by criteria / Create object association

It can find them and it can merge them, and those are two very different handovers. Searching for likely duplicates and reading both records side by side is safe. The merge itself absorbs one record into the other, and HubSpot does not offer a way back through the API.

What you end up with. A reviewed list of duplicate pairs, and the merges you approved carried out.

Start with it doing the work and checking with you.

Never without. A merge cannot be undone through the API and the absorbed record is gone, so approve each pair yourself and name which record survives, because conflicting property values resolve in favor of the primary.

Built on: Search contacts by criteria / Read contacts / Search companies / Merge contacts / Merge two companies of same type