Miniature model: a maze of navy walls; paper tiles travel along the corridors toward the rooms.
Example workflow · Illustrative demo4 running todayFor Customer service teams, front desks and branch managers

I · Customer Service & Voice

Every customer message answered, in the customer’s language.

Messages, emails and voice notes in one inbox. Voice notes in Urdu and English are transcribed, and replies are drafted from your own policies for a person to approve, unless you agree otherwise in writing.

Illustration

01 · The problem

Voice notes go unheard until someone has a quiet moment. Complaints are answered by whoever sees them first, or not at all.

Answers differ by who replies, because nobody checks the policy.

Who it is for: Customer service teams, front desks and branch managers.

02 · How it works

The workflow, stage by stage.

  1. 01Message or voice note arrives
  2. 02Transcribed; doubtful lines marked
  3. 03Reply drafted from your policies
  4. 04A person approves
  5. 05Complaint owned and timed

03 · Try it

Voice note to reply, with sample data.

An illustrative demo for a fictional organisation. Click through it; nothing is sent, paid or changed anywhere.

Voice note to reply · Illustrative demo
Voice note · 0:41 · Roman Urdu
Transcript
Asks whether the alteration can be ready by Friday; one line marked doubtful
Draft reply
Alterations take 3 working days (sample policy §2.1); Friday is possible if dropped off by Tuesday
Owner
Farah, workshop · reply approved 11:12

Example output · sample data for a fictional organisation

04 · Example output

What lands on someone’s desk.

The kind of page this module produces each day, shown with sample figures.

Voice note · 0:41 · Roman Urdu
Transcript
Asks whether the alteration can be ready by Friday; one line marked doubtful
Draft reply
Alterations take 3 working days (sample policy §2.1); Friday is possible if dropped off by Tuesday
Owner
Farah, workshop · reply approved 11:12

Example output · sample data for a fictional organisation

05 · Capabilities

What runs today, and what we would build.

Status as of 4 October 2026.

  • RunningIn daily use, in our own organisations or at a client.
  • Done onceA service delivered once, as a written finding.
  • PlannedIn our planned range. Intended, not yet built.
  • ConceptAn idea shown to explore what we can build.

Running today

  • Team inboxEvery channel in one inbox, with an owner on each conversation.
    Running
  • Voice notes readerUrdu and English voice notes transcribed. Short Urdu clips can come back garbled, so doubtful lines are marked.
    Running
  • Voice copilotBriefings and answers for the owner by voice.
    Running
  • Customer assistantsDrafts from your own policies on WhatsApp, Instagram, website chat, email and SMS; your team sees each draft and its sources.
    Running

Explore what we can build

  • Voice deskVoice notes and calls turned into text on your premises; replies read aloud.Intended to run on your DS
    Planned
  • Phone assistantCalls answered at any hour, routine questions handled, the rest passed to a person with a note.Needs an outside service
    Planned
  • Feedback and complaintsEvery complaint logged, owned and timed; patterns reported monthly.Your DS or your own servers
    Planned

Nothing in this list is claimed as running. Each would be scoped in a written finding and delivered one department at a time.

06 · How it connects

Part of one record, not a separate tool.

Tracer

Tracer tells the manager which conversations have waited too long.

Atelier OS

Each conversation is linked to the customer’s record and orders.

Where it runs

The voice desk is planned; where voice notes would be transcribed is written into your data schedule. A phone assistant needs an outside service, and your data schedule says so.

Connections

WhatsApp, email and your website chat; a phone line only through an outside service.