Document mixed-cohort Free and Pro rollout - #53
Conversation
roshanjonah
commented
Aug 24, 2026
roshanjonah
commented
- Documents Free at two mailboxes and 50 provider-accepted recipients per UTC day, plus Pro at $7 per team per month.
- Publishes per-event rates of $0.000500 for connected outbound and inbound, and $0.000750 for managed Amazon SES.
- Explains that new teams enter the new plans at activation while existing teams retain current access until the September 24 cutover.
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9b0ee919c0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| If you're using a Free team, you can have **1 domain**. Check your current | ||
| limit on the **Domains** page. Free limits are fixed. If you need more | ||
| capacity, delete an unused domain or upgrade to Pro. See [Team |
There was a problem hiding this comment.
During the pre-cutover window, this applies the fixed-limit instruction to every Free team, although account/team-limits.mdx:40 says legacy teams can still use increase requests until 24 September. A legacy Free owner whose Domains page still offers that action is therefore incorrectly told to delete a domain or upgrade; qualify this note for new-plan Free teams or document the legacy exception.
AGENTS.md reference: AGENTS.md:L5-L5
Useful? React with 👍 / 👎.
|
|
||
| With Free, you get two mailboxes and can send to up to 50 provider-accepted recipients per UTC day across all sending routes. These limits are fixed. If you hit one, delete an unused resource or upgrade to Pro. Provider quotas, safety controls, account health restrictions, and managed Amazon SES limits still apply on Pro. | ||
|
|
||
| Every account can have one active Free team. Existing paid access, resources, and balances remain in place during the rollout. |
There was a problem hiding this comment.
This states that one active Free team is already a universal account limit, but the updated changelog says additional existing Free teams become read-only only from the 24 September effective date. During the mixed-cohort rollout, accounts with grandfathered active Free teams can therefore exceed this number; qualify the statement for new-plan teams or state when the restriction starts.
AGENTS.md reference: AGENTS.md:L5-L5
Useful? React with 👍 / 👎.
| New Free teams may add **one** account of their own. The managed account is not included in this limit. The **Accounts** page displays your current limit and allows you to request more capacity when usage reaches 80%. | ||
| | Plan | Your own sending accounts | More capacity | | ||
| | ---- | ------------------------- | ------------- | | ||
| | Free | 1; the managed account does not count | Delete an account or upgrade to Pro | |
There was a problem hiding this comment.
After this section changes Free capacity to deletion or upgrade only, use-cases/cold-email-outreach.mdx:261-265 still tells readers of the new-Free sending-account limit to follow these links “for capacity requests.” New Free teams cannot submit such a request, so update that FAQ as part of this rollout to direct them to deletion or Pro instead.
AGENTS.md reference: AGENTS.md:L5-L5
Useful? React with 👍 / 👎.
1 participant
