Skip to content

A message comes in. The collaborator does the rest.

Recognises your customer, rereads their record in your software, answers, and asks you about anything outside its mandate.

Demonstration

WhatsApp · 10:02

Hi, what's the status of my file 2481?

Your customer

The collaborator's report

  1. Customer recognised by their number
  2. File 2481 reread in your software
  3. Answer sent, payment link attached
  4. Reminder set for 23 September

In the name of Your company · 10:02

Your file 2481 is confirmed for 24 September. There is €180.00 left to pay: here is your link.Pay €180.00

One turn, step by step

Every message starts the same turn again. Pick a step: the phone replays it.

Your companyBusiness account
  1. Hi, what's the status of my file 2481?
Demonstration

Its knowledge, your data

Two families that never mix: what you have taught it, and what your software says right now.

Demonstration

A question from your customer

Its knowledge

Frozen at the last collection

Your website, your texts, your questions and answers: collected, indexed, searched in its own words.

Live data

Reread just now

The data of your software, reread by a call at the moment of answering.

Its answer From your software

Your order 10482 is being prepared; delivery expected on 16 September.

Answers without you, and you try it first

Born free: reading in service, writing paused, answers without you. You try its replies in the sandbox, and give it less freedom whenever you want to review.

Demonstration

Drafts, you read, you send. Nothing goes out without you.

Writing into your softwarePausedIt is set separately, gesture by gesture.

  • The sandbox

    The same collaborator, on your real data: only the output is held back. A rehearsal, not a simulation.

  • The trail

    Every step is written down: what was searched, the procedures started, the gestures attempted in your software and what came back.

  • The figures

    Answers proposed, sent as they were, taken over. Sandbox runs do not count.

  • Moving down, always

    At any moment, with no condition. The kill switch is one click away.

Where to speak, and with what freedom

WhatsApp for the moment, email for attachments and records. One thread per customer, whichever way they came.

  1. The collaborator carries its default freedom.

  2. Each channel can refine it: without you on WhatsApp, a proposal on email.

  3. On a thread, you take over, then you hand it back.

Demonstration

The collaboratorAnswers without you

WhatsAppLike the collaborator

Thread · Customer 2479You have taken over

EmailProposes

Takes the initiative too

Your software reports an event, the collaborator starts the conversation. Before anything is sent, Coplace checks five things, in this order.

This step sends nothing: it decides. A refusal gives all its reasons, and a price we do not know is called unknown, never free.

Demonstration
Event received from your softwareOrder 10482 shippedorder.shipped
  1. The contactRecognised by their number
  2. Their consentGiven
  3. A template approved by Meta“Order shipped”
  4. The channelWhatsApp, in service
  5. The costEstimated before sending

May write

The console, to take over

Four areas, nothing more. You see what was settled without you, and you take over in one move.

Demonstration

Today

Done without you

  • File 2481: answer and payment link
  • Order 10482: tracking sent
  • Appointment on the 18th: reminder kept

In progress

  • Follow up on the receipt for file 2466
  • Reminder tomorrow, 9:00 am

For you

Grant a €30 goodwill gesture on file 2481?

Outside the mandate: above €20

Try it on your own software.

Connecting happens from a screen. Writing stays paused until you put it in service.