Deliverd compared with Slack and Teams buttons
A button in Slack is quick to add.
Who pressed it is the work.
Slack's Block Kit and Teams' Adaptive Cards both put an approve button where people already talk, and for a team's own agent that can be all it needs. What happens after the press is your application's: checking the request came from the platform, deciding whether that account belongs to someone allowed to approve, and keeping a record of it.
Free to start · Approvers never need a seat · No card required
Human-in-the-loop infrastructure for AI agents. An agent asks a person for an approval, a review or an answer, and carries on when they respond. Below is how that compares with Slack and Teams buttons, and where the two work together.
Credit where it is due
What chat buttons do well.
Where people already are
A Block Kit button in Slack, or an Adaptive Card in Teams, puts the request in the conversation, and answering is one press without leaving it.
Cards that keep up
In Teams, Universal Actions can update a card after the decision, showing who approved it and when, and show different people different buttons on the same card.
Approvals inside Teams
The Approvals app in Teams lists the approvals a person has sent and received, including those started from Power Automate, SharePoint and Dynamics 365.
The boundary
Where it stops.
The press comes to your server
Slack posts each press to your app's request URL and expects an acknowledgement within three seconds. Verifying the signature, acting on the press and updating the message are your app's work.
An account is not an approver
The payload says which Slack user pressed. Whether that account belongs to someone in your organisation who may decide this request — and who is not the person who asked — is a question your code answers.
Each platform is its own build
A Slack app reaches Slack. A Teams bot reaches Teams, and Outlook through Universal Actions. Approvers who use neither need another route to the same decision.
The history is the conversation
What your own buttons did lives in the channel and your app's logs, unless you also write it somewhere that can be exported and cannot be edited.
Every point above was read from Slack's interactivity documentation, Slack on verifying requests, Microsoft's Universal Actions for Adaptive Cards overview and Microsoft's guide to Approvals in Teams on 10 October 2026. Products change; if something here is out of date, tell us and we will correct it.
Where Deliverd fits
What Deliverd adds.
One request, every channel
Deliverd posts the request as a Slack message and a Teams card, emails it and pushes it to a phone, and every copy is redrawn without buttons once anyone decides.
The person behind the account
The first press links the chat account to an active member of your organisation, from what Slack or Microsoft hold about that account rather than anything in the message.
Single sign-on respected
Where your organisation requires single sign-on, a Teams press counts only when Microsoft names the Entra identity your sign-on recorded. Anyone else decides from the page, as they would from the email.
The page's rules, from chat
A press goes through the same decision as the page: an agent cannot decide, a requester cannot approve their own request, and a settled request cannot be decided twice.
Back to the agent, on the record
The decision returns to the agent that asked, through the SDK or a signed callback, and is written to the audit trail with the person as the actor.
Working together
Keep your own bot.
A bot your team already uses can keep the conversation and hand the decision to Deliverd, whose app posts the approval beside it. Your bot stays the place people talk to the agent; the approval, the check on who pressed and the record come from Deliverd.
Questions.
Do we have to build a Slack app or a Teams bot?
No. An administrator connects Deliverd's Slack app, or adds its Teams app package, once for the organisation.
What happens when someone who may not decide presses Approve?
Nothing is decided, and they are told so privately. The message does not say who may decide, because that is a fact about somebody else's request.
What does the card look like after a decision?
It is redrawn without buttons, with the outcome and who decided, so nobody presses Approve on something already settled.
Is chat the only channel?
No. Email and the page work for every approver; chat and phone notifications are added beside them, never instead.
Ask the right person before the agent acts.
Approvals, reviews and requests from any agent, with the record kept. Free to start. No credit card.