An AI receptionist that works inside your HubSpot data

What the agent can do in HubSpot during a call

Once HubSpot is connected and turned on for the agent, the agent can use it mid-conversation instead of promising that someone will get back to the caller. It goes through HubSpot's own remote MCP server, so it sees the same records your team sees, limited to what the connecting user can reach.

• Find the record: search contacts and companies using what the caller tells it, such as a name, an email address or a company.
• Read it: open deals and tickets to answer status questions with real data, not a guess.
• Update what changed: a new email address, a corrected company name, or a ticket or deal property you allow it to change.
• Log activity while the call is live: a call, a note or a meeting on the record.

What happens after the call

When the call ends, Daber AI writes a summarized call engagement into HubSpot, linked to the contact, with the summary, sentiment and outcome. It can be assigned to an owner by email address, so the rep it concerns gets notified instead of finding it days later. It runs on outbound and campaign calls too. If the write fails, the call doesn't: the failure is recorded so it can be fixed, and the recording, transcript and summary stay in Daber AI either way.

What the agent can and can't do in HubSpot

Read and write are listed separately on purpose. Turn on only the actions your agent needs.

What you need to connect HubSpot

You need a HubSpot account and a HubSpot user whose permissions cover the records the agent should read and change. HubSpot's MCP server respects that user's permissions, and HubSpot says the tools it offers vary by subscription, user permissions and account setup.

1. 1Sign up for Daber AI and build your agent, or open the one you already have.
2. 2Add HubSpot from the tools you can connect, then sign in to HubSpot and approve access. Use a HubSpot user that has only the access the agent needs.
3. 3Test the connection, turn HubSpot on for the agent, and choose which actions it may use. For example, read and log, but not update deals.
4. 4Tell the agent in its instructions when to use HubSpot: look the caller up at the start, check the ticket when they ask about a repair, log a note before hanging up.
5. 5Run a test call in your browser and check the record in HubSpot.

An example call

A customer calls a home-services company about a repair. The agent asks for the email on the account, finds the contact in HubSpot and reads the open ticket: the part has arrived and the visit is booked for Thursday morning. The caller says the gate code has changed. The agent adds a note with the new code to the ticket and confirms the visit. When the caller hangs up, a summarized call lands on the contact, assigned by email to the technician's manager, and nobody had to type anything.

Where it stops

The HubSpot connection is an API integration, not a calling app installed inside HubSpot. Be clear about these limits before you rely on it:

• It only reaches what the connecting HubSpot user can reach. If that user can't see a pipeline, neither can the agent.
• It doesn't delete records, send marketing email or edit your workflows.
• It only uses HubSpot when its instructions say to. A caller asking it to change something isn't enough on its own.
• If you use another CRM, the signed webhook at the end of each call carries the same summary, sentiment and outcome to any system you choose.