Use cases

Anywhere people describe something your software needs as fields

One engine, any schema. Some workflows below have a built-in example schema you can try right now; the rest are a custom schema away — define the fields in the builder and test them with your voice.

Example schema · try it

Logistics & delivery

Turn a spoken delivery request into a complete order.

The problem: Delivery requests arrive as phone calls and WhatsApp voice notes. Someone has to listen, re-type addresses and phone numbers, and call back for what was missed.
The benefit: Orders arrive structured and validated; staff review instead of re-typing.

Try it live See how it works

What someone says

«مرحبا، بدي أبعث طلب من مطعم حمادة بالجبيهة للشميساني، المستلم أحمد ورقمه 0791234567، وإذا ممكن يوصل قبل الساعة خمسة.»

“Hi, I want to send an order from Hamada restaurant in Jubeiha to Shmeisani — receiver Ahmad, 0791234567 — before five if possible.”

What your software gets

delivery_order

{

"pickup": "مطعم حمادة - الجبيهة",

"dropoff": "الشميساني",

"receiverName": "أحمد",

"receiverPhone": "0791234567",

"timePreference": "قبل الساعة 5"

}

Example schema · try it

Restaurants

Spoken orders become items, quantities and notes.

The problem: Phone orders are fast for customers and slow for staff: items get misheard and quantities get lost between the call and the kitchen.
The benefit: Kitchen-ready tickets with quantities verified against what was said.

Try it live See how it works

What someone says

«بدي ٣ شاورما دجاج و٢ بطاطا، والتوصيل على خلدا.»

“I'd like 3 chicken shawarma and 2 fries, delivered to Khalda.”

What your software gets

restaurant_order

{

"items": [{"name": "شاورما دجاج", "quantity": 3}, {"name": "بطاطا", "quantity": 2}],

"address": "خلدا"

}

Custom schema

E-commerce

Customers describe what they want and where it goes.

The problem: Customers in voice-first markets would rather describe an order or a return than fill a form on a small screen.
The benefit: Requests land in your system as structured records, not transcripts.

Build this schema See how it works

What someone says

«بدي أرجع الجاكيت اللي طلبته مبارح، القياس صغير، وخلي المندوب ييجي عالبيت بعد العصر.»

“I want to return the jacket I ordered yesterday — it's too small — have the courier come to the house after the afternoon.”

What your software gets

custom schema

{

"request": "إرجاع",

"item": "الجاكيت",

"reason": "القياس صغير",

"timePreference": "بعد العصر"

}

Illustrative output — define these fields as a custom schema to get it. There is no built-in example for this one.

Custom schema

Customer support

Voice requests become structured tickets.

The problem: Support calls end as free-text notes. Categorising and routing them is manual work that delays the answer.
The benefit: Tickets pre-filled with the order reference and a verified phone number.

Build this schema See how it works

What someone says

«طلبي رقم ١٢٤٥٧ وصل ناقص، ما في مشروبات، ورقمي 0781112233.»

“My order 12457 arrived incomplete — the drinks are missing. My number is 0781112233.”

What your software gets

custom schema

{

"orderRef": "12457",

"issue": "طلب ناقص",

"detail": "ما في مشروبات",

"phone": "0781112233"

}

Illustrative output — define these fields as a custom schema to get it. There is no built-in example for this one.

Example schema · try it

Field services

Service requests arrive as structured tickets.

The problem: Customers call to report a fault. Someone writes down the problem, the address and how urgent it is — and calls back for what was missed.
The benefit: Tickets with a verified number, the location as spoken, and an urgency your dispatch can sort by.

Try it live See how it works

What someone says

«المكيف ما بيبرد، أنا بالصويفية قرب مكة مول، اسمي خالد ورقمي 0795551234، والموضوع مستعجل.»

“The AC isn't cooling. I'm in Sweifieh near Mecca Mall — I'm Khaled, 0795551234 — and it's urgent.”

What your software gets

field_service_request

{

"customerName": "خالد",

"phone": "0795551234",

"problem": "المكيف ما بيبرد",

"location": "الصويفية قرب مكة مول",

"urgency": "urgent"

}

Example schema · try it

Booking & reservations

Spoken requests become structured bookings.

The problem: Booking by phone means someone must be free to answer, write it down, and read it back.
The benefit: Relative dates resolved in code from the caller's current time — never guessed by a model.

Try it live See how it works

What someone says

«بدي أحجز عند الدكتور أحمد بكرا الساعة خمسة العصر، اسمي سارة ورقمي 0781234567.»

“I'd like to book with Dr. Ahmad tomorrow at 5 in the afternoon. I'm Sara, 0781234567.”

What your software gets

appointment_booking

{

"customerName": "سارة",

"phone": "0781234567",

"doctor": "أحمد",

"date": "2026-09-25",

"time": "17:00"

}

Example schema · try it

Internal operations

Employees submit forms — like leave requests — by voice.

The problem: Leave requests, incident reports and stock counts are slow to type on a phone, so they arrive late or incomplete.
The benefit: Structured requests from the people doing the work; the end date is checked to follow the start date.

Try it live See how it works

What someone says

«أنا سامر، بدي إجازة سنوية من الأحد للخميس بسبب سفر.»

“I'm Samer — I'd like annual leave from Sunday to Thursday, I'm travelling.”

What your software gets

hr_leave_request

{

"employeeName": "سامر",

"leaveType": "annual",

"startDate": "2026-09-27",

"endDate": "2026-10-01",

"reason": "سفر"

}

Custom schema

Custom applications

Define a schema; let users fill it by voice.

The problem: Every business has its own forms. Building speech recognition, understanding and validation for each one is a project of its own.
The benefit: Your fields, your validation rules — one API.

Build this schema See how it works

What someone says

«اسم الزبون خالد، رقمه 0795556677، بده عرض سعر لتركيب طاقة شمسية بالسلط.»

“Customer Khaled, 0795556677, wants a quote for a solar installation in Salt.”

What your software gets

custom schema

{

"customer_name": "خالد",

"phone": "0795556677",

"request": "عرض سعر طاقة شمسية",

"city": "السلط"

}

Illustrative output — define these fields as a custom schema to get it. There is no built-in example for this one.

Have a workflow in mind?

Tell us what people say and which fields you need. We'll show you how the schema would look.

Request a demo See how it works