AI where you
already talk
Appto coworker sits in your Slack or Microsoft Teams — in channels and in direct messages. Wise answers there: the same assistant, the same company context and the same integrations as appto in the browser. Nobody moves their work into a new window.
Meet Wise,the new coworker.
Marta Z.·sales
Hi @Wise, can you work out what Kamex pays over 24 months?
No commands and no syntax — an ordinary sentence in the thread is enough. That is why the whole team writes to it, not the two people who like new toys.
Once in a DM,once in front of the team.
You talk to the coworker the way you talk to anyone in the company: privately when it only concerns you, or in the channel when the answer is useful to everyone. It is the same conversation and the same context — only who sees it changes.
Draft me a reply to the email from Kamex. Firmer, but without straining the relationship.
Done. I kept to the terms in your quote standard and did not go below the margin threshold. The version to send is in the attachment.
Reply to Kamex — v2.docxIn a DM it is just the two of you: Wise knows the company context and your permissions, but nobody else sees the conversation.
Kamex is asking about the date. Does anyone know where we stand?
@Wise check Pipedrive and tell us whether end of September is realistic.
Stage Negotiation, start agreed for 15 September, the rollout standard is six weeks — the realistic date is 27 October.
2 replies in the threadIn a channel the question and the answer stay for the whole team — sources included. The next person does not ask it a second time.
It does not just answer.It does what you ask.
From a thread in Slack or Teams the coworker reaches for the same tools as appto in the browser — reading and writing. The same company skills, the same integrations, the same work; only handed over wherever you happen to be.
@Wise make a quote for Kamex over 24 months, send it to Anna Nowak and set me a follow-up for Thursday.
-
Price list 2026.xlsx
Termfromto12 months4%8%24 months8%12%36 months10%15%read the discount band
-
PipedriveKamex LogisticsPLN 128,400NegotiationQuote over 24 months, 10% discount. Sent to a.nowak@kamex.pl.
added a note and moved the stage
-
Quote — Kamex v4
Cooperation quotePDFQuote — Kamex v4.pdf24 months10% discountassembled the document on your template
-
Gmail
Toa.nowak@kamex.plSubjectCooperation quote — 24 monthsPDFQuote — Kamex v4.pdf318 KBSent · 11:04sent the message with the attachment
-
Marta’s calendar
Thursday, 12 September9:0010:00Follow-up: Kamex10:00 – 10:3011:00set the follow-up for Thursday
Close to a thousand integrations. See what appto does inside tools
Let Wise into one channel
It catches whatyou missed.
The coworker does not only wait to be called. Once an hour it goes through the channels you pointed it at and decides for itself whether it has anything to add. A channel with no new messages costs nothing — the bot does not even ask the model.
Kasia M.·Tuesday, 11:04
Does anyone know whether the Kamex tender needs a bid bond? The submission deadline is tomorrow.
Wise·spoke up on its own
Yes — 3% of the order value, payable by 12 September. It is in the tender docs on page 14, section “Bid bond”. A copy is on the drive in the Tenders 2026 folder.
Tomek W.·Wednesday, 15:22
I promised Velpol a start on 22 September, we will sort it out with the team.
Wise·spoke up on its own
In the schedule Velpol starts on 6 October — 22 September is from the previous version, changed after the meeting on 2 September. Worth confirming before the customer writes that date down.
Marta Z.·Thursday, 9:47
Sitting down to the Velpol quote, it has to go out today.
Wise·spoke up on its own
Piotr sent Velpol a quote on Friday — it is on the drive as “Velpol — quote v3.docx”. If this is meant to be a new version, I can start from that one instead of from scratch.
Different channel,different context.
To sales you pin different documents, different skills and a different assistant than to rollouts. None of it is created here — you pick from what you already have in appto. By default Wise answers in every channel.
The sales channel — the assistant calculates on your price list and keeps the thresholds from your decisions.
Plus all the company’s general knowledge — shared across every channel.
A setting for the whole organization. It moves the confidence thresholds and the cap on interjections per pass at once.
The default. It speaks up only when it is sure it adds something nobody has written yet.
Context, skills, assistants, integrations and permissions are shared across all of appto. The coworker only uses them — you set them once, in one place.
Let Wise intoone channel.
Start with the one where “who would know that?” comes up most often. Installing is one click in Slack or Teams — you add the other channels once you see it works.
No card. Your account takes 30 seconds.
Before you let it in
The usual questions about AI sitting in your messenger. Got a different case? We will show it in your Slack or Teams and say plainly what is possible.
How is this different from appto in the browser?
In nothing but the window. The coworker is one of the entrances to appto — it reaches for the same company context, the same skills, the same assistants and the same integrations. You change where you ask from, not the tool.
Does Wise read all our conversations?
No. The mode where the coworker speaks up unprompted covers only the channels an administrator points it at — channel by channel or all at once, automatically covering new ones if you set it that way. Direct messages are outside that mode: there it answers only when called.
Does the coworker see more than an employee?
No. Permissions follow the person: if somebody cannot access a document or a record in the CRM, the coworker will not answer them on that basis — not in a channel and not in a DM.
What does it cost, given the bot scans channels every hour?
A channel where nothing happened costs nothing — the bot does not even ask the model. You pay for real answers, exactly as for a conversation in the app. A run of failed charges automatically switches the autonomous mode off.
We use Teams, not Slack.
The coworker works the same in both: messages, replies in threads, mentions and attachments, working in channels rather than only in messages to the bot. In Teams it also reads pasted images and files from the channel, including the ones kept in SharePoint. Teams accounts are matched to appto accounts by email address, with no manual mapping.
We have several companies and several workspaces.
Every organization gets a separate installation: its own settings, its own access and its own conversation history. Usage statistics are separated too — Slack apart, Teams apart.
