Logistics
Aligning the week's deliveries
Deadline, dock and owner come out in ten messages, and when it's time to follow up nobody can find who took what.
Summary with decisions and owners
Platform · Messages
The team talks. The AI answers when called.
Direct conversations and group rooms, with people and agents. Call an agent or a team with @ and the answer lands in the same discussion, with the access of whoever asked.
See how it worksSkyller · Messages · Weekly deliveries
Messages · Weekly deliveries
Skyller Messages screen: on the left, the conversation list, with rooms and colleagues; next to it, the Weekly deliveries room, where Bruno, Carla and Diego agree on Aurora's delivery. Ana calls the Logistics Analyst with @ to summarize what was decided; the agent works and answers in the conversation, quoting the request, with Ana's access.Demonstration · illustrative data
PEOPLE AND AGENTS
in the same conversation
@ CALLS THE AI
it acts only when someone asks
WITH THE ACCESS OF WHOEVER ASKED
what not everyone can see goes only to whoever asked
READ BY 3
who read it and how far
In your day
The agreement that gets lost in the chat today.
Sales
Preparing the reply to the client
Aurora asks for a new date, three people share opinions in the room and someone still has to write the email.
Email ready for your approval
HR
Settling a policy question on the spot
Someone asks in the room how reimbursement works. The answer comes from the company policy, not from whoever happens to be online.
Answer with the asker's access
How it works
From conversation to request, in six steps.
01
Open the conversation
New conversation talks to one colleague; New room brings a group together, with a name and up to 200 participants across people, agents and teams.
02
Invite who takes part
A room is invite-only. Whoever joins later doesn't see the history from before they joined, and only the person who created the room removes participants.
03
Call the AI
Type @ or use Call agent or team. The agent joins the room if it isn't there yet, and the request goes out only when you send the message.
04
Get it in the discussion
The answer comes in the request's discussion. Before showing it to everyone, Skyller checks every source against every member of the room.
05
Decide what is sensitive
A sensitive action opens an approval card in the discussion. Only whoever asked sees Approve and Decline, and the card expires in 30 minutes.
06
Follow along
Read by N shows who read and how far, presence shows who is online, and whoever was mentioned gets the notice in Skyller.
Live proof
The AI answers with the access of whoever asked.
Ana asks
In the Weekly deliveries room, inside the discussion: “@Logistics Analyst prepare the email telling Aurora about the new delivery date.”
What happens
- 01The agent reads the discussion where it was called and drafts the text, with Ana's access.
- 02Skyller checks the sources against every member of the room. The carrier contract isn't open to everyone: the reply goes only to Ana, with the reason.
- 03Sending is a sensitive action: the approval card appears in the discussion. Only Ana sees Approve and Decline; the others see “Waiting for Ana's approval”.
Result
Ana decides whether to publish the reply to the room and whether the email goes out. The actions are recorded.
Skyller · Replies · Weekly deliveries
Replies · Weekly deliveries
Ana@Logistics Analyst prepare the email telling Aurora about the new delivery date
Logistics AnalystAI agent
Reply sent only to youThe reply used the carrier contract, which not everyone in this conversation can access.When you publish, everyone in this conversation will see the reply, including people who can't access the sources.
Send email to the clientTo: compras@aurora.example · Subject: New delivery dateThe card expires in 30 minutes.
Demonstration · illustrative data
Waiting for Ana's approval
Good to know
- The approval card expires in 30 minutes, and the window to publish the reply to everyone ends after 7 days.
- Publishing to everyone warns that the whole room will see the reply, including people who can't access the sources.
- Of the room's attachments, the AI receives only the file name.
Capabilities
Everything Messages already does.
Select a topic to see its capabilities, conditions, and limits.
- Direct conversation
- New conversation opens a dialogue with one colleague and reuses whatever already exists between you. You can also start from People, with Send message. In the phone browser, one area shows at a time.
- Group rooms
- New room asks for a name, and whoever creates it is already a member. Up to 200 participants fit, across people, agents and teams. For a private conversation with the AI, the path is Chat.
- Replies, discussions and reactions
- Reply by quoting the message: the quote follows the original and shows “Message removed” or “Message unavailable” when it goes away. Open a discussion (“View discussion · 3 replies”) so the topic doesn't cross the room, and react with 👍 ❤️ 😄 🎉 👀 or ✅.
- Attachments
- Any file type, up to 10 pending at a time and 25 MB each; you can also paste from the clipboard. Images open with a preview, and other files show as a card to download. If a send fails, there is Try again or Discard.
- Call an agent or team with @
- Type @ or use Call agent or team, next to Attach file. Only active agents and teams the person can access appear; workflows can't be called from here. Picking one inserts the mention in the draft and adds the AI to the room, but nothing goes out until the person sends.
- The AI acts when someone asks
- It acts only when a person sends a text message that mentions it. Otherwise the room carries on among people, and a card or task is created only if someone asks.
- What the AI reads
- The discussion where it was called: up to the 30 most recent messages (about 12,000 characters), read with the access of whoever asked. In a direct conversation between two colleagues, that conversation. Call the agent inside the discussion for it to read the conversation; a loose mention in the room carries only the request.
- The company's context
- Besides the discussion, the agent uses the company profile and brand, the documents whoever asked can see, the systems connected to it and its own instructions. Personal profile and memory stay out of Messages. Adding an agent to a room doesn't give members access to its documents, Kanbans or systems.
- Answer checked before it goes to everyone
- Skyller checks every source against every current member of the room. If all can access, all see the answer, with the seal “Answered with Ana's access”. If not, the room sees “Reply sent only to Ana”, with the reason, and only Ana has Show reply (for herself) and Publish to everyone, which is open for 7 days. If the check fails, the answer goes only to whoever asked, for safety.
- Approval, questions and generated files
- A sensitive action opens a card in the discussion: only whoever asked sees Approve and Decline, the others see “Waiting for Ana's approval”, and the card expires in 30 minutes. You can also decide in Skyller's approvals panel. The agent can ask a question on a card that only whoever asked answers, for up to 24 hours. Generated files arrive as files in the discussion, and whoever asked can Stop the answer.
- Presence, reading and notices
- Online, Away (after 5 minutes without interaction), Offline or Presence unavailable, which doesn't mean offline; presence is for people only. On your messages, “Read by 3” shows who confirmed reading and how far, and counts only when the message reaches the screen with the tab in use. When someone mentions you, the notice appears in Skyller; email is optional.
- Invite-only, isolated by company
- Whoever joins later doesn't see the history from before they joined. Adding someone to a direct conversation opens a new room, and the original conversation and its history stay apart. Only the person who created the room removes participants. Data is isolated by company, files open only when logged in, for the room's members, and the actions are recorded.
Real application
One delivery, from alignment to record.
A topic that goes through several people, settled in one room, with the AI called at the right moment and the decisions in the hands of whoever asked.
- 01Administrator
Enables the agents and connectors the logistics area can use.
- 02Logistics
Creates the Weekly deliveries room and invites the team, agents and teams that will take part.
- 03Ana
Calls the Logistics Analyst inside the discussion and asks for a summary of what was decided and who owns what.
- 04Ana
Decides what leaves the discussion: publishes the answer to the room when the sources aren't open to everyone, and approves or declines the sensitive action.
- 05Bruno
Sees “Waiting for Ana's approval” in the discussion and moves on with his part: tells the driver and sends the plate to the front gate.
- 06The team
Follows through “Read by” and Skyller's notices. The actions are recorded.
The company decides
- Which agents and teams exist and who accesses each one
- Which systems are connected to each agent and what it can do in them
- Which documents each person can see, which defines what the AI uses in the answer
- Which actions of each enabled function count as sensitive and wait for approval
Frequently asked questions
What usually stalls the decision.
Next step
Open a room with this week's topic.
Create the room, invite who takes part and call the area's agent inside the discussion. To see it with your company's data, talk to a specialist or start the free trial.