SOCLOUD
Clientlogin Start a project

Agents, by SoCloud

A bench that works the hours you don’t.

Your factories, forwarders and vendors answer while you sleep. Agents read what comes in, draft the changes with their sources attached, and have it waiting when you wake up. Nothing is saved until a person ticks it.

01 / One night

The update is already in a thread. Someone has to read it.

This is one night with the bench as it’s built to run, told on a sample order. Today Agent 001 is in beta and checks hourly on weekdays. Times are Los Angeles.

  1. Theirs starts.

    It’s morning at the factories. Replies to today’s questions start landing in email, in the team channel and on the task board.

  2. Logistics reads.

    It goes through the freight threads and the carrier updates. It reads. It never writes back as you.

  3. A date slips, and a draft appears.

    The forwarder says a sailing rolled. The agent drafts the change, PO-27014, ETA Nov 12 to Nov 18, with the message it came from.

  4. Paperwork arrives.

    A packing list and a vendor invoice come in. Intake reads them into fields and matches them to the order.

  5. One page, before the first coffee.

    What’s true now, what moved overnight, and what needs a person.

  6. A person ticks.

    You read the drafts and tick the ones that are right. Each tick updates the record, and the history says who did it.

02 / The bench

Four agents, named for their jobs.

No mascots. Each one has a number, a job and an honest status: live, in beta, or still being built.

Agent 001Beta
Logistics

Reads freight threads and carrier updates. Drafts ETA, vessel, container and status changes for a person to tick.

Reads
Email, Slack and ClickUp
Drafts
Shipment updates, new shipments, risks
Checks
Hourly on weekdays, while in beta
Today
In beta, running with one team
Agent 002Live
Intake

Reads documents into the record, so nobody retypes an invoice or a packing list.

Reads
Invoices, packing lists, labels and tags
Drafts
Fields matched to the order
Then
A person confirms before anything posts
Today
Live
Agent 003Beta
Answers

Ask a question in plain words. The answer comes from your own records and shows where it came from.

Reads
Your records and documents
Gives
Answers with their sources
Where
Inside your OS
Today
In beta, in testing
Agent 004In development
Production

Will follow sample and production threads with your vendors and keep each development’s status current.

Will read
Vendor threads and portal updates
Will draft
Sample and production status
Today
Being built. Not available yet

03 / Where they listen

Said plainly: what works today.

TodayEmail, Slack and ClickUp

Connected and in daily use. An agent reads the inboxes, channels and boards you point it at.

In developmentiMessage

A lot of real updates live in group texts. An agent that sits in one isn’t built yet.

By forwardingWhatsApp and WeChat

Forward a message or a file and the agent reads it. It doesn’t sit inside those apps.

  • Rule 01Always visible. An agent says hello in a thread and never hides.
  • Rule 02Every draft carries its source: who said it, where, and when.
  • Rule 03Nothing is saved or sent without a person’s yes.
  • Rule 04Every change is logged with who and what, before and after.

Next

Put a bench on your threads.