Askel connects your product to customer Teams tenants using Microsoft Graph so you can post messages, react to channel activity, and surface notifications where enterprise users already spend their day. No webhooks to manage, no bot registrations to maintain, and no tokens that expire and break silently on a Friday afternoon.
Send formatted cards, plain text, and adaptive cards to public channels like #general-announcements or private channels like #finance-alerts. Direct-message an individual user when the notification is personal.
Enumerate the customer's teams and channels so your product can present a picker in settings. Users choose exactly where notifications land rather than having to paste in an ID.
React to new channel messages, replies in threads, and @mentions of your bot. Askel delivers the event payload to your configured endpoint so your product can respond in near real time.
Fetch the last N messages from a channel or a specific chat thread. Useful for building context-aware responses, audit exports, or activity feeds inside your product.
Initiate a conversation with a specific Teams user even without a prior message from them. Practical for onboarding prompts, approval requests, and escalation alerts that need guaranteed delivery.
For customers who prefer a simpler setup, Askel can also use a connector webhook URL to post formatted messages into a channel without requiring admin consent for the full Graph scope.
You sell a customer-success platform. A new customer, Bridgewater Manufacturing, runs entirely on Microsoft 365 and Teams. Their CS team monitors account health in your product but wants critical risk alerts posted directly to their #account-escalations Teams channel so nothing falls through the cracks during busy sprints.
Bridgewater's Microsoft 365 admin clicks Connect Teams inside your product. Askel launches the Microsoft consent screen listing the Graph scopes required: ChannelMessage.Send, Channel.ReadBasic.All, and Team.ReadBasic.All. The admin approves, and Askel stores the refresh token.
Askel reads Bridgewater's teams and channels and presents them in your settings UI. The CS lead selects the Bridgewater Engineering team and the #account-escalations channel. Your product stores the channel ID against the Bridgewater account record.
In your product, create a workflow: when an account's health score drops below 40, call the Askel API to post an adaptive card to the stored channel. The card shows account name, health score, days since last activity, and a deep link to the risk view in your product.
Register a channel subscription so that when a CS rep replies to the alert card inside Teams, your product receives the message payload. The reply is logged against the account's activity timeline, closing the loop without requiring the rep to switch apps.
Trigger a manual health-score drop on a test account. The adaptive card appears in #account-escalations within seconds. A CS rep replies from Teams, and the reply surfaces in your product's activity log. Askel's delivery log confirms Graph accepted the message and the subscription is active.
Customer's Microsoft 365 admin clicks Connect inside Askel and consents to the requested Microsoft Graph scopes on the Microsoft consent screen. Askel stores the refresh token; per-request access is bounded to the channels and teams granted.
© 2025 Askel.ai. All rights reserved.