Your Teams channel gets the summary while the caller is still in the car park
Zapier catches our webhook on a paid plan and posts into a channel you pick. It shows the call. It does not book anything.
Caller
“I'm ringing on behalf of the school. We need a quote for the hall floor before the governors meet on the 14th.”
What happened next
- Call captured with the caller's name, number and the deadline they gave
- Summary posted to the Estimating channel in your Teams workspace
- Quote owner saw the 14th in the first line and claimed it in the thread
How GreetKeeper connects to Microsoft Teams
Three states, and we publish the one that is true rather than the one that reads best.
| Tool | How it connects | What that means |
|---|---|---|
| Microsoft Teams | Through Zapier |
What Teams is doing here
Microsoft Teams is the chat and meetings tool bundled with Microsoft 365. Most businesses on Microsoft already run internal messages through it.
Its API lets an approved connector post a message into a channel inside a team. Zapier uses that to write the call summary as a normal message that anyone in the channel can read and reply to.
If your staff already have Teams open all day, this puts the call in front of them without adding another app to check. That is the practical case for it.
Where the summary appears
As a message in one channel, inside one team, posted by the connector.
You choose the team and the channel during setup. A dedicated channel inside the team that owns phone work is better than the team's General channel, which everyone already ignores.
The message holds the caller's number, what they wanted and the summary. Add the transcript link so the detail is one click away rather than pasted into the channel.
Replies happen in the message thread. Teams keeps that thread under the original post, so a week later you can still see who took the call and what came of it.
Connecting Teams
You need permission to add a connector to the team. In many businesses that is an admin, not you.
Check whether you can add apps to the team
Microsoft 365 admins often restrict this. Find out before you build the Zap, because discovering it at the authorization step wastes the rest of the setup.
Set the hook, then connect Microsoft Teams
Open the Zap with Webhooks by Zapier and Catch Hook, and save the address in GreetKeeper. Then sign in with a work account that belongs to the team. Choose the channel-message action, then pick the team and the channel from the two dropdowns.
Compose the message
Lead with the number and the reason for the call. Teams truncates long messages in the channel list, so the useful part has to be early.
Test it and set the channel notification level
Place a real call. Then ask each person in the channel to set notifications to all new posts, or the message arrives and nobody is told about it.
What this connection leaves out
Questions about Microsoft Teams and GreetKeeper
Does this work with a personal Microsoft account?
You need a work or school account that is a member of the team. Personal accounts cannot post into an organization's channels.
Can it post into a private channel?
Support for private channels depends on your tenant settings and the connector's permissions. Test with one before you rely on it, and have a standard channel as the fallback.
Will the caller see any of this?
No. The Teams message is internal. The caller hears only what happened on the call itself.
What do we need on the Zapier side?
A paid plan. GreetKeeper has no Zapier app yet, so the call comes in through Webhooks by Zapier, which Zapier treats as premium. The Teams step follows it.
Put a real call in your channel
Bring the team name. Two minutes, no card.