Aokie

What is Aokie?

Aokie connects an existing mobile phone to a Windows computer through a supported external USB Bluetooth adapter. The phone retains its number and remains the device that receives the call. Aokie supplies call control, audio handling and the configured AI voice conversation through an OAIY-managed plugin.

The connected front desk is a SoftN application hosted by FormLogic. Calls, transcripts, messages, appointment requests and follow-up work can be viewed alongside other business records. The result joins the phone conversation to an operational workflow rather than treating it as an isolated chat session.

From a ringing phone to an app record

The plugin receives call control and audio over its supported Bluetooth path. Speech recognition turns the caller’s audio into text, a configured language model selects a response, and text-to-speech plays the reply. The local path uses separate speech and model services. Remote providers can be selected deliberately, with the corresponding data leaving the machine.

Aokie emits durable events for the connected application. A write-before-emit outbox, acknowledgements, replay and idempotency support delivery across interruptions. That mechanism helps retain events and avoid duplicate records; it does not remove the need to monitor a disconnected host or a failing integration.

• Answer, reject, end and initiate supported calls from the console.
• Capture caller and assistant transcript turns with interruption context.
• Collect appointment requests for a reviewed confirmation workflow.
• Prepare SMS drafts and send through the configured approval path.
• Inspect phone state, local service readiness and event delivery backlog.

An editable front desk, not a fixed call log

The Aokie starter organises Calls, Appointments, Messages, Transcripts, Follow-ups and Device logs. Its SoftN source can be downloaded and edited. The same forms can also be shared into another FormLogic application so an existing business workspace gains a front-desk view instead of a separate island of records.

Authentication belongs to the host session and is not embedded into the downloadable client. App permissions and event-to-flow bindings still need to be reviewed when composing workspaces. Sharing a form is not the same as automatically transferring every automation that can act on it.

Hardware and behaviour must be tested together

The managed beta targets Windows 10/11 x64 and a supported external USB Bluetooth adapter. The voice path uses a specialised dongle transport, and the hardware guide explains driver changes and restoration. Compatibility depends on controller firmware, audio endpoints, the phone and the mobile network. “Any Bluetooth adapter” is not a supported blanket claim.

Auto-answer is opt-in. Begin with manual test calls, confirm speech and transcript delivery, and then enable the behaviours needed by the business. Call waiting, holding and automated callbacks need validation on the actual handset and carrier. Code-level tests do not establish that every radio and network combination behaves the same way.

Requests, approvals and privacy boundaries

An appointment request is not a confirmed booking. The captured name, service and proposed time must be checked by staff or an intentionally configured backend workflow. A spoken readback from a language model does not prove that a time slot is available or reserved.

Similarly, an SMS marked sent means the phone accepted the operation; it is not a carrier delivery receipt. The application should preserve these distinctions so staff can make decisions from the actual state rather than a reassuring but misleading label.

Local speech and model processing are available, but local-first does not mean data can never leave the computer. Remote endpoints receive the text or audio needed for their configured operations. FormLogic may store the resulting business records on its host. Review consent, retention and access rules for the deployment.

Plan a supervised pilot

Check the hardware guide, install OAIY and the Aokie plugin, configure the speech and model services, and pair the intended phone. Install the FormLogic receptionist starter and review its settings and flow bindings. Make test calls and send test messages only with participants and numbers under your control.

Keep the local computer running, monitor the plugin and verify that events reach the intended app. Aokie is proprietary, pre-1.0 software with explicit hardware-beta limits. Release packaging, signing and compatibility should be checked before a wider deployment.