Skip to content

fix(console): preserve enterprise Chatwoot routing on dev - #47489

Closed
Slickstef11 wants to merge 1 commit into
devfrom
enterprise-chatwoot-live
Closed

fix(console): preserve enterprise Chatwoot routing on dev#47489
Slickstef11 wants to merge 1 commit into
devfrom
enterprise-chatwoot-live

Conversation

@Slickstef11

Copy link
Copy Markdown
Contributor

Why

Companion to production hotfix #47488 for https://opencode.ai/enterprise. Keep the same fix on dev so a subsequent production release preserves the intended enterprise form email routing.

The original #47437 targeted v2, which is not the live website deployment path. This branch starts from the shared dev/production commit and contains only the four-line email routing change; no V2 changes are included.

What

  • Replace the hardcoded shared mailbox destination with Resource.ENTERPRISE_SALES_INBOX_EMAIL.value.
  • Declare and link that SST secret to Console.
  • Preserve Salesforce, EmailOctopus, email content, subject, and prospect Reply-To.

Deployment prerequisite

Configure ENTERPRISE_SALES_INBOX_EMAIL for the dev SST stage before merging, using the team's intended development inbox destination. Do not publish the address in this PR.

Local SST verification is blocked by unavailable Cloudflare API credentials. The stage secret has not been confirmed. This PR deploys the development site only; #47488 is the PR that targets the live production website.

Verification

  • bun install --frozen-lockfile with Bun 1.3.14.
  • bun typecheck in packages/console/app — passed.
  • Repository pre-push hook — all 30 typecheck tasks passed.
  • git diff --check — passed.
  • Two changed files, three additions, one deletion.

Port the email routing fix from #47437 onto the production website release path without bringing in V2 changes.
@Slickstef11 Slickstef11 closed this Sep 5, 2026
@vimtor
vimtor deleted the enterprise-chatwoot-live branch September 5, 2026 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants