My Daily Brief shows a holding banner instead of a real read
My Daily Brief shows a holding banner instead of a real read
I imported a CSV but no metrics populated
I imported a CSV but no metrics populated
Forepost couldn’t find a usable
created_at column. Open ▸ Adjust column mapping below the upload area and pick the right column manually.If you’ve already mapped created_at and the preview is still blank, the column values aren’t parsing as dates. Check that the CSV uses ISO timestamps or a common locale format (e.g. 2026-05-09T12:00:00Z or 09/05/2026 12:00).My Daily Brief email landed in spam
My Daily Brief email landed in spam
This is almost always a first-time-sender learning phase issue. Once:
- Mark the message as not spam in Gmail/Outlook.
- Add
noreply@forepost.aito your contacts.
dkim=pass, spf=pass, dmarc=pass in the email’s authentication headers. If dmarc=fail appears, contact kian@forepost.ai."Send brief now" returns an error
"Send brief now" returns an error
| Status | Meaning | Fix |
|---|---|---|
400 with a missing field | Workspace below the completeness threshold | Fill in the named fields in Settings |
| 403 “Email not verified on this account” | Subscription email isn’t verified on your Clerk account | Verify it in your account settings, then save |
| 429 “Too many sends” | You’ve hit the rate limit (5/hour for manual sends) | Wait an hour. Scheduled sends aren’t affected. |
I'm not receiving Weekly Watch even though it's enabled
I'm not receiving Weekly Watch even though it's enabled
Three checks:
- The digest only sends on Mondays in your local timezone. Today might just not be Monday.
- It only sends if your workspace is data-complete that morning. See above.
- It only sends once a week — if the previous one was sent within the last 6 days, the next won’t send yet.
Triage isn't drafting replies for new conversations
Triage isn't drafting replies for new conversations
Three checks:
- Intercom must be connected. Settings → Integrations → Helpdesk integrations. The OAuth token is required for both polling and sending.
- Triage must be enabled. Settings → Integrations → Triage. The toggle gates the cron poll and the nav item.
- The poll cadence is every ~10 minutes. Click Poll Intercom on the Triage page to force one immediately.
drafted: 0 in that case.A Triage draft failed to Send to Intercom
A Triage draft failed to Send to Intercom
Two common causes:
- The conversation closed in Intercom since the draft was generated. Triage will mark it
resolvedon the next poll. Discard the draft. - Your Intercom token expired or was revoked. Reconnect via Settings → Integrations → Helpdesk integrations.
Accounts → Sync from Intercom returned 0 accounts
Accounts → Sync from Intercom returned 0 accounts
Intercom returned no companies for your workspace. Two checks:
- Your Intercom workspace actually has companies attached (some teams skip the company model). Forepost’s sync uses the Companies API; if you only use individual contacts, this won’t populate.
- The OAuth scope you authorised includes company read. Reconnect Intercom to re-grant scopes if needed.
The forwarded email opens with no recipient
The forwarded email opens with no recipient
That’s expected. Forepost composes the subject and body but doesn’t fill in the To: line — you choose the recipient in your mail client. Intentional: the email goes from your account, with your signature.
Still stuck?
Email kian@forepost.ai with:- The page or action that broke
- A screenshot of the error if there is one
- Your account email address