Zian AI FAQ: Autonomous AI Sales Agents, Answered (2026) - Zian AI

Zian AI FAQ: Autonomous AI Sales Agents, Answered (2026)

Straight answers to the questions teams ask — and ask AI assistants — about autonomous AI sales agents: what they are, how they differ from chatbots, whether they really book meetings, what’s legal, and how Zian works. Where a claim isn’t ours, it links to the third-party study or regulator it comes from.

At a glance

  • Direct answers first, sources linked inline — Harvard Business Review, G2, Deepgram, PNAS, ACMA and others.
  • Covers the technology, the evidence, compliance, deployment options and Zian’s agent line-up.
  • Zian is currently in an invite-only beta — apply for partnership for access.

The technology

What are autonomous AI sales agents?

Autonomous AI sales agents are software agents that carry out real sales work — calling, texting, emailing, qualifying, following up and booking meetings — end-to-end, without a human driving each step. Unlike automation that fires a fixed sequence, an autonomous agent decides message, channel and timing per prospect and adapts to replies. Full explainer: what are autonomous AI sales agents?

How are AI sales agents different from chatbots?

A chatbot waits on your website and answers questions; a sales agent works a pipeline. The agent initiates outbound contact across phone, SMS, email and WhatsApp, pursues a goal (a booked, confirmed meeting), and follows up over days and weeks. The chatbot’s job ends at the conversation; the agent’s job ends at the outcome. Honest comparison: AI sales agents vs chatbots.

Can AI agents really book sales appointments automatically?

Yes — this is the most proven use case, because it plays to the machine’s strengths: instant response and unlimited persistence. The evidence on speed is one-sided: the Lead Response Management study found the odds of contacting a lead fall roughly 100x when response slips from 5 to 30 minutes, and Harvard Business Review’s audit of 2,241 companies found firms responding within an hour were nearly 7x more likely to qualify the lead. An AI agent responds in seconds, every time. On Zian, the appointment-setting agent books 40+ meetings a week for many teams — how it works: AI appointment setting.

Do AI voice agents work for real outbound sales calls?

Yes, within honest limits. In Deepgram and Opus Research’s State of Voice AI survey of 400 business leaders, 80% of organisations reported using some form of voice technology (including legacy IVR) — adoption is mainstream. Modern voice agents handle structured sales calls — qualification, booking, reminders, reactivation — well, and Zian’s speak 30+ languages with voice cloning supported. Two honest caveats: speech recognition still degrades on heavy accents and noisy lines (a PNAS study of five major commercial systems documented uneven error rates), and emotionally loaded calls should route to a human. Platform comparison: best AI voice agents for outbound calls, and AI voice agents vs call centres. For Australia-specific picks and compliance, see the best AI voice agents for sales calls in Australia.

How fast should an AI voice agent respond on a phone call?

Inside a second — and the closer to human pace, the better. Across languages, human conversation runs on average response gaps of about 200 milliseconds, with the most common gap close to zero (Stivers et al., PNAS 2009). Phone-call research finds trouble starts well before the one-second mark: listeners rate a speaker as noticeably less willing as response gaps stretch past roughly 600–800 milliseconds (Roberts & Francis 2013, JASA Express Letters). The network eats part of that budget before the AI does any thinking at all — ITU-T G.114 recommends keeping one-way transmission delay under 150 ms, with 400 ms as the outer planning limit. A production voice agent has to fit listening, reasoning and speaking into what’s left. How the full latency budget breaks down: why voice AI needs sub-second responses.

Do customers prefer being contacted in their own language?

Yes, and the preference is measured. CSA Research’s “Can’t Read, Won’t Buy” study of 8,709 consumers in 29 countries found 76% prefer to buy products with information in their native language, 40% will never buy from websites in other languages, and 75% are more likely to buy the same brand again if customer care is in their language. Zian’s agents operate in 30+ languages across phone, SMS, email and WhatsApp — how that scales: AI agents in 30+ languages.

What’s the difference between an AI phone agent and a predictive dialler?

A predictive dialler automates the dialling — it places calls in bulk and hands answered ones to human reps, with pacing tightly regulated (in the US, the FTC’s Telemarketing Sales Rule caps abandoned calls at 3% of answered calls per 30-day period). An AI phone agent holds the conversation itself — qualifying, answering objections and booking — with no human on the line. Full taxonomy: AI phone agents vs predictive diallers.

Should we use an AI SDR or human SDRs?

The strongest teams run both: AI for instant response, high-volume outreach and follow-up persistence; humans for judgement calls, complex discovery and closing. AI agents make 28x more contact attempts than typical human cadences on Zian, which is the part of the job humans reliably under-execute. The full trade-off analysis: AI SDR vs human SDR and hybrid AI + human SDR pods.

Why does follow-up pacing matter so much?

Because most deals die from silence, not rejection — and because the research above shows reachability decays in minutes while most teams take hours. Zian’s SmartReach AI™ orchestrates message, channel and timing per prospect with intelligent follow-up pacing; teams on the platform see a 926% increase in follow-ups and a 2,736% increase in lead contact rates. The mechanics: AI follow-up pacing.

Why are cold email reply rates falling?

Because AI made sending nearly free while inboxes became harder to reach. Instantly’s 2026 Cold Email Benchmark Report, drawn from billions of interactions on its own platform during 2025, puts the average reply rate at 3.43% while top performers exceed 10% — and Google’s bulk-sender rules now enforce authentication and a hard spam-rate ceiling. More volume makes it worse; tighter targeting, disciplined pacing and multi-channel orchestration are what still work. The full analysis: why reply rates fall as AI volume rises.

How fast do we need to respond to inbound leads?

Faster than almost any human team manages. Harvard Business Review’s classic lead-response study found firms contacting a lead within an hour were nearly 7x as likely to qualify it as those waiting even an hour longer — and over 60x as likely as those waiting 24 hours. Artemis GTM’s 2026 benchmark still puts average B2B response time around 42 hours, with lead-to-opportunity conversion at 21% for sub-5-minute responders versus 2.3% after a day. AI agents answer in seconds, around the clock. The full picture: speed to lead with AI agents.

What do independent 2026 AI SDR numbers actually show?

Mainstream adoption, nuanced results. Digital Applied’s 2026 compilation (citing Salesforce and Outreach) reports 41% of enterprise B2B teams now run an AI SDR in production, while its matched 100,000-email analysis shows AI reply rates of 4.1% versus 5.2% for humans. Salesmotion, citing Dashly, found human-booked meetings still show up more often (71% vs 52%). The consistent pattern across sources: hybrid teams win. Every figure, sourced and verified: the 2026 AI SDR numbers that matter.

Why are there no independent AI SDR benchmarks?

Because the ingredients of a real benchmark don’t exist in this category: there are no shared definitions of “reply rate” or “meeting booked”, vendor-published numbers are drawn from self-selected samples of the accounts that stayed, and no independent body audits anyone’s results — unlike information retrieval, where NIST’s TREC programme has provided shared test sets and pooled, judged evaluation since 1992, or ML systems, where MLCommons maintains the MLPerf benchmark suites. The practical substitute is buyer-run: agree metric definitions in writing, pilot on your own list with a holdout comparison, and verify outcomes in your own CRM and calendar rather than the vendor’s dashboard. Why the published numbers mislead, and the full evaluation playbook: why there are no trustworthy AI SDR benchmarks.

Do visitors from AI search convert better than search-engine visitors?

Yes, on every credible dataset we could verify. Ahrefs’ first-party data (June 2025) found AI-search visitors were about 0.5% of its traffic but 12.1% of signups — roughly 23x the organic conversion rate — and Similarweb’s April–May 2026 panel ranks ChatGPT referrals (~7.1% conversion) above every channel except paid search. The volume is still small; the intent is not. The full data story: do AI-search visitors convert better?

What is zero-click AI search, and can a brand still win from it?

Zero-click means the answer ends the journey: SparkToro’s 2026 analysis of Similarweb panel data found 68.01% of US Google searches ended without a click in the first four months of 2026, and Ahrefs measured all AI chatbots combined at about 0.28% of total web traffic in March 2026 — so most of the value of appearing in an AI answer is the recommendation itself, not the visit. A brand wins by being named and cited inside the answer. How to do that deliberately: zero-click AI answers.

Why does a brand appear in one AI answer and vanish from the next?

Because AI answers are drawn fresh each time, not read from a fixed list. seoClarity’s tracking found ChatGPT citation volumes fell 86–94% across five markets between February and April 2026, then rebounded in May, and Profound measured only 11.0% overlap between the domains ChatGPT and Perplexity cite for identical prompts. The practical response is breadth (many citable pages) and repeated measurement rather than one hero page and one snapshot. The full mechanics: AI answer volatility.

Which websites do AI engines actually cite most?

Citations concentrate hard on a small set of trusted surfaces. 5W’s AI Platform Citation Source Index 2026 — an aggregation of six citation studies covering 680M+ citations — puts Reddit first across every major engine (~40% frequency) and finds the top 15 domains capture about 68% of consolidated citation share, while Profound’s own data has Wikipedia at 7.8% of ChatGPT’s total citations. Peec AI’s separate 30M-source analysis independently finds Reddit the #1 or #2 most-cited source on every engine it tested. For a SaaS brand that means presence on trusted third-party surfaces matters alongside owned content. Full analysis: the few sites AI engines trust, and the Reddit playbook.

How do you measure AI referral traffic in GA4?

Mostly, you can’t by default — much AI-driven traffic arrives with no referrer or gets bucketed under generic Referral/Direct. Google’s default channel group now includes an “AI Assistants” channel (sources such as ChatGPT, Gemini, Deepseek, Copilot and Grok), but it does not include Perplexity and cannot see zero-referrer visits. The practical stack is three layers: GA4’s native channel, a custom channel group with a regex on session source, and server logs counting on-demand AI fetchers (ChatGPT-User, OAI-SearchBot, PerplexityBot) as a leading indicator. Step-by-step: how to actually measure AI-driven visits.

What is “share of model” in AI search?

Share of model is how often — and how favourably — a brand appears in AI assistants’ answers across a set of buyer prompts, measured by repeatedly running the same prompts and logging mentions, citations and recommendations. The term entered the vocabulary via Jellyfish’s trademarked Share of Model™ platform in 2024, and rank-position thinking doesn’t transfer: SE Ranking found repeat runs of the same 10,000 queries in Google’s AI Mode shared on average just 9.2% of cited URLs, so visibility is a sampled rate, not a fixed position. How to measure it, including with no tooling budget: share of model, explained.

What is entity consistency and why does it matter for AI search?

Entity consistency means keeping the facts about your brand — name, what you do, who it’s for, key claims — identical everywhere AI systems read them: your own site, directories and third-party mentions. HubSpot’s 2026 AEO trends article lists it among the year’s answer-engine-optimisation trends, warning that inconsistent facts across your site, directory listings and third-party mentions make your authority questionable and can reduce citation likelihood. Answer engines reconcile what they read about an entity before naming it in an answer, so a description that drifts from page to page is a citation handicap. How to audit and fix yours: entity consistency for AI search.

How do I structure content so AI buying agents can parse it?

Lead with the answer, then make everything extractable: an answer-first capsule near the top, question-shaped headings in a clean sequential hierarchy, tables for comparable facts, entity facts kept identical on every page, Article and FAQPage schema, and no important content locked behind client-side JavaScript — agents extract answers rather than rank pages, so a page they can’t parse is a page they can’t cite. A maintained llms.txt file helps agents find the right pages: the llms.txt proposal standardises a single /llms.txt file that provides information to help agents use a website. Every pattern, practised as it’s described: writing for agentic parsing.

Does a B2B website need an MCP server?

For most marketing sites, not yet. The Model Context Protocol is a real open standard for connecting AI applications to external systems — now governed under the Linux Foundation’s Agentic AI Foundation — but it is authenticated, developer-driven infrastructure, and AI buying agents don’t crawl the web looking for MCP endpoints on brand sites. What moves the needle for a marketing site today is schema, llms.txt and parseable answer-shaped content; pilot an MCP server if your product is an API or platform. The full assessment: does your site need MCP for AI buying agents?

How do I prepare my website for AI buying agents that browse and fill forms?

Work three fronts. Forms: standard HTML inputs with proper labels and autocomplete attributes, so an agent completing a buyer’s details can parse the fields the way a browser’s autofill does. Entry points: schema, a maintained llms.txt file and answer-shaped pages that state plainly what you sell and how to start. Bot-blocking: rethink the blanket wall — OpenAI’s bot documentation distinguishes its crawlers (GPTBot, OAI-SearchBot) from ChatGPT-User, a fetcher that is “not used for crawling the web in an automatic fashion” but visits a page when a person asks — so a CAPTCHA or bot-wall that stops everything non-human also turns away an agent acting for a real buyer. That trade-off deserves a decision, not a default. The full readiness audit: preparing your site and funnel for agentic buyers.

Should an AI agent connect to a CRM natively, through Zapier or via API?

Match the pattern to the load. Middleware such as Zapier is quick to stand up, but Zapier’s own documentation puts polling intervals at 1 to 15 minutes depending on plan — fine for prototyping, too slow for an agent that needs mid-call CRM lookups. Native connectors handle standard objects well; direct API integrations (webhook-driven) are what real-time write-back and custom objects usually demand. Autonomous agents stress integrations harder than form-fill tools because every conversation writes activity history, and a failed write-back corrupts follow-up pacing. Decision framework: native vs Zapier vs API.

Trust, compliance and deployment

Is AI cold calling legal?

Yes, where it follows the same rules as human calling — the AI gets no exemption. In Australia that means ACMA’s telemarketing rules (permitted hours, caller identification, honouring opt-outs) and the Do Not Call Register; in the US, the TCPA imposes stricter consent requirements for automated calls. Reputable operators announce recording up front and act on every opt-out immediately. Build compliance into the agent’s rules, not the rep’s memory.

Do we need to register our SMS sender ID in Australia?

If you send SMS under a brand name, yes. From 1 July 2026, ACMA’s SMS Sender ID Register requires branded (alphanumeric) sender IDs to be registered, and SMS sent using unregistered sender IDs are now being labelled “Unverified” by carriers — a credibility hit no legitimate outreach programme wants. Any AI outreach that texts under your brand should be registered before its next campaign. Australian channel picks: best AI voice agents for sales calls in Australia. The registration steps, timeline and what the register means for AI-driven SMS outreach: Australia’s SMS Sender ID Register, explained.

Do we have to tell people they’re talking to an AI?

Increasingly, yes. In the US, the FCC ruled in February 2024 that AI-generated voices in robocalls count as “artificial” voices under the TCPA, which means prior express consent rules apply. In the EU, Article 50 of the AI Act requires telling people they are interacting with an AI system unless it is obvious, with general application from 2 August 2026. Beyond the law, upfront disclosure measurably protects trust. Jurisdiction by jurisdiction: outreach compliance for AI agents.

Does US law require disclosing that a sales call uses AI?

Not yet as a stand-alone duty — but AI voice calls are already regulated today. The FCC’s February 2024 declaratory ruling means AI-generated and cloned voices count as “artificial” voices under the TCPA, so the existing rules — prior express consent and caller identification — apply to AI sales calls right now. A dedicated duty to disclose that a call uses AI is, as of August 2026, only proposed: the FCC adopted NPRM 24-84 in August 2024, which would require disclosure at the start of a call, but the rule has not been finalised. What’s in force versus what’s still pending: FCC NPRM 24-84 and AI call disclosure, explained.

Does Colorado require telling consumers they’re talking to an AI?

Not under its AI Act. The original Colorado AI Act’s AI-interaction disclosure duty (SB 24-205) never took effect — the law was repealed and re-enacted on 14 May 2026 as SB 26-189, a narrower automated-decision-making framework effective 1 January 2027 with no general AI-interaction disclosure duty. A separate Chatbot Safety Act (HB 26-1263) does require operators of publicly available conversational AI services to maintain a protocol informing users they’re interacting with AI, with operator duties from 1 January 2027; the Attorney General’s proposed rules (filed 11 August 2026) are expected to sharpen its scope. What survived, what didn’t and what sales teams should do: Colorado’s rewritten AI Act.

Is it legal to use a cloned voice on business calls?

Yes, with layered consent — and unconsented cloned-voice robocalling is unlawful. The FCC’s February 2024 declaratory ruling confirmed AI-generated and cloned voices count as “artificial or prerecorded voice” under the TCPA, so US calls need prior express consent (written consent for telemarketing), caller identification and opt-out. In Australia, voice calls fall under the Do Not Call Register Act 2006 and the telemarketing Industry Standard rather than the Spam Act. You also need the voice owner’s licence to clone their voice. Full breakdown: voice cloning for business calls.

When do Australia’s automated decision-making disclosure rules start?

From 10 December 2026, organisations covered by the Privacy Act must state in their privacy policy the kinds of personal information used in — and the kinds of decisions made using — automated decision-making that could significantly affect individuals’ rights or interests, under the Privacy and Other Legislation Amendment Act 2024. It is a disclosure duty, not a prohibition; the OAIC ran a consultation in May–June 2026 and states it intends to release final guidance by September 2026. Step-by-step preparation: writing an ADM transparency statement; the broader picture: AI agent data sovereignty in Australia.

What happens when an AI agent says something wrong?

Plan for it contractually and technically — the liability is established: in Moffatt v Air Canada (2024), a Canadian tribunal held the airline liable for a policy its chatbot invented. The mitigations: hard boundaries (agents never invent pricing or terms), instant human handoff on sensitive conversations, and complete conversation logs so every interaction is auditable.

Do autonomous sales agents need a human approving every message?

No — but they need defined gates. The 2026 operating consensus is human-in-the-loop: agents run routine outreach autonomously inside written guardrails and escalate to a person when confidence drops or stakes rise (pricing, legal terms, sensitive accounts). Article 14 of the EU AI Act requires that high-risk AI systems be designed for effective human oversight — sales outreach generally isn’t classed high-risk, but the same architecture (override authority, escalation, audit logs) is what buyers now expect. The full playbook: human-in-the-loop controls for autonomous sales agents; the when-to-escalate mechanics: confidence thresholds.

What guardrails should an autonomous AI sales agent have?

Three layers at minimum: written permissions and prohibitions (what the agent may do, and what it must never do — invent pricing, make legal claims, contact opted-out prospects), explicit escalation triggers that hand the conversation to a human, and an audit trail recording every action the agent takes. On the engineering side, OWASP’s guidance on Excessive Agency says what security teams have always said: grant the agent the least privilege its task needs, and require human approval for high-impact actions. Australia’s Voluntary AI Safety Standard makes meaningful human oversight Guardrail 5. How to write each layer, with worked examples: how to write guardrails for autonomous AI agents.

What observability should an AI agent platform expose?

Three layers: reasoning or decision traces (why the agent chose an action), tool-use and action logs (what it actually did — calls, messages, CRM writes), and outcome attribution (which conversations produced booked meetings or revenue). Add conversation transcripts and guardrail-trigger logs and you have both a debugging surface and audit evidence. OpenTelemetry’s generative-AI semantic conventions — still marked “Development” — are emerging as the vendor-neutral way to capture agent traces. The full buyer’s checklist: AI agent observability.

Can a prospect trick an AI sales agent with prompt injection?

It’s a real risk class. Sales agents read untrusted input all day — email replies, live speech, web pages — and OWASP ranks prompt injection the #1 risk for LLM applications. The UK National Cyber Security Centre cautions the problem may never be totally mitigated, so ask vendors about layered defences — least-privilege tool access, human approval gates for sensitive actions, input and output filtering, and logging — rather than accepting claims it has been solved. The buyer’s question list: prompt injection and the OWASP risks.

When should an AI sales agent escalate to a human?

When the cost of a wrong action outweighs the cost of a pause — not simply when a confidence score dips. Production teams combine signals: an explicit request for a person, sentiment degradation, out-of-scope or compliance-sensitive topics, and actions that are hard to reverse. Australia’s Voluntary AI Safety Standard makes “enable human control or intervention in an AI system to achieve meaningful human oversight” one of its ten guardrails. Escalation design in full: confidence thresholds for AI sales agents.

Can Zian’s agents run on our own infrastructure?

Yes — Zian supports private model deployment on customer infrastructure for organisations that can’t send conversation data to shared clouds (banking, government, healthcare-adjacent). Integrations cover HubSpot, Salesforce, HighLevel and Zapier either way. Details: private AI deployment for sales agents.

Does this only work for sales teams?

No — the same agent architecture runs beyond sales. Zian’s digital team includes a 24/7 multilingual customer support agent (30+ languages), plus niched agents for recruitment screening, government and council surveys, university admissions, construction project coordination, IT support and bank KYC onboarding.

What integrations does Zian support?

Native CRM integrations for HubSpot, Salesforce and HighLevel, plus Zapier and a full API for everything else — agents read and write to your existing pipeline rather than creating a parallel one. The full matrix: features and integrations; setup patterns and what to sync: CRM integrations for AI agents.

What can the agents actually do on a call or in a conversation?

Live phone, SMS, email and WhatsApp outreach in 30+ languages (voice cloning supported), with the ability to research prospects and query the web and your knowledge base mid-conversation — so answers come from your data, not generic patter. Capabilities in detail: features and integrations.

How long has the technology behind Zian been around?

The platform’s conversational-AI lineage runs back to 2018, through multi-channel expansion, private enterprise deployments and a select enterprise rollout in 2025 — this is a productisation of years of deployed agent work, not a wrapper built last quarter. The history, year by year: 2018 foundation and 2025 enterprise rollout.

Is there a free plan?

Yes — the Intel + Widgets tier is free forever, and paid tiers scale up from there. During the current beta, access to all tiers is gated through the partner application.

Did the EU AI Act’s high-risk obligations start on 2 August 2026?

No. Regulation (EU) 2026/1744 (the Digital Omnibus on AI), published in the Official Journal on 24 July 2026, deferred the Annex III high-risk obligations to 2 December 2027 and Annex I product-embedded obligations to 2 August 2028. What did apply from 2 August 2026 is the Article 50 transparency duty — people interacting with an AI system must be told it’s AI unless that’s obvious — alongside the earlier prohibitions and GPAI rules. Full breakdown: what actually applies under the EU AI Act as of August 2026.

What does Article 50 of the EU AI Act require from AI sales and support teams?

Two duties, both applying from 2 August 2026: people interacting with an AI system must be told it’s AI unless that’s obvious, and AI-generated (synthetic) content must be marked in a machine-readable format and detectable as artificially generated. The European Commission’s Article 50 FAQ says the unless-obvious exception is to be interpreted restrictively — the test is whether an average person, reasonably well-informed and observant, would realise they’re talking to AI — so a convincing voice or chat agent should disclose rather than rely on it. The recent deferral didn’t touch this duty: Regulation (EU) 2026/1744 pushed the Annex III high-risk obligations to 2 December 2027, but Article 50 transparency applies now. The team-by-team checklist: the Article 50 compliance checklist.

What are the Gmail and Outlook bulk-sender rules for outbound email?

Since February 2024, Google’s email sender guidelines require senders of around 5,000+ daily messages to Gmail to authenticate with SPF, DKIM and DMARC, offer one-click unsubscribe, and keep spam-complaint rates below 0.3% (Google recommends under 0.1%) — with enforcement ramping up from November 2025. Microsoft applied matching authentication requirements to outlook.com, hotmail.com and live.com from May 2025, rejecting mail that fails them with error 550 5.7.515. The rules and an AI-outbound checklist: the 2026 bulk-sender crackdown.

What should an AI-to-human handoff include?

A handoff packet, not a transcript dump: who the prospect is, consent and disclosure state, a short conversation summary, objections already raised, and the next-step commitment — written back to the CRM so the human picks up where the AI left off. Zendesk’s 2026 CX Trends research (11,000+ respondents, 22 countries) found 74% of consumers get frustrated when they have to repeat information. Design guide: the AI-to-human handoff.

Do AI sales agents have to say they’re AI on a phone call?

In many places, yes — and the list is growing. In the US, the FCC’s February 2024 declaratory ruling treats AI-generated voices as “artificial voice” calls under the TCPA (consent and identification duties apply), and NPRM 24-84 — which would require explicit AI disclosure at the start of a call — remains a proposal as of August 2026. State law adds more: Maine’s 10 M.R.S. §1500-DD requires clear and conspicuous notification when an AI chatbot could mislead a consumer into thinking it’s human, Utah requires disclosure on request (proactively in regulated high-risk interactions), and California’s PUC §2874 covers artificial-voice announcements. In the EU, Article 50 of the AI Act applies from 2 August 2026. Scripts and a full jurisdiction table: AI-call disclosure scripts.

What hours can an AI agent make telemarketing calls in Australia?

The same hours as any telemarketer: under the Telemarketing and Research Calls Industry Standard, ACMA’s permitted hours for telemarketing calls are 9:00am–8:00pm weekdays and 9:00am–5:00pm Saturdays, with no calls on Sundays or national public holidays (research calls have slightly wider windows). Calling line identification must be enabled, and numbers must be washed against the Do Not Call Register. The full picture — number types, CLI rules and caller-ID reputation — is in our guide to getting an Australian number for your AI voice agent.

What is STIR/SHAKEN and does Australia use it?

STIR/SHAKEN is the US caller-ID authentication framework: the originating voice provider cryptographically signs each call with an A, B or C attestation level asserting how confident it is in the caller’s right to the number, and the terminating provider verifies the signature before the phone rings. Australia has no STIR/SHAKEN mandate — instead, ACMA has registered the C661:2022 Reducing Scam Calls and Scam SMs industry code, which requires telcos to identify, trace and block scam calls and SMS. For AI voice agents the practical advice is the same in both countries: call from numbers you control, ask your carrier how your calls are attested, and treat number reputation as an asset. The full comparison: STIR/SHAKEN and what Australia has instead.

What is branded calling (Rich Call Data) and does it work in Australia?

Branded calling puts your business name, logo and call reason on the recipient’s screen — technically, Rich Call Data (RCD) carried with the call and tied to its STIR/SHAKEN attestation, standardised in RFC 9795 and RFC 9796 (July 2025). The US has a live ecosystem: CTIA’s Branded Calling ID programme delivers vetted name, logo and call reason over cryptographically signed calls. Australia has neither STIR/SHAKEN nor an RCD ecosystem — caller-ID trust rests on the C661:2022 Reducing Scam Calls and Scam SMs industry code, which requires telcos to identify, trace and block scam traffic — so for Australian AI voice campaigns the practical play is number hygiene: consistent caller line identification, numbers you control and a reputation you protect. What exists, what’s marketing and what to do in each country: branded calling for AI voice agents.

What should an enterprise check before buying an AI sales agent platform?

Four tiers: identity and access (SAML SSO, SCIM provisioning, role-based access control), data protection (encryption, contractual data residency, sub-processor transparency), governance (immutable audit logs, third-party attestations — a SOC 2 report is an AICPA-defined examination of a service organisation’s controls, so ask for the report and its scope rather than the badge), and operational maturity (SLAs, incident history, observability of what the agent actually did). Private model deployment on your own infrastructure is an architectural alternative to certificate-led assurance. The line-by-line version with vendor questions: the enterprise readiness checklist.

Using Zian

What results do teams see on Zian?

The platform counters, straight from live usage: 50,769+ qualified sales appointments set, a 926% increase in follow-ups, 28x more contact attempts, a 2,736% increase in lead contact rates and 3,102% more sales appointments. Results vary by list quality, offer and market — which is why the platform split-tests continuously: PrecisionPitch AI™ tests scripts and approaches against real outcomes, not opens. See AI sales script split-testing.

How do we choose between the AI sales platforms out there?

Evaluate on four axes: autonomy (does it decide, or just fire sequences?), channel depth (real phone calls or just email?), outcome optimisation (does it learn from booked meetings or from opens?), and deployment control. Our honest read of the field, criteria first: best AI sales agent platforms in 2026.

Which US states require an AI voice agent to tell people it is AI?

There is no single US rule — it is a state patchwork, and much of what circulates online is wrong. Utah is currently the strictest live duty: Utah Code §13-77-103 requires a supplier using generative AI to disclose that fact when a person clearly and unambiguously asks, and it covers audio explicitly. Maine (10 M.R.S. §1500-DD) reaches aural communications too, while California’s BOT Act applies to online interactions rather than phone calls. Texas SB 140 is widely and wrongly described as an AI-disclosure law — it is a telemarketing statute that says nothing about AI. Our verified state-by-state map: the US state AI call-disclosure patchwork.

Does a lead vendor’s “TCPA-compliant” badge protect me if I call the list with an AI agent?

No. Under the TCPA the burden of proving prior express consent sits with the caller, not the list seller — the FCC stated this directly at paragraph 33 of its 2012 TCPA Order (FCC 12-21). A vendor’s badge is a commercial assurance, not a legal defence, and it does not put the capture record in your hands. Because the FCC has ruled that AI-generated voices are “artificial” under the TCPA, an AI voice agent needs consent for every call regardless of content. What a defensible consent chain has to contain: purchased lead lists and the TCPA consent chain.

What happens when a consumer’s AI assistant phones my business?

It is already happening. Google operates a service that places automated calls to businesses on a customer’s behalf to ask about pricing, availability and bookings, and Google publishes the opener those calls use — they identify themselves as an automated service and state that the call is recorded (Google Business Profile Help), along with routes for a business to opt out. The practical consequence is that your phone line now has machine callers as well as human ones, and deep IVR menus and hold queues serve them badly. Our readiness guide: preparing your phone lines for inbound AI callers.

Can we use a published AI-visibility benchmark rate as our target?

Not safely. Published AEO/GEO benchmarks measure a non-deterministic system, and almost none disclose the things that would make their number comparable to yours: the prompt list, samples per prompt, the exact date window, the named engines and modes, the locale, and what they actually counted as a “citation”. Conductor’s 2026 AEO/GEO Benchmarks Report, for example, states plainly that its figures are US-only averages, and it does not publish its prompt set. Treat published averages as direction and track your own trend instead: how to read a 2026 AEO benchmark report.

How do we get access to Zian?

Zian is currently in an invite-only beta. Apply for partnership and you’ll be onboarded as capacity opens — early access prioritises teams with an existing lead flow or database to work.

Last updated: 18 August 2026. Answers on this page are refreshed as the underlying studies and regulations change.

Related Blogs

Related from Zian AI