Johnni AI: an Australian AI receptionist for trades

What Johnni is

Johnni starts with a recognisably Australian service-business problem: the phone rings while the owner is on the tools, driving, quoting, or already speaking with a customer. Its answer is not simply to take a message. The product is designed to understand the enquiry, apply the business's rules, and move the customer toward a useful outcome while the opportunity is still live.

That local focus is a genuine strength. Johnni is built and marketed around Australian voices, trade language, suburbs, service areas, and field-service systems such as ServiceM8 and Simpro. Its examples range from a one-van operator to a larger office-backed team. The business can use Johnni for every call, after-hours or overflow cover, or only when the team does not answer. Existing numbers can be forwarded to a local number, so the customer-facing number does not necessarily have to change.

Behind the conversation, Johnni offers a dashboard, call records, and a basic CRM for businesses that do not already use one. The combination turns the receptionist into a front door for the workflow: answer the enquiry, decide whether it fits, book it or transfer it, and preserve the result for the team. Johnni also advertises capacity for up to 20 simultaneous calls. Treat that as a useful scale claim to demonstrate during buying, rather than an uptime or capacity guarantee in the absence of a published service commitment.

Calls, booking, and warm transfers

The core Johnni journey is easy to understand. A new caller explains the job; Johnni can collect the name, phone number, email, address, service need, and preferred time, then check live availability and offer a booking. Service-area radius, route, and calendar rules are intended to keep the appointment inside the operator's patch and avoid an impractical run across town. Once the call ends, the team can receive a summary and review the transcript and recording in the dashboard.

Qualification is where the promise becomes operationally valuable. Johnni can use the business's services, pricing knowledge, hours, coverage area, and availability to distinguish a bookable lead from work the team does not take. Owners can edit the voice, hours, services, service area, and knowledge content, and Johnni says a change is live on the next call. That gives an operator a direct way to adjust the front desk as the roster, service mix, or season changes.

When the right outcome is a person rather than a booking, Johnni advertises a warm transfer. The recipient hears context before accepting the conversation; if nobody picks up, the AI can return to the caller and collect the details instead of dropping the customer into voicemail. This is a meaningful design choice for urgent or high-value work, and it deserves a live test with both an answered and a missed transfer. The result should show the expected caller ID, attempt sequence, fallback, staff alert, and saved record.

Johnni also describes guardrails around approved information, repeated questions, silence, maximum call length, and suspicious behaviour, alongside automatic scoring of completed calls. Those controls suggest an active quality loop rather than a set-and-forget script. Before launch, define the exact emergency path, human override, review process, and behaviour when a guardrail fires, because those details are not fully published.

Web voice, text, and outbound work

A customer journey does not always begin with a ring. Johnni's website widget lets a visitor start by typing and switch to a live voice conversation without losing the context already shared. The visitor can ask a question, explain the job, and book without leaving the site. For someone browsing after hours who is not ready to call a stranger, that creates a lower-friction path into the same booking workflow.

Johnni also reaches out. Its outbound examples include calling a fresh website or Facebook lead, following up an open quote, and reactivating a previous customer. SMS and email broaden that follow-through. Used together, these channels support a credible promise: respond at the moment of intent, keep the conversation moving, and return the outcome to the business rather than waiting for someone to clear an inbox the next morning.

The strongest version of that experience is one continuous record. During a demo, follow a lead from the original form or website conversation through the outbound call, qualification, booking, confirmation, and staff view. For each outbound use case, agree on the trigger, approved message, contact frequency, caller identity, consent, opt-out or suppression rule, and the event that stops further attempts. That is how channel breadth becomes useful work instead of a new queue to reconcile.

Integrations and workflow depth

The workflow becomes more valuable when the job lands where the team already works. Johnni names ServiceM8, Simpro, ServiceTitan, HubSpot, Pipedrive, Zoho, and Google Calendar and says APIs can connect other systems. Its dedicated pages describe three particularly relevant field-service paths:

• With ServiceM8, Johnni describes answering questions about services and pricing, scheduling visits, and creating or updating jobs.
• With Simpro, it describes gathering job details, booking appointments, updating schedules, and sending summaries.
• With ServiceTitan, it describes collecting customer and job information, booking into the schedule, and sending notifications and summaries.

That is a good local-market integration story, particularly for an Australian trade business already running ServiceM8 or Simpro. The proof, however, is the completed object rather than a logo. Johnni's About page displays a wider software ecosystem across CRM, calendar, automation, payments, support, and messaging, but a logo by itself does not establish a native connector, certification, or every write action a business may need.

Bring the live account and make one real job travel end to end. Confirm customer lookup and creation, job or appointment creation, availability, rescheduling, notes, duplicate handling, retries, failure alerts, and who supports the connection. ServiceTitan's appearance is evidence of a described workflow, not evidence that Johnni is ServiceTitan-certified or commercially available in the United States.

Australian-dollar pricing mechanics

Johnni sells a configured service rather than a public package. The homepage describes a custom build plus a flat monthly amount that varies with call-flow complexity: a one-van operator and a six-van team are different implementations. Johnni also promotes no contract, with access continuing to the end of the billing period after cancellation.

The terms add an important layer to that simple headline. They allow monthly subscription charges at the beginning of the billing cycle and usage charges, calculated per minute, after the cycle. The written quote should therefore state, in AUD, how the flat monthly amount and any metered usage work together. It should separate the custom-build or setup fee, included minutes, per-minute or overage rates, and charges for warm transfers, outbound calls, SMS, email, numbers, and integrations. It should also say whether GST is included and spell out any free-trial duration, conversion date, and cancellation deadline.

Johnni's Australian cost guide gives a broad market range of $300 to $1,000 or more per month. That is not a Johnni rate card, and the guide does not label the currency beside that range. Treat it as context only and insist that the actual proposal explicitly says AUD and identifies tax. The terms permit cancellation at the end of the current billing period and do not offer change-of-mind refunds, so the quote and billing date should be clear before launch.

Implementation and support

The visible starting point is a demo or trial, followed by a custom setup shaped around the business's call flow. Forwarding makes a staged launch practical: begin with after-hours, overflow, or unanswered calls, make sure bookings and handoffs behave properly, then expand coverage when the team trusts the result. That is a sensible path for a small operator who wants relief without changing the front office all at once.

The acceptance session should feel like a day in the business. Run a new customer and a known customer, an out-of-area request, a full calendar, an answered and missed warm transfer, a caller who changes a detail, and a question outside the approved knowledge. Follow each conversation from the first ring to the saved customer, appointment or job, staff notification, and any follow-up. Also confirm forwarding, caller ID, peak-call behaviour, voicemail or staff fallback, emergency routing, and the owner of subsequent call-flow changes.

Support is defined by the applicable order. Johnni's terms exclude training, hardware setup, software development, and data recovery unless separately agreed; delivery dates are estimates, and beta services have reduced assurances. A good order will therefore name the onboarding owner, launch sequence, number and forwarding help, monitoring and failure alerts, escalation contact, support hours, and any uptime, response, or service-credit commitment. Those details are not standardised on the public site, but they can be made concrete before the first live call.

Privacy, data, and call controls

Johnni's data story is framed by the Australian Privacy Act and Australian Privacy Principles. Its policy covers identity and contact information, technical and transaction data, account profiles, and interaction data such as call direction, duration, recordings, and transcripts. It also anticipates health and financial information when the receptionist is used in a healthcare setting.

The policy says personal information can be stored on servers in Australia, the United States, and the European Union. It requires the customer or practice to disclose Johnni's involvement and obtain consent where required so a caller or patient can choose not to participate. Johnni describes reasonable security, breach notification where applicable, and destruction or de-identification when information is no longer required.

There is a distinction worth preserving in a security review. A parenthetical statement connects SOC 2 Type I and II, HIPAA, and GDPR language to US or EU servers and transferred data. It does not, by itself, establish that Johnni as a company holds a SOC 2 report or independent HIPAA certification. Ask for the report and scope, data-processing terms, legal contracting entity, and evidence that applies to the proposed service.

The public material does not set exact retention periods, encryption specifications, a subprocessor list, model-training rules, tenant isolation, SSO or role controls, audit logs, or a standard DPA or BAA route. It also moves between Johnni.ai and Johnni.au naming without clearly identifying the legal controller. For ordinary trade calls, those are still reasonable contract questions; for healthcare, payment, or other sensitive conversations, they are launch conditions.

Best-fit scenarios

Johnni is at its most persuasive when a local trade or service business already has demand but cannot answer consistently. A one-van plumber can forward only missed and after-hours calls, protect the daytime number, and let Johnni collect the job and offer a real slot. The value is immediate and bounded: fewer calls die in voicemail while the owner is on site.

A growing team can use more of the workflow. Johnni can qualify by service and suburb, keep the route inside the configured patch, book into ServiceM8 or Simpro, and warm-transfer urgent or valuable work with context. Website voice and text can catch the after-hours visitor, while outbound callbacks can reach a new form lead before it cools. Here, the integration and fallback tests matter as much as the voice itself because several people depend on a clean job record.

Johnni can also be attractive for seasonal peaks and overflow. Its advertised concurrency gives an air-conditioning, roofing, plumbing, or pest-control business a way to absorb the day when demand spikes. The buying conversation should translate that claim into expected peak volume, queuing behaviour, failure handling, and a service commitment. For highly regulated or complex multi-location operations, the data package, permission controls, reporting, and governance deserve more scrutiny before the broad channel story becomes a deployment decision.

Strengths and limitations

Johnni's strongest quality is coherence. The Australian voice and trade focus, local service-area logic, flexible call forwarding, live booking, contextual transfer, website conversation, outbound follow-up, and ServiceM8 or Simpro story all point at the same job: turn an enquiry into useful work without pulling someone off the tools. The ability to change core business settings and start with limited call coverage makes that promise approachable for a small operator as well as a growing team.

Its public detail is less complete at the operating edges. Integration logos go beyond the object-level behaviour described. Onboarding time, support hours, uptime, service credits, human fallback, guardrail review, and detailed data controls depend on the order or further diligence. Johnni reports more than 50,000 handled calls, more than 1,600 hours of talk time, and a 63.4% booking rate for “real enquiries.” Those figures show live use, but the public site does not define the cohort, period, denominator, exclusions, or audit method. An anonymous revenue example is encouraging proof of possibility, not a forecast for the next buyer.

The right response is not to discount Johnni's promise. It is to demonstrate the few paths that determine value for the specific business, attach clear commercial and support terms, and judge the result in that context.

What a US operator cannot assume

Johnni should be read first as an Australian product, not a globally generic receptionist. Its natural Australian voice, trade examples, local-number forwarding, ServiceM8 and Simpro emphasis, Privacy Act framework, NSW governing law, and AUD buying context form a real local-market fit. Australian readers should verify that fit at the practical level: number coverage in their area, support hours, relevant field-service connection, GST treatment, data terms, and the entity named on the order. The footer currently combines “made in Brisbane” wording with an Adelaide, South Australia address, so it is sensible to identify the contracting entity and service contact.

That same strength creates a clear boundary for a US buyer. Johnni's site does not establish US commercial availability, numbers or carriers, nationwide coverage, support hours, outbound and do-not-call controls, a US contracting entity, US pricing, or a US-specific data package. A ServiceTitan page proves a described integration path, not American availability. A US operator would need written answers on telephony, recording consent, outbound compliance, emergency handling, support, data residency, subprocessors, tax, currency, and the signing entity before treating Johnni as a procurement option.

Where Broccoli fits

Johnni deserves real credit for a locally shaped Australian receptionist: its voices, trade language, ServiceM8 and Simpro relevance, forwarding options, booking logic, and warm-transfer fallback are designed around the way Australian service businesses work. For an Australian operator, that context can matter more than a superficially longer feature list. Confirm Johnni's local number and support availability, AUD and GST terms, exact integration behaviour, and data package, then judge the workflow on a real call.

Broccoli addresses a broader, US-oriented operating need. It is an all-in-one trades and home-services lead-management platform across inbound and outbound voice and SMS, website chat, speed-to-lead, qualification, booking and dispatch, follow-up, QA and coaching, and multi-location reporting. That unified scope carries the lead from first response through the revenue workflow and gives managers a consistent view of conversion quality, follow-through, team performance, and location results.

For a US home-services company that wants that complete revenue workflow, Broccoli is the clear choice. It is not presented here as a drop-in Australian equivalent to Johnni: market availability, telephony, compliance, currency, support, and local integrations matter. Australian readers should verify Johnni's regional and operational fit; US operators can book a Broccoli demo and run their real lead sources, qualification rules, booking and dispatch paths, follow-up, QA, and multi-location reporting through one system.

Conclusion

Choose Johnni when the central problem is an Australian trade or service business missing calls, delaying web leads, or losing the next action between the conversation and the calendar. Its local voice and workflow focus, live booking, warm transfers, website voice and text, outbound follow-up, and field-service connections create a credible path from enquiry to booked work. Start with a defined forwarding condition, prove the hard call paths and system writes, and make the AUD price, GST, support, availability, consent, and data terms explicit in the order.

Choose Broccoli when a US home-services operator wants more than receptionist coverage: one platform to own inbound and outbound voice and SMS, website chat, speed-to-lead, qualification, booking and dispatch, continued follow-up, QA and coaching, and reporting across locations. That complete lead-to-revenue system makes Broccoli the stronger US decision, while Johnni remains a credible, locally informed choice for Australian buyers who confirm the fit in their own market and workflow.

Book a Broccoli demo and run your complete US home-services revenue workflow

Sources

1. Johnni homepage — Product scope, call handling, booking, channels, integrations, and current commercial positioning.
2. Johnni terms and conditions — Billing, usage charges, cancellation, refunds, support scope, liability, and governing law.
3. Johnni privacy policy — Personal information, recordings and transcripts, storage regions, consent, and security language.
4. Johnni ServiceM8 integration — Service information, scheduling, and job creation or update workflow.
5. Johnni ServiceTitan integration — Caller detail collection, calendar booking, notifications, and summaries.
6. Johnni Simpro integration — Booking and field-service workflow positioning.
7. Johnni AI appointment setter — Appointment-setting and follow-up use cases.
8. About Johnni — Australian positioning and displayed software ecosystem.
9. Johnni free trial — Trial entry point; confirm the current duration and conversion terms.
10. Johnni guide to AI receptionist costs in Australia — General Australian market range, not a Johnni rate card.