Both, configurable per chatbot. Incoming Webhooks are simpler to set up and still widely supported for one-way notifications. Workflows triggered by When a Teams webhook request is received support richer two-way scenarios and are Microsoft's recommended path going forward. Pick whichever fits your tenancy.

A header with the chatbot name and visitor identifier, a body with the conversation transcript (last N messages, configurable), context fields like the originating page URL and mapped variables you choose to expose, and an action button that deep-links to the conversation in the WordPress admin.

Yes, and it is best practice. SleekAI shows a configurable handoff message in the chat widget like Connecting you with a teammate, this usually takes a minute. The widget then switches into waiting mode until a human responds via the return webhook or a configurable timeout fires.

On the Teams side, the Workflow gathers the human's reply (from a card response, a channel message, or an explicit form) and POSTs it back to a SleekAI endpoint with a signed payload. SleekAI matches the payload to the open conversation and renders the reply in the visitor's chat widget in real time.

Each chatbot has a fallback timeout. If no human responds within that window, SleekAI sends a configurable follow-up message to the visitor (Our team will reply by email shortly), captures the visitor's email if it is not already known, and continues the conversation through email through your Postmark, Mailgun, or SMTP integration.

Yes. The webhook URL is the only credential needed, and it is tenant-scoped by Microsoft so even the URL leaking outside Teams will not let an attacker post to channels they cannot otherwise access. SleekAI also signs return-webhook payloads with HMAC so spoofed return calls cannot inject bogus messages into a live chat.

Yes. Each chatbot has its own escalation configuration, so a sales bot can post to a sales-leads channel while a support bot escalates to a support-overflow channel, and an internal compliance bot escalates to a trust-and-safety channel. One install, multiple bots, multiple Teams destinations.

Microsoft has been gradually shifting from classic Office 365 Connectors to Workflows. SleekAI supports both the classic Incoming Webhook URL format and the Workflows trigger URL, so existing setups keep working and new setups can use the recommended Workflows path without changes on the SleekAI side.