Callease AI

  • Automation
  • Voice AI
  • B2B
Callease AI — AI voice agents

Automated phone calls handled by human-like AI voice agents, built for Australian businesses.

Who it was built for

The business, and what they came with.

Built for

Callease AI

Sells AI phone agents to Australian businesses on subscription. Their customer is the clinic, agency or trades business that keeps missing calls.

The brief

For those businesses a missed call is a lost job, and voicemail does not recover it. The agent had to hold a normal conversation, put work into a real calendar, and be set up by the customer without a developer in the room.

What we delivered

What Callease AI has now that they did not have before.

  • Agents the customer configures

    Persona, knowledge base and business rules are structures in the product rather than code. A new customer launches a tailored agent the same day they sign.

  • Conversation that keeps pace

    Audio, transcription, model reasoning and speech stay in step so replies land inside half a second. Slower than that and callers talk over the agent, then hang up.

  • Calls that end in a booking

    The agent checks live availability, books the meeting and writes the lead into the CRM. The outcome sits in a calendar, not in a voicemail queue.

  • Local numbers

    Australian SIP numbers are provisioned per customer, because an unfamiliar interstate caller ID gets answered far less often.

  • Transcripts and call analytics

    Every call is reviewable, so scripts are tuned on evidence and a failing flow is caught the same day instead of at the end of the month.

Where the growth comes from

Why each piece of the build pays for itself.

  • The phone is answered at 9pm

    Enquiries that used to reach voicemail become booked jobs, and after-hours cover costs a subscription rather than a night shift.

  • People only take qualified calls

    The agent screens and books, so paid sales time goes to conversations that are already worth having.

  • One agent, then fifty

    Because agents are configured rather than built, onboarding a customer is a setup task instead of a project. That is the difference between an agency and a software business.

The business analysis

Market, model and architecture. Every figure is either cited or labelled as a model.

Callease sells a subscription against a cost its buyers already pay and cannot see: the enquiry that rang out. The commercial question is therefore not whether an AI agent can hold a conversation — several vendors have settled that — but whether the recovered call is worth more than the subscription, and whether one customer can be onboarded without an engineer. Everything below is an attempt to answer those two questions with figures that can be checked.

Calls answered live
37.8%
Of inbound calls to 85 small businesses across 58 industries. The remaining 62% reached voicemail or nothing at all.

Source · 411 Locals inbound-call study, as reported by Zadarma

Employing businesses in Australia
994,178
Of 2,729,648 actively trading businesses at 30 June 2025. The employing subset is the population that staffs a phone.

Source · Australian Bureau of Statistics, Counts of Australian Businesses

Forecast CAGR, AI voice agents
39.0%
2026 to 2033, on a market valued at USD 2.5bn in 2025.

Source · Grand View Research, AI Voice Agents Market Report

Reply latency target
< 500ms
The product's own design budget for the gap between a caller finishing and the agent starting.

Model · Design target set during the build, not a measured production average.

The market it sells into

The category Callease competes in is young enough that its size is still being argued about, and the forecasts differ by an order of magnitude depending on whether a research house counts voice agents as their own market or as a slice of conversational AI. Taking the narrowest credible definition — software whose product is an autonomous voice agent on a telephone line — Grand View Research values the global market at USD 2.5bn in 2025 and forecasts USD 35.2bn by 2033, a 39.0% compound annual growth rate, with North America holding 38.1% of 2025 revenue 1.

AI voice agents — global market, USD billions

One research house's view of the category. The 2025 figure is that report's base-year estimate; the two later columns are its forecast, and are drawn hollow for that reason.

  • $2.5bn
  • $3.5bn
  • $35.2bn
  • 2025
  • 2026
  • 2033

Hollow columns are the published forecast, not a measurement.

Source · Grand View Research, AI Voice Agents Market Report

The Australian Bureau of Statistics counted 2,729,648 actively trading businesses at 30 June 2025, of which 994,178 were employing 2; 97.3% of all Australian businesses had fewer than twenty staff 3. Those two facts set the shape of the product. The addressable buyer is small, has no IT department, and the person who would configure an AI agent is the same person answering the phone — which is why "the customer configures it, not us" is a commercial requirement rather than a nicety.

Serviceable market, narrowed step by step

A top-down cut of the ABS business count. Each step removes businesses for which a voice agent has no job to do; the percentages applied are assumptions, and they are named so they can be argued with.

All actively trading businesses
2.73m

ABS, 30 June 2025. Includes sole traders with no staff and no inbound call volume.

Employing businesses
994k

ABS. Someone is paid to be reachable, so an unanswered call has a cost attached to it.

Booking- or enquiry-led sectors
~300k (assumed 30%)

Health, trades, real estate, hospitality, professional services. Assumption, not a published figure.

Plausible near-term buyers
~30k (assumed 10%)

Willing to route a live line to software today. Assumption.

Model · ABS business counts, then two stated assumptions (30% sector fit, 10% near-term willingness). The first two rows are published data; the last two are ours and are labelled as such.

The buyer's problem, in numbers

The best-documented study of what actually happens to small-business phone calls tracked 85 businesses across 58 industries: 37.8% of inbound calls were answered by a person, 37.8% went to voicemail, and 24.3% received no response at all 4. The important part is the last figure. A voicemail is a weak recovery path; no response is none.

Where an inbound call to a small business ends up

85 businesses, 58 industries. The two right-hand segments are the product's entire addressable event: a call that reached no human.

Answered by a person38%
The only outcome that can convert today.
Went to voicemail38%
Recoverable in principle, rarely recovered in practice.
No response at all24%
Not even a voicemail option. Unrecoverable without automation.

Source · 411 Locals inbound-call study, as reported by Zadarma

The alternative to software here is people, and people are the reason the problem persists. Median weekly earnings for a receptionist in Australia are AUD 1,175 5, or roughly AUD 61,100 a year before superannuation, penalty rates or cover for leave. Answering a phone across all 168 hours of a week rather than a 38-hour ordinary week takes about 4.4 of those people.

That number is why the pricing conversation is short. A subscription does not have to beat a receptionist on quality of conversation to be worth buying. It has to beat the marginal cost of the hours a receptionist is not there, which is where most of the missed calls are.

Where the revenue comes from

Three revenue mechanics sit inside the build, and they are not equally valuable. Ranking them is the difference between a product that grows and an agency that bills.

MechanicWhat it does commerciallyDepends onCeiling
Answered after-hours callsConverts an enquiry that previously reached voicemail into a bookingReliable telephony, local caller IDBounded by the buyer's own call volume
Qualification before a humanMoves paid sales time onto conversations already worth havingGrounded reasoning over a knowledge baseBounded by headcount saved
Self-serve agent configurationTurns onboarding from a project into a setup taskPersona, knowledge and rules as data, not codeThe one that scales

Where engineering effort went, by commercial purpose

A retrospective apportionment of build effort against what each part earns. It explains the priorities; it is not a timesheet.

41%on making agents configurable rather than bespoke
Agent configuration system41%
Persona, knowledge base and business rules as structures a customer edits.
Voice orchestration and latency27%
Keeping audio, transcription, reasoning and speech in step.
CRM and calendar automation18%
The part that turns a conversation into a booked, recorded outcome.
Transcripts and analytics14%
Evidence for tuning scripts, and the first place a failure shows up.

Model · Our own apportionment of build effort across the four workstreams, reconstructed after delivery. Directional, and rounded.

The constraint the whole product is built around

Everything difficult about this system comes from one number. A caller will tolerate roughly half a second of silence before assuming the line is dead or talking over the reply. That budget has to contain the full round trip — audio in, transcription, model reasoning against the customer's knowledge base, speech synthesis, audio out — and any component that blows it takes the conversation with it.

The stack, by responsibility

Grouped by what each layer is accountable for, because the interesting question is not which technologies were used but what would have to change to scale the thing.

  1. Configuration surface

    Where a customer builds and tunes their own agent, and reads what it did. The commercial moat lives here, not in the voice.

    • Next.js
    • TypeScript
    • Tailwind CSS
    • Call analytics
    • Agent setup
  2. Orchestration

    Coordinates the live call: telephony events in, reasoning out, integrations fired without blocking the conversation.

    • Node.js handlers
    • Voice webhooks
    • Synthflow call flows
  3. Transient state

    Holds what a call needs while it is happening, and makes automation jobs safe to retry when a downstream system is slow.

    • Redis
    • Session state
    • Retry-safe jobs
  4. System of record

    Everything that must survive the call: transcripts, logs, per-customer configuration and agent settings.

    • MongoDB
    • Transcripts
    • Call logs
    • Customer config
  5. Business systems

    Where a successful call becomes a commercial fact — a calendar entry, a CRM record, a follow-up.

    • CRM
    • Calendar
    • Payments

One inbound call, end to end

The spine is the happy path. The offshoots are what happens when it is not, which is where a voice product is actually judged.

  1. Call lands on a local Australian number

    Numbers are provisioned per customer. An unfamiliar interstate caller ID is answered far less often, so this is a conversion decision disguised as telephony configuration.

  2. Session opens, agent context loaded

    Persona, knowledge base and business rules for that customer are pulled into the session. Held in Redis, because none of it needs to outlive the call.

  3. Speech to text, then grounded reasoning

    The model answers against that customer's knowledge base rather than from general knowledge. Grounding is what keeps it from inventing a price.

  4. Can the agent close this itself?decision

    Intent is matched against what the agent is allowed to do — book, quote, qualify, or none of the above.

    • Out of scope → hand to a human
    • Caller asks for a person → transfer
    • Low confidence → capture details and escalate
  5. Live availability checked, meeting booked

    Writing into a real calendar rather than a queue. A booking that a human has to re-key is not an automated booking.

  6. CRM record written, follow-up triggered

    Fired through retry-safe jobs, so a slow CRM delays the record and never the conversation.

  7. Transcript stored and scored

    The call becomes evidence: the script is tuned on it, and a flow that has started failing is visible the same day rather than at month end.

What we would watch

An honest analysis names the ways the model breaks. These are the three that matter for this one, and none of them are engineering problems.

RiskWhy it bitesEarly indicator
Vendor concentration in voiceCall-flow execution sits with one provider, so its pricing and its latency are the business's pricing and latencyGross margin per minute moving without a change on our side
Regulatory disclosureRules on disclosing automated callers are tightening across jurisdictions; a mandated disclosure at the top of every call changes conversionConsent and disclosure requirements entering telecommunications guidance
Configuration debtThe moat is that customers configure agents themselves. Every exception built for one customer erodes itSupport requests that end in a code change rather than a settings change

References

  1. 1.AI Voice Agents Market Size And Share Report, 2026–2033 · Grand View Research
  2. 2.Counts of Australian Businesses, including Entries and Exits · Australian Bureau of Statistics
  3. 3.Number of small businesses in Australia · Australian Small Business and Family Enterprise Ombudsman
  4. 4.The Hidden Cost of Missed Calls (411 Locals inbound-call study) · Zadarma
  5. 5.Receptionist — median weekly earnings · Victorian Government careers data

How an agent goes live

The path a real user takes, in order.

  1. Persona

    Tone, accent and the boundaries of what it will discuss.

  2. Knowledge

    Company specifics and FAQs loaded into the agent's context.

  3. CRM

    Connected so a qualified call creates a record.

  4. Calendar

    Availability checked and meetings booked directly.

  5. Scripting

    The conversation tuned to one business goal per agent.

  6. Number

    A local Australian line provisioned and routed.

  7. Launch

    Live monitoring, then tuning from real transcripts.

Who it is for

The people whose problem this solves, and what they came for.

  • Support teams

    Need cover for FAQs and first-line triage outside office hours.

  • Sales and marketing agencies

    Qualify leads and run outreach at a volume no team can dial.

  • Booking-led businesses

    Medical, real estate and hospitality, where the appointment is the sale.

Reference

For the technical reader. Everyone else has what they need above.

The engineering write-up

How Callease AI was actually built, in detail.

The closest work to Callease AI, scored for relevance rather than picked by position.

Want the version of this built for your business?

Fifteen minutes with the people who shipped it. No deck, no account manager.