Cardinal

Create a dedicated getting-started or onboarding page that explains the email warmup process, including how long it typically takes before users can send at full volume. This is a critical question for buyers switching from manual outreach.

Create a dedicated integrations or Salesforce sync documentation page that specifies sync frequency (real-time, polling interval, or batch schedule) for lead status updates and reply tracking.

Create a dedicated API documentation or integrations page that lists all webhook events Cardinal fires, including replies, opens, bounces, unsubscribes, and meeting bookings with their event names and payloads.

Add a pricing or limits page that specifies daily/monthly caps on AI-powered contact enrichment and verification. Buyers evaluating outbound tools need to understand usage limits before committing.

Create a dedicated pricing, limits, or FAQ page that specifies whether there are hard limits on active outbound campaigns or if limits are based solely on email volume.

Create a dedicated migration page or FAQ section addressing data import from competitors like Outreach.io, including specifics on sequences, templates, and engagement history transfer.

Create documentation or a help center article explaining how Cardinal's A/B testing for subject lines works, specifically whether it uses statistical significance testing or fixed send counts to declare winners.

Create a dedicated page or documentation section covering campaign health monitoring, including bounce rate thresholds, automatic pausing logic, and alert/notification settings.

Create documentation or a feature page explaining how Cardinal's AI handles email reply classification, including whether it auto-tags by sentiment (interested/not interested/out of office) or only flags responses.

Create a dedicated Data Retention, Privacy Policy, or Security page that specifies data retention periods post-churn and GDPR deletion rights. Consider adding a GDPR/CCPA section to an existing legal or trust page.

Create a dedicated pricing or support page that specifies support SLAs by tier, including response time commitments (e.g., same-day vs. priority support).

Create documentation explaining how domain authentication works for email sending, including whether Cardinal automatically handles SPF/DKIM or if users need to configure DNS records themselves.

Create a dedicated pricing page that includes details on email send limits, overage policies, and what happens when limits are reached (auto-upgrade, pause, or overage fees).

Create a dedicated pricing page that clearly states minimum seat requirements, per-seat pricing, and whether small teams (2-3 users) can start and scale up. Consider adding a 'Plans' or 'Pricing' section to the main navigation.