Noah
After a test, the audiogram and measurements come into SONUS AI and attach to that customer's record — the fitting AI and the audiologist read the same data.
Import
What travels
- Audiograms
- Test measurements
- Test dates
Integrations
Keep your tools. Noah, ERP / POS, CRM, single sign-on, LINE and your own systems — data flows through one workflow.
What connects
What each integration carries, and in which direction — one card each.
After a test, the audiogram and measurements come into SONUS AI and attach to that customer's record — the fitting AI and the audiologist read the same data.
Import
What travels
Products and stock follow the system you already run; orders closed in SONUS AI sync back, so stores and HQ reconcile to the same numbers.
Two-way sync
What travels
Customer details and service history stay in step both ways — marketing or service teams keep their CRM, and stores never key the same record twice.
Two-way sync
What travels
Staff sign in to SONUS with their company account (SAML / OAuth) — no extra password — and accounts and permissions are managed in one place.
Sign-in
What travels
When a booking or follow-up comes due, SONUS sends the reminder or check-in over LINE — in the app customers already open every day.
Sent by SONUS
What travels
Internal systems read and write through a standard REST API; when something happens — a booking made, a device handed over — a webhook tells your systems.
Read, write & events
What travels
These are typical set-ups; the exact scope and direction of each connection are confirmed during onboarding.
How it gets connected
Integrations follow the three rollout phases: map, connect, then pilot before going live everywhere.
Build & prepare
List the systems stores and HQ use, their data fields and owners — then decide what connects, and how.
Build & prepare
Agree what comes in, what goes out and who can see it — set up and tested during the build, with our specs and support.
Pilot → all stores
Pilot in one or two stores, check the data is right, then roll out to every store — with no store downtime.
Connected — controlled and auditable
Questions
No. SONUS SYSTEM connects to what your stores and HQ already run; what comes in and what goes out is decided together during onboarding.
Usually not. An operations or clinical lead can run it; for integrations, we provide specs and support.
They depend on store count, the systems to connect and workflow maturity, and are confirmed during onboarding. A full rollout takes about 2–3 months in three phases.
We can scope a custom connection on the standard API and webhooks — tell us what you run.
Talk to us about an integrationWe confirm scope and timeline during onboarding.