Servly

Workflow engine: e‑services the persona can actually finish

Answering questions is half the job. People come to get something done: renew a licence, book an appointment, update their details. Design those services once in a visual builder, and the persona runs them in conversation on every surface.

Animation: a request moves through a service. It fails validation once and retries, detours to answer a side question, passes a one-time passcode check and a condition, calls your system's API, and finishes by sending a webhook.

Four building blocks

Drag them onto the canvas, connect them, and write each prompt in Arabic, English or both.

Step
One screen of the service: an introduction, then the inputs you need, asked one at a time or grouped into a short form.
Condition
Branch on what someone answered: equals, contains, greater than, is empty and the other common checks.
API call
Call your own system with the answers so far: method, headers, a templated body, response mapping and a timeout.
End
Close the service with a confirmation and send the completed submission to your systems by webhook.

Inputs can be text, number, email, phone, date, choice or a one-time passcode. When a step needs video, the engine generates the introduction and prompt clips in the persona's own voice.

34 validation rules, written for the region

Every input can carry its own rules and its own error message in both languages, so people hear exactly what to fix.

Identity across the GCC

  • Emirates ID
  • Saudi national ID
  • Qatar ID
  • Bahrain CPR
  • Oman ID
  • Kuwait civil ID

Phone numbers across the GCC

  • UAE
  • Saudi Arabia
  • Qatar
  • Bahrain
  • Oman
  • Kuwait

Dates

  • In the past
  • In the future
  • Minimum age

Everything else

  • Required
  • Email
  • URL
  • Length
  • Range
  • Pattern
  • Starts or ends with
  • Numbers only
  • Letters only

How the persona runs a service in conversation

The flow you design becomes a conversation, not a form bolted onto a chatbot.

  1. 1

    Find

    The persona matches what someone asks to the right service, using each flow's name and trigger phrases, with Arabic spelling variations normalized.

  2. 2

    Offer

    It proposes the service in plain words and waits for a yes. A bare “no” never cancels a service someone has already started.

  3. 3

    Collect

    Each answer is checked as it arrives. If it doesn't pass, the persona explains why and asks again, without losing the answers already given.

  4. 4

    Detour

    If someone stops to ask a side question, the persona answers it and then brings them back to the step they were on.

  5. 5

    Finish

    On completion the submission goes to your systems by webhook, retried with backoff if your endpoint is busy. Abandoned services are recorded too.

See where people drop off

Every step, input, retry and API call is tracked, so you can fix the question that loses people instead of guessing.

  • Completion funnel for every step: how many entered, how many finished, how long they took
  • Which inputs fail validation most and how often people retry
  • Peak hours, trends over time and API call results
  • Every submission with its answers, for inspection or export to CSV or JSON

Bring one service to the demo

Pick the e-service your customers ask about most. We'll build it in the workflow engine with you.

Book a demoRead the docs