Make the next decision visible.

PDCC turns your Gmail and personal Telegram signals into an owned, explainable attention queue. Connect an identity to begin.

Fail-closed by defaultTelegram content stays restricted. Unknown, mixed, expired, or unauthorised provenance never becomes an AI input.

FIRST STEP

Connect your workspace

Your PDCC account owns every profile, chat selection and action.

or connect Telegram after Google sign-in

Google login establishes your PDCC identity. Telegram QR is a separate account connection and never uses a made-up challenge. Connect Telegram from the signed-in workspace.

Dashboard

Attention and projects in one board — every number drills down to owned evidence.

Settings

Sources and what each connector is allowed to capture.

CONNECTED SOURCES · CAPTURE DETAIL

ADD A SOURCE

GHGitHub

SLSlack

JRJira

WAWhatsApp

OLOutlook

CALCalendar

GitHub, Jira, WhatsApp, Outlook and Calendar connectors are not deployed in this staging environment.

Slack · read-only public channels

Checking owner-bound Slack installation…

Read-only, AI denied. Slack message text is not stored by this integration.

Stopping signals here disables PDCC routing; remove the app separately in Slack to uninstall it from the workspace.

ACCOUNT CONTROLS

Profiles and chat monitoring

owner-bound

Notifications

Push contains no source content. Opening or resuming always synchronizes authoritative state.

Checking this device…

Telegram chats

Reply Center

ACTION PLAN · REVIEW BEFORE SEND

Account
Target
Reply reference
Draft version
Authorization

Live authenticated API and ownership checks are required.