Quick answer: An AI voice agent can answer and place WhatsApp calls through Meta’s Cloud API Calling. In production you need a messaging limit of at least 2,000 unique recipients a day; outbound calls also need the user’s permission and a business number outside the US, Canada, Egypt, Vietnam and Nigeria. From 1 October 2026, the post-call utility message costs A$0.0148 in Australia.
Every Meta figure below is from Meta’s own WhatsApp Business Platform documentation, read on 24 September 2026. The pieces you join are Meta’s Graph API and webhooks (or SIP over TLS) for signalling, WebRTC with the Opus codec (or SDES-SRTP, or G.711 PCMA/PCMU) for media, an agent runtime such as LiveKit or Pipecat, and, in Australia, the Spam Act 2003 as the ACMA explains it. From 1 October 2026 Meta charges for utility messages sent inside the 24-hour customer service window, which changes what the message after a call costs.
Can an AI voice agent answer WhatsApp calls?
Yes. Meta’s calling FAQ answers the question directly: “Yes. Meta only provides the raw media stream and how it is processed is entirely flexible. Many businesses use automated voicebots including AI bots to answer calls from WhatsApp users.” It then points to the WhatsApp Business Solution Terms for restrictions on AI use cases.
Those restrictions are clause 4.7 of the Terms (last modified 23 September 2026). “AI Providers”, meaning providers and developers of artificial intelligence or machine learning technologies, including but not limited to large language models, generative AI platforms and general-purpose AI assistants, as determined by Meta in its sole discretion, are “strictly prohibited from accessing or using the WhatsApp Business Platform, whether directly or indirectly, for the purposes of providing, delivering, offering, selling, or otherwise making available such technologies when such technologies are the primary (rather than incidental or ancillary) functionality being made available for use, as determined by Meta in its sole discretion”, except in certain countries Meta lists. Two further limbs matter to a voice-agent builder: “you may retain an AI Provider as your Solution Provider”, and if you do, WhatsApp Business Platform Data, including anonymous, aggregate or derived forms of it, may not be used to create, develop, train or improve AI models, except to fine-tune a model for your exclusive use that improves no other model.
Where your deployment sits is Meta’s call, not your vendor’s, so read clause 4.7 in full before you build.
How to set up the WhatsApp Calling API for an AI voice agent
This is the order Meta’s prerequisites force on you. Step 1 decides whether the rest is worth doing.
- Day one: check the two gates no code can get around. Business-initiated calling is available everywhere Cloud API is except the United States, Canada, Egypt, Vietnam and Nigeria, and Meta’s note is explicit: “The business phone number’s country code must be in this supported list.” The person you call can be in any Cloud API country; a +61 business number is not excluded. Then check your messaging limit in WhatsApp Manager: Meta requires “a daily messaging limit of at least 2,000 unique recipients”. If either gate fails you can still build and test (step 6), but not go live.
- Put the number on Cloud API and wire the app. The number must be on Cloud API, not the WhatsApp Business app. Subscribe your app to the
callswebhook field (unless you use SIP), keep the same app subscribed to the number’s Messaging account, and confirm it holdswhatsapp_business_messaging. Meta recommends reusing your messaging app rather than creating a calling-only one. - Enable calling and set the call settings: inbound call control, business call hours, callback requests, and optionally voicemail, call-icon countries and
additional_codecsfor G.711. - Choose the signalling and media path from the table below. For most AI voice agents the default fits: Graph API and webhooks, WebRTC with Opus.
- Connect the agent runtime. The call connect webhook carries an SDP offer (inbound) or SDP answer (outbound). Meta lists five mandatory media rules, and breaking any one fails the call: supported codecs only, a 48 kHz clock rate for Opus, a 20 ms ptime for Opus, a single audio SSRC, and a DTMF clock rate of 8 kHz. It also recommends ICE-FULL on your side against its ICE-LITE stack, acting as the DTLS client, and never waiting for WhatsApp to send the first RTP packet, which can deadlock both sides.
- Test on a public test number, issued after the Get Started flow. Calling is off by default on test numbers, the 2,000-recipient rule does not apply, and call limits are relaxed (see the limits table). Sandbox accounts are for Tech Partners only.
- Build the permission flow for outbound calls. A call without permission returns error 138006. Meta offers three ways to get permission: send a call permission request (free-form inside an open customer service window, or as a template); enable
callback_permission_statusso a user who calls you grants it automatically; or let the user grant it from your business profile. Permission is temporary (7 days) or permanent, and only the user can grant or revoke it. Then place the call withPOST <PHONE_NUMBER_ID>/calls. - Send the follow-up and check its price. A user accepting your call opens or refreshes the 24-hour customer service window. For a utility message inside it, the status webhook’s
pricingobject shows"billable": falseand"type": "free_customer_service"through 30 September 2026, and"billable": trueand"type": "regular"from 1 October 2026.
You are finished when a call from your public test number gets two-way audio with the agent, a permissioned business-initiated call returns an ACCEPTED status webhook, and the follow-up’s webhook shows the billable and type values expected for that date.
Which media path should my AI agent use: WebRTC, SIP or SDES?
Meta documents exactly three signalling and media configurations. All three use Opus as the audio codec, and the two SIP options need Meta to enable them explicitly.
| Default after enabling calling | SIP with WebRTC | SIP with SDES media | |
|---|---|---|---|
| Signalling protocol | Graph API + webhooks | SIP (needs explicit enablement) | SIP (needs explicit enablement) |
| Signalling transport | HTTPS | TLS | TLS |
| Media protocol | WebRTC (ICE + DTLS + SRTP) | WebRTC (ICE + DTLS + SRTP) | SDES SRTP (needs explicit enablement) |
| Audio codec | Opus | Opus | Opus |
| Fits best when | Your agent runtime already speaks WebRTC (LiveKit, Pipecat SmallWebRTC) | You run a SIP server with TLS and digest auth and want SIP call control | Your SIP stack handles SRTP keyed by SDES but not ICE and DTLS |
Meta’s notes add that SDES can replace ICE and DTLS under Graph API signalling too, and that PCMA and PCMU (G.711) are supported as additional codecs. The call-settings page warns that G.711 means transcoding against Opus on the user’s side, “which can add latency to the call”, at about 64 kbps per direction. For a voice agent, where every millisecond sits inside the turn, keep Opus end to end.
On SIP, TLS is mandatory and your certificate’s subject name must cover the SIP domain configured on the number; Meta’s own domain is wa.meta.vc. A business-initiated INVITE is answered with 407 and resent with digest credentials, using the password Meta generates per number and app. Do not send REGISTER (it fails with 403), and note that enabling SIP switches off the calling Graph API endpoints for that number. Meta’s certificate check, which we ran on 24 September 2026 against a valid host, a deliberately wrong hostname and a plain-HTTP port, is:
openssl s_client -quiet -verify_hostname {hostname} -connect {hostname}:{port}
A good certificate prints only verify return:1 lines, one per depth. A wrong name adds verify error:num=62:hostname mismatch at depth 0, and the verify return:1 lines still follow it, so check for the error line rather than counting return lines. And a port not speaking TLS ends in an SSL routines error (ours read “wrong version number”, Meta’s example “unexpected eof”). Pointing an agent straight at a SIP endpoint is covered in our guide to a direct SIP AI voice agent with no Twilio in the path.
One rule overrides the design. Meta’s integration-patterns page says: “Our terms disallow use of PSTN on any leg of the WhatsApp call in the overall call flow”, adding that “SIP trunk by itself is not disallowed because technically a SIP trunk can be used without any PSTN at all.” So handing a WhatsApp call to a human on a mobile number is out. The call-settings page, though, gives G.711’s main use as interoperability with “legacy telephony infrastructure and PSTN gateways that do not support Opus”. When two Meta pages read differently, get the answer in writing from Meta or your Solution Partner before bridging to a phone network.
The WhatsApp calling limits, in one table
These are the numbers an outbound agent has to be built around, from Meta’s call-permission, business-initiated-calls, call-settings and FAQ pages.
| Limit | Production number | Public test number or sandbox |
|---|---|---|
| Messaging limit required before calling works | At least 2,000 unique recipients a day | Not required |
| Call permission requests to one user | 1 in 24 hours, 2 in 7 days | 25 a day, 100 a week |
| What resets the request limits | Any connected call (business- or user-initiated) between you and that user | Not stated |
| Temporary permission lasts | 7 calendar days (168 hours) from approval | Not stated |
| Connected calls to one user | 100 every 24 hours (temporary or permanent permission) | Relaxed (no figure published) |
| Consecutive unanswered or rejected calls before a system message asks the user to reconsider | 2 | 5 |
| Consecutive unanswered or rejected calls before permission is revoked automatically | 4 | 10 |
| New calls initiated per business number | 10,000 per 24 hours | Not stated |
| Concurrent calls a number can receive | 5,000 | Not stated |
| High negative feedback (blocks, reports) | Business-initiated calling, user-initiated calling or both paused for 7 days | Not stated |
| Too many inbound calls not picked up | Email warning, then the call button is hidden from users | Not stated |
| Maximum call duration | No limit | No limit |
Two rows shape an AI agent’s design. The 4-strike revocation means counting unanswered calls per user and stopping at three, because the fourth loses the permission. The 2-in-7-days cap means a user who ignores two requests cannot be asked again that week, unless a connected call resets it. An agent that retries on a fixed timer burns through both. The 100-calls row rarely binds; Meta’s changelog shows it rising from 5 to 10 a day on 13 October 2025 and to 100 on 19 December 2025.
Where LiveKit and Pipecat stand on WhatsApp calling
LiveKit and Pipecat, two open-source voice-agent frameworks with public WhatsApp calling feature requests, both document a WhatsApp route on their own sites as at 24 September 2026.
| Framework | What its own docs describe | Where it runs | Open request on GitHub |
|---|---|---|---|
| LiveKit | A WhatsApp Connector that brings WhatsApp calls into a LiveKit room, with outbound (DialWhatsAppCall) and inbound flows; works with WhatsApp Cloud API v23.0, v24.0, v25.0 or v26.0 |
“Connectors are available in LiveKit Cloud only”; self-hosted LiveKit servers are not supported, but agents can run anywhere | livekit/agents #3375, “Whatsapp calling API support”, opened 8 September 2025, still open |
| Pipecat | A WhatsApp Business Calling guide and a WhatsAppTransport that let a Pipecat bot receive WhatsApp voice calls, built on SmallWebRTCTransport |
Pipecat applications and Pipecat Cloud (separate guide) | pipecat-ai/pipecat #2811, “Option to Initiate Outbound Whatsapp Business Call”, opened 8 October 2025, still open |
The LiveKit issue is the original feature request and stays open. A related one, livekit/sip #281, “Support Opus on SIP Trunks”, closed on 24 September 2026; we have not checked which release carries it, so read LiveKit’s SIP release notes before relying on it. On the Pipecat issue, a maintainer wrote on 20 March 2026 that outbound is a lower priority because business-initiated calling is restricted in the US, where most of the team is, and that they are “open to a community contribution for this”.
What does the follow-up message cost after a WhatsApp AI call?
We call this the 1 October follow-up flip: the confirmation or summary an agent sends straight after a call is free until 30 September 2026 and charged from 1 October 2026, unless it goes as a free-form reply within the free tier.
The rules, from three Meta pages: user-initiated calls are free. Business-initiated calls are billed in six-second pulses, by the country code called and by monthly volume tier, and a part pulse counts as whole, so a 56-second call is 9.33 pulses billed as 10. A user accepting your call opens or refreshes the 24-hour customer service window. Utility templates inside that window are free until 30 September 2026 and charged at the utility rate from 1 October. On the same date, service messages (free-form replies, which Meta says can be powered by a person “or by a 3rd-party AI solution”) become charged at the utility rate, after a free tier of 1,000 a month per business number, shared by all 1:1 and group service replies, with no roll-over.
The worked example. An Australian business on a +61 number places 500 business-initiated calls a month to Australian WhatsApp users, all connected, each 170 seconds, with one follow-up per call inside the window. Australia is billed at Meta’s “Rest of Asia Pacific” rate, and 500 calls sits well inside the list-rate tiers (up to 50,000 call minutes and 150,000 utility messages), so all figures are AUD list rates.
- Pulses per call: 170 ÷ 6 = 28.33, billed as 29. Per pulse: A$0.0148 a minute ÷ 10 = A$0.00148 (Meta publishes a per-minute rate and bills in six-second pulses; dividing by ten is our reading of how they combine).
- Per call: 29 × A$0.00148 = A$0.04292. Per month: 500 × A$0.04292 = A$21.46 for 1,450 billed minutes, against A$20.97 if billed by the second.
- Follow-ups: 500 × A$0.0148 = A$7.40 for utility; 500 × A$0.0952 = A$47.60 for marketing through 30 September, and 500 × A$0.1095 = A$54.75 from 1 October, when that rate rises.
| Monthly line, 500 connected calls of 170 s to +61 users | Through 30 Sep 2026 | From 1 Oct 2026 |
|---|---|---|
| Call minutes (29 pulses × A$0.00148 × 500) | A$21.46 | A$21.46 |
| Follow-up as a utility template, inside the 24-hour window | A$0.00 | A$7.40 |
| Follow-up as a free-form (service) reply, inside the window, within the number’s 1,000 free service messages that month | A$0.00 | A$0.00 |
| Same free-form reply once the number’s 1,000 free service messages are used up | A$0.00 | A$7.40 |
| Follow-up as a utility template, sent after the window has closed | A$7.40 | A$7.40 |
| Follow-up as a marketing template | A$47.60 | A$54.75 |
| Total, calls + utility follow-up inside the window | A$21.46 (A$0.04292 a call) | A$28.86 (A$0.05772 a call) |
From the table: the utility follow-up adds about 34% to this call bill from 1 October (A$7.40 on A$21.46). A free-form reply is the one follow-up that stays free, but only while the whole number, every other chat reply included, stays under 1,000 service messages that month. A marketing template costs more than the calls: A$54.75 against A$21.46. None of these lines includes the permission requests, each of which is a message billed as a free-form reply or at its template category (Meta’s example is created as MARKETING or UTILITY).
Two dates matter. Without a payment method by 30 September 2026, Meta delivers service messages only within the free tier from 1 October, and calls already need one. And Meta changes rates only on the first day of a quarter, so the next possible move after 1 October is 1 January 2027. The rate cards say nothing about GST; check your first invoice. The SMS side has its own fee stack in the US, set out in our breakdown of A2P 10DLC costs for two-way AI SMS agents.
Australian rules for the WhatsApp message after the call
The Spam Act 2003 regulates commercial electronic messages. Section 5(1) defines an electronic message as one sent using an internet carriage service or another listed carriage service to an electronic address in connection with an email account, an instant messaging account, a telephone account or a similar account, which covers a WhatsApp message. Section 5(5) excludes a message “sent by way of a voice call made using a standard telephone service”; whether a WhatsApp VoIP call is one is a question for your legal adviser, not this page. Telemarketing calls are a separate regime, covered in our guide to Do Not Call Register rules for AI voice agents.
The ACMA’s guidance says you need consent first, and the message must identify you, give your contact details and offer an unsubscribe that has clear instructions, is honoured within 5 working days, costs nothing beyond the usual cost of replying, works for at least 30 days, and needs no login, account or extra personal information. One line matters for WhatsApp calling: “You cannot send an electronic message to ask for consent, because this is a marketing message.” A cold call permission request template to a stranger sits uncomfortably close to that. The ACMA recognises express and inferred consent, and says inferred consent (from an existing relationship the marketing directly relates to) is not as reliable as express consent. The cleaner pattern is express consent first, by one of the four routes the ACMA lists (a form, a tick-box, over the phone, face to face), with a record of who consented, when and how, because under the Act the proof is on you.
Should I build WhatsApp calling myself or hand it over?
The do-it-yourself cost is not Meta’s rates (A$28.86 a month in the example above). It is the state your system keeps: per-user permission status and 7-day expiry, the request counters and what resets them, an unanswered-call counter that stops at three, a service-window clock per user, template approvals, restriction webhooks, a payment method on every Messaging account, and a media server meeting Meta’s five mandatory rules. Each breaks quietly, usually as a user you can no longer call.
| Your situation | What the numbers say | Sensible route |
|---|---|---|
| Business number registered in the US, Canada, Egypt, Vietnam or Nigeria | Business-initiated calling is not available for these business numbers | Build inbound only, or register a number in a supported country |
| Messaging limit below 2,000 unique recipients a day | Production calling will not enable | Grow the messaging tier first; build against a public test number meanwhile |
| You already run a WebRTC voice agent on LiveKit Cloud or Pipecat | Adding WhatsApp is a transport, a webhook handler and the permission state above | Build it yourself |
| Inbound calls only | User-initiated calls are free; no permission logic needed | Build it yourself |
| Outbound across WhatsApp, phone, SMS and email, with follow-up pacing | Four channels, each with its own consent, cadence and cost rules, including the WhatsApp limits in the table above | Consider a platform that already orchestrates channels |
That last row is where Zian works. Zian AI lists live phone, SMS, email and WhatsApp outreach among its agent channels, with SmartReach AI™ deciding the message, channel and timing and pacing follow-up, and a learning engine that tracks around 420,000 data points across more than 10,000 leads a day. This page does not claim Zian places calls through the WhatsApp Calling API; what it describes is Meta’s API, and the arithmetic holds whoever runs it. How the call, the WhatsApp follow-up and any SMS or email are sequenced is covered in our multi-channel outreach orchestration playbook. Zian is in partnership-application beta.
Frequently asked questions
Can an AI voice agent answer WhatsApp calls?
Yes. The Meta calling FAQ says Meta only provides the raw media stream, that how it is processed is entirely flexible, and that many businesses use AI bots to answer WhatsApp calls. Clause 4.7 of the WhatsApp Business Solution Terms restricts AI Providers and, where an AI Provider is your Solution Provider, the use of WhatsApp data to train AI models, so read it first. Source: Meta WhatsApp Calling FAQ.
Can my business call customers on WhatsApp from Australia?
Yes, if the user has given you permission. Business-initiated calling is available wherever Cloud API is available except for business numbers in the United States, Canada, Egypt, Vietnam and Nigeria, and a +61 number is not on that list. Your number also needs a daily messaging limit of at least 2,000 unique recipients. See the availability section of the Meta Cloud API Calling overview.
How many times can a business call the same WhatsApp user?
Up to 100 connected calls every 24 hours per business and user pair. The tighter limits are on asking: 1 call permission request in 24 hours and 2 in 7 days. After 2 consecutive unanswered or rejected calls the user sees a prompt to reconsider, and after 4 the permission is revoked automatically. Details are in the Meta guide to obtaining user call permissions.
How much does a WhatsApp business call cost in Australia?
User-initiated calls are free. Business-initiated calls to Australian numbers are A$0.0148 a minute for the first 50,000 minutes a month, the Rest of Asia Pacific rate on the Meta AUD cards effective 1 July and 1 October 2026, measured in six-second pulses. See the Meta Calling API pricing page.
Is the WhatsApp message after a call free?
Until 30 September 2026, a utility template sent inside the 24-hour customer service window is free. From 1 October 2026 it is charged at the utility rate, A$0.0148 per message to Australian users. A free-form reply inside the window becomes a charged service message on the same date, but each business number gets 1,000 free service messages a month. The rules are on the Meta WhatsApp pricing page.
Can I connect WhatsApp calls to my existing SIP server?
Yes, with SIP over TLS and digest authentication against the Meta SIP domain wa.meta.vc, once Meta enables SIP on the number. The Meta integration patterns page says its terms disallow PSTN on any leg of a WhatsApp call, though a SIP trunk that never touches the PSTN is allowed. See the Meta SIP configuration guide.
Does LiveKit or Pipecat support WhatsApp calling?
Both document a route as at 24 September 2026. The LiveKit WhatsApp Connector handles inbound and outbound calls in LiveKit Cloud only; the Pipecat WhatsAppTransport receives calls, and outbound is open feature request 2811. See the LiveKit WhatsApp Connector docs and the Pipecat WhatsApp guide.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| Business-initiated calling excluded for US, Canada, Egypt, Vietnam and Nigeria business numbers; 2,000 unique-recipient messaging limit; three signalling and media configurations; Opus default, PCMA and PCMU additional; sandbox limits 25 a day and 100 a week, 5 and 10 unanswered; sandbox for Tech Partners only; changelog dates for 5 to 10 (13 Oct 2025) and 10 to 100 (19 Dec 2025) calls a day | Meta, Cloud API Calling overview (updated 26 Jun 2026) | developers.facebook.com | 24 Sep 2026 |
| 100 connected calls every 24 hours; 1 request in 24 hours and 2 in 7 days; 7-day (168-hour) temporary permission; 2 and 4 consecutive unanswered calls; three ways to obtain permission; template category MARKETING or UTILITY | Meta, Obtain user call permissions (updated 26 Jun 2026) | developers.facebook.com | 24 Sep 2026 |
| 10,000 new calls per 24 hours per business number; error 138006 | Meta, Business-Initiated Calls (updated 26 Jun 2026) | developers.facebook.com | 24 Sep 2026 |
| 7-day pause for negative feedback; call button hidden for low pickup; G.711 about 64 kbps per direction, adds transcoding latency, primary use is legacy telephony infrastructure and PSTN gateways | Meta, Configure Call Settings (updated 6 Jul 2026) | developers.facebook.com | 24 Sep 2026 |
| TLS mandatory, wa.meta.vc, 407 then digest auth; openssl certificate check | Meta, SIP Configuration Guide (updated 22 Sep 2026) | developers.facebook.com | 24 Sep 2026 |
| 5,000 concurrent calls; no maximum call duration; AI voicebots permitted; REGISTER fails with 403 | Meta, WhatsApp Calling FAQ (updated 16 Sep 2026) | developers.facebook.com | 24 Sep 2026 |
| Supported codecs only, Opus 48 kHz, 20 ms ptime, single SSRC, DTMF 8 kHz; ICE-FULL, DTLS client and first-RTP recommendations; reuse the messaging app; PSTN disallowed on any leg | Meta, Integration Patterns (updated 16 Sep 2026) | developers.facebook.com | 24 Sep 2026 |
| Six-second pulses, 56 s billed as 10 pulses; user-initiated calls free; window opens when a user accepts your call; A$0.0148 a minute for 0 to 50,000 minutes, Rest of Asia Pacific, on the AUD calling cards effective 1 Jul 2026 and 1 Oct 2026 | Meta, Calling API Pricing (updated 11 Sep 2026) and its AUD rate cards | developers.facebook.com | 24 Sep 2026 |
| Utility A$0.0148 and marketing A$0.0952 (AUD card effective 1 Jul 2026); utility and service A$0.0148 and marketing A$0.1095 (AUD card effective 1 Oct 2026); utility list tier to 150,000 messages; Australia mapped to Rest of Asia Pacific; utility in window free to 30 Sep and charged from 1 Oct 2026; 1,000 free service messages a month per number; rate changes only on the first day of a quarter | Meta, Pricing on the WhatsApp Business Platform (updated 10 Sep 2026) and its AUD rate cards | developers.facebook.com | 24 Sep 2026 |
| Service messages charged from 1 Oct 2026; payment method needed by 30 Sep 2026; service replies may be powered by a 3rd-party AI solution | Meta, Upcoming pricing updates for Meta Business Agent, service and utility messages (updated 25 Aug 2026) | developers.facebook.com | 24 Sep 2026 |
| Clause 4.7 AI Providers | WhatsApp Business Solution Terms (last modified 23 Sep 2026) | whatsapp.com | 24 Sep 2026 |
| WhatsApp Connector, LiveKit Cloud only, Cloud API v23.0 to v26.0 | LiveKit documentation | docs.livekit.io | 24 Sep 2026 |
| Issue #3375 opened 8 Sep 2025, open; livekit/sip #281 closed 24 Sep 2026 | LiveKit, GitHub | github.com/livekit/agents; github.com/livekit/sip | 24 Sep 2026 |
| WhatsAppTransport receives calls via SmallWebRTCTransport | Pipecat documentation | docs.pipecat.ai | 24 Sep 2026 |
| Issue #2811 opened 8 Oct 2025, open; maintainer comment 20 Mar 2026 | Pipecat, GitHub | github.com/pipecat-ai/pipecat | 24 Sep 2026 |
| Spam Act 2003 s 5(1) and s 5(5) | Federal Register of Legislation (Compilation No. 10) | legislation.gov.au | 24 Sep 2026 |
| Unsubscribe within 5 working days, working for 30 days; express and inferred consent; four ways to give express consent; cannot message to ask for consent | ACMA, Avoid sending spam (last updated 29 Nov 2024) | acma.gov.au | 24 Sep 2026 |
| Worked example: 29 pulses, A$21.46, A$20.97, A$7.40, A$47.60, A$54.75, A$28.86, 34% | Zian AI, arithmetic on the Meta rates above; the 500 calls and 170 seconds are illustrative inputs, not measurements | This page | 24 Sep 2026 |
| Around 420,000 data points across more than 10,000 leads a day | Zian AI, first-party figures about our own platform | zian.ai | 24 Sep 2026 |