For teams running Retell voice agents with HubSpot

Do your HubSpot records match what callers actually said?

Ilsara would independently compare your Retell call transcripts with HubSpot records, highlighting differences to investigate and explaining later changes.

See the sample report Register your interest

Read-only by design: it would never write to HubSpot or change your Retell agents.

This is a product preview using synthetic data. Historical analysis and self-service account connections are planned, not currently available.

Customer, 1 min 12 s into the call

“Thursday morning works, not Wednesday.”

Appointment in HubSpot

Wednesday 09:00

Difference to explain

Synthetic example from the sample report below.

Sample report, synthetic data

One call. Two records. Side by side.

Pick a finding to see the caller’s words next to the HubSpot value. Open the evidence to see the timestamps and the record’s history.

Northside Home Services, booking agent

50 synthetic calls1–14 Sep 2026Times in BST (Europe/London)

Difference to explain Appointment call_7f2a…3 Sep 2026

The caller moved the visit to Thursday. HubSpot shows Wednesday.

What the caller said

“Thursday morning works, not Wednesday.”

Customer, 1 min 12 s into the call

What appeared in HubSpot

Wednesday 09:00

Appointment property, written just after the call

Show evidence and historyHide evidence and history

Transcript

Customer“Thursday morning works, not Wednesday.”

01:12–01:15 into the call. Call on 3 Sep 2026, 14:00–14:03 BST

Record history Planned feature

Before the callEmptyNew contact
After the callWednesday 09:00Retell integration, 3 Sep, 14:04 BST
NowWednesday 09:00No change since

What to check. The value written after the call is the first day the caller mentioned. Confirm the booking with the customer before the visit.

Finding 1 of 6

118Match
14Difference to explain
9Changed after the call
9Not established on the call

Illustrative only: 150 field comparisons across 50 synthetic calls. These are not customer results and not a measure of accuracy.

What the four labels mean

Match: HubSpot shows what the caller said.
Difference to explain: HubSpot shows something else. That is a question to look at, not proof of an agent error. It may be intended.
Changed after the call: The value written after the call was later changed by a person, an import or another tool, or by an unknown source.
Not established on the call: The caller never gave a clear answer, so there is nothing firm to compare.

Three steps. Read-only throughout.

How it would work once built. These steps are planned and not available yet.

Planned

Connect Retell

Give read-only access to past calls: transcripts, timings and the values your agent captured.
Planned

Connect HubSpot

Give read-only access to contacts and their property history.
Planned

Review each finding

See the caller’s words beside the HubSpot value, with the evidence. You decide what needs action.

Your systems stay as they are

It reads. It never writes.

Ilsara would sit beside your setup and only review what already happened. More limits are in the questions below.

Never writes to HubSpot, and never edits, deletes or corrects your records.
Never changes your Retell agents, prompts, webhook settings or calls.
Never blocks or delays anything your agent writes.

Questions you might have

Is a difference an agent error?

Not automatically. A difference is something to explain. The record may have been set that way on purpose, or the caller may have been unclear. Every finding shows its evidence so you can decide.

Why would HubSpot keep its old value?

Some integrations are set not to overwrite values that already exist. In that case an unchanged value may be exactly what you configured. The audit shows it so you can confirm it is the behaviour you want.

What if a record changed after the call?

The planned history view would show the value before the call, just after it, and now, with the recorded source of each change, such as an import or a teammate’s edit. That keeps later changes from being blamed on the call.

When the history does not say who made a change, the audit says the source is unknown. It does not guess.

What does “independent” mean here?

It means a separate tool from the one that wrote the data. It does not mean the audit is proven accurate or always right. That is why every finding shows the caller’s words and timestamps for you to check.

Which calls would be compared?

Only calls that can be linked to exactly one HubSpot contact. A call that might belong to more than one contact is left out rather than compared with the wrong record.

What happens to call data?

Your calls in Retell and your records in HubSpot are never edited or deleted. The plan is for Ilsara to delete its own stored copies of call data on a fixed schedule, and for you to be able to disconnect both accounts at any time. Both are planned and not yet available.

Would it change how my agent works?

No. It is not a voice-quality tool, and it would not change how your agent talks or behaves. It would also not prevent or block anything your agent writes to HubSpot. It only reviews what already happened.

What can I use today?

You can explore the interactive sample report today. Live account connections and historical audits are not available yet. This preview helps us understand whether teams want the proposed product.

Tell us about your setup

We are looking for agencies and service businesses that already use Retell with HubSpot. 4 short questions, under a minute.

Your answers are stored by Tally in the EU on behalf of Ilsara. See the privacy notice below.

What we will ask

Your work email
Whether you use Retell and HubSpot together
Whether you would connect read-only access at launch
Which monthly price range you would consider. This shows interest only, not a commitment to pay.

Optional: your company name or website, and a message.

Privacy notice

Who runs this test. This test is run under the project name Ilsara. Full legal identification of who is responsible is not yet included in this notice. To contact us, use our Contact us form.

When you visit this page. Cloudflare Pages hosts this page. To deliver it, Cloudflare processes your IP address and browser details. We use Cloudflare Web Analytics to measure page views, visits, referral sources and page performance. The page loads a Cloudflare measurement script and sends measurement data to Cloudflare. According to Cloudflare, this analytics service does not use cookies or browser storage and does not track people across websites. Visits are not a count of unique people, and our own checks may be included.

When you answer the questions. Tally, our form service, stores your email, your answers, and your company name or website and message if you give them, on our behalf, on its servers in the EU (Google Cloud, Belgium). Your answers are not emailed to us; we read them in Tally. We use them only to measure interest in this test and, if you agree, to contact you about early access. We do not sell your answers. Tally’s form page can keep a random session ID, a random respondent ID and your unfinished answers in your browser’s local storage, and can send error reports to Sentry, the error-monitoring service Tally uses, in the US.

When you contact us. Tally stores your email, subject and message in the EU on our behalf, then emails a copy to our private mailbox using SendGrid, its email service in the US. Our email provider, Google, processes that copy and our replies. We use them only to reply to you. Our reply comes by email from our own address.

How long we keep it. Our schedule: we delete interest-form answers 90 days after the four-week test ends, and contact messages, the copy in our mailbox and our replies 90 days after your request is resolved. Providers’ backups are separate from our schedule: Tally says deleted form data is removed from its backups within 90 days; Google says deleted data can remain in its backup systems for up to 6 months.

Your choices. You can ask us to see, correct or delete your answers, or withdraw your agreement to be contacted, at any time through our Contact us form. A privacy request never requires agreeing to be contacted about early access. You can also complain to the data protection authority where you live.