How to route Aircall calls by whether the caller is already in HubSpot

When every call lands in one queue, two things go wrong. Existing clients wait behind cold leads and have to explain who they are again. New leads wait behind support calls and hang up. Caller-aware routing fixes both.

The short answer

Check who is calling before you decide where the call goes.

• Known caller (their number is on a HubSpot contact): send them to their contact owner, their account team, or support.
• New caller (no match): send them to sales, or to a short menu that asks what they need.

What the native integration does and doesn't do

The standard Aircall and HubSpot integration is excellent for logging. It matches calls to contacts, records them on the timeline, and lets your team call from HubSpot.

Routing based on that match takes a little more. The call flow has to make its decision before anyone answers, so it needs the lookup result while the caller is still ringing.

How I set it up

On a recent build, the working pattern was:

1. Look up the caller. When a call arrives, the number is checked against HubSpot contacts.
2. Branch on the result. Known and unknown callers are sent down different paths. In that project, the cleanest way to do this in Aircall was to use its API together with two Smartflow numbers, one for each path.
3. Route known callers by owner. The HubSpot contact owner decides which teammate or team rings first, with a fallback to a shared support group.
4. Route new callers to sales. With a short greeting, and a voicemail or callback option out of hours.
5. Log everything. Every call, both paths, is still logged on the HubSpot timeline so nothing is lost.

Things to decide before you build

• Who "owns" a caller? Contact owner, company owner or a team? Pick one rule.
• What happens when the owner is busy? Ring the team, go to voicemail, or offer a callback.
• What about callers with several contacts on one number? Decide a tie-break, such as the most recently active contact.
• Out-of-hours behaviour for each path.

Testing checklist

• Call from a number that exists in HubSpot with an owner
• Call from a number that exists with no owner
• Call from a brand-new number
• Call while the owner is offline or on another call
• Call out of hours
• Confirm each call appears on the right HubSpot record

Frequently asked questions

Can Aircall route calls based on HubSpot data?

Yes, but it needs a lookup step before the call is answered. The native integration logs calls and matches contacts; routing on that match is done by checking the caller against HubSpot as the call arrives and branching the call flow.

Do I need a developer for this?

You need someone comfortable with Aircall's call flows and API and with HubSpot's contact data. It's a focused build, usually days rather than weeks.

Will calls still be logged in HubSpot?

Yes. Both paths keep normal Aircall logging, so every call shows on the contact's timeline.

Does this work with other phone systems?

The same idea works with RingCentral, Quo, Nextiva or Amazon Connect: look up the caller, branch the flow, log the call. The setup steps differ by platform.