Arkan · the platform

Intelligence in motion.

Six functions, one orchestrator.

Arkan runs 24/7. Pick a lead to follow its journey, or select any part of the system to see what it does.

Illustration: sample leads and values, not client data. Solid edge: live · dashed: in build · faded: next.

Sample

0255075100

20 / 100 · Cold

Phoenix is on a call with Lead A, qualifying intent, direction and desire.

Came in via web chat

Lead A · journeySample

HermesInquiry form+10
HermesContact info+10
PhoenixPhoenix call+25
ChronosTour booked+15
AtlasDocuments+20
MaestroBrief sent
NexusPayment link
NexusPayment cleared+10
NexusPaid and enrolled+10

Lead A · failedIllustrative

FailedFollow-upRe-enter

Lead A has no failed engagements in this run.

Orchestrator / Maestro

Orchestration

In progress

The control layer over the whole platform. Maestro is the orchestration intelligence, running on a CRM that is not just a system of record but a system of intelligence: one control surface where every activity is logged and visualized, the knowledge base runs, and the institution runs the entire platform from a single place.

Receives: Every outcome from every agent, the moment it happens.
Does: Scores it, decides the next step, and routes the lead to the right agent or to follow-up.
Passes on: The lead to its next agent, and a brief to the enrollment team once it is hot.

How it works

Sees every activity across all agents in one control surface
Routes each lead, applicant, and payer to the right agent and stage
Hands off between agents and people without dropping context
Deploys as your system of record, or a layer over your existing one

Connects to

Your CRM

Salesforce

HubSpotEvery agent

Replaces operations and coordination roles

Connects to every agent. Deploys as 36nine's own CRM and system of record, or as a control layer over your existing CRM and systems.

How we built Arkan

We built Arkan the way we build for clients.

Arkan started as one system for one client, not a platform. What worked became Arkan. What did not was rebuilt until it did.

Strategy-led

Every build starts from a business case.

The first build solved one problem worth paying to fix: inquiries that went unanswered, and the leads lost in the gaps.

Data-driven

Decisions come from the numbers, not a deck.

We keep what moves a number and rebuild what does not. An early voice agent reached fewer than one in ten of the calls it placed, so we rebuilt it. Connect rates climbed into the thirties, and held.

In production

Systems your team runs daily, not pilots.

Every agent is built inside a live operation and corrected until it runs on its own. We ship the part that is ready, prove it, then build the next.

The platform

Three in production, three in build, one next.

Live today, running in real operations

Inquiries Hermes answers every channel, at any hour.
Voice Phoenix places calls and qualifies leads in conversation.
Scheduling Chronos books visits and meetings end to end.

In build, shipping into the same system as each one proves out

Orchestration Maestro
Applications Atlas
Analytics Apollo

Coming next

Payments Nexus

Maestro is the orchestrator: as each function ships, it joins the same ring and runs as one system.

The platform grows in the open. Arkan website

Built and run by 36nine.

See it running against your own numbers.

Book a strategy session→