Freshness: Last reviewed 2026-05-20. Audience: see page title and Start Here path. Status: current unless marked archived or private.
ACQ CRM Start Here Back to Home
Task-First Docs

Start here, then choose the guide by the job you are trying to do.

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.

Last Reviewed

May 26, 2026Update this date after any workflow, quota, provider, or docs hierarchy change.

Private Depth

Admin RunbookArchitecture, provider IDs, routing, cron jobs, storage, costs, and health checks are kept in the private runbook.

Audience Paths

Pick the path that matches the person, not the file name.

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.

Campaign operator

For email/SMS campaign setup, approval, metrics, opt-in rules, and guardrails.

  • Start with Internal Operations Guide.
  • Use Health Dashboard in CRM for live status.

System admin

For architecture, provider routing, cron jobs, storage, costs, and operational checks.

  • Use the private Admin System Runbook.
  • Do not share provider IDs in user-facing docs.

Repo contributor

For code, CLI, Codex, GitHub, and change-management workflow.

  • Start with Operations Guides.
  • Follow the Change Management Protocol.

Leader or reviewer

For a quick understanding of readiness, limitations, and current campaign posture.

  • Start here.
  • Use Health Dashboard for live status.

Historical audit

For evidence from a past health check or implementation review.

  • Use dated health-check reports only as snapshots.
  • Do not treat old reports as current behavior.

Current State Summary

Short version of what is live today.

#AreaCurrent State
1Production CRMhttps://crm.acquira.co
2Email campaignsResend Transactional Pro, 50,000 monthly emails, unlimited daily sends, CRM sends through Resend Email API.
3SMS campaignsTwilio Marketing Messaging Service. Hard-capped at 500 recipients per campaign and 500 campaign recipients per day by default.
4InboxGmail-backed shared inbox. Default view should cover the last 3 months.
5MetricsCampaign 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.
6Known caveatsDuplicate cleanup, manual-review duplicate groups, GitHub Actions billing/spending-limit block, advanced nested segment groups, and database governance follow-ups.

Documentation Rules

How to keep the docs useful after this cleanup.

#RuleDescription
1One front doorNew teammates should start here instead of choosing from a long document list.
2User pages stay task-firstUser-facing pages explain what to do, when to do it, and which guardrails matter.
3Admin details stay privateProvider IDs, routing internals, cron details, storage internals, and deeper cost notes belong in the private Admin System Runbook.
4Freshness metadata stays visibleMaintained pages show last-reviewed date, audience, and source-of-truth status.
5Health checks are audit historyDated health checks record evidence from a review. They are not the main operating manual.