The Servly platform · partner briefing
One engine behind every conversation
Servly answers from your customer’s approved knowledge, completes their e-services, and meets people as an avatar, a copilot or text, in Arabic and English.
Conversation agentKnowledgeWorkflowsAvatar personaCopilotAnalytics
The platform at a glance
Surfaces change; the knowledge, services and rules stay in one place
SurfacesHumanoid avatar · browser copilot · Mendix apps · messaging and phone (early access)
Conversation agentDetects intent · asks to clarify · remembers · switches language · hands over
Knowledge · WorkflowsApproved Q&A and gap tracking · visual e-services with validation
ProvidersLanguage model · speech-to-text · voice · avatar video, swappable
Your systemsAPI calls · webhooks · REST API · CSV and JSON exports
Why customers buy
Six problems the platform takes off the front desk
Repeated questionsStaff answer the same things all day.
Inconsistent answersEvery answer is the same approved text and video.
Many dialectsArabic varieties and English, even mixed.
After hoursAvailable whenever the screen is on.
Services need a visitThe persona completes the request itself.
No insightEvery question and drop-off is measured.
The conversation agent
It decides how to handle every message
Detects what people wantAsks before it assumesRemembers the sessionSwitches Arabic and EnglishHands over to a person
Search answersSearch servicesOffer a serviceStart · advance · cancel
Play an answer or stepAsk to clarifyRemember and recallLog a knowledge gap
Agent mode: eight audited tools that stay inside the customer’s tenant.
Knowledge
Documents become an approved answer library
Any content. PDF with OCR for scans, Word, Excel, text and images.
AI drafts and audits. Bilingual Q&A from documents; weak questions flagged and refined.
The team decides. Suggestions are approved or rejected before going live.
Personality. Recorded greetings, thanks, goodbyes and “not my area” replies.
Answering
It answers from approved content, or says it doesn’t know
Speech to text→
Meaning + keywords→
AI picks the best of 10→
The approved video plays
No confident match→
Logged as a gap→
Answered once→
Known from then on
Workflows
Most assistants stop at answers. Servly finishes the job.
A licence renewal, a booking, an application: the persona offers the service, collects and checks every answer, and hands the result to the customer’s systems.
StepAn intro and its inputs
ConditionBranches on answers
API callAsks their system
EndSends the submission
The workflow builder
A licence renewal, drawn on the canvas
Start→
Applicant details→
Verify (passcode)→
Check eligibility→
Eligible?
YesUpload documents→Webhook
OtherwiseExplain why not→Logged
Auto-layout, a Test button for API calls, and a Run button to try the whole flow before launch.
Inputs and validation
Every answer is checked before the next question
TextNumberEmailPhoneDateChoiceOne-time passcodeFile upload
34ready-made rules
- 19 general: required, length, pattern, ranges
- 3 dates: past, future, age limits
- 6 national IDs, one per GCC country
- 6 mobile formats, one per GCC country
Please enter a valid mobile numberيرجى إدخال رقم جوال صحيح
A workflow in conversation
Five stages, from a question to a finished request
- FindSpots a service in the question or its trigger words.
- OfferAnswers, then offers to do it now.
- CollectAsks each question, checks each answer.
- DetourAnswers a side question, then resumes.
- FinishConfirms and sends the submission.
Connecting to their systems
Workflows talk to real back ends, safely
API call node. Method, URL, headers and body from the answers so far; reply fields feed conditions.
Resilient. Timeouts, continue on error, and a Test button in the builder.
One-time passcodes. Six digits, five minutes, limited attempts, single use.
Webhooks. Completed and abandoned events; HTTPS only, retried, never to private addresses.
Every submission also exports as CSV or JSON. The customer’s system stays the system of record.
The flow recorder
Walk through the e-service once; Servly builds the workflow
- RecordAn admin clicks through the real web form.
- BuildFields become steps and inputs, ready to edit.
- VoiceThe avatar’s lines are pregenerated per step and language.
- GuideThe copilot walks users through the real page.
It records labels and page structure, never the values typed.
Analytics
What people ask, what works, and where services lose people
Usage. Sessions, questions per session, voice versus typed, sites and screens.
Answer quality. Matches and score per answer, answers people leave after, coverage.
Workflow funnel. Starts, completions, abandonments, drop-off per step.
Inputs and APIs. Failed checks and retries per input, API success, peak hours, exports.
The persona
A face and a voice, from one photo
From a real person. A portrait is animated into a natural idle loop.
Or generated. Describe the look; AI creates the persona.
Voice. A custom voice, or a standard one matched to the avatar.
Lip-sync. Every recorded answer and step is lip-synced to that voice.
Languages
Arabic first, English always
Modern StandardEmiratiSaudiQatariKuwaitiBahrainiOmaniEgyptianLevantine
People can mix Arabic and English in one sentence. Workflows can be Arabic, English or bilingual; the on-page copilot also speaks Urdu.
Where it runs
One engine, every place people meet it
Website. A floating launcher, added with two lines of HTML.
Holobox and kiosk. Full-screen mode for cabinets and lobby screens.
Browser copilot. The face rides an AI cursor that points, highlights and fills forms.
Mendix apps. Widgets and example pages in the Syntiva DevKit.
A person, when needed: with Pairly, an agent joins live on the same page.
What customers manage
One console for content, persona, services and teams
Knowledge. Documents, Q&A tools, suggestions, intent replies, gaps.
Workflows. Canvas, submissions, analytics, test runs, clip generation.
Persona. Avatars, voices, dialects and the Playground.
Delivery and team. Embed code, copilot workspace, providers, roles, embedded agent console.
console.syntiva.tech
Security and governance
Safe to put in front of the public
Tenant isolation. Every record and search index belongs to one customer.
Scoped keys. Embed keys tied to one knowledge base and listed domains.
Protected admin. Behind single sign-on access control; roles per product.
Safe webhooks. HTTPS only, never to private network addresses.
Spend caps. Daily AI limits per knowledge base.
Privacy and audit. Contact details redacted, encrypted in transit, audit logs.
Next steps
Start with one place, twenty questions and one service
- Build
- One demo for your sector: top questions and one workflow, in Arabic and English
- Demo
- Their real questions, a service completed live, a gap answered
- Pilot
- One place, a short fixed period, agreed measures
avatar.syntiva.tech · console.syntiva.tech · cobrowse.syntiva.tech