One voice.
Every step behind it.

VOCA answers from knowledge you approve, turns requests into tasks and brings your team in at the right moment.

A request passes through three layers: the knowledge it is answered from, the action that records it with an owner, and the handoff to a person when needed.
Fig. 01 — One request, three layers

Illustrative

How it works

From a first message to a closed request.

Five steps, the same in every industry. Each one shows what the customer sees and what your team sees.

Step 1 of 5

Open

The customer opens VOCA from a link or QR code and picks English or Arabic. Where identity matters, access is checked before anything is shown; in hotels, against a current stay.

Customer · startPhone

Where identity matters

Checked first

Continue

Team · overviewWorkspace

Access
Verified
Language
Arabic or English
Ends
When the stay or case ends
Illustrative screens — sample content

01 / Capabilities

Knowledge. Action. Handoff.

Three things every conversation needs, set up around your business.

01

Grounded in your knowledge

VOCA answers from the services, hours, policies and rules you approve. If it does not know, it says so and offers your team.

  • Guided setup — no prompt writing
  • Instructions generated and versioned for you
  • Facts live in one place, not in the model

02

Connected to the next step

A request becomes a task with a reference, the customer or location, an owner and a deadline. VOCA says it is sent only after it is recorded.

  • Paid or binding actions ask for confirmation first
  • Repeats never create duplicates
  • Switched-off services are refused, everywhere

03

Your team stays involved

Staff see every conversation, take over at any moment and leave private notes. VOCA stops answering while a person is helping.

  • Takeover and return to VOCA
  • Overdue requests flagged for escalation
  • Internal notes never reach the customer

02 / The customer experience

Speak. See. Confirm.

While the customer talks, the right card appears: hours, a code, the status of a request. Typing works too, in English or Arabic.

  • Cards come from the same record the voice uses, so what is said and shown never differ
  • Sensitive details, such as a Wi-Fi password, are shown only to a verified customer — never spoken
  • Arabic and English, with full right-to-left layout
Review before sendingAwaiting confirmation

Callback — Tuesday, 5 pm

This sends a request to the team. Price and availability are confirmed by staff — it is not a confirmed booking.

Confirm requestChange

Illustrative card

03 / Honest by default

Never “done” before it is.

Every request has a real status from a real record. If something cannot be done, VOCA says so and offers your team.

See how it is controlled →
Request lifecycleReal statuses
1

Received

Recorded with a reference. The customer is told it was sent.

2

Accepted

A team member takes it, within the time you set.

3

In progress → Completed

Or Not possible / Cancelled, with the reason shown honestly.

04 / The team workspace

Every conversation. In view.

A three-pane workspace for the people who act on requests.

Requests

Filter by status, department or location. “Needs attention” shows what is overdue.

Conversation

The customer’s messages and your replies in one thread, refreshed live.

Takeover

Take the conversation, reply as a named person, and hand it back when done.

Private notes

Notes for colleagues stored separately — there is no path for a customer to read them.

05 / Setup

Set up. Check. Launch.

You choose services and facts in plain forms. Vocalabs writes the instructions, checks them and launches only after approval.

  1. Choose your services

    Switch services on or off, add hours and locations, choose who owns each request.

  2. Instructions are generated

    No prompt to write. Secrets and live facts are never placed in the instructions.

  3. Quality check

    Missing facts are named as blockers. Services that need a connection are flagged.

  4. Approve and publish

    Versions are kept. Roll back to an earlier setup at any time.

06 / What is included

Available today. Scoped in a pilot.

We separate what works now from what depends on your systems.

CapabilityStatusNotes
Knowledge from approved sourcesAvailableServices, hours, locations, policies and rules.
Voice and typed customer screenAvailableContextual cards, English and Arabic.
Requests, statuses and team workspaceAvailableAccept, escalate, take over, private notes.
Verified customer accessAvailableVerified before anything is shown. For hotels, tied to a current stay and ending at checkout.
Property, booking and billing systemsScoped in pilotNot connected by default. Until connected, these services create staff requests, not bookings.
Telephone linesScoped in pilotDepends on your provider and numbers.

Next step

See it on your own use case.

Tell us what your first agent should help with.