From Live Demo To Onboarding: How Aroha Calls Gets A Business Live
What happens after a business owner tries the live demo, chooses a plan, pays through Stripe, and submits the onboarding brief that creates the managed Aroha AI workspace.
The demo is meant to prove the call experience
A live AI receptionist demo should not be a slideshow. The owner should be able to talk to the receptionist, ask real questions, test a booking or quote scenario, and hear whether the conversation feels calm and useful. Aroha Calls lets visitors talk to Grace in the browser, call the demo line, or request a phone callback from the Aroha number.
The sales call should be plain English
Many business owners are not technical and should not have to be. A useful demo call should explain what the system does in normal language: it answers calls, books appointments, drafts emails, remembers customers, sends follow-up, escalates urgent calls, and gives the owner a summary. The owner should leave knowing whether Lite, Essentials, Professional, or Premium fits the business.
Plan selection comes before setup
The plan decides the managed package: number count, minutes, Email AI, messages, CRM depth, Aurora, analytics, workflows, and support level. Aroha Calls supports NZD and USD pricing and sends the customer through Stripe checkout so billing, invoices, renewals, and cancellation stay clean.
Onboarding turns business knowledge into operating rules
After checkout, onboarding asks the questions that matter: business details, service area, hours, service list, pricing rules, booking rules, Google Calendar ownership, Gmail or inbox needs, follow-up behaviour, customer memory, urgent handoff, compliance boundaries, and who should receive the Aroha AI login invite. Those answers become the setup brief.
Aroha AI receives the setup brief
Behind the scenes, Aroha Calls sends a signed provisioning event to Aroha AI. That payload includes the customer, selected plan, subscription status, onboarding answers, requested integrations, unlocked Aroha AI tools, demo number, and the managed setup workflow. Aroha AI can then create the organisation and return the login URL when ready.
The owner should get a simple result
The end result should not feel like a technical project. The owner gets the Aroha AI login, the team can see calls and customer memory, Google Calendar booking rules are configured, inbox drafts are ready where included, and Aroha Group can tune the system after real calls. The owner should know what is live, what is waiting on them, and who to contact.
Why this process matters
AI reception fails when it is treated as a generic bot. It works when the business rules are clear, the calendar is connected safely, the inbox process has approval rules, and the system knows when to escalate. The Aroha Calls flow is designed to take a curious visitor from demo to plan to onboarding to Aroha AI workspace without forcing them to become a software operator.