SDKs for apps: ORYKSA inside your own application, for customers only
By Weslley Harakawa
Many businesses already have their own app. ORYKSA's client SDKs put ORYKSA inside it, so that business's customers talk to the employee without leaving the application.
What the SDKs do
Text chat, voice with the universal engine (the same listening, the same cut, the same whisper) and the employee's spoken voice. The developer embeds a chat view or a voice screen and ORYKSA handles the rest: transcription, reply, voice and records in the business's Activities.
What the SDKs do not do
The SDKs serve customers. They do not expose the owner's tools: they do not create or edit Activities at the app user's request, they do not show the dashboard, they do not give access to other conversations. The separation is enforced on the server, with client keys that are different from the owner's keys and request limits per session.
Public API
Underneath the SDKs is the public client API, with sessions, messages, spoken voice and audio quality telemetry. Anyone who prefers can call the API directly. The developer documentation is at developer.oryksa.com.
The same employee everywhere
A customer who talks to the employee in the business's app is the same contact who writes on WhatsApp: history and rules are shared, and the business keeps seeing everything in its dashboard.
