Enterprise and public sector

Conversation services for regulated industries and the public sector.

Governed releases, your identity provider, integration with the systems you already run, and a delivery team that stays with you. Use AI where it helps, or switch on No-AI mode where rules must decide.

For enterprises and public services that run conversations at scale: the public sector and public safety, telecommunications, critical infrastructure, transportation, health and financial services.

A question answered with the evidence trail behind itA person asks what changed in the booking flow since the last release. On the Camlin Insight console the answer is a trail on one thread: the Blueprint change and who approved it, the plan from the compliance review, the release that went live on voice and chat, and the live event linked back to the step that changed. The Assistant avatar reports from the corner.“What changed in the bookingflow since the last release?”Camlin InsightBlueprint historybooking flow · since the last releaseBlueprint change · booking flowAgent edit, approved by the team leadPlan from the compliance reviewGoals, discussion and accepted outcomeRelease went liveVoice and chat · replaced the previous versionLive event · transfer failedLinked back to the step that changedThe question, answered with the evidence.

Governance

Checked, versioned and approved, with a test for every path

Drafted with AI or built from templates, guided wizards and plain commands: the same controls apply either way.

  • Checked before it saves

    Every change is checked against structure rules: one Start, every path routed, nothing orphaned.

  • A test for every path

    Run across channels before you publish, so every route from Start to End has been exercised.

  • Releases you can stand behind

    Releases are immutable, promotion goes through pre-production by default, and rollback is one step.

  • Roles and audit

    Owner, admin, editor and viewer roles in the platform, and an audit log of administrative changes.

Identity

  • Single sign-on through your OIDC identity provider, with tokens validated against its published keys.
  • Roles are managed in the platform and do not change when the provider does.
  • A Keycloak claim preset is configurable, for identity that runs inside your own network.

Integration

  • API calls from any step, each with a success route and an error route.
  • Camlin Server collections, lookups and counters for the data behind a service.
  • Transfer and handoff to your people, with the context of the conversation.
  • Open SIP for carriers and trunks.

With AI or without

Your choice, per organization and per step

The same checks, tests and approval apply either way, and you can change your mind later.

AI when you want it

  • Drafts from plain language. Describe the service and agents draft the Blueprint, the interactions, the prompts and the channel logic, on models you host if you prefer. You review and approve before anything ships.
  • Understands and answers open conversation. AI understanding, sentiment and generation steps sit beside menus and forms, so a caller can say what they need in their own words.
  • Your own keys. AI steps in the running service use your own keys, so the relationship with the model provider stays yours.
  • Design-time AI, separable from the runtime. Let AI help your team design and review, and decide separately whether the running service uses AI steps at all.

Rules when you need them

Switch on No-AI mode for an organization or a whole installation and every decision follows rules your team approved. The platform refuses AI routes while you build and AI steps when you save and run. Intent matching, menus, forms, knowledge answers and integrations keep working. In No-AI mode, for a given published version, input and data, the outcome is the same.

Delivery

Our team in Australia designs, builds, hosts and supports Camlin Connect, and has built IVR and service-automation platforms since 2011.

Accessibility

Wheelchair Book & Ride, Sydney’s booking service for wheelchair-accessible taxis, operated by SCIA and funded by Transport for NSW, takes bookings by voice, web and mobile and is built to WCAG 2.1 AA. Read the case study

Deployment options

Hosted where you need it

Every organization is recorded with one of four deployment kinds. The status says what is live today and what we deliver with your team.

  • Shared platform

    Live

    Our US platform in N. Virginia with its own sign-in and data stores, or our Australian platform in Sydney. The fastest path to a working service.

  • Dedicated host

    Live

    Single-tenant compute and storage for one organization, operated by Nuamedia. Separation without running it yourself.

  • Your cloud

    Delivered with your team

    The platform installed in your own cloud account, under your network boundaries and monitoring. Planned and delivered with your team.

  • Disconnected install

    Delivered with your team

    For networks that cannot depend on the internet. Licenses are signed files verified locally, with no activation call. Planned and delivered with your team.

Where your data lives

  • US accounts are hosted in AWS US East (N. Virginia), speech included. VoiceID, billing, website enquiries and picture-to-3D jobs are kept in Sydney.
  • The exceptions, stated plainly: AI model providers when you use AI, and our stock avatar voices, which are made by a speech provider outside the United States. With No-AI mode on, AI steps are refused, so decisions do not go to a model provider.
  • Installs in your environment keep data inside your boundary. The privacy policy lists what is kept where, and the deployment page has the detail.

Next step

Book a briefing

Tell us the service, the hosting model and the rules you need to meet. We will show it running.

Telecommunications