Send reminders and alerts to your team in Microsoft Teams
Set up Current's Teams app for your own staff in a few steps, so checklist reminders, hot tickets and service desk alerts arrive in Microsoft Teams as cards you can act on, with email as the fallback.
On this page · 21 sections
- What it does for you
- Before you start
- What goes to Teams
- What a Teams alert shows
- Acting from Teams
- Snooze
- Send me sample alerts
- How to make each alert arrive
- Set it up
- Choose who gets what
- The rule for each alert
- Each person's own switches
- What the approval covers
- New staff, leavers and updates
- Prefer to upload the app yourself
- If something does not arrive
- Your own team, and your customers
- One guided Microsoft setup
- Directory access between workspaces
- Another administrator can help
- Existing customers
Put Current's alerts where your team already works: an SLA breach, an urgent ticket on an account or a checklist item due today reaches the right person in Microsoft Teams, and the email goes only when Teams can't deliver it. Your engineers stop missing alerts buried in an inbox, and nobody has to keep Current open to hear about them.
What it does for you
| Where in Current | What you get |
|---|---|
| Alerts | Checklist reminders, hot tickets, service desk alerts (Assigned to you, A customer replied, SLA breach, Possible outage and the rest), new leads routed to someone and billing work arrive in each person's Teams activity feed or as cards in a chat with your workspace's own app. Each card says why it reached you and where things stand now, updates for everyone when anyone acts, and lets you act without leaving Teams. You decide which kinds go, who gets them and whether email still goes too. |
Current can send your own people their checklist reminders, hot ticket alerts and service desk alerts in Microsoft Teams. A Teams administrator signs in with Microsoft once so Current can publish your workspace's own Teams app to your organization, a Microsoft admin approves Current once, and the app reaches your team. You choose which alerts go to Teams, whether Teams replaces the email or arrives alongside it, and who gets each kind. By default Teams replaces the email. Email still goes to anyone Teams could not reach, and whenever a Teams message could not be delivered.

Before you start
- Your workspace uses Current's service desk. This setting lives in Settings › Service desk (the Desk settings row in the service desk opens the same place), so workspaces without the service desk do not see it.
- You are a tenant admin or a service manager. Tenant admins also see a Put Current in your team's Teams step on the Setup card; service managers start from Settings › Service desk › Teams for your team. Other roles do not see the setting.
- You have, or can sit with, a Teams administrator (to publish the app) and a Microsoft admin who can approve apps for your organization (to approve Current). One Global administrator can do both in a row.
- Your team works in one Microsoft 365 organization. Current learns which one when the Teams administrator signs in on the Publish step.
What goes to Teams
- Checklist reminders: the morning message listing a person's checklist items that are due.
- Hot tickets: the alert an account's owners, and anyone on your workspace's hot ticket alert list, get when one of its tickets is urgent, a security incident, unhappy or a billing complaint.
- Service desk alerts: Assigned to you, A customer replied, Current needs your approval, SLA breach, SLA escalated and Possible outage.
Three more alerts follow the same setup without a card of their own: a new lead routed to a person, billing work assigned to a person (a won quote's billing step), and seat growth on a company a person is account manager for (a service on that company grew by at least 3 seats and 10% over 30 days). Once Teams alerts are on, they go to Teams for everyone they are for. A new lead and billing work go to Teams instead of email, with the email as the fallback. A seat growth alert is never emailed: without Teams it stays in the bell. A person who switches one of these alerts off in their own Notifications gets neither its Teams message nor its email; the bell still rings. Seat growth alerts have a workspace switch of their own under Settings, Sales and CRM.
Each message still arrives in the bell in Current. In Teams, alerts start in each person's activity feed, and move into a one to one chat with the app by themselves once Current knows chat works for your Microsoft organization; in the chat each alert is a card you can act on. In the Microsoft organization where Current's Teams bot is registered, chat works from the start. A customer replied keeps its activity feed line beside the card that carries the customer's message.
When a person adds the app in Teams, it sends them a welcome card: what arrives, how it is set up and what they can type. Typing Help in the chat with the app shows it again, and typing samples sends them a sample of each alert.
What a Teams alert shows
In the chat with your Teams app, each alert arrives as a card with five parts, so you can tell at a glance what it is, whether anyone has dealt with it and why it reached you.
- What and where: the kind of alert (for example Security incident or Assigned to you), the ticket, task, lead or message it is about, and the company.
- The facts: why it was flagged, who reported it and how to call them, who it is assigned to and when it is due.
- Where it stands now: for example "Handled by Jane Cole at 2:14 PM", "Assigned to Sam Rivera", "Ticket closed" or "Nobody has acted on this yet".
- Why you got this: for example "You own Northwind Dental in Current." or "No account manager is assigned to Northwind Dental, so it goes to every tenant admin and sales leader."
- Who else got it: up to two names and how many others, when the alert went to more than one person.
When anyone acts on the alert, in Teams or in Current, every card that went out for it changes in place, usually within two minutes, and a card you open days later shows where things stand at that moment. Once the alert is done (handled, closed, approved, acknowledged or moved to someone else), its buttons go away and only Open and More stay. Change what you get is under More.

An alert in the activity feed is one line with a link, because Microsoft does not let Current change an activity feed item after it is sent. The link opens the record in Current, where its status is always up to date. A ticket closed in your PSA shows as closed the next time its card is opened.
Acting from Teams
A button on a card does the same thing as the matching button in Current, as the person who pressed it. Current checks who pressed it, with Microsoft and again in Current, and what that person may do in Current before it acts. Nothing a Teams press does can go beyond what you can do in Current: if you can't do it in Current, the card says so and nothing changes.
| Button | On | What it does |
|---|---|---|
| Mark handled, Not right | Hot tickets | Marks the alert handled, or tells Current it was wrong. The company's account managers, sales leaders, tenant admins and anyone who got the alert can press them. In Current they are on the company page, for people with CRM access; someone without CRM access who got an alert about a desk ticket presses them here. |
| Take it | Hot tickets, SLA alerts and rule alerts, on a ticket in Current that nobody holds yet | Assigns the ticket to you. Not offered on a ticket that lives in your PSA. |
| Approve, Reject | Current needs your approval | Approves or rejects the change Current proposed on a ticket you hold. A proposed reply to a customer, or a runbook, opens in Current instead. |
| Done | Checklist reminders | Ticks that checklist item. One Done for each item, for up to five items; the rest open with the task. |
| Done | Billing work | Marks the billing work done. Not offered when the work lives in a ticket in your PSA. |
| Acknowledge | Team messages that ask for it | Marks the message read and acknowledged. The whole message is on the card, so you read it before you press. |
| Got it | Every card, under More | Marks the alert seen in your bell in Current. Where an alert went to several people, their cards show who saw it. |
Approving an order and changing a company's account manager stay in Current: those cards carry Open and Assign an owner, never a button that does it for you.
Buttons work for 14 days after an alert is sent. After that the card says it is more than 14 days old and offers Open Current. Buttons appear only for people Current added the app for; anyone else gets the same card without them.
Snooze
Under More, Snooze for 1 hour or Snooze until tomorrow morning (9:00 in your workspace's time zone) brings the alert back to you as a new card later. Snooze changes nothing in Current and nothing for anyone else who got the alert. If someone acts on it in the meantime, it does not come back, and your card shows how it ended. You can snooze the same alert three times.
Send me sample alerts
In Settings › Service desk › Teams for your team, Send me sample alerts sends you one fictional card of each alert you can get in this workspace (for your role, with the modules it has on), in your chat with the app, about one a second. Each is marked as a sample and uses made-up companies and people. Its buttons answer as a sample (for example "Sample: you marked this handled") and change nothing in Current. You can send a set twice an hour. Typing samples in the chat with the app, or choosing Send me sample alerts on its help card, does the same.
Where Current can't chat with your Microsoft organization yet, the samples arrive in your activity feed as one-line alerts without buttons.
How to make each alert arrive
Sample alerts are the fastest way to see every card. To see a real one, have a second account do the thing that sends it, because Current never alerts you about your own change. Each real alert also needs Send alerts to Teams on and the app added for you.
| Alert | What to do | When it arrives |
|---|---|---|
| Assigned to you | Another person assigns an open ticket to you. | Within about 2 minutes. |
| Hot ticket | An Urgent ticket opens, or a ticket is set to Urgent, on a company you own, on any company while you are on your workspace's hot ticket alert list, or on a company with no account manager while you are a tenant admin or a sales leader. | 3 to 10 minutes, and up to about 35 while Current checks that a person wrote it. |
| Current needs your approval | A ticket you hold, on a board where Current asks before changing a priority, gets an urgent-sounding message. | 3 to 5 minutes. |
| SLA breach | A ticket on an SLA plan passes its response target while SLA tracking is live. | Within about 5 minutes of the breach. |
| Possible outage | Three or more tickets from one company that Current groups as one problem. | Within a few minutes of Current spotting it. |
| Checklist reminder | You own an open checklist item due yesterday, today or tomorrow. | Weekday mornings between 9:00 and noon in your own time zone. |
| New lead | Another person routes a lead to you. | Within about 5 minutes. |
| Billing work | Another person uses Request contract change, or converts a won quote, with you as the billing owner. | 10 to 15 minutes. |
| Order | An order needs your second approval in Procurement. | Within about 5 minutes. |
| Team message | Someone in a meeting you belong to sends a headline to it as a team message. | Within about 5 minutes. |
Rule alerts reach Teams once they are switched on for your workspace; until then, the samples show what they look like. A new buying signal on a company you own reaches Teams as it comes in.
Set it up
In the service desk, open Settings, choose Teams for your team, then Set up. The steps open in one window with three parts: Prepare (Check), Connect (Publish, Approve) and Finish (Install, Test and turn on). You can close it and come back at any point; Continue setup picks up where you stopped.
- 1CheckCurrent shows what will happen and who is needed. Choose Continue.
- 2PublishChoose Sign in with Microsoft and sign in as a Teams administrator or a Global administrator of your organization (Microsoft asks you to pick the account, so you can hand the keyboard to your admin). Current builds your workspace's own app, named after your workspace with Alerts at the end and carrying your logo, and publishes it to your organization's Teams app catalog. When it is done the step reads Published, with the app's name and version. Current uses that sign-in for the publish only and does not keep it.
- 3ApproveChoose Approve in Microsoft. A Microsoft admin signs in and approves Current for your organization. Back in Current the check runs by itself and reads Approved, or names the permission that is still missing; choose Check again after fixing it.
- 4InstallOnce Approve passes, Current installs the app for everyone it is for (the people in the alerts you send to Teams, never a partner viewer). The step shows how many are installed, how many are waiting and any problems, each with its reason and a Try again button. This can take a few minutes. You can close the window; Current carries on. If you closed it before Approve passed, choose Install for everyone when you come back. While automatic install is not switched on for your workspace, the step says so and Continue moves on: Current adds the app for nobody yet, and each person can add it themselves in Teams, under Apps › Built for your org.
- 5Test and turn onChoose Send me a test. Current sends you one message and the result says where it arrived: in the chat or in your activity feed. Send me sample alerts sends you a card of each alert, if you want to see them. Then choose Turn on. Choose who gets what then takes you to the choices described in the next section.
The three presses that matter are Sign in with Microsoft, Approve in Microsoft and Turn on. Later, Send alerts to Teams in the section switches every Teams alert on or off.
Choose who gets what
After setup, Desk settings › Teams for your team has one card for each kind: Checklist reminders, Hot tickets and Service desk alerts. Each control saves as soon as you change it.
- Send to Teams: switch a whole kind off and it goes back to email only. The bell and the email follow each person's own choices, exactly as before Teams.
- Email: Teams instead of email, or Teams and email. Checklist reminders, hot tickets and service desk alerts all start on Teams instead of email. If your workspace already sent service desk alerts to Teams before this setup, those kept their email too, so Service desk alerts start on Teams and email there. With Teams instead of email, the email still goes when Teams could not deliver the message or cannot reach the person.
- Who gets this in Teams: Everyone it's for, or Only these, then the roles, pods and people you pick (anyone matching any one of them). Everyone else still gets email.
- Service desk alerts also have one switch per type under Which service desk alerts, so you can keep, for example, SLA breach and Possible outage in Teams and leave Assigned to you on email.
The rule for each alert
Your choices above are the rule for your whole team, and each person can only take away from it. A person gets an alert in Teams when all of these hold: its kind is sent to Teams, its type is switched on (for service desk alerts), the person is in the kind's audience, their own Teams switch for it is on, and the app is installed for them. The email follows each person's own email switch: it goes when the kind is set to Teams and email, or when Teams could not deliver the alert. The bell in Current always rings.
Each person's own switches
Each person can switch single alerts off in Teams for themselves, in Notifications from their account menu. They can never switch an alert on in Teams beyond what your choices send them. Under Microsoft Teams they see a switch for Checklist items due, Hot tickets and Possible outage when your workspace sends that kind to them in Teams. Service desk alerts have a Teams column in the Service desk block, one switch per alert; one SLA switch there covers both SLA breach and SLA escalated. An alert switched off in Teams still comes by email when that person's email switch for it is on.
"Your workspace sends this to you by email." means the person is not in that kind's Teams audience. "Your Teams app isn't installed for you yet." means the install has not reached them yet; they ask you if it stays that way.
What the approval covers
Microsoft's admin approval is all or nothing for an app. When your Microsoft admin approves Current, the approval screen lists every permission on Current's Microsoft app, not only the Teams ones: TeamsAppInstallation.ReadWriteSelfForUser.All (install the app for a person), TeamsActivity.Send (post to a person's activity feed), the mail permissions Current's other Microsoft 365 features use (Mail.Read, Mail.ReadWrite, Mail.Send and Sites.Selected), and AppCatalog.ReadWrite.All for every person in your organization. That last one only lets someone who is already a Teams administrator publish apps; Current itself publishes only during the Publish sign-in above. Current uses only what each feature asks for: approving for Teams does not switch on mailbox capture or any other feature.
If your workspace already connected Microsoft 365, nothing that works today stops working before you approve again. Until then, publishing asks for a Microsoft admin's approval first, installing waits for the approval, and alerts keep going by email.
New staff, leavers and updates
- New staff: once automatic install is on, Current installs the app for a new member of your workspace by itself, within about ten minutes of them joining or moving into a role that gets alerts in Teams.
- Leavers: when someone is disabled or becomes a partner viewer, Current removes the app from their Teams.
- Someone removed the app themselves: Current does not add it back. Choose Try again beside their name if they want it again.
- Your logo or workspace name changed: choose Update the app in Teams. It asks for the same Teams administrator sign-in, then publishes the new version, and Current upgrades everyone's app.
- Switching Send alerts to Teams off sends every alert back to email. The app stays installed and silent; a Teams administrator can remove it in the Teams admin center (Teams apps › Manage apps).
Prefer to upload the app yourself
On the Publish step, choose Download the zip instead, then Download the zip. You get a zip file built for your workspace. In the Teams admin center: 1. Open Teams apps › Manage apps. 2. Choose Actions › Upload new app, and pick the zip you downloaded. Back in Current, choose I've uploaded it; Current looks for your app as it adds it for your team, and Approve, Install, and Test and turn on work as above. I've uploaded it is offered only once Current has confirmed your Microsoft organization: either it is the organization where Current's Teams bot is registered, or someone already signed in with Microsoft on the Publish step. Until then, someone signs in with Microsoft on the Publish step (Publish with Microsoft instead) so Current can confirm your organization.
If something does not arrive
Each message below is what the setup shows, and what to do about it.
- "The Microsoft sign-in was cancelled. Nothing was changed." Choose Sign in with Microsoft again.
- "A Microsoft admin needs to approve Current for your organization first." The account that signed in cannot approve the publish permission. Use Approve in Microsoft first, then publish again.
- "That account can't publish Teams apps." Sign in as a Teams administrator or a Global administrator.
- "You signed in to a different Microsoft organization than the one your team uses." Sign in with an account from your own organization.
- "Most of your team signs in to a different Microsoft organization than the account you used." Sign in with an account from the organization your team uses.
- "Current can't tell yet that this Microsoft organization is yours." Ask a Global administrator to prove it from the Microsoft 365 card at the top of Settings › Integrations, then publish again.
- The organization is already connected to Current as one of your customers' organizations. It can't also be used for your team's Teams app; sign in with your own organization's account.
- "Another Current workspace already uses this Microsoft organization for Teams." Contact us so we can sort it out.
- "An older copy of your Teams app is installed." or "Your Teams already has another app that uses Current's bot." Remove the old app in the Teams admin center (Teams apps › Manage apps), then try again.
- "Microsoft refused the app. Nothing was changed." Try again; if it happens again, contact us. "Microsoft already has this version." Try again in a minute.
- "A Microsoft admin needs to approve Current before it can add the app for your team." Choose Approve in Microsoft.
- "Publish your Teams app first." Go back to the Publish step.
- "Current could not find this person in your Microsoft organization." Their Current email may not be their Microsoft sign-in. They can connect Microsoft 365 in Settings, then choose Try again.
- "This person does not have Microsoft Teams." Give them a Teams licence, then choose Try again.
- "Your Teams settings block this app for this person." In the Teams admin center, allow the app in the app permission policy that applies to them.
- "Microsoft asked Current to slow down." or "Microsoft did not answer." Nothing to do: Current carries on by itself.
- "Current's Teams connection needs attention on our side." We are told automatically and fix it on our side.
- "Teams setup for your team is not available yet." This setup is not open for your workspace yet.
- "The app isn't installed for you yet. Add it for your team first, then try again." Current has not added the app for you yet. While automatic install is off, add it yourself in Teams, under Apps › Built for your org.
- The test arrived in the activity feed, not in a chat. That is expected until Current knows chat works for your organization. Alerts go to the activity feed in the meantime.
- "You can send sample alerts twice an hour." Wait an hour, then choose Send me sample alerts again.
- "Sample alerts are not available for your workspace yet." Alert cards are not switched on for your workspace yet; alerts arrive as they do today.
- "Sent 4 of 13 sample alerts, then one didn't go through." Microsoft did not answer for one card, so Current stopped rather than send it twice. Try again in a few minutes.
- "This alert is more than 14 days old." Its buttons have expired. Choose Open Current to see where it stands.
- "You can't do this in Current, so you can't do it from Teams." The button asks Current, as you, and your role cannot do this. Open the record in Current or ask the person who can.
- The Setup card says Teams setup is partly done, or that Teams alerts are paused. Open Settings › Service desk › Teams for your team to see which step is waiting or what changed (for example, the approval was removed). While paused, alerts go by email.
Your own team, and your customers
Teams for your team is for your own staff: the people it messages are the members of your own workspace.
One guided Microsoft setup
A workspace administrator opens Settings › Integrations and chooses Microsoft setup on the Microsoft 365 card. Current checks the connections already in place and continues with the first unfinished part.

- 1Review the workspaceCheck the workspace name and the capabilities shown. Existing connections stay in place. If a connection cannot be checked, choose Check again before continuing.
- 2Approve at MicrosoftIf organization approval is missing, a Microsoft global administrator approves Current. Microsoft lists the full permissions configured for the shared app, including mail, calendar, files, directory access and Teams. This setup does not change your staff-mailbox capture setting. The Teams app has a separate approval later in the same flow.
- 3Read the directory, where enabledVerify the directory and connect your own account with the approved user-profile permission. Choose Read directory, then review people and manager suggestions in People. Reading never creates accounts, changes roles or publishes reporting relationships.
- 4Finish TeamsWhere guided Teams setup is available, add Current to your organization's app catalog, approve it and review installation progress. Existing Teams policies still apply. Choose Send me a test yourself, check its result and explicitly turn on delivery when ready.
- 5Return when neededAfter a Microsoft sign-in, the same browser returns you to the relevant step. Reopening setup checks the saved connections again, so completed work does not need repeating.
Directory access between workspaces
A Microsoft directory keeps one owning Current workspace. If two workspaces need people and manager suggestions from that directory, their administrators can approve a separate, scoped read grant in Microsoft setup, under Directory access between workspaces. This does not move ownership or copy the owning workspace's people, tokens or records.
- 1Review the owner's offerThe receiving administrator chooses Copy access request in Microsoft setup and sends the link to the directory owner. Its administrator opens the link in the owning workspace, checks the receiving workspace name, chooses exact Microsoft-verified domains and an expiry no more than one year away, then chooses Review offer and Offer access. No directory read is enabled yet. Entering the workspace ID manually remains available under the advanced options.
- 2Approve in the receiving workspaceIts administrator signs in as themselves, opens Microsoft setup and reviews the same offer. Choose Review and approve, check the names, domains and expiry, then choose Approve access. The administrator's own Microsoft connection must belong to that directory and have permission to read people.
- 3Read and reviewWhere the operating rhythm is enabled, refresh the directory in the receiving workspace. Only members with a sign-in domain named in the grant are included. Managers outside that scope are not shown. Matching people stays inside the receiving workspace; publishing reporting relationships remains a separate review.
- 4End accessEither workspace's administrator can choose Revoke access. Further reads stop, including a refresh already in progress. Access expires on the shown date and never renews automatically. Revocation remains available if the workspace is billing-frozen or the operating rhythm is off.
If your connected Microsoft account is not an administrator, choose Approve with another Microsoft account in the access review. Sign in with a Global Administrator or Privileged Role Administrator from that directory. This one-time check approves only the recipient, domains and expiry you reviewed; it keeps your connected mail and calendar account. Complete it within 15 minutes, or start again. The receiving workspace still approves separately and uses its own connection when reading people.
Grant approvals and revocations are recorded. An expired or revoked grant, a removed approving administrator, or an owner disconnect stops reads. Each refresh uses the receiving administrator's own Microsoft connection and rechecks the grant. Mailbox capture remains a separate permission.
Another administrator can help
Copy setup link for an administrator who already belongs to this Current workspace. They sign in with their own Current and Microsoft accounts. The link is a shortcut, not an invitation, and grants no access. A link for another workspace asks you to open that workspace with its own administrator sign-in.
Existing customers
Use the same Microsoft setup button. Current skips completed parts and preserves your current settings. Advanced Microsoft settings opens the existing controls for individual connections and staff-mailbox capture. Ordinary staff can still connect their own account in Settings › Your settings › Microsoft 365.
