Your reps need to make and receive calls, mostly on mobiles and often in the field, and just focus on the conversation. In the background the call should be transcribed, an AI summary generated, and that summary logged against the right contact in HubSpot and carried through to NetSuite. This is the companion to the NetSuite integration scope, covering the calling decision.
On our call you asked me to take away one piece of homework: your reps need to make and receive calls, mostly on mobiles and often out in the field, and just focus on the conversation. In the background, the call should be transcribed, an AI summary generated, and that summary logged against the right contact in HubSpot and carried through to NetSuite. You are not particularly attached to keeping the audio recordings themselves; the summary is what matters.
The hard part is inbound calls to a mobile number. Outbound calls made through HubSpot are already well covered. Inbound calls that land on a rep's mobile over the ordinary phone network are invisible to HubSpot unless something captures them, and that is where the options below come in.
One piece of context from the demo: office calling currently runs on 8x8, and you are open to replacing it if something better exists. 8x8 has its own HubSpot integration (8x8 Work for HubSpot) that screen pops inbound callers and logs calls, with recording links, against the right records, so the desk bound decision is really between keeping 8x8 connected to HubSpot or consolidating onto a platform like Aircall, rather than a forced migration.
HubSpot's built in calling works from the desktop and the mobile app. Outbound calls can be recorded and transcribed, and HubSpot's calling notetaker generates AI summaries with action items. Your Sales Hub Professional seats include this, with a pool of 3,000 calling minutes per account per month and up to three HubSpot provided phone numbers, and extra minutes can be purchased if needed.
The catch is inbound. To receive and auto log inbound calls, the number being called must be a HubSpot provided number. A rep's existing mobile number can be registered for outbound caller ID, and on Android the HubSpot app will do a screen pop when a known contact rings, prompting the rep to log the call. But an inbound call to the rep's own mobile number is not recorded or transcribed. HubSpot's in person meeting notetaker (which records face to face conversations through the mobile app) is currently an iOS only beta, and your team is on Android, so it does not help here yet.
Good for outbound and for desk based calling on HubSpot numbers. Does not solve inbound to mobiles.
Aircall is the option I mentioned on the call. It is a cloud phone system: you provision business numbers in Aircall, calls ring the rep through the Aircall app on desktop or mobile, and every inbound and outbound call is recorded, transcribed and summarised by Aircall's AI, with sentiment and action items. Its HubSpot integration is deep and certified: calls, recordings, transcripts and AI summaries land on the contact, deal or ticket timeline automatically, in near real time, and can trigger HubSpot workflows. It also brings proper inbound features like IVR call trees, routing, business hours and warm transfer, which would suit your customer service and internal sales teams well.
The trade off is that it is VoIP. Calls travel over the internet (wifi or mobile data), so quality depends on the connection. For desk bound staff on office wifi that is a non issue. For reps driving between sites in patchy coverage areas, a data based call can be shakier than an ordinary mobile call. Reps would also be answering calls in the Aircall app on a business number, rather than on their existing mobile number, so numbers would need porting or reissuing.
The strongest all round option for desk bound teams. Usable in the field, but call quality depends on mobile data coverage.
Salestrail takes the opposite approach. Instead of replacing the phone system, it sits on the rep's Android phone and captures the ordinary SIM calls they already make and receive on their existing number, inbound and outbound, including WhatsApp calls. Call activity logs automatically to the matching HubSpot contact, with playback links to the recordings in the timeline. Because the call itself is a normal mobile network call, quality is exactly what your reps get today, regardless of data coverage. Reps keep their numbers and change nothing about how they call. It is also cheap: published pricing is USD $8 per user per month, plus $3 for the recording add on and $7 for the CRM integration, so roughly USD $18 per user per month before annual discounts.
The trade offs are worth being clear eyed about. Recording is Android only (which suits you), and it works through either the handset's built in call recorder or Salestrail's own APK; Salestrail themselves advise testing that both sides of the conversation are audible on your specific handsets before buying, because Android's recording behaviour varies by manufacturer. To be precise on the AI point: Salestrail captures, logs and records, but it does not itself transcribe recordings or generate AI summaries (its speech to text feature is for dictating notes after a call). The transcription and summary step would be a small Kongo built process that picks up each recording, transcribes it, generates the summary and writes it to the call record in HubSpot, from where the integration carries it to NetSuite. We would prove both the audio quality and this summary flow in a short trial before you commit.
The most practical way to capture inbound calls to existing mobile numbers in the field. Needs a trial to lock in the transcription and summary flow.
Both Telstra and Optus offer network level call recording powered by Dubber. Recording happens inside the carrier's mobile network itself, so every call on an enrolled service is captured with nothing installed on the handset, no app to open and no dependence on data coverage. The Dubber platform provides transcription and AI insights, and recordings can be pushed to other systems via its APIs, which is where a Kongo built connection into HubSpot and NetSuite would come in.
The trade offs: your mobile services need to be on the right carrier plans (for example Telstra's enterprise mobile services), there is a per service monthly cost through the carrier, and it is the most involved option commercially. It captures everything by default, which is powerful but also raises the compliance bar. One thing to weigh given your emphasis on stability: Dubber remains operational and continues to announce new partnerships as recently as late 2025, but it has had a difficult run as a listed company, including a trading suspension in 2022 after its FY22 revenue was found to have been overstated by around 29%. If you want this path, the first step is a conversation with your Telstra or Optus account manager to confirm current availability, pricing and the commercial standing of the offer on your plans.
The most bulletproof capture of mobile calls, but the heaviest to set up. Worth considering if complete coverage becomes a compliance requirement rather than a convenience.
| Scenario | A. HubSpot calling | B. VoIP (Aircall) | C. Mobile capture (Salestrail) | D. Carrier (Dubber) |
|---|---|---|---|---|
| Desk bound, outbound | Yes Recorded, transcribed, AI summary | Yes Recorded, transcribed, AI summary | n/a Not designed for this | Yes On enrolled services |
| Desk bound, inbound | Yes Only on a HubSpot provided number | Yes With IVR, routing and queues | n/a Not designed for this | Yes On enrolled services |
| In the field, outbound on mobile | Yes Via the app, over mobile data | Yes Via the app, over mobile data | Yes Ordinary SIM call on existing number | Yes Ordinary call, captured in network |
| In the field, inbound to a mobile number | No Screen pop and manual log only | Yes If the business number rings the app; depends on data coverage | Yes Captures inbound SIM calls to the existing number | Yes Full capture, no handset dependency |
| Call quality dependency | Internet connection | Internet connection | Mobile network (as today) | Mobile network (as today) |
| Reps keep existing mobile numbers | Outbound caller ID only | No Business numbers via the app | Yes | Yes |
| AI summary into HubSpot | Native | Native, certified integration | Via a Kongo built step. Salestrail records and logs but does not summarise | Via a Kongo built connection to Dubber's APIs |
| Effort to stand up | Low | Low to moderate | Low, plus a short trial | Highest. Carrier plans and commercials |
Whichever capture option you choose, the pattern for NetSuite is the same. The call, its transcript and the AI summary are logged as a call activity in HubSpot first. From there, the HubSpot to NetSuite integration carries it across: calls sync bidirectionally under the standard connector, and under a Kongo built custom integration we write the call and its summary into NetSuite as an activity against the matching contact and company, in whichever NetSuite field or notes layout Liam prefers. So the calling decision and the integration decision are independent; any of the four options above feeds the same pipe.
Recording and transcribing calls is regulated in Australia under Commonwealth and state surveillance and listening devices legislation, and the consent rules differ by state. The safe practice is a simple disclosure, for example a line in the inbound greeting for office numbers and a standard verbal disclosure for reps, plus a short retention window given you care about the summary rather than the audio. We will bake the consent and retention settings into whichever tools you land on, and you should run the final policy past your legal advisor.