# Raintree Follow-Up Desk Capability Claims

> This ledger is meant to make the home page easier to audit. It is not a substitute for live verification against current official platform docs.

Verdicts here describe platform mechanisms, not whether a specific customer workspace has already granted access. Every integration depends on customer configuration, installation, OAuth scopes, admin policy, data retention, and the product scope agreed during onboarding.

## Claim Ledger

| Page claim or depiction | Capability verdict | Appearance verdict | Caveats | Primary sources |
| --- | --- | --- | --- | --- |
| Raintree can post or reply in Slack channels or DMs as an app/bot. | Supported. Slack apps can post messages to public channels, private channels, DMs, and threads when the app has the right permissions and channel access. | Idealized but achievable. Real Slack messages must use Slack message surfaces and Block Kit, not arbitrary CSS. | Requires Slack app installation, `chat:write`-style permissions, channel membership where applicable, and workspace policy approval. | [Slack chat.postMessage](https://docs.slack.dev/reference/methods/chat.postMessage), [Slack Block Kit](https://docs.slack.dev/block-kit/) |
| Raintree can show structured Slack output such as source cards, checklists, buttons, and compact tables. | Supported with limits. Slack Block Kit supports structured message blocks and interactive elements; table blocks are documented for table-like output. | Idealized but achievable. The landing mockup should be read as a simplified representation of Block Kit output. | Slack imposes block counts, element constraints, accessibility fallback text, interaction handling, and rate limits. | [Slack blocks](https://docs.slack.dev/reference/block-kit/blocks), [Slack table block](https://docs.slack.dev/reference/block-kit/blocks/table-block), [Slack button element](https://docs.slack.dev/reference/block-kit/block-elements/button-element) |
| Raintree can read approved Slack channel history or thread replies to detect unanswered work. | Supported with limits. Slack documents retrieval of conversation history and thread replies. | Not a visual claim. | Requires history scopes and access to the relevant conversation. Slack has material rate-limit caveats, including stricter limits for `conversations.history` and `conversations.replies` on some commercially distributed non-Marketplace apps. | [Slack retrieving messages](https://docs.slack.dev/messaging/retrieving-messages), [Slack conversations.replies](https://docs.slack.dev/reference/methods/conversations.replies), [Slack scopes](https://docs.slack.dev/reference/scopes) |
| Raintree can post, update, or send proactive follow-up messages in Microsoft Teams. | Supported with limits. Teams bots can send and receive messages, and Teams documents proactive messages when the app is installed or otherwise allowed. | Idealized but achievable. Real Teams output is constrained by Teams bot messages and Adaptive Cards. | Proactive messaging requires app installation and conversation references or approved Graph installation flows. Notification content should explain why the user is receiving it. | [Teams bot conversations](https://learn.microsoft.com/en-us/microsoftteams/platform/bots/build-conversational-capability), [Teams proactive messages](https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/conversations/send-proactive-messages) |
| Raintree can show Teams blocker rows, owner tables, card actions, and short manager notes. | Supported with limits. Teams supports Adaptive Cards in bot and message extension contexts, including text, graphics, buttons, and card actions. | Idealized but achievable. The page's row/table treatment is a product illustration; Teams cards have their own renderer and styling limits. | Teams supports Adaptive Cards up to documented platform versions and notes limits such as unsupported positive/destructive action styling and mobile/narrow-form-factor truncation risks. | [Teams card types](https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-reference), [Teams card actions](https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-actions), [Teams card design](https://learn.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/design-effective-cards) |
| Raintree can read approved Teams posts, files, or notes to find delivery blockers. | Supported with important consent limits. Microsoft Graph can list channel messages and chat messages, and Teams supports RSC patterns for bots to receive channel/chat messages without @mentions in configured scopes. | Not a visual claim. | Requires tenant/app consent, resource-specific consent or Graph permissions, and may vary across standard channels, private/shared channels, chats, and protected APIs. Files usually live through SharePoint/OneDrive access rules. | [Graph list channel messages](https://learn.microsoft.com/en-us/graph/api/channel-list-messages?view=graph-rest-1.0), [Graph list chat messages](https://learn.microsoft.com/en-us/graph/api/chat-list-messages?view=graph-rest-1.0), [Teams RSC permissions](https://learn.microsoft.com/en-us/microsoftteams/platform/graph-api/rsc/resource-specific-consent), [Teams receive channel messages with RSC](https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/conversations/channel-messages-for-bots-and-agents) |
| Raintree can participate in LINE group chats and send follow-up messages. | Supported. LINE Official Accounts using the Messaging API can join group chats when enabled, receive webhook events, reply, and push messages to groups. | Idealized but achievable. Real LINE messages must use LINE-supported message types, bubbles, quick replies, and Flex Message constraints. | The bot must be invited and allowed to join groups. Messages sent through the Messaging API cannot be unsent or deleted through that API. | [LINE group chats](https://developers.line.biz/en/docs/messaging-api/group-chats/), [LINE send messages](https://developers.line.biz/en/docs/messaging-api/sending-messages/), [LINE Messaging API FAQ](https://developers.line.biz/en/faq/tags/messaging-api/) |
| Raintree can read LINE group chat history as an approved source. | Limited / easy to overstate. LINE webhooks can deliver new message events after the Official Account is present, but the page should not be read as claiming arbitrary historical backfill from LINE group chats. | Not a visual claim. | For LINE, Raintree should rely on messages received through webhooks while the bot is present, customer-provided records, or another approved source of truth. Avoid implying retroactive access to old LINE group history. | [LINE receive messages](https://developers.line.biz/en/docs/messaging-api/receiving-messages/), [LINE group chats](https://developers.line.biz/en/docs/messaging-api/group-chats/) |
| Raintree can read approved Gmail or shared inbox messages and draft/send email follow-ups. | Supported with consent and review. Gmail API supports authorized mailbox access and sending email. | Not a host-UI visual claim. | Requires OAuth scopes, user or domain consent, and possibly Google app verification/security review depending on scope sensitivity. Shared inbox behavior depends on how the inbox is implemented. | [Gmail API overview](https://developers.google.com/workspace/gmail/api/guides), [Gmail list messages](https://developers.google.com/workspace/gmail/api/guides/list-messages), [Gmail send message](https://developers.google.com/workspace/gmail/api/reference/rest/v1/users.messages/send), [Gmail scopes](https://developers.google.com/workspace/gmail/api/auth/scopes) |
| Raintree can search approved Google Drive folders, project files, and handoff docs. | Supported with consent. Drive API supports listing, searching, and retrieving file metadata or content when permitted. | Not a host-UI visual claim. | Requires declared OAuth scopes, Drive permissions, and possibly domain/admin approval. The product should not imply access to files the installing user or service account cannot access. | [Drive API overview](https://developers.google.com/workspace/drive/api/guides/about-sdk), [Drive search files](https://developers.google.com/workspace/drive/api/guides/search-files), [Drive files.list](https://developers.google.com/workspace/drive/api/reference/rest/v3/files/list), [Drive scopes](https://developers.google.com/workspace/drive/api/guides/api-specific-auth) |
| Raintree can watch approved Google Calendar signals such as meetings, dates, reminders, or due windows. | Supported with consent. Calendar API exposes calendars, events, free/busy data, settings, and related resources. | Not a host-UI visual claim. | Requires Calendar OAuth scopes and customer approval. "Due windows" may come from Calendar, operating notes, project tools, or customer rules rather than Calendar alone. | [Calendar API overview](https://developers.google.com/workspace/calendar/api/guides/overview), [Calendar API reference](https://developers.google.com/workspace/calendar/api/v3/reference), [Calendar scopes](https://developers.google.com/workspace/calendar/api/auth) |
| Raintree can save operating notes, rules, exceptions, source links, and decisions for future follow-ups. | Supported as product-owned storage, provided the customer authorizes what is saved. | Not a host-UI visual claim. | This is not a Slack/Teams/LINE platform guarantee. It depends on Raintree's own data model, retention policy, privacy controls, and customer agreement. | Product-owned capability; verify through Raintree implementation and policy, not a host-platform API alone. |
| Raintree can infer likely owners, stalled loops, next steps, and escalation timing. | Supported as application logic when based on approved source data. | Not a host-UI visual claim. | This is probabilistic workflow software, not a platform primitive. It should be reviewed by users and tuned per workflow. Avoid reading it as a guarantee of perfect attribution or fully autonomous management. | Product-owned capability; verify through Raintree implementation, customer configuration, and evaluation evidence. |
| The broad channel list includes Slack, Teams, LINE, WhatsApp, Telegram, Signal, Email, SMS, Google Chat, Discord, Mattermost, DingTalk, Feishu/Lark, and WeChat. | Vague / roadmap-like unless scoped in a specific customer deployment. Many of these platforms have bot APIs, but capability varies materially by platform, region, policy, approval, and message type. | Logo list is a channel-direction signal, not proof of feature parity. | Treat Slack, Teams, LINE, Gmail, Drive, and Calendar as the concrete mechanisms documented in this ledger. Treat other logos as potential integration targets until separately documented. | Platform-specific docs must be checked per target before making a production promise. |

## Overall Assessment

The home page's core promise is technically plausible when read narrowly: an installed, permissioned app can check approved sources, summarize stalled work, name likely owners, and bring follow-ups back to Slack, Teams, LINE, email, and related work systems. The honest caveats are material: host-platform UI is constrained, data access requires consent and scopes, Teams and Slack history access has permission and rate-limit realities, LINE should not be represented as arbitrary historical group-chat access, and "likely owner" or "what stalled" is product intelligence rather than a native platform guarantee.