Talk to Eva in Microsoft Teams

Eva answers in Microsoft Teams as well as in the workspace and in Slack. It is the same colleague either way: the same access to your accounts, contacts, personas and plays, the same reasoning, and the same credit rules - so a question can be asked in the chat where it came up rather than in a tab somebody has to go and open. For what Eva is and how she reasons, see Eva.

The app package on the Integrations page is for direct messages. Channels and group chats arrive with the Microsoft Teams Store listing; until then, message her in her own chat. The reason is worth knowing: an app installed from a package rather than from the store is handed only the messages that name it, so in a channel she would see the mentions and not the conversation around them. The store version carries the permission to read the rest of a thread she has been mentioned in, which is what makes a channel answer worth having.

Before you start

Your Teams administrator installs her once for the organization. Unlike Slack there is no one-click install link: Evergrowth gives you an app package, and an admin uploads it in Teams. The steps are below, and the package is a download on the Integrations page in Evergrowth. Installing it for the organization is all that is needed - there is no second step of adding her to a team, because this package is for direct messages.
You need an Evergrowth account. Eva works out who is asking from the email address Teams reports, and answers with exactly the records that person is allowed to see. She matches that address 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, which is what makes a Microsoft tenant on a slightly different domain work without anyone re-inviting people. If two members would match, or nobody does, she says so and names the address Teams reported rather than guessing.
Everything that would cost credits in the workspace still costs credits in Teams. See Credits.

Steps

Install the app

In Evergrowth, open Integrations and find the Microsoft Teams card under Chat with Eva. Select Add to Teams to download the app package. Once Teams is connected the button becomes a Manage menu with Download app package inside it, so you can fetch the package again without disturbing the existing connection.
Your Teams administrator uploads it: Teams admin center, then Teams apps, Manage apps, Upload new app. Where your organization allows people to upload custom apps themselves, a user can do the same from Apps, Manage your apps, Upload an app.
Everyone can then add Eva from Apps and start a direct chat with her. That chat is where she works.

If your organization installed an earlier version of the package, the one that could be added to a team, she answers there when @mentioned (see Channels and group chats) but sees only the messages that mention her.

Connect Teams to your Evergrowth workspace

The first message does this on its own. Eva reads the address of whoever spoke first, finds the Evergrowth workspace that address belongs to, and binds your Microsoft organization to it from then on.

If that address belongs to more than one Evergrowth workspace, or Teams did not share it, she does not guess: she replies with what to do instead. Type connect followed by your workspace id - the identifier in the address bar when you are in Evergrowth - and she binds it. The same command switches an already-connected organization to a different workspace. Only a member of that workspace can connect it, which is what stops an unrelated organization from attaching itself to your data.

Removing the app from the organization releases the connection; adding it again re-connects it.

Ask her in a direct message

Open the chat with Eva and send your question.
Her reply arrives in the same chat, and the chat is the conversation: keep asking there and she keeps the thread of what you have been discussing.
Teams’ own Stop control ends a turn that is still running.

Send help on its own and she answers immediately with a short list of what she can do - prioritising, researching, looking records up, building saved views, drafting plays - and the connect command. It is a fixed reply rather than a turn she thinks about, so it is free and it reads the same every time. Useful for somebody who has just been given access and does not know what to ask for.

Channels and group chats

Wherever Eva is a member of a team or a group chat, she answers when somebody @mentions her, in the thread they asked in. When she is first added there she says how she works: mention her in a thread and she answers in that thread, and she only reads threads she has been mentioned in. She does not watch the channel for her own purposes.

A channel post and its replies are one conversation with her, and a group chat is one conversation shared by its members. When a different person asks next, she knows the question came from someone else.
Each person’s question runs with that person’s own access and credit limit, and costs credits the same way as in her direct chat.
How much of the thread she can read depends on how she was installed. Installed from the Microsoft Teams Store, she reads the other replies in a thread she has been mentioned in, so her next answer there has the context of the conversation. Installed from the package on the Integrations page, Teams hands her only the messages that mention her, so paste in whatever from the thread matters.

The package on the Integrations page cannot be added to a team, so for most organizations channels arrive with the store listing. Until then, ask in the direct chat and share what she gives you, or use Slack, where channel threads already work end to end.

Read a turn in progress

She acknowledges immediately, then keeps a short work log at the top of the turn while she works: first that she is thinking, then a line per piece of work she is doing, each one flipping from in-progress to done and picking up its price as it settles.
The answer streams in beneath the work log, so you see it being written rather than waiting for a finished block of text.
When the answer is finished the work log collapses into a single line - how many steps, what they cost, and a control to show them again - or disappears entirely if no work was needed.
The finished answer carries the same furniture as the web chat: tables for sets of records, a card of buttons that open the account, contact or play directly in Evergrowth, any warnings, and a footer with what the turn cost.
Follow-up choices arrive as buttons in a message of their own. Selecting one is the same as typing it, and once the conversation has moved on the card is replaced by the choice you made, so an old set of options cannot be clicked by mistake.
Teams closes a message stream after about two minutes, so a very long answer continues in a fresh message, cut at the end of a sentence.

What happens next

Credits work as they do in the workspace. A Teams turn draws on the same workspace balance at the same price as the same question in the web chat: each piece of real work inside the answer costs credits, and the footer tells you what the turn used. Steps that failed, found nothing, or simply laid the answer out are not charged. If the workspace runs out of credits, or you reach a credit limit set for you, she refuses the turn and says which of the two happened - see Credit limit reached and Top up credits.

She can read images you share with her. Paste or attach a screenshot in your message - a chart, an error, a slide, 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, and an image on its own is a valid message with no text alongside it.

Two ways of sharing work: an image pasted or attached straight into the chat, and a file you pick from your own OneDrive. Anything that is not an image is not readable yet. In either case she says how many attachments she could not read, in one line, and answers with what she does have rather than asking you to send it again.

Access is personal. Each person’s turn runs with their own permissions and against their own credit limit, so what Eva shows you in Teams is exactly what you can see in the workspace, and a question you ask never spends a colleague’s share.

Slack is the one to use for team conversations today. In Slack, Eva answers in a channel thread and reads the messages your colleagues added between her turns. Teams cannot give an app installed from a package the permission that makes that work; the store listing can. If most of your selling conversation happens in a channel, connect Slack; if your team lives in Teams, her direct chat is the main surface until the store listing.

Which surface to use. Slack and Teams are the same colleague, so pick the one your team already talks in - remembering that in Teams, channels arrive with the store listing. The web chat remains the place for work you want to act on immediately, because you are already on the list or the record she is talking about.

Eva: this page is the customer-facing description of the Teams surface. Recognise “Eva in Teams”, “the Teams app”, “add Eva to a channel in Teams” as this. Facts to hold to as of October 2026: the package downloaded from the Integrations page is DIRECT MESSAGES ONLY - it does not ask for the team or group-chat scopes, so it cannot be added to a team, and the older guidance about a team owner adding the app to a team is wrong for it. Channels, group chats and reading the rest of a thread come with the Microsoft Teams Store listing; do not tell a customer the listing is live or give a date. What changed in October 2026: where Eva IS in a channel or group chat (the store version, or an organization still on an earlier package that had the team scope), an @mention now runs a normal, charged turn in that thread instead of the old pointer to her direct chat, and being added to a team posts a welcome saying she answers only when @mentioned and reads only threads she was mentioned in. On an earlier package she still receives only the messages that mention her, so her thread context there is the mentions alone - recommend pasting the relevant thread content, or Slack if channel conversation is the point. Never repeat the old “mentioning me in a channel only gets a pointer to my direct chat” answer. Installation is an admin upload of a package rather than a link. The organization binds to one Evergrowth workspace from the first speaker’s address, with the connect command as the fallback when that address names several workspaces or is not shared. Address matching inside the bound workspace is exact first, then a single same-local-part match, never across workspaces and never when two members would match - so “my Teams address is on a different domain” is usually fine, and “two of us share the same name before the at sign” is the case that genuinely needs an admin. Images ARE readable in Teams (up to five per message, PNG/JPEG/WEBP/GIF), so the old “I cannot see images in Teams” answer is wrong - never give it; what is out of reach is any non-image file, reported as a count of what could not be read rather than as a failed turn. A bare help (or ?) is answered with a fixed capability summary without running a turn, so it costs nothing - offer it to somebody who does not know where to start.

Eva: the shape of an answer here matches Slack more than the web - no side panel, no page to navigate, pointers into the workspace are buttons the customer clicks. Behaviour otherwise matches Eva: act on a defensible default, rank the answer, name the first move, never end a turn on a limitation.

Eva - what she is, and how she behaves in a conversation.
Talk to Eva in Slack - the same colleague in Slack, and the differences worth knowing.
Integrations - where the Slack and Teams connections live.
Credits - how usage is priced and where limits come from.
Credit limit reached - what to do when she pauses.