Voice agent development for Australian teams that need calls to actually convert.

Strong — voice is the workload where same-zone overlap matters most, and Australia is one of our better windows. India Standard Time is UTC+5:30, AEDT is UTC+11, so our 9:30am IST is your 3pm AEDT — a four-hour afternoon overlap with Sydney, Melbourne, and Brisbane working days every weekday. AEST (winter) shifts the overlap by one hour but the pattern holds. For Perth (AWST, UTC+8), the overlap is even stronger — our 9:30am IST is your noon AWST, giving most of an afternoon together. Daily standups and twice-weekly demos with real call traces (latency-per-turn, hand-off success, conversion numbers) run inside your business hours. Written async updates land before your morning standup. For voice incidents during peak AEDT traffic, an on-call engineer is reachable; for after-hours emergencies, a tech lead is on rotation.

Yes — and this is the question Sydney and Melbourne clients ask first. ElevenLabs and Cartesia both ship Australian English voices that hold a Sydney general or Melbourne accent across an entire call without drifting to American or British mid-sentence (a common failure mode of cheaper TTS that Australian customers notice within ten seconds — the vowels go wrong, the rising intonation disappears, the agent says 'check' instead of 'cheque'). Regional voices — Queensland, Western Australian — are available where the use case calls for them. For STT, Deepgram Nova-3 and AssemblyAI both handle Australian English including regional accent variation at production-grade word error rates; the failure mode of American-trained STT models misrecognising Australian vowels is something we test for explicitly in the eval set. We do voice auditions in week one — your team picks the voice on a real call sample with Australian reviewers, not on a marketing demo.

Yes. Engagement defaults align with the Privacy Act 1988 and the 13 Australian Privacy Principles. Call recordings, transcripts, and prompt logs are encrypted at rest and in transit; retention follows your policy (the agent does not retain audio indefinitely just because storage is cheap). Every model and tool call is audit-logged with timestamp, prompt version, model, input, output, and operator identity — exportable for an OAIC inquiry. A Privacy Impact Assessment is run for engagements processing audio at scale or operating on sensitive information. For APP 8 (cross-border disclosure of personal information), we explicitly map the data flow in your DPA — exactly where personal information is processed and which overseas endpoints (if any) receive it. PII redaction patterns cover TFN, Medicare numbers, driver licence numbers, and ABNs in customer context. The NDB scheme breach playbook is referenced in the DPA and tabletop-exercised in week one.

Your call. We default to AWS ap-southeast-2 (Sydney), AWS ap-southeast-4 (Melbourne), Azure Australia East (Sydney), Azure Australia Central (Canberra) for federal-adjacent work, or GCP australia-southeast1 (Sydney) / australia-southeast2 (Melbourne). For LLM inference, we route Claude (Anthropic), GPT-4o (Azure OpenAI Service Australia East), or self-hosted Llama 3 on vLLM inside your VPC — picked per your DPA's APP 8 third-party processing terms. Twilio voice media routes via Australian PoPs; Deepgram and ElevenLabs both offer Australian-region processing options with appropriate DPAs. For clients with strict no-overseas-inference requirements (federal-adjacent, defence, healthcare), we self-host the entire voice pipeline (Whisper STT, open AU English TTS, Llama 3 dialog manager) inside your ap-southeast-2 VPC.

Yes for the controls that affect the voice agent. For APRA-supervised banks and authorised deposit-taking institutions, our DPA includes documentation required under CPS 230 (operational risk management) and CPS 234 (information security) for third-party arrangements — material risk assessment, sub-processor management, incident reporting, and exit and continuity planning. The voice agent's script governance, audit-log retention, and escalation pathways are documented to support APRA examination. AUSTRAC-aware controls cover transaction-related disclosures and suspicious-activity escalation on collections and account-servicing calls. ASIC RG 271-aligned internal-dispute-resolution paths are wired into the agent so a complaint is escalated to a human within the required timeframe. We do not provide regulatory advice; we build the controls and ship the audit logs your CRO and your APRA relationship manager can defend.

No — Aiinfox itself does not currently hold an IRAP assessment, and we will not pretend otherwise. We are a foreign engineering provider, not an Australian-hosted SaaS, so IRAP assessment of our own platform is not the relevant control. What we do for federal and defence-adjacent voice clients is structure the engagement so the voice workload runs inside the customer's existing IRAP-assessed cloud boundary (typically AWS Australia or Azure Australia Central at PROTECTED classification); our engineers connect over a privileged-access path the customer's security team controls. If your engagement requires our own IRAP assessment, we will say so on the first call and recommend an Australian provider that holds one.

Yes — voice takeover audits are routine. Step one is reading the call recordings and traces, the latency telemetry, the refusal-rate and hand-off-success numbers, the AU English voice quality, the APP 8 compliance posture, and the CRM write-back data. Step two is shipping the smallest valuable change to prove we understand the system — usually swapping in a true Australian TTS voice, fixing barge-in handling, the escalation threshold, or the CRM write-back race condition the previous vendor skipped. Step three is the longer-term rebuild plan if one is needed. Most voice takeovers we see did not need a full rewrite; they needed proper turn-detection, a confidence-based refusal layer, a voice that actually sounds Australian, and a senior engineer on the build.

Most v1 voice agent engagements at Aiinfox land between AUD $55,000 and AUD $200,000 fixed-price for a focused build — an outbound campaign, an inbound deflection flow, or an APRA-aware fintech voice agent. Larger multi-quarter engagements with custom fine-tuning, bespoke evals, IRAP-boundary integration work, multi-accent voices, and integration into a regulated platform typically reach AUD $250,000 to AUD $420,000. The cost difference versus a Sydney or Melbourne voice AI consultancy lands roughly 30 to 50 percent lower on senior rates — useful, but the headline is the engineer on your kickoff call writes your dialog manager, your CRM integration, your APRA-aware script logic, and your eval suite through launch. No swap-out to a junior pool mid-engagement.