Miniature model: four brass channels across a navy plinth, carrying paper tokens to four small paper houses.
Example workflow · Illustrative demo4 running todayFor Commercial heads, admissions offices, sales teams and front desks

D · Smart CRM & Lead Operations

Every enquiry answered, assigned and followed.

Enquiries from WhatsApp, the website, email and the phone land in one inbox. Each gets an answer from your own price list and policies, an owner and a next step.

Illustration

01 · The problem

Enquiries wait for hours, or are lost between personal phones and a shared inbox.

Nobody can say how many came in last week, who answered them, or what became of them.

Who it is for: Commercial heads, admissions offices, sales teams and front desks.

02 · How it works

The workflow, stage by stage.

  1. 01An enquiry arrives on any channel
  2. 02Answered from your price list and policies
  3. 03Assigned to an owner with a next step
  4. 04Follow-ups scheduled
  5. 05Won or lost, with the reason recorded

03 · Try it

Enquiry desk, with sample data.

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

Enquiry desk · Illustrative demo
Enquiry desk · yesterday
Arrived
41 enquiries: WhatsApp 26, web form 8, email 5, phone notes 2
Answered
39 within 15 minutes; 2 waiting for a price from the workshop
Assigned
Every enquiry has an owner and a next step
Booked
6 measurement visits, 4 campus visits

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.

Enquiry desk · yesterday
Arrived
41 enquiries: WhatsApp 26, web form 8, email 5, phone notes 2
Answered
39 within 15 minutes; 2 waiting for a price from the workshop
Assigned
Every enquiry has an owner and a next step
Booked
6 measurement visits, 4 campus visits

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

  • Customer assistantsAnswers on WhatsApp, Instagram, website chat, email and SMS from your own price list and policies, with the draft and its sources in view.
    Running
  • Team inboxEvery channel in one inbox, with an owner on each conversation.
    Running
  • Customer memoryEach customer’s history, preferences and past orders in one place.
    Running
  • Bookings, offers and reviewsVisits booked, offers sent and reviews asked for from the same record.
    Running

Explore what we can build

  • Sales pipelineEvery enquiry with a stage, an owner and a next step; quotations sent from the record.Your DS or your own servers
    Planned
  • Appointments and schedulingBookings against real availability, reminders sent, cancellations refilled from a waiting list.Your DS or your own servers
    Planned
  • Loyalty and repeat businessCustomers recognised, rewarded and reminded at the right moment.Needs an outside service
    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 commercial head which enquiries have waited too long, and why.

Atelier OS

A won enquiry becomes an order or an application on the same record, with its history attached.

Where it runs

The assistants draft their answers with a cloud AI service, named in your data schedule; the messages themselves travel through WhatsApp and email.

Connections

Meta’s WhatsApp and Instagram APIs, email, SMS and your website chat. Each connection is listed in your data schedule.

07 · Proof

Every enquiry in a university’s admission intake answered and given an owner.

A university · University · a client, not named

Read the case