You told us the summary matters, not the audio, and reps should just focus on the call. The simplest way to get there is one platform: HubSpot becomes the phone system. Your office numbers port into HubSpot calling, every call logs itself with an AI summary, and the integration carries it to NetSuite. No extra telephony vendor.
Your reps make and receive calls, mostly on mobiles and often out in the field, and they should just focus on the conversation. In the background, the call needs to be summarised and that summary logged against the right contact in HubSpot, then carried through to NetSuite. You are not attached to keeping the audio; the summary is the point.
Only one part of this is genuinely hard: an inbound call landing on a rep's mobile out in the field. Every other call can run through HubSpot itself, so the answer is one platform, not a stack of telephony tools.
Every call ends up as an AI summary on the right HubSpot record, then flows to NetSuite. There are three ways in, depending on where the rep is, and all of them are HubSpot.
Two things we confirm up front. First, porting eligibility for your specific numbers in Australia, plus the carrier paperwork (a letter of authorisation and a recent bill); the port runs while 8x8 keeps working, so there is no gap in service. Second, that HubSpot's IVR covers your call flows as they are today; it handles menus and team routing well, and we map your current 8x8 setup against it before committing the numbers. If any number cannot port or a flow does not fit, that number simply stays on 8x8 in the interim.
Wherever the call is captured, the pattern into NetSuite is the same. It is logged as a call activity in HubSpot first, with its AI summary. From there the HubSpot to NetSuite integration carries it across and writes the call and summary into NetSuite as an activity against the matching contact and company, in whichever NetSuite field or notes layout Liam prefers. So the way you capture the call and the way it reaches NetSuite are separate; all three inbound routes above feed the same pipe.
The field trade-off, stated plainly. The recap is the rep's own account of the call, not a word for word transcript, and it asks reps to spend 20 seconds after each call. In return you add no telephony vendor, nothing depends on data coverage, and you skip the hard part entirely. If a full verbatim recording of every field call ever becomes a must-have, that is a dedicated capture tool on the handset or in the carrier network, and a separate decision for later. It is not needed now.
Recording actual calls is regulated in Australia under Commonwealth and state surveillance and listening devices legislation, and the rules differ by state. The field recap sidesteps most of this, because the rep is recording their own summary rather than the customer's voice. For desk calls recorded in HubSpot, the safe practice is a simple disclosure line in the greeting and a short retention window, given you care about the summary rather than the audio. We set the consent and retention options in HubSpot, and you should run the final policy past your legal advisor.