Changelog
What is new in ColdMeetings
New in ColdMeetings, one entry per area: the API, domains, campaigns, prospects, replies and sending guards.
The API
A REST API for the whole workflow, with a machine-readable description and one error format.
- Endpoints for the account, plans, sending domains, mailboxes, campaigns, prospects, events, replies and the suppression list.
- An OpenAPI 3.1 document and an llms.txt file describe every endpoint.
- Requests carry a bearer key that starts with cm_live_. Every error uses one envelope with a code, a message, a fix, a docs link, a retryable flag and a request id.
Domains and DNS record checks
Register a sending domain you already own, get the records it needs and check them against live DNS.
- Registering a domain returns the SPF and DMARC records to publish, and the DKIM record once the mailbox host has issued its key.
- The check reads live DNS for SPF, DKIM and DMARC. A domain counts as authenticated only when all three are published.
- Plans cap the number of sending domains: 12 on Professional, 40 on Enterprise.
- Mailboxes show their daily send capacity. A new mailbox starts at 5 sends a day and grows by age to 40 a day from the fifth week, through real low-volume sends. There is no warmup pool.
Campaigns with sequences
Draft a campaign, write its sequence, see what blocks launch, pause it and read its report.
- A sequence has up to 6 steps and up to 4 variants per step, for A/B tests. The first step has no delay and later steps wait at least a day.
- A preflight check lists everything that still blocks a launch: the plan, the sequence, missing prospects and missing authenticated mailboxes.
- Pausing always pauses the campaign here, even when the sending engine cannot be reached.
- The report shows sent, bounce, complaint and reply rates, reply intents and meetings booked.
- Active campaigns are capped by plan: 5 on Professional, 20 on Enterprise.
Prospect import gates
Every imported prospect passes the same gates, and a skipped one is listed with its reason.
- Duplicates inside the request and addresses already imported are skipped.
- Addresses on your suppression list are skipped.
- Prospects in the EU, the UK and Israel are skipped as region blocked.
- Each address is verified. Only valid ones are imported, and risky ones only when you ask for them.
- Each imported prospect costs one credit. Credits are held first, charged only for prospects imported, and released if the import fails.
Reply handling and the opt-out rule
Replies are recorded and sorted, and a request to stop is always honored first.
- Opt-out wording such as unsubscribe, remove me, take me off, opt out, or do not email is matched by a fixed rule before anything else runs.
- A match marks the reply as an opt-out and adds the address to the suppression list at once.
- A meeting cannot be booked for an address on the suppression list.
Sending guards
Checks that run in code, so a campaign cannot skip them.
- Every step of a sequence must contain the unsubscribe token and the sender address token, or the sequence is refused.
- A subject that pretends to be part of an earlier thread, such as one starting with Re: or Fwd:, is refused.
- A hard bounce or a spam complaint suppresses the address.
- A campaign is paused after 3 complaints, or when complaints pass 0.3 percent of messages sent once at least 100 have gone out.
This website
The first version of the public site.
- Pages for how it works, the product, pricing, documentation, the help center, free calculators, this changelog, about, contact and the legal pages.
- Every page has a plain markdown version, and the site publishes a sitemap and an llms.txt file.