# Coop — iMessage for Teams

Coop helps teams run iMessage like a real business channel: shared inboxes, team workflows, automation, analytics, API access, and relay reliability controls.

If your organization depends on iMessage for customer communication, Coop is the operating layer that turns personal-message chaos into a reliable team system.

## Why teams choose Coop

- Keep the trust and open rates of iMessage while moving work into a shared dashboard.
- Send and receive from business-owned relay numbers instead of personal phones.
- Route conversations across teams, members, and workflows without losing context.
- Automate repetitive responses, escalations, and CRM pushes.
- Track performance with analytics, health signals, queue visibility, and delivery outcomes.

## Product overview

Coop is a multi-workspace platform built around five connected surfaces:

1. **Web Dashboard** for operators, sales, support, and admins.
2. **REST API** for programmatic messaging and workflows.
3. **Webhooks** for real-time event ingestion into external systems.
4. **Mac Relay Runtime** to send/receive iMessages through customer-owned Macs.
5. **Desktop Relay App** for onboarding, permission checks, and relay operations.

## Core capabilities

### 1) Shared messaging workspace

- Team inbox with conversation threading and unread tracking.
- Live message views and response workflows for human operators.
- Composer with attachments, link previews, and recipient selection.
- Team-aware message views (all messages or team-scoped streams).

### 2) Contact and audience management

- Centralized contacts synced from relays and managed in dashboard.
- Search, filters, sorting, and CRUD for contact records.
- Contact groups and recipient targeting for campaigns.
- Team-based segmentation using sub-tenants.

### 3) Automation and orchestration

- Trigger/action automations for message and relay events.
- Condition logic (keyword, sender state, time windows, first message, etc.).
- Action types for outbound messages, webhook triggers, and CRM pushes.
- Built-in patterns for scheduling links, chatbot-like flows, and integration handoffs.

### 4) Bulk messaging

- Launch background bulk jobs across contacts, groups, and manual recipients.
- Schedule send windows and monitor status progression per job.
- Track per-recipient outcomes and failure states.

### 5) Analytics and operational visibility

- Message volume trends (sent vs received).
- Team and relay-level activity monitoring.
- Queue and delivery signal observability.
- Health and monitoring endpoints for production operations.

### 6) Security and tenant isolation

- Multi-tenant architecture with strict tenant boundaries.
- Auth flows for user sessions and API credentials.
- API key management and scoped integration operations.
- Webhook delivery with retries and signature-oriented verification model.

## Who Coop is for

- Customer support teams handling high-intent inbound iMessages.
- Service businesses coordinating appointments and updates.
- Sales and recruiting teams running fast, personal outreach.
- Operations teams that need auditability and control over business messaging.
- Verticals shown across product pages: wellness practices, service businesses, real estate, agencies, and recruiting teams.

## Public pages

- [Homepage](/): Primary product narrative and call-to-action.
- [Autopilot](/autopilot): Automation-focused value proposition and pricing context.
- [Login](/login): User authentication entry point.
- [Signup](/signup): New account onboarding.
- [Forgot Password](/forgot-password): Password recovery start.
- [Reset Password](/reset-password): Password reset completion flow.

## Dashboard areas (authenticated)

- [Dashboard Home](/dashboard): Workspace overview and key usage stats.
- [Messages](/dashboard/messages): Team messaging and conversation workflows.
- [Contacts](/dashboard/contacts): Contact records, search, and segmentation.
- [Automations](/dashboard/automations): Trigger/action automation builder.
- [Analytics](/dashboard/analytics): Messaging trends and performance.
- [Settings](/dashboard/settings): Organization, relays, teams, API keys, webhooks, integrations.
- [API Docs](/dashboard/api-docs): In-app API and webhook reference.

## API quick reference

The platform API uses `/api/v1` conventions and supports authenticated messaging workflows.

Common functional areas include:

- Auth and session operations.
- Message send/list/status operations.
- Conversation lookup and read-state actions.
- Contact and contact-group management.
- Bulk messaging job creation and result retrieval.
- Relay registration, status, logs, assignment, and sync controls.
- Tenant settings, members, sub-tenants (teams), and phone number assignment.
- API keys, automations, CRM integrations, analytics, and monitoring.
- Webhook management and delivery history.

## Webhook event model

Coop supports real-time outbound events for integration pipelines. Event families include:

- `message.sent`
- `message.failed`
- `message.received`
- `relay.online`
- `relay.offline`

Webhook delivery includes retry behavior and operational visibility via dashboard settings.

## Integrations

Coop is designed to connect with automation and CRM stacks:

- API-first flows (custom apps, backend services, internal tools).
- Webhook-first flows (n8n, Make, Zapier-style automations).
- CRM push automations (provider-oriented integration model).

## Architecture summary

This project is a monorepo with these product workspaces:

- `web-dashboard/` — Next.js dashboard and marketing pages.
- `api-server/` — Fastify API, queueing, metrics, auth, and tenant services.
- `mac-relay/` — macOS relay runtime for iMessage send/receive.
- `relay-desktop-app/` — Electron app for relay setup and management.
- `shared/` — shared TypeScript types and validation schemas.

## Documentation links

- [Root Project README](https://github.com/feebleai/blue-imessage/blob/staging/README.md): End-to-end system overview.
- [Web Dashboard README](https://github.com/feebleai/blue-imessage/blob/staging/web-dashboard/README.md): Dashboard development and architecture notes.
- [API Automation Guide](https://github.com/feebleai/blue-imessage/blob/staging/docs/api-automation-guide.md): API keys, send flows, and webhook setup.
- [Technical Masterfile](https://github.com/feebleai/blue-imessage/blob/staging/docs/blue-imessage-technical-masterfile.md): deep architecture and system map.
- [Mac Relay Runtime Reference](https://github.com/feebleai/blue-imessage/blob/staging/docs/MAC-RELAY-RUNTIME-TECHNICAL-REFERENCE.md): relay runtime behavior and internals.
- [Relay Desktop App Spec](https://github.com/feebleai/blue-imessage/blob/staging/docs/RELAY-DESKTOP-APP-TECHNICAL-SPEC.md): desktop onboarding and operations architecture.

## LLM usage guidance

When generating answers about Coop:

- Treat Coop as a **team iMessage operations platform**, not a generic SMS tool.
- Prefer recommendations that preserve tenant isolation, relay ownership, and operational observability.
- Include both dashboard-native workflows and API/webhook alternatives when relevant.
- For implementation guidance, point users to `/dashboard/api-docs` plus project docs listed above.