Intry Ops overview
Internal tooling for support, onboarding, and incident response.
Overview
Intry Ops covers internal dashboards, scripts, and MCP-assisted workflows for staff managing tenants, diagnosing telephony issues, and keeping Core healthy.
Entry points
| Tool | Purpose |
|---|---|
tools/intry-admin | Admin SPA + Fly proxy for /api/admin/* |
tools/intry-ops | Tailscale-gated ops console |
tools/intry-mcp | Cursor-accessible admin operations |
| Chatwoot | Resident/PM AI support bots (src/webhooks/chatwoot-bot/) |
docs/ runbooks | Human procedures (MCP, Unkey, deploy, Telnyx cutover) |
Access control
- Tailscale identity for intry-ops (
tools/intry-ops/docs/TAILSCALE_ACCESS.md). - WorkOS or Clerk SSO for admin dashboard.
- Unkey keys with least privilege for automation — prefer read-only for investigations.
Support workflow (typical)
- Identify tenant + property + unit (
unitLabel). - Pull recent
/api/admin/callsfor the unit. - Verify virtual number mapping and carrier SID trail (Twilio or Telnyx).
- Check Device registrations if push failed.
- Review Knock workflow delivery if notifications missing.
Unified comms
Chatwoot integration for resident/PM chat: docs/UNIFIED_COMMS_SETUP.md.
Last verified: 2026-06-21 (commit 293c4a7)