Abbie — your AI coworker, in the channels you already work in
Abbie is an AI coworker from QuivaWorks that works inside Slack. @mention her in a channel, message her directly, or reply in a thread she's already part of, and she answers using your organisation's own knowledge — no new tool for your team to learn.
Installing needs a QuivaWorks account and permission to add apps to your Slack workspace. Everything on this page is readable without signing in.
The answer already exists somewhere. Finding it is the job.
Every team keeps its working knowledge in three places at once: the documents nobody can find, the systems only two people know how to query, and the channel where it was explained six weeks ago. So the same questions get asked again, and someone stops what they're doing to answer them.
Abbie lives in Slack as a normal member of the conversation. @mention her in a channel or send her a direct message — no new tab, no separate product to log into to get an answer.
She answers using your organisation's own knowledge in QuivaWorks — your documents, records and the systems you've connected — rather than starting from a blank page every time.
She reads messages addressed to her, and nothing else — unless someone in the channel explicitly agrees to a one-time, bounded catch-up read.
Exactly what Abbie does in your workspace
Every behaviour below is something you will see in Slack itself.
Type @Abbie followed by your question in any public
or private channel she's been invited to. That mention is what makes the message hers —
she does not answer channel conversation she wasn't addressed in.
- Works in public and private channels
- Only messages addressed to her — a mention, or a reply in a thread she's already part of — are read to be answered
The moment she accepts a message, Abbie adds an :eyes: reaction to it. That's your confirmation she has it and is working — so nobody is left wondering whether the question landed.
- Appears within seconds of your message
- No reaction means she never received it
Her answer is posted as a threaded reply to your message, so the channel stays readable. Each thread keeps its own conversation and memory — the same way a session works in the QuivaWorks web chat.
- Follow-ups in that thread need no further @mention
- A different thread is a fresh conversation
Open a DM with Abbie and just talk — no @mention needed, because every message in that DM is addressed to her by definition. Use it for anything you'd rather not ask in front of a channel.
- In a group DM, @mention her as you would in a channel
- She also DMs you your one-time account-linking link
Attach a file to a message addressed to her and she downloads and reads it to answer you. She can send files back into the same conversation too — a generated document, spreadsheet or chart.
- Only files attached to messages addressed to her
- She never browses your workspace's file library
When Abbie is invited to a channel she introduces herself and asks, with Yes, learn this channel and No thanks buttons, whether she may read that channel's recent history once to learn what the team works on. Nothing is read until someone answers Yes.
- Bounded: last 30 days, maximum 200 messages, once
- Decline and the history is never read
- She posts her summary back into that channel
Abbie in Slack
Each capture below shows the behaviour described above, in a real Slack workspace.
What happens after you click Add to Slack
Six steps, none of them long. You'll need permission to add apps to your Slack workspace.
- Sign in to QuivaWorks The Add to Slack button opens the QuivaWorks integrations page. Sign in, or create an account if you don't have one yet — Abbie answers from your organisation's knowledge, so she needs an organisation to belong to.
- Authorise the app in Slack Choose Connect Slack and Slack shows you its own permission screen listing exactly what Abbie is asking for. Pick your workspace and select Allow. You're returned to QuivaWorks.
- Confirm the connection Your workspace now appears as connected on the QuivaWorks integrations page, and Abbie appears in your Slack sidebar under Apps. That's the installation done.
- Link your Slack account to your QuivaWorks account Ask to link your account and Abbie sends you a single-use link by direct message in Slack. Opening it ties your Slack identity to your QuivaWorks user, so she answers you with your permissions — never someone else's. Each person in the workspace does this once.
-
Invite her to a channel
In any channel, run
/invite @Abbie. She introduces herself and asks — with Yes, learn this channel and No thanks buttons — whether she may read that channel's last 30 days once. Either answer is fine; she works either way. -
Ask her something
Type
@Abbieand your question. Within a second or two she adds a 👀 reaction to your message, then posts her answer as a threaded reply.
You'll know it worked when…
Your Slack workspace is listed on the QuivaWorks integrations page.
She appears under Apps in Slack and replies to a direct message.
Inviting her to a channel produces her introduction and the Yes / No prompt.
An @mention gets the eyes reaction, then a threaded reply.
What Abbie reads — and what she doesn't
The same disclosure that appears on the Slack Marketplace listing.
Message and file data she reads
- Messages addressed to her. An @mention in a channel or group DM, a one-to-one direct message, or a reply in a thread she is already part of — read in order to answer it.
- Channel history, only after an explicit Yes. When she is invited to a channel she asks in that channel, with Yes / No buttons, before reading up to the last 30 days (maximum 200 messages) of it once, so she can learn what the team works on. Nothing is read until someone answers Yes.
- Files attached to messages addressed to her. Downloaded and read in order to answer you. She can also send files she produced back into the same conversation.
- Basic workspace and profile details. Workspace name, channel names and membership, and member display name and work email — used to know which channels she is in, to let an administrator invite colleagues to QuivaWorks from Slack, and to link a Slack user to their QuivaWorks account so Abbie answers as that person. Not used for anything else.
What she never does
- Answer, or read to answer, channel conversation she was not addressed in.
- Read channel history without an explicit Yes in that channel — or read more than the 30 days / 200 messages / once that the prompt discloses.
- Browse your workspace's file library. Only files attached to messages addressed to her are read.
- Store personal facts about individuals out of channel conversation, or attribute a stored statement to a named person.
- Store credentials or other sensitive personal data found in messages.
What is kept, and who controls it. What Abbie learns from a channel is stored as organisation-level summaries, which your administrators can view and delete at any time in QuivaWorks under Abbie → Organisational memory. Removing Abbie from a channel stops delivery from that channel immediately; uninstalling the app from your workspace stops everything immediately.
Direct messages work differently, on purpose. In a direct message Abbie may also remember something about you personally, so she can pick up where you left off. That is stored against your own QuivaWorks account rather than in the organisation's shared memory, and is used to personalise your own later conversations. You can view, edit and delete them yourself under Abbie → Synapse Memory → Personal; your administrators have no surface to view them.
Read the policy before you install
All three documents below are public — no account needed.
How QuivaWorks collects, uses, stores and deletes your data, including data received from Slack, and how to exercise your rights.
The terms that govern use of QuivaWorks and of Abbie in your Slack workspace.
Security practices, sub-processors, data residency and compliance posture, in one place.
Getting help with Abbie for Slack
You do not need a QuivaWorks account to contact us.
Email: support@quiva.ai — the fastest route, and open to anyone. Tell us your Slack workspace name and what you were doing when the problem appeared.
Web form: quiva.ai/help-center/contact — publicly accessible, no sign-in and no account required.
Help Center: quiva.ai/help-center — guides and answers to common questions.
Our commitment: we respond to every support request within 2 business days. Security reports go to security@quiva.ai and privacy requests to privacy@quiva.ai.
Put Abbie in your channels
Install takes a couple of minutes. Invite her to one channel, ask one question, and decide from there.
Ungated page • Public privacy policy • Support at support@quiva.ai within 2 business days