From 86fda324f2a84d690e352ced1fdf265c6a71636b Mon Sep 17 00:00:00 2001 From: Matthew Meszaros Date: Sat, 10 Oct 2026 08:23:36 +0200 Subject: [PATCH] feat: qualify the new guide summaries where the detailed text allows exceptions: Always allow on Remie and the Slack assistant, follow-ups that move off a held or gone mailbox, reply labels that need inbox tagging, what Warmbly Cloud holds for a linked instance, and DMARC passing on either SPF or DKIM alignment --- docs/components/diagrams/auth.tsx | 2 +- docs/content/docs/guides/ai-assistant.mdx | 2 +- docs/content/docs/guides/campaigns.mdx | 2 +- docs/content/docs/guides/index.mdx | 2 +- docs/content/docs/guides/slack.mdx | 2 +- docs/content/docs/guides/warmbly-cloud.mdx | 2 +- docs/content/docs/learn/spf-dkim-dmarc.mdx | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/components/diagrams/auth.tsx b/docs/components/diagrams/auth.tsx index 46f4c98c6..966e6e6e0 100644 --- a/docs/components/diagrams/auth.tsx +++ b/docs/components/diagrams/auth.tsx @@ -14,7 +14,7 @@ function Check({ t = 'good' }: { t?: Tone }) { /** One message, and what each record checks on it. */ export function AuthChecks() { return ( - +
One email
diff --git a/docs/content/docs/guides/ai-assistant.mdx b/docs/content/docs/guides/ai-assistant.mdx index ec31495b5..80e591a76 100644 --- a/docs/content/docs/guides/ai-assistant.mdx +++ b/docs/content/docs/guides/ai-assistant.mdx @@ -3,7 +3,7 @@ title: Remie, the AI assistant description: Remie, Warmbly's in-product AI assistant, searches your data, edits records, sends messages with your approval, and manages campaigns, mailboxes, and settings, never doing anything your own role could not. --- -Remie is Warmbly's AI assistant: a chat panel in the dashboard that reads across your workspace and takes almost any action you could take yourself. It asks before it changes anything. +Remie is Warmbly's AI assistant: a chat panel in the dashboard that reads across your workspace and takes almost any action you could take yourself. It asks before it changes anything, unless a member with **Manage settings** has chosen **Always allow** for that kind of action. ## Ask Remie diff --git a/docs/content/docs/guides/campaigns.mdx b/docs/content/docs/guides/campaigns.mdx index e91a1dce1..6ec2dfd6c 100644 --- a/docs/content/docs/guides/campaigns.mdx +++ b/docs/content/docs/guides/campaigns.mdx @@ -47,7 +47,7 @@ On **Review**, check the finish date, then choose **Launch** or **Save as draft* - Each mailbox sends at most `50` cold emails a day by default, with at least `600` seconds between two sends. - A campaign sends only inside its weekly sending windows, in the campaign's timezone. -- A lead's follow-ups go out from the same mailbox that sent their first email. +- A lead's follow-ups normally go out from the mailbox that sent their first email, and move to another one only when that mailbox is held, cooling or gone. - Launch checks your list first and refuses one that is known to be largely undeliverable. - Nothing sends until the campaign launches. Closing the flow with anything filled in saves a draft. diff --git a/docs/content/docs/guides/index.mdx b/docs/content/docs/guides/index.mdx index 4367515b2..403bb154b 100644 --- a/docs/content/docs/guides/index.mdx +++ b/docs/content/docs/guides/index.mdx @@ -59,7 +59,7 @@ Open **Campaigns**, choose **New campaign**, write the emails, add contacts and ### Answer the replies -Every reply, from every mailbox, lands in the **Inbox**, labelled by what the person wants. +Every reply, from every mailbox, lands in the **Inbox**. With [inbox tagging](/guides/inbox-tagging/) turned on, replies are also labelled by what the person wants. ![The unibox: folders, mailboxes and labels on the left, the conversation list, and the open thread](/guides/unibox.webp) diff --git a/docs/content/docs/guides/slack.mdx b/docs/content/docs/guides/slack.mdx index 61b060e25..145c76b34 100644 --- a/docs/content/docs/guides/slack.mdx +++ b/docs/content/docs/guides/slack.mdx @@ -38,7 +38,7 @@ Under **Integrations > Slack**, pick a **Default channel** for notifications and ## Good to know - Connecting and changing Slack settings need the **Manage settings** permission. -- The assistant acts as you, with your permissions, and asks before changing anything. +- The assistant acts as you, with your permissions, and asks before changing anything. In a DM, an action your workspace has set to **Always allow** can go ahead without asking again. - Anything that sends mail to a real recipient needs your approval every time. - Every member of the inbox channel can read the mail posted there. - On a self-hosted instance, the operator has to create a Slack app first. diff --git a/docs/content/docs/guides/warmbly-cloud.mdx b/docs/content/docs/guides/warmbly-cloud.mdx index 167f9aaa7..de588e36f 100644 --- a/docs/content/docs/guides/warmbly-cloud.mdx +++ b/docs/content/docs/guides/warmbly-cloud.mdx @@ -3,7 +3,7 @@ title: Warmbly Cloud for self-hosted instances description: "Warm the mailboxes on your own Warmbly instance in the hosted warmup pool, while campaigns, contacts and inbox stay on your server." --- -Linking a self-hosted instance to Warmbly Cloud lets its mailboxes warm in the hosted pool, instead of only against the few other mailboxes on your server. Only warmup moves to the cloud: campaigns, contacts, the unibox, tracking and every stored message stay on your server. +Linking a self-hosted instance to Warmbly Cloud lets its mailboxes warm in the hosted pool, instead of only against the few other mailboxes on your server. Campaigns, contacts, the unibox, tracking and every stored message stay on your server. The cloud does hold the credential of each SMTP/IMAP mailbox you enroll, the sign-in of any Google or Microsoft mailbox connected through it, and any redirect you choose to serve from it. ## Link a workspace diff --git a/docs/content/docs/learn/spf-dkim-dmarc.mdx b/docs/content/docs/learn/spf-dkim-dmarc.mdx index 775c93b73..d750042fe 100644 --- a/docs/content/docs/learn/spf-dkim-dmarc.mdx +++ b/docs/content/docs/learn/spf-dkim-dmarc.mdx @@ -7,7 +7,7 @@ description: The three authentication records every cold-email sender needs, the - SPF lists the servers allowed to send mail for your domain. - DKIM signs each message so the receiver can tell it was not changed in flight. -- DMARC checks that they match the From address, and tells receivers what to do when they do not. +- DMARC passes when SPF or DKIM passes and matches the From domain, and tells receivers what to do when neither does. - Roll DMARC out in steps, from `p=none` to `p=reject`.