CRM user
For day-to-day contact, pipeline, inbox, SMS, call, and campaign usage.
- Start with the User Guide.
- Use the Internal Operations Guide for campaign rules.
The CRM docs are now organized around tasks and audiences. Technical depth still exists, but the admin-only material lives behind a private runbook instead of being the first thing teammates see.
Pick the path that matches the person, not the file name.
For day-to-day contact, pipeline, inbox, SMS, call, and campaign usage.
For email/SMS campaign setup, approval, metrics, opt-in rules, and guardrails.
For architecture, provider routing, cron jobs, storage, costs, and operational checks.
For code, CLI, Codex, GitHub, and change-management workflow.
For a quick understanding of readiness, limitations, and current campaign posture.
For evidence from a past health check or implementation review.
Short version of what is live today.
| # | Area | Current State |
|---|---|---|
| 1 | Production CRM | https://crm.acquira.co |
| 2 | Email campaigns | Resend Transactional Pro, 50,000 monthly emails, unlimited daily sends, CRM sends through Resend Email API. |
| 3 | SMS campaigns | Twilio Marketing Messaging Service. Hard-capped at 500 recipients per campaign and 500 campaign recipients per day by default. |
| 4 | Inbox | Gmail-backed shared inbox. Default view should cover the last 3 months. |
| 5 | Metrics | Campaign stats use CRM campaign recipient rows plus provider webhooks stored in CRM. Email also includes clicked links, recipient geography, and Open/Read Trends for schedule planning. |
| 6 | Known caveats | Duplicate cleanup, manual-review duplicate groups, GitHub Actions billing/spending-limit block, advanced nested segment groups, and database governance follow-ups. |
How to keep the docs useful after this cleanup.
| # | Rule | Description |
|---|---|---|
| 1 | One front door | New teammates should start here instead of choosing from a long document list. |
| 2 | User pages stay task-first | User-facing pages explain what to do, when to do it, and which guardrails matter. |
| 3 | Admin details stay private | Provider IDs, routing internals, cron details, storage internals, and deeper cost notes belong in the private Admin System Runbook. |
| 4 | Freshness metadata stays visible | Maintained pages show last-reviewed date, audience, and source-of-truth status. |
| 5 | Health checks are audit history | Dated health checks record evidence from a review. They are not the main operating manual. |