Stop doing the admin. Let the system do it.

Pick one. Most clients start with the outcome that's bleeding the most money, usually missed calls or overdue payments for tradies, missed calls or no-shows for clinics. We build that one piece, prove it works, then add the next outcome when you're ready. We don't bundle for the sake of it.

No, though they connect. Custom automations covers the admin layer around calls, leads, payments, and workflows. If you need an AI to actually hold a phone conversation, that's the dedicated AI receptionist build. If you need an online booking system with reminders and no-show prevention as the core project, that's booking automation. We'll tell you which one (or which combination) fits on the discovery call.

Almost certainly yes if you're an Australian service business. Almost certainly no if you're a high-volume e-commerce store or a B2B SaaS. Different problems, different solutions. The discovery call is where we figure out which one you are.

Depends on scope. A single-outcome build (just missed-call recovery, say, or just invoicing-and-chasing) is much less than a full multi-outcome stack. We quote after the discovery call so the number matches the work. There's no public price list because no two builds are the same.

Yes, surcharging a card payment is legal in Australia, with one hard rule: the surcharge can't be more than what it actually costs you to accept that card. You can't use it as a profit line. The ACCC enforces this and it's set by the RBA's surcharging rules. We configure any surcharge to reflect only your real cost of acceptance, so you stay on the right side of it. Plenty of businesses choose to absorb the fee instead, and we'll talk you through both on the discovery call.

No, and neither do you. Card details are tokenised by the PCI-compliant processor (Stripe or Square): they hold the actual card data in their secure vault and hand your system a token that stands in for it. LUNA never touches a raw card number, and neither does your business.

Yes, those are the two we set up most. Payments reconcile automatically against the matching invoice in Xero or MYOB, so your books stay current without anyone doing manual matching at month-end. If you're on something else (QuickBooks, Reckon), we'll check the integration on the discovery call before we promise anything.

We use whatever's right for the job. GoHighLevel for businesses that want SMS + email + CRM + automations in one platform. n8n for businesses that want server-side automation they can self-host. Zapier or Make for one-off integrations. Custom code where the existing tools can't handle it. We pick what works for your business, not what we're certified to sell.

We work with regulated healthcare (AHPRA), pharmaceutical/cosmetic (TGA), financial services (ASIC), and legal practices regularly. Every automation built for a regulated business, including payment flows, is reviewed against the relevant compliance rules before it goes live.

You take everything with you. All accounts are in your name. We hand over documentation of what's been built, what's running where, and what each automation does. The system keeps running. You either find another agency to take it on, or your in-house person picks it up.

First outcomes (missed-call recovery, instant lead response, faster invoicing) usually generate measurable results within 2 weeks. Payment-cycle changes (days-to-pay, recovered failed payments) show up within the first billing cycle. The bigger benefit, the 'I've stopped thinking about this' feeling, usually arrives at the 90-day mark.