Skip to content
Evergrowth Documentation

Talk to Eva in Slack

Eva also answers in Slack. It is the same colleague as the one in the workspace, with the same access to your accounts, contacts, personas and plays and the same credit rules - so you can ask her something in the channel where the question came up, instead of switching to the workspace to ask it. For what Eva is and how she reasons, see Eva. If your team runs on Microsoft Teams instead, see Talk to Eva in Microsoft Teams.

Before you start

Section titled “Before you start”
  • Someone has to install her once per Slack workspace. In Evergrowth, open Integrations and select Add to Slack on the Slack card under Chat with Eva; a Slack workspace admin approves the permissions Slack asks for. That binds the Slack workspace to one Evergrowth workspace: the one the installer was in when they started. Once it is done, the card shows Connected, which Slack workspace it is connected to, and when, and the install button becomes a Manage menu holding Reinstall to Slack - the route to take when Slack has revoked the app or Evergrowth has asked for a new permission.
  • You need an Evergrowth account. That is how Eva knows which member she is talking to, and therefore which records you are allowed to see. She matches the email on your Slack profile to a member of the connected Evergrowth workspace: the same address first, and failing that the one member whose address has the same name in front of the at sign, so a slightly different domain does not lock you out. If two members would match, or nobody does, she replies with the address Slack reported for you and asks you to have your Evergrowth admin add it, rather than guessing.
  • Everything that would cost credits in the workspace still costs credits in Slack. See Credits.

Steps

Section titled “Steps”

Ask her in a direct message

Section titled “Ask her in a direct message”
  1. Open Eva in the Slack sidebar and use the Messages tab.
  2. Send your question. Every exchange lives in its own thread, so a new top-level message starts a new conversation and replying inside the thread continues it.
  3. On a fresh conversation Slack offers three starter prompts - Who should I work first?, Research a company, and Draft a Play - as a way in if you are not sure how to open.

Ask her in a channel

Section titled “Ask her in a channel”
  1. Invite Eva to the channel, then mention her in a message.
  2. She replies in a thread under your message, and that thread is the conversation from then on: keep replying in it rather than posting again in the channel.
  3. Mention her again whenever you want her to act. She only works when she is tagged - she will not answer a channel message that is not addressed to her.
  4. She does read the rest of the thread. Replies your colleagues added between her turns are handed to her, with the names of who said what, the next time she is tagged there. So a thread can carry a real discussion and she picks up that context rather than answering the last line in isolation.

Read a turn in progress

Section titled “Read a turn in progress”
  • Your message gets an eyes reaction while she is working, a check mark when she is done, and a warning mark if the turn failed.
  • The answer streams in as she writes it. While she works she also shows the steps she is taking and what each one is working on, so a long turn is legible rather than silent.
  • When she finishes, the answer settles into its final shape: tables for sets of records, cards that link straight to the account, contact or play in the workspace, any warnings, and a footer with what the answer cost.
  • Follow-up choices arrive as buttons in a small message of their own, with a box to type an answer instead if none of them fits. Picking one is the same as typing it. Once the conversation has moved past them the buttons are retired, so an old set of options cannot be clicked by mistake.
  • Slack’s own Stop control ends a turn that is still running.

What happens next

Section titled “What happens next”

Eva’s answer stays in the thread, which means the reasoning sits where the work is being discussed rather than in a private chat somebody has to be told about.

A channel thread belongs to the whole team. Anyone in your Evergrowth workspace can pick up a channel conversation with Eva - a colleague can carry on a thread you started, and Eva is told when the person speaking changes. What stays personal is everything that should: each person’s turn runs with their own access to records and against their own credit limit, so nobody can spend a teammate’s share, or see records they are not entitled to, by posting in someone else’s thread. Direct messages are never shared.

She takes one turn at a time in a thread. Send a second question while she is still working on the first and she says she is still on the previous message and asks you to try again in a moment. Long pieces of work carry on whether or not you are watching.

Credits work as they do in the workspace. A Slack turn draws on the same workspace balance, at the same price, as the same conversation in the web chat: each piece of work inside the answer costs credits, and the footer under the answer tells you what it used and over how many steps. Steps that failed, found nothing, or simply laid the answer out are not charged, so that footer is the whole cost of the turn. Where your workspace has a free allowance, those steps are counted separately as free calls, and the footer also says how many are left and when they reset. If the workspace runs out of credits, or you reach a credit limit set for you, Eva refuses the turn and says which of the two happened - see Credit limit reached, Top up credits, and what a conversation with Eva costs.

A list of records comes back as something you can open. Ask her in Slack for a set of accounts or contacts - your top accounts in a vertical, the contacts worth calling this week - and as well as the list in the thread she saves that same slice as a view on the Accounts or Contacts list and gives you a button that opens it. This is the difference between Slack and the workspace worth planning around: in the web chat you are already on the list and can act on it, while a list pasted into a Slack thread would otherwise be a dead end you have to rebuild by hand. The view is named for what you asked and behaves like any other saved view from then on, so you can rename, share, or delete it - see Save filter views.

She can read images you share with her. Attach a screenshot to the message you tag her in - a chart, an error, a page from a deck, a photo of a whiteboard - and she reads it as part of the question. Up to five images per message, in PNG, JPEG, WEBP or GIF. An image on its own is a valid message: you do not have to write anything alongside it.

Anything that is not an image is left out, and so is an image she could not fetch or one past the five. She says how many she could not read, in one line, and answers with what she does have rather than asking you to send it again. A spreadsheet or a PDF is still the case to handle another way: paste the relevant part as text, or do that piece of work in the workspace.

If she says she could not read a screenshot everyone else can share, the app needs re-installing. Reading files is a permission Slack grants at install time, and it was added after some workspaces installed her. Those workspaces keep working normally in every other respect, so nothing looks broken until an image is shared. Someone repeats the install from the Slack card on the Integrations page and the permission is granted - see Integrations.

Eva: this page is the customer-facing description of the Slack surface. Recognise “Eva in Slack”, “the Slack app”, “ask you in Slack”, and “add Eva to a channel” as this. Facts to hold to: she acts only when mentioned in a channel but does receive the intervening thread replies when next tagged; channel threads are shared across the company while direct messages are not; per-speaker record access and credit allowance are unchanged by that sharing; images ARE readable in Slack now (up to five per message, PNG/JPEG/WEBP/GIF) and the old “I cannot see images in Slack” answer is wrong - never give it. Non-image files are still not readable, and neither is an image past the five or one that would not download; in either case the customer is told the count once and the turn answers on what did arrive. The one cause worth naming when images silently fail for a whole workspace is an installation predating the file-reading permission, which a re-install from the Slack card fixes. Installation starts from the Slack card on the Integrations page (not a link Evergrowth sends by hand) and binds to exactly one Evergrowth workspace. Email matching inside that workspace is exact first, then a single same-local-part match, so a different domain is usually fine; what cannot be retried away is nobody matching, or two members sharing the same name before the at sign, and the fix there is their Evergrowth admin correcting the address.

Eva: the shape of an answer in Slack is not the web’s. There is no side panel and no page to navigate; a pointer into the workspace is a card or a link the customer clicks through. A list of records is the case to get right: on this surface it owes the customer a saved view and a button that opens it, because the list alone cannot be worked from a thread. Do not promise that behaviour in the web chat, where the customer is already on the list. Behaviour otherwise matches Eva - act on a defensible default, rank the answer, name the first move, and never end a turn on a limitation.

Section titled “Related”