* chore: Hide "Learn More" button in feature spotlight for self-hosted (#12675) * feat: single query for reporting event stats (#12664) This PR collapses multiple queries fetching stats from a single table to a single query ```sql SELECT user_id as user_id, COUNT(CASE WHEN name = 'conversation_resolved' THEN 1 END) as resolved_count, AVG(CASE WHEN name = 'conversation_resolved' THEN value END) as avg_resolution_time, AVG(CASE WHEN name = 'first_response' THEN value END) as avg_first_response_time, AVG(CASE WHEN name = 'reply_time' THEN value END) as avg_reply_time FROM "reporting_events" WHERE "reporting_events"."account_id" = <account_id> AND "reporting_events"."created_at" >= '2025-09-14 18:30:00' AND "reporting_events"."created_at" < '2025-10-14 18:29:59' GROUP BY "reporting_events"."user_id"; ``` ### Why this works? Here's why this optimization is faster based on PostgreSQL internals: - Single Table Scan vs Multiple Scans: Earlier we did 4 sequential scans (or 4 index scans) of the same data, with the same where clause, now in a single scan all 4 `CASE` expressions are evaluated in a single pass. - Shared Buffer Cache Efficiency: PostgreSQL's shared buffer cache stores recently accessed pages, with this, pages are loaded once and re-used for all aggregation, earlier with separate queries we were forced to re-read all from the disk each time - Reduced planning and network overhead (4 vs 1 query) ### How is it tested 1. The specs all pass without making any changes 2. Verified the reports side by side after generating from report seeder #### How to test Generate seed data using the following command ```bash ACCOUNT_ID=1 ENABLE_ACCOUNT_SEEDING=true bundle exec rake db:seed:reports_data ``` Once done download the reports, checkout to this branch and download the reports again and compare them * chore: Update translations (#12625) * chore: Migrate mailers from the worker to jobs (#12331) Previously, email replies were handled inside workers. There was no execution logs. This meant if emails silently failed (as reported by a customer), we had no way to trace where the issue happened, the only assumption was “no error = mail sent.” By moving email handling into jobs, we now have proper execution logs for each attempt. This makes it easier to debug delivery issues and would have better visibility when investigating customer reports. Fixes https://linear.app/chatwoot/issue/CW-5538/emails-are-not-sentdelivered-to-the-contact --------- Co-authored-by: Sojan Jose <sojan@pepalo.com> Co-authored-by: Shivam Mishra <scm.mymail@gmail.com> * chore(deps-dev): bump vite from 5.4.20 to 5.4.21 (#12700) Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.4.20 to 5.4.21. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vitejs/vite/releases">vite's releases</a>.</em></p> <blockquote> <h2>v5.4.21</h2> <p>Please refer to <a href="https://github.com/vitejs/vite/blob/v5.4.21/packages/vite/CHANGELOG.md">CHANGELOG.md</a> for details.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/vitejs/vite/blob/v5.4.21/packages/vite/CHANGELOG.md">vite's changelog</a>.</em></p> <blockquote> <h2><!-- raw HTML omitted -->5.4.21 (2025-10-20)<!-- raw HTML omitted --></h2> <ul> <li>fix(dev): trim trailing slash before <code>server.fs.deny</code> check (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/20968">#20968</a>) (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/20970">#20970</a>) (<a href="cad1d31d06">cad1d31</a>), closes <a href="https://redirect.github.com/vitejs/vite/issues/20968">#20968</a> <a href="https://redirect.github.com/vitejs/vite/issues/20970">#20970</a></li> <li>chore: update CHANGELOG (<a href="ca88ed7398">ca88ed7</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="adce3c22c6"><code>adce3c2</code></a> release: v5.4.21</li> <li><a href="cad1d31d06"><code>cad1d31</code></a> fix(dev): trim trailing slash before <code>server.fs.deny</code> check (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/20968">#20968</a>) (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/20970">#20970</a>)</li> <li><a href="ca88ed7398"><code>ca88ed7</code></a> chore: update CHANGELOG</li> <li>See full diff in <a href="https://github.com/vitejs/vite/commits/v5.4.21/packages/vite">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/chatwoot/chatwoot/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore: Update translations (#12708) * chore(sidekiq): log ActiveJob class and job_id on dequeue (#12704) ## Context Sidekiq logs only showed the Sidekiq wrapper class and JID, which wasn’t helpful when debugging ActiveJobs. ## Changes - Updated `ChatwootDequeuedLogger` to log the actual `ActiveJob class` and `job_id` instead of the generic Sidekiq wrapper and JID. > Example > ``` > Dequeued ActionMailer::MailDeliveryJob 123e4567-e89b-12d3-a456-426614174000 from default > ``` - Remove sidekiq worker and unify everything to `ActiveJob` * chore: Enforce custom role permissions on conversation access (#12583) ## Summary - ensure conversation lookup uses the permission filter before fetching records - add request specs covering custom role access to unassigned conversations ## Testing - bundle exec rspec spec/enterprise/controllers/api/v1/accounts/conversations_controller_spec.rb ------ https://chatgpt.com/codex/tasks/task_e_68de1f62b9b883268a54882e608a8bb8 * fix: parameterize agent name (#12709) * chore: Remove channel icons from the create inbox page (#12727) # Pull Request Template ## Description This PR removes the frame containing all channel icons from the “Create Inbox” page. ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) ## How Has This Been Tested? ### Screenshots **Before** <img width="1314" height="1016" alt="image" src="https://github.com/user-attachments/assets/2b773495-9ddb-48b4-b15d-9aef18259ce1" /> **After** <img width="1314" height="979" alt="image" src="https://github.com/user-attachments/assets/f4dc64cf-516c-4faf-a45c-2f7de05cc29b" /> ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules * fix: Use gap-4 instead of margins to define space between elements (#12728) We should avoid using margins to define space between elements, instead use the gap utility. The problem with this particular instance was that if Google auth was turned off and SSO is available, there is a weird spacing at the top caused by the margin from the SSO element. This PR will fix that. It also introduces a gap between the divider and the button, but that should be okay. * feat(ee): Add a service to fetch website content and prepare a persona of Captain Assistant (#12732) This PR is the first of many to simplify the process of building an assistant. The new flow will only require the user’s website. We’ll automatically crawl it, identify the business name and what the business does, and then generate a suggested assistant persona, complete with a proposed name and description. This service returns the following. Example: tooljet.com <img width="795" height="217" alt="Screenshot 2025-10-25 at 2 55 04 PM" src="https://github.com/user-attachments/assets/9cb3594a-9c9c-4970-a0a1-4c9c8869c193" /> Example: replit.com <img width="797" height="176" alt="Screenshot 2025-10-25 at 2 56 42 PM" src="https://github.com/user-attachments/assets/6a1b4266-aab6-455f-a5e3-696d3a8243c9" /> * chore: Adds URL-based search and tab selection (#12663) # Pull Request Template ## Description This PR enables URL-based search and tab selection, allowing search queries and active tabs to persist in the URL for easy sharing. Fixes [CW-5766](https://linear.app/chatwoot/issue/CW-5766/cannot-impersonate-an-account), https://github.com/chatwoot/chatwoot/issues/12623 ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? ### Loom video https://www.loom.com/share/422a1d61f3fe4278a88e352ef98d2b78?sid=35fabee7-652f-4e17-83bd-e066a3bb804c ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules * chore: Add tab params for inbox configuration (#12665) # Pull Request Template ## Description This PR enables active tabs in inbox settings to persist in the URL for easy sharing. ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? ### Loom video https://www.loom.com/share/63820ecb17ea491a9082339f8bb457b6?sid=4fef1acd-b4fd-431f-855c-7647015a330f ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules --------- Co-authored-by: Muhsin <muhsinkeramam@gmail.com> * feat: Changelog card components (#12673) # Pull Request Template ## Description This PR introduces a new changelog component that can be used in the sidebar. Fixes https://linear.app/chatwoot/issue/CW-5776/changelog-card-ui-component ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? ### Screencast https://github.com/user-attachments/assets/42e77e82-388a-4fc9-9b37-f3d0ea1a9d7f ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules --------- Co-authored-by: Muhsin <muhsinkeramam@gmail.com> * chore: Remove linear integration feature flag (#12716) This PR removes the linear integration feature flag since the integration is pretty much stable and we do display the Linear CTA for users who aren't connected. Fixes https://linear.app/chatwoot/issue/CW-5819/remove-linear-feature-flag-from-front-end * chore: Update translations (#12722) Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com> * perf: Add database index on conversations identifier (#12715) **Problem** Slack webhook processing was failing with 500 errors due to database timeouts. The query `Conversation.where(identifier: params[:event][:thread_ts]).first` was performing full table scans and hitting PostgreSQL statement timeout. **Solution** Added database index on conversations.identifier and account_id. * fix: Extend phone number normalization to Twilio WhatsApp (#12655) ### Problem WhatsApp Cloud channels already handle Brazil/Argentina phone number format mismatches (PRs #12492, #11173), but Twilio WhatsApp channels were creating duplicate contacts when: - Template sent to new format: `whatsapp:+5541988887777` (13 digits) - User responds from old format: `whatsapp:+554188887777` (12 digits) ### Solution The solution extends the existing phone number normalization infrastructure to support both WhatsApp providers while handling their different payload formats: ### Provider Format Differences - **WhatsApp Cloud**: `wa_id: "919745786257"` (clean number) - **Twilio WhatsApp**: `From: "whatsapp:+919745786257"` (prefixed format) ### Test Coverage #### Brazil Phone Number Tests **Case 1: New Format (13 digits with "9")** - **Test 1**: No existing contact → Creates new contact with original format - **Test 2**: Contact exists in same format → Appends to existing conversation **Case 2: Old Format (12 digits without "9")** - **Test 3**: Contact exists in old format → Appends to existing conversation - **Test 4** *(Critical)*: Contact exists in new format, message in old format → Finds existing contact, prevents duplicate - **Test 5**: No contact exists → Creates new contact with incoming format #### Argentina Phone Number Tests **Case 3: With "9" after country code** - **Test 6**: No existing contact → Creates new contact - **Test 7**: Contact exists in normalized format → Uses existing contact **Case 4: Without "9" after country code** - **Test 8**: Contact exists in same format → Appends to existing - **Test 9**: No contact exists → Creates new contact Fixes https://linear.app/chatwoot/issue/CW-5565/inconsistencies-for-mobile-numbersargentina-brazil-and-mexico-numbers * fix: Timezone offset reports broken by DST transition (#12747) ## Description Fixes timezone offset parameter in V2 reports API that was broken by DST transitions. The issue occurred when UK DST ended on October 26, 2025, causing the test to fail starting October 27th. ~~**Initial diagnosis:** The root cause was that `timezone_name_from_offset` used `zone.now.utc_offset` to match timezones, which changes based on the current date's DST status rather than the data being queried.~~ **Actual root cause:** The test was accidentally passing before DST transition. During BST, `timezone_name_from_offset(0)` matched "Azores" (UTC-1) instead of "Edinburgh" (UTC+0), and the -1 hour offset coincidentally split midnight data into [1,5]. After DST ended, it correctly matched "Edinburgh" (UTC+0), but this grouped all conversations into one day [6], exposing that the test data was flawed. The real issue: Test data created all 6 conversations starting at midnight on a single day, which cannot produce a [1,5] split in true UTC. Fixes CW-5846 ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality not to work as expected) - [ ] This change requires a documentation update ## How Has This Been Tested? **Test that was failing:** ```bash bundle exec rspec spec/controllers/api/v2/accounts/reports_controller_spec.rb:25 ``` **Changes:** ~~1. Fixed `timezone_name_from_offset` to use January 1st as reference date instead of current date~~ ~~2. Converted timezone string to `ActiveSupport::TimeZone` object for `group_by_period` compatibility~~ **Revised approach:** 1. Freeze test time to January 2024 using `travel_to`, making timezone matching deterministic and aligned with test data period 2. Start test conversations at 23:00 instead of midnight to properly span two days and test timezone boundary grouping 3. Keep `zone.now.utc_offset` (correct behavior for real users during DST) **Why this works:** - Test runs "in January 2024" → `zone.now.utc_offset` returns January offsets consistently - Offset `-8` correctly matches Pacific Standard Time (UTC-8 in January) - Real users in PDT (summer) with offset `-7` → correctly match Pacific Daylight Time - No production impact, test is deterministic year-round **Verification:** - Test now passes consistently regardless of current DST status - Timezone matching works correctly for real users during DST periods - Reports correctly group data by timezone offset across all seasons ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [x] Any dependent changes have been merged and published in downstream modules --------- Co-authored-by: Shivam Mishra <scm.mymail@gmail.com> Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com> * fix: Captain response builder not getting triggered (#12729) ## Summary - Fix captain response builder not getting triggered for cases where responses are created as completed. ## Testing Instructions - Test articles with firecrawl - Test articles without firecrawl - Test PDF documents --------- Co-authored-by: Pranav <pranav@chatwoot.com> * chore: Update captain pending FAQ interface (#12752) # Pull Request Template ## Description **This PR includes,** - Added new pending FAQs view with approve/edit/delete actions for each response. - Implemented banner notification showing pending FAQ count on main approved responses page. - Created dedicated route for pending FAQs review at /captain/responses/pending. - Added automatic pending count updates when switching assistants or routes. - Modified ResponseCard component to show action buttons instead of dropdown in pending view. Fixes https://linear.app/chatwoot/issue/CW-5833/pending-faqs-in-a-different-ux ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? ### Loom video https://www.loom.com/share/5fe8f79b04cd4681b9360c48710b9373 ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules --------- Co-authored-by: Pranav <pranav@chatwoot.com> * fix: Exclude authentication templates from WhatsApp template selection (#12753) This PR add the changes for excluding the authentication templates from the WhatsApp template selection in the frontend, as these templates are not supported at the moment. Reference: https://www.chatwoot.com/hc/user-guide/articles/1754940076-whatsapp-templates#what-is-not-supported * feat: Template types components (#12714) # Pull Request Template ## Description Fixes https://linear.app/chatwoot/issue/CW-5806/create-the-story-book-components-for-template-typestext-media-list **Pending** Need to standardize the structure to match the template/campaigns. ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? ### Screenshots <img width="669" height="179" alt="image" src="https://github.com/user-attachments/assets/42efd292-8520-4b05-81ec-8bc526fc12db" /> <img width="646" height="304" alt="image" src="https://github.com/user-attachments/assets/431dd964-006c-4877-a693-dae39b90df4c" /> <img width="646" height="380" alt="image" src="https://github.com/user-attachments/assets/9052e31f-9292-4afb-8897-13931655fa00" /> <img width="646" height="272" alt="image" src="https://github.com/user-attachments/assets/873d2488-e856-4a0d-8579-cc1bcc61cc8e" /> <img width="646" height="490" alt="image" src="https://github.com/user-attachments/assets/14c2aa42-bf27-475f-aa70-fe59c1d00e9b" /> <img width="646" height="281" alt="image" src="https://github.com/user-attachments/assets/1f42408e-03e8-4863-b4c7-715d13d67686" /> ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com> * fix: update omniauth to latest to resolve heroku deployment issues (#12749) # Pull Request Template ## Description Fixes https://github.com/chatwoot/chatwoot/issues/12553 Heroku build was failing due to `omniauth` version mismatch. Also, added `NODE_OPTIONS=--max-old-space-size=4096` to handle OOM during Vite build. ## Type of change Please delete options that are not relevant. - [x] Bug fix (non-breaking change which fixes an issue) ## How Has This Been Tested? - Tested on heroku ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [x] Any dependent changes have been merged and published in downstream modules * chore: Improvements in pending FAQs (#12755) # Pull Request Template ## Description **This PR includes:** 1. Added URL-based filter persistence for the responses pages, including page and search parameters. 2. Introduced a new empty state variant for pending FAQs — without a backdrop and with a “Clear Filters” option. 3. Made the actions, filter, and search row remain fixed at the top while scrolling. Fixes https://linear.app/chatwoot/issue/CW-5852/improvements-in-pending-faqs ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? ### Loom video https://www.loom.com/share/1d9eee68c0684f0ab05e08b4ca1e0ce9 ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules * fix: run captain v2 outside the transaction (#12756) * feat: Always process email content (#12734) Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com> * feat: Bulk actions for contacts (#12763) Introduces APIs and UI for bulk actions in contacts table. The initial action available will be assign labels Fixes: #8536 #12253 ## Screens <img width="1350" height="747" alt="Screenshot 2025-10-29 at 4 05 08 PM" src="https://github.com/user-attachments/assets/0792dff5-0371-4b2e-bdfb-cd32db773402" /> <img width="1345" height="717" alt="Screenshot 2025-10-29 at 4 05 19 PM" src="https://github.com/user-attachments/assets/ae510404-c6de-4c15-a720-f6d10cdac25b" /> --------- Co-authored-by: Muhsin <muhsinkeramam@gmail.com> Co-authored-by: iamsivin <iamsivin@gmail.com> Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com> * feat: Enable opensearch on paid plans automatically (#12770) - enable `advanced_search feature` on all paid plans automatically ref: https://github.com/chatwoot/chatwoot/pull/12503 * chore: Make contacts bulk action bar sticky (#12773) # Pull Request Template ## Description This PR makes the contacts bulk action bar sticky while scrolling. ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) ## How Has This Been Tested? ### Screenshots <img width="1080" height="300" alt="image" src="https://github.com/user-attachments/assets/21f8f3c6-813e-4ef6-b40a-8dd14e6ffb26" /> <img width="1080" height="300" alt="image" src="https://github.com/user-attachments/assets/bb939f1d-9a13-4f9f-953d-b9872c984b74" /> ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules * chore: Add dependant destroy_async for sla events (#12774) Added the destroy_async to prevent timeout during SLA policy deletion by processing SLA events asynchronously. * chore: Update translations (#12748) * feat: Add company backfill migration for existing contacts (Part 1) (#12657) ## Description Implements company backfill migration infrastructure for existing contacts. This is **Part 1 of 2** for the company model production rollout as described in [CW-5726](https://linear.app/chatwoot/issue/CW-5726/company-model-setting-it-up-on-production). Creates jobs and services to associate existing contacts with companies based on their email domains, filtering out free email providers (gmail, yahoo, etc.) and disposable addresses. **What's included:** - Business email detector service with ValidEmail2 (uses `disposable_domain?` to avoid DNS lookups) - Per-account batch job to process contacts for one account - Orchestrator job to iterate all accounts - Rake task: `bundle exec rake companies:backfill` ~~*NOTE*: I'm using a hard-coded approach to determine if something is a "business" email by filtering out emails that are usually personal. I've also added domains that are common to some of our customers' regions. This should be simpler. I looked into `Valid_Email2` and I couldn't find anything to dictate whether an email is a personal email or a business one. I don't think the approach used in the frontend is valid here.~~ UPDATE: Using `email_provider_info` gem instead. **Pending - Part 2 (separate PR):** Real-time company creation for new contacts ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? ```bash # Run all new tests bundle exec rspec spec/enterprise/services/companies/business_email_detector_service_spec.rb \\ spec/enterprise/jobs/migration/company_account_batch_job_spec.rb \\ spec/enterprise/jobs/migration/company_backfill_job_spec.rb # Run RuboCop bundle exec rubocop enterprise/app/services/companies/business_email_detector_service.rb \\ enterprise/app/jobs/migration/company_account_batch_job.rb \\ enterprise/app/jobs/migration/company_backfill_job.rb \\ lib/tasks/companies.rake ``` **Performance optimization:** - Uses `disposable_domain?` instead of `disposable?` to avoid DNS MX lookups (discovered via tcpdump analysis - `disposable?` was making network calls for every email, causing 100x slowdown) ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules --------- Co-authored-by: Sojan Jose <sojan@pepalo.com> * feat: Add company auto-association for contacts (CW-5726 Part 2) (#12711) ## Description Implements real-time company auto-association for contacts based on email domains. This is **Part 2** of the company model production rollout (CW-5726). **Task:** - When a contact is created with a business email, automatically create and associate a company from the email domain - When a contact is updated with an email for the first time (email was previously nil), associate with a company - Preserve existing company associations when email changes to avoid user confusion - Skip free email providers and disposable domains **Dependencies:** ⚠️ Requires PR #12657 (Part 1: Backfill migration) to be merged first **Linear ticket:** [CW-5726](https://linear.app/chatwoot/issue/CW-5726/company-model-setting-it-up-on-production) ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? - Service specs: Tests business email detection, company creation, association logic, edge cases (existing companies, free emails, nil emails) - Integration specs: Tests full callback flow for contact create/update scenarios - All tests passing: 10 examples, 0 failures - RuboCop: 0 offenses ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules (PR #12657 pending) --------- Co-authored-by: Sojan Jose <sojan@pepalo.com> * fix: Optimize Message search_data to prevent OpenSearch field explosion (#12786) ## Description Refactored the `Message#search_data` method to prevent exceeding OpenSearch's 1000 field limit during reindex operations. **Problem:** The previous implementation serialized entire ActiveRecord objects (Inbox, Sender, Conversation) with all their JSONB fields, causing dynamic field explosion in OpenSearch. This resulted in `Searchkick::ImportError` with "Limit of total fields [1000] has been exceeded". **Solution:** Whitelisted only necessary fields for search and filtering, and flattened JSONB `custom_attributes` into key-value pair arrays to prevent unbounded field creation. Linked to: CW-5861 ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality not to work as expected) - [x] This change requires a documentation update ## How Has This Been Tested? - Verified rubocop passes with no offenses - Code review of search field usage from `enterprise/app/services/enterprise/search_service.rb` - Analyzed actual search queries to determine required indexed fields **Still needed:** - Full reindex test on staging/production environment - Verify search functionality still works after reindex - Confirm field count is under 1000 limit ## Changes Made ### Before - Indexed 1000+ fields (entire AR objects with JSONB) - `inbox` = full Inbox object (23+ fields + JSONB) - `sender` = full Contact/User/AgentBot object (10+ fields + JSONB) - `conversation` = full push_event_data - Dynamic JSONB keys creating unlimited fields ### After - ~35-40 controlled fields - Whitelisted search fields: `content`, `attachment_transcribed_text`, `email_subject` - Filter fields: `account_id`, `inbox_id`, `conversation_id`, `sender_id`, `sender_type`, etc. - Flattened `custom_attributes`: `[{key, value, value_type}]` format - Helper methods: `search_conversation_data`, `search_inbox_data`, `search_sender_data`, `search_additional_data` ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules ## Post-merge Steps After merging, the following steps are required: 1. **Reindex all messages:** ```bash bundle exec rails runner "Message.reindex" ``` 2. **Verify field count:** ```bash bundle exec rails runner " client = Searchkick.client index_name = Message.searchkick_index.name mapping = client.indices.get_mapping(index: index_name) fields = mapping.dig(index_name, 'mappings', 'properties') puts 'Total fields: ' + fields.keys.count.to_s " ``` 3. **Test search functionality** to ensure queries still work as expected --------- Co-authored-by: Vishnu Narayanan <iamwishnu@gmail.com> Co-authored-by: Pranav <pranav@chatwoot.com> * fix: Avoid introducing new attributes in search (#12791) Fix `Limit of total fields [1000] has been exceeded` https://linear.app/chatwoot/issue/CW-5861/searchkickimporterror-type-=-illegal-argument-exception-reason-=-limit#comment-6b6e41bd * fix: Gate Sidekiq dequeue logger behind env (#12790) ## Summary - wrap the dequeue middleware registration in a boolean env flag - document the ENABLE_SIDEKIQ_DEQUEUE_LOGGER option in .env.example * feat: Bulk delete for contacts (#12778) Introduces a new bulk action `delete` for contacts ref: https://github.com/chatwoot/chatwoot/pull/12763 ## Screens <img width="1492" height="973" alt="Screenshot 2025-10-31 at 6 27 21 PM" src="https://github.com/user-attachments/assets/30dab1bb-2c2c-4168-9800-44e0eb5f8e3a" /> <img width="1492" height="985" alt="Screenshot 2025-10-31 at 6 27 32 PM" src="https://github.com/user-attachments/assets/5be610c4-b19e-4614-a164-103b22337382" /> * fix: Video bubble click and play issue (#12764) Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com> * feat: Differentiate bot and user in the summary (#12801) While generating the summary, use the appropriate sender type for the message. * fix: Invalid image URL issue in Help Center articles (#12806) * feat: allow bots to handle campaigns when sender_id is nil (#12805) * fix: Add empty line before signature in compose conversation editor (#12702) Co-authored-by: Shivam Mishra <scm.mymail@gmail.com> * feat: Enhance button interactions (#12738) * fix: Remove the same account validation for whatsapp channels (#12811) ## Description Modified the phone number validation in Whatsapp::ChannelCreationService to check for duplicate phone numbers across ALL accounts, not just within the current account. ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) ## How Has This Been Tested? - Added test coverage for cross-account phone number validation - Using actual UI flow <img width="1493" height="532" alt="image" src="https://github.com/user-attachments/assets/67d2bb99-2eb9-4115-8d56-449e4785e0d8" /> ## Checklist: - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules * feat: Update Captain navigation structure (#12761) # Pull Request Template ## Description This PR includes an update to the Captain navigation structure. ## Route Structure ```javascript 1. captain_assistants_responses_index → /captain/:assistantId/faqs 2. captain_assistants_documents_index → /captain/:assistantId/documents 3. captain_assistants_scenarios_index → /captain/:assistantId/scenarios 4. captain_assistants_playground_index → /captain/:assistantId/playground 5. captain_assistants_inboxes_index → /captain/:assistantId/inboxes 6. captain_tools_index → /captain/tools 7. captain_assistants_settings_index → /captain/:assistantId/settings 8. captain_assistants_guardrails_index → /captain/:assistantId/settings/guardrails 9. captain_assistants_guidelines_index → /captain/:assistantId/settings/guidelines 10. captain_assistants_index → /captain/:navigationPath ``` **How it works:** 1. User clicks sidebar item → Routes to `captain_assistants_index` with `navigationPath` 2. `AssistantsIndexPage` validates route and gets last active assistant, if not redirects to assistant create page. 3. Routes to actual page: `/captain/:assistantId/:page` 4. Page loads with correct assistant context Fixes https://linear.app/chatwoot/issue/CW-5832/updating-captain-navigation ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules --------- Co-authored-by: Pranav <pranav@chatwoot.com> Co-authored-by: Sojan Jose <sojan@pepalo.com> * fix: Handle login when there are no accounts (#12816) * chore: Update translations (#12794) * chore(docs): Fix typos in some files (#12817) This PR fixes typos in the file file using codespell. * refactor: strategy pattern for mailbox conversation finding (#12766) Co-authored-by: Pranav <pranav@chatwoot.com> Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com> * fix: Issue with processing variables in outgoing email content (#12799) Co-authored-by: Shivam Mishra <scm.mymail@gmail.com> Co-authored-by: Vinay Keerthi <11478411+stonecharioteer@users.noreply.github.com> Co-authored-by: Sojan Jose <sojan@pepalo.com> * fix: hide pdf citations in captain faq responses (#12839) * fix: Use contact_id instead of sender_id for Instagram message locks (#12841) Previously, the lock key for Instagram used sender_id, which for echo messages (outgoing) would be the account's own ID. This caused all outgoing messages to compete for the same lock, creating a bottleneck during bulk messaging. The fix introduces contact_instagram_id method that correctly identifies the contact's ID regardless of message direction: - For echo messages (outgoing): uses recipient.id (the contact) - For incoming messages: uses sender.id (the contact) This ensures each conversation has a unique lock, allowing parallel processing of webhooks while maintaining race condition protection within individual conversations. Fixes lock acquisition errors in Sidekiq when processing bulk Instagram messages. Fixes https://linear.app/chatwoot/issue/CW-5931/p0-mutexapplicationjoblockacquisitionerror-failed-to-acquire-lock-for ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) * fix: label tags for contactable inboxes (#12838) * chore: Improve captain layout (#12820) * feat: allow selecting month range in overview reports (#12701) Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com> Co-authored-by: iamsivin <iamsivin@gmail.com> * fix: respect status parameter when creating articles via API (#12846) ## Description The Articles API was ignoring the `status` parameter when creating new articles. All articles were forced to be drafts due to a hardcoded `@article.draft!` call in the controller, even when users explicitly sent `status: 1` (published) in their API request. This PR removes the hardcoded draft enforcement and allows the status parameter to be respected while maintaining backward compatibility. Fixes #12063 ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) ## How Has This Been Tested? **Before:** - API POST with `status: 1` → Created as draft (ignored parameter) - API POST without status → Created as draft **After:** - API POST with `status: 1` → Created as published ✅ - API POST without status → Created as draft (backward compatible) ✅ - UI creates articles → Still creates as draft (UI doesn't send status) ✅ **Tests run:** ```bash bundle exec rspec spec/controllers/api/v1/accounts/articles_controller_spec.rb # 17 examples, 0 failures ``` Updated tests: 1. Changed 2 existing tests that were verifying the broken behavior (expecting draft when published was sent) 2. Added new test to verify articles default to draft when status is not provided 3. All existing tests pass, confirming backward compatibility ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes Co-authored-by: Sojan Jose <sojan@pepalo.com> * feat: allow querying reporting events via the API (#12832) * feat(webhooks): add name to webhook (#12641) ## Description When working with webhooks, it's easy to lose track of which URL is which. Adding a `name` (optional) column to the webhook model is a straight-forward solution to make it significantly easier to identify webhooks. ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? Model and controller specs, and also running in production over several months without any issues. | Before | After | | --- | --- | | <img width="949" height="990" alt="image copy 3" src="https://github.com/user-attachments/assets/6b33c072-7d16-4a9c-a129-f9c0751299f5" /> | <img width="806" height="941" alt="image" src="https://github.com/user-attachments/assets/77f3cb3a-2eb0-41ac-95bf-d02915589690" /> | | <img width="1231" height="650" alt="image copy 2" src="https://github.com/user-attachments/assets/583374af-96e0-4436-b026-4ce79b7f9321" /> | <img width="1252" height="650" alt="image copy" src="https://github.com/user-attachments/assets/aa81fb31-fd18-4e21-a40e-d8ab0dc76b4e" /> | ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [x] Any dependent changes have been merged and published in downstream modules * perf: speed up docker builds (#12859) - Use separate keys to avoid cache overwrites across different architecture builds https://linear.app/chatwoot/issue/CW-5945/perf-speed-up-docker-builds ### 25 mins ---> 5mins ## before <img width="971" height="452" alt="image" src="https://github.com/user-attachments/assets/535cebd6-6c16-48d1-a62d-ffb6f2fc9b08" /> ## after <img width="940" height="428" alt="image" src="https://github.com/user-attachments/assets/359eb313-4bb5-4e0e-9492-a8ad48645159" /> * chore: Update missing places with new colors (#12862) # Pull Request Template ## Description This PR updates the colors in places that were missed during the color update migration. ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules * fix: Brand installation name not showing (#12861) # Pull Request Template ## Description Fixes https://linear.app/chatwoot/issue/CW-5946/fix-brand-installation-name-issue-in-dyte ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules * fix: migrate from deprecated annotate gem to annotaterb (#12845) ## Description The `annotate` gem has been deprecated and users are experiencing annotation errors with the new Rails 7 `serialize` syntax. This PR migrates to `annotaterb`, the actively maintained fork. Users reported errors when running `make db`: ``` Unable to annotate app/models/installation_config.rb: no implicit conversion of Hash into String Unable to annotate app/models/installation_config.rb: no implicit conversion of nil into Array ``` This PR updates the Gemfile and rake configuration to use `annotaterb` instead. Fixes #11673 ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) ## How Has This Been Tested? Tested locally with the following steps: 1. Run `bundle install` - successfully installed annotaterb 4.20.0 2. Run `RAILS_ENV=development bundle exec rails db:chatwoot_prepare` - completed without annotation errors 3. Run `RAILS_ENV=development bundle exec rails annotate_rb:models` - successfully annotated all models including InstallationConfig 4. Verified InstallationConfig model annotations are present and correct ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] My changes generate no new warnings - [x] New and existing unit tests pass locally with my changes * chore: disable worker MemoryHigh throttling in systemd unit (#12871) - set MemoryHigh to infinity in deployment/chatwoot-worker.1.service so the worker is throttled only by the existing MemoryMax hard limit - prevents cgroup reclaim from slowing Sidekiq under transient spikes while still keeping the hard stop at 1.5 GB * chore: Update translations (#12818) * fix: revert annotaterb migration due to persistent annotation errors (#12881) ## Description This PR reverts the migration from the `annotate` gem to `annotaterb` introduced in PR #12845. The annotation errors reported in #11673 persist with both gems, and the old `annotate` gem handles the errors more gracefully by continuing to process other models instead of crashing. **Testing reveals both gems fail with the same underlying issue:** **Old annotate gem (3.2.0):** ``` Unable to annotate app/models/installation_config.rb: no implicit conversion of Hash into String Unable to annotate app/models/installation_config.rb: no implicit conversion of nil into Array Model files unchanged. ``` (Logs error but continues processing) **New annotaterb gem (4.20.0):** ``` ❯ bundle exec annotaterb models ruby/3.4.4/lib/ruby/gems/3.4.0/gems/reline-0.3.6/lib/reline/terminfo.rb:2: warning: ruby/3.4.4/lib/ruby/3.4.0/fiddle.rb was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0. You can add fiddle to your Gemfile or gemspec to silence this warning. Also please contact the author of reline-0.3.6 to request adding fiddle into its gemspec. Annotating models bundler: failed to load command: annotaterb (ruby/3.4.4/bin/annotaterb) ruby/3.4.4/lib/ruby/3.4.0/psych/parser.rb:62:in 'Psych::Parser#_native_parse': no implicit conversion of Hash into String (TypeError) _native_parse @handler, yaml, path ^^^^^^^^^^^^^^^^^^^^ from ruby/3.4.4/lib/ruby/3.4.0/psych/parser.rb:62:in 'Psych::Parser#parse' from ruby/3.4.4/lib/ruby/3.4.0/psych.rb:457:in 'Psych.parse_stream' from ruby/3.4.4/lib/ruby/3.4.0/psych.rb:401:in 'Psych.parse' from ruby/3.4.4/lib/ruby/3.4.0/psych.rb:325:in 'Psych.safe_load' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activerecord-7.1.5.2/lib/active_record/coders/yaml_column.rb:37:in 'ActiveRecord::Coders::YAMLColumn::SafeCoder#load' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activerecord-7.1.5.2/lib/active_record/coders/column_serializer.rb:37:in 'ActiveRecord::Coders::ColumnSerializer#load' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activerecord-7.1.5.2/lib/active_record/type/serialized.rb:22:in 'ActiveRecord::Type::Serialized#deserialize' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activemodel-7.1.5.2/lib/active_model/attribute.rb:175:in 'ActiveModel::Attribute::FromDatabase#type_cast' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activemodel-7.1.5.2/lib/active_model/attribute.rb:43:in 'ActiveModel::Attribute#value' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activemodel-7.1.5.2/lib/active_model/attribute_set.rb:37:in 'block in ActiveModel::AttributeSet#to_hash' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activesupport-7.1.5.2/lib/active_support/core_ext/enumerable.rb:78:in 'block in Enumerable#index_with' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activesupport-7.1.5.2/lib/active_support/core_ext/enumerable.rb:78:in 'Array#each' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activesupport-7.1.5.2/lib/active_support/core_ext/enumerable.rb:78:in 'Enumerable#index_with' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activemodel-7.1.5.2/lib/active_model/attribute_set.rb:37:in 'ActiveModel::AttributeSet#to_hash' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/activerecord-7.1.5.2/lib/active_record/model_schema.rb:499:in 'ActiveRecord::ModelSchema::ClassMethods#column_defaults' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/model_wrapper.rb:68:in 'AnnotateRb::ModelAnnotator::ModelWrapper#column_defaults' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/model_wrapper.rb:139:in 'block in AnnotateRb::ModelAnnotator::ModelWrapper#built_attributes' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/model_wrapper.rb:136:in 'Array#map' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/model_wrapper.rb:136:in 'AnnotateRb::ModelAnnotator::ModelWrapper#built_attributes' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/column_annotation/annotation_builder.rb:15:in 'AnnotateRb::ModelAnnotator::ColumnAnnotation::AnnotationBuilder#build' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/annotation/annotation_builder.rb:52:in 'block in AnnotateRb::ModelAnnotator::Annotation::AnnotationBuilder::Annotation#columns' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/annotation/annotation_builder.rb:51:in 'Array#map' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/annotation/annotation_builder.rb:51:in 'AnnotateRb::ModelAnnotator::Annotation::AnnotationBuilder::Annotation#columns' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/annotation/annotation_builder.rb:26:in 'AnnotateRb::ModelAnnotator::Annotation::AnnotationBuilder::Annotation#body' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/annotation/annotation_builder.rb:35:in 'AnnotateRb::ModelAnnotator::Annotation::AnnotationBuilder::Annotation#build' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/annotation/annotation_builder.rb:71:in 'AnnotateRb::ModelAnnotator::Annotation::AnnotationBuilder#build' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/project_annotator.rb:43:in 'AnnotateRb::ModelAnnotator::ProjectAnnotator#build_instructions_for_file' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/project_annotator.rb:17:in 'block in AnnotateRb::ModelAnnotator::ProjectAnnotator#annotate' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/project_annotator.rb:13:in 'Array#map' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/project_annotator.rb:13:in 'AnnotateRb::ModelAnnotator::ProjectAnnotator#annotate' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/annotator.rb:21:in 'AnnotateRb::ModelAnnotator::Annotator#do_annotations' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/model_annotator/annotator.rb:8:in 'AnnotateRb::ModelAnnotator::Annotator.do_annotations' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/commands/annotate_models.rb:17:in 'AnnotateRb::Commands::AnnotateModels#call' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/runner.rb:38:in 'AnnotateRb::Runner#run' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/lib/annotate_rb/runner.rb:11:in 'AnnotateRb::Runner.run' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/annotaterb-4.20.0/exe/annotaterb:18:in '<top (required)>' from ruby/3.4.4/bin/annotaterb:25:in 'Kernel#load' from ruby/3.4.4/bin/annotaterb:25:in '<top (required)>' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/cli/exec.rb:58:in 'Kernel.load' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/cli/exec.rb:58:in 'Bundler::CLI::Exec#kernel_load' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/cli/exec.rb:23:in 'Bundler::CLI::Exec#run' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/cli.rb:455:in 'Bundler::CLI#exec' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/vendor/thor/lib/thor/command.rb:28:in 'Bundler::Thor::Command#run' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in 'Bundler::Thor::Invocation#invoke_command' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/vendor/thor/lib/thor.rb:527:in 'Bundler::Thor.dispatch' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/cli.rb:35:in 'Bundler::CLI.dispatch' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/vendor/thor/lib/thor/base.rb:584:in 'Bundler::Thor::Base::ClassMethods#start' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/cli.rb:29:in 'Bundler::CLI.start' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/exe/bundle:28:in 'block in <top (required)>' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/lib/bundler/friendly_errors.rb:117:in 'Bundler.with_friendly_errors' from ruby/3.4.4/lib/ruby/gems/3.4.0/gems/bundler-2.5.16/exe/bundle:20:in '<top (required)>' from ruby/3.4.4/bin/bundle:25:in 'Kernel#load' from ruby/3.4.4/bin/bundle:25:in '<main>' ``` (Crashes immediately, stops all processing) **Root cause:** The `InstallationConfig` model uses YAML serialization (`serialize :serialized_value, coder: YAML`) on a JSONB database column. When annotation tools read column defaults, PostgreSQL returns JSONB as a Hash, but YAML expects a String, causing the type error. The migration to annotaterb doesn't solve the problem - both gems encounter the same error. The old gem is preferable as it continues working despite the error. Reverts #12845 Related to #11673 ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) ## How Has This Been Tested? 1. Reverted commit559d1b6572. Ran `bundle install` to reinstall annotate gem v3.2.0 3. Ran `RAILS_ENV=development bundle exec annotate` - Result: Logs errors for InstallationConfig but completes successfully 4. Re-applied the annotaterb changes and tested `bundle exec annotaterb models` - Result: Crashes with full stack trace and stops processing ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] My changes generate no new warnings - [x] New and existing unit tests pass locally with my changes --- *Edited to truncate environment-specific info from error dump* * chore: Hide assistant switcher on paywall screen (#12875) * feat: Assignment service (v2) (#12320) ## Linear Link ## Description This PR introduces a new robust auto-assignment system for conversations in Chatwoot. The system replaces the existing round-robin assignment with a more sophisticated service-based architecture that supports multiple assignment strategies, rate limiting, and Enterprise features like capacity-based assignment and balanced distribution. ## Type of change - [ ] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? - Unit test cases - Test conversations getting assigned on status change to open - Test the job directly via rails console ## Checklist: - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Adds a new service-based auto-assignment system with scheduled jobs, rate limiting, enterprise capacity/balanced selection, and wiring via inbox/handler; includes Redis helpers and comprehensive tests. > > - **Auto-assignment v2 (core services)**: > - Add `AutoAssignment::AssignmentService` with bulk assignment, configurable conversation priority, RR selection, and per-agent rate limiting via `AutoAssignment::RateLimiter`. > - Add `AutoAssignment::RoundRobinSelector` for agent selection. > - **Jobs & scheduling**: > - Add `AutoAssignment::AssignmentJob` (per-inbox bulk assign; env-based limit) and `AutoAssignment::PeriodicAssignmentJob` (batch over accounts/inboxes). > - Schedule periodic run in `config/schedule.yml` (`periodic_assignment_job`). > - **Model/concerns wiring**: > - Include `InboxAgentAvailability` in `Inbox`; add `Inbox#auto_assignment_v2_enabled?`. > - Update `AutoAssignmentHandler` to trigger v2 job when `auto_assignment_v2_enabled?`, else fallback to legacy. > - **Enterprise extensions**: > - Add `Enterprise::InboxAgentAvailability` (capacity-aware filtering) and `Enterprise::Concerns::Inbox` association `inbox_capacity_limits`. > - Extend service via `Enterprise::AutoAssignment::AssignmentService` (policy-driven config, capacity filtering, exclusion rules) and add selectors/services: `BalancedSelector`, `CapacityService`. > - **Infrastructure**: > - Enhance `Redis::Alfred` with `expire`, key scan/count, and extended ZSET helpers (`zadd`, `zcount`, `zcard`, `zrangebyscore`). > - **Tests**: > - Add specs for jobs, core service, rate limiter, RR selector, and enterprise features (capacity, balanced selection, exclusions). > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 0ebe187c8aea73765b0122a44b18d6f465c2477f. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com> Co-authored-by: Shivam Mishra <scm.mymail@gmail.com> * fix: Change contact_inboxes.source_id to text column (#12882) ## Description Fixes CW-5961 where IMAP email processing failed with `ActiveRecord::RecordInvalid: Validation failed: Source is too long (maximum is 255 characters)` error. This changes the `contact_inboxes.source_id` column from `string` (255 character limit) to `text` (unlimited) to accommodate long email message IDs that were causing validation failures. Fixes CW-5961 ## Type of change - [x] Bug fix (non-breaking change which fixes an issue) ## How Has This Been Tested? - Added spec test validating `source_id` values longer than 255 characters (300 chars) - All existing `contact_inbox_spec.rb` tests pass (7 examples, 0 failures) - Migration applied successfully with reversible up/down methods - Verified `source_id` column type changed to `text` with `null: false` constraint preserved ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes * feat: allow configuring attachment upload limit (#12835) ## Summary - add a configurable MAXIMUM_FILE_UPLOAD_SIZE installation setting and surface it through super admin and global config payloads - apply the configurable limit to attachment validations and shared upload helpers on dashboard and widget - introduce a reusable helper with unit tests for parsing the limit and extend attachment specs for configurability ------ [Codex Task](https://chatgpt.com/codex/tasks/task_e_6912644786b08326bc8dee9401af6d0a) --------- Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com> Co-authored-by: iamsivin <iamsivin@gmail.com> * feat: Customizable webhook timeout configuration (#12777) ## Summary - Ability to configure the webhook timeout for Chatwoot self hosted installations fixes: https://github.com/chatwoot/chatwoot/issues/12754 * feat: Control the allowed login methods via Super Admin (#12892) - Control the allowed authentication methods for a chatwoot installation via super admin configs. [SAML, Google Auth etc] ------ [Codex Task](https://chatgpt.com/codex/tasks/task_e_6917d503b6e48326a261672c1de91462) --------- Co-authored-by: Pranav <pranav@chatwoot.com> Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com> * chore: Update translations (#12876) * feat: Backend - Companies API endpoint with pagination and search (#12840) ## Description Adds API endpoint to list companies with pagination, search, and sorting. Fixes https://linear.app/chatwoot/issue/CW-5930/add-backend-routes-to-get-companies-result Parent issue: https://linear.app/chatwoot/issue/CW-5928/add-companies-tab-to-dashboard ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? Added comprehensive specs to `spec/enterprise/controllers/api/v1/accounts/companies_controller_spec.rb`: - Pagination (25 per page, multiple pages) - Search by name and domain (case-insensitive) - Counter cache for contacts_count - Account scoping - Authorization To reproduce: ```bash bundle exec rspec spec/enterprise/controllers/api/v1/accounts/companies_controller_spec.rb bundle exec rubocop enterprise/app/controllers/api/v1/accounts/companies_controller.rb ``` ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules --------- Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com> Co-authored-by: iamsivin <iamsivin@gmail.com> Co-authored-by: Shivam Mishra <scm.mymail@gmail.com> Co-authored-by: Sojan Jose <sojan@pepalo.com> * feat: Companies page (#12842) # Pull Request Template ## Description This PR introduces a new Companies section in the Chatwoot dashboard. It lists all companies associated with the account and includes features such as **search**, **sorting**, and **pagination** to enable easier navigation and efficient management. Fixes https://linear.app/chatwoot/issue/CW-5928/add-companies-tab-to-dashboard ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? ### Screenshot <img width="1619" height="1200" alt="image" src="https://github.com/user-attachments/assets/21f0a666-c3d6-4dec-bd02-1e38e0cd9542" /> ## Checklist: - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my code - [x] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules --------- Co-authored-by: Vinay Keerthi <11478411+stonecharioteer@users.noreply.github.com> Co-authored-by: Shivam Mishra <scm.mymail@gmail.com> * feat: Add Amazon SES inbound email support (#12893) ## Summary - add AWS ActionMailbox SES gems - document SES as incoming email provider - note SES option in configuration ## Testing - `bundle exec rubocop config/initializers/mailer.rb config/environments/production.rb Gemfile` ------ [Codex Task](https://chatgpt.com/codex/tasks/task_e_68bbb7d482288326b8f04bb795af0322) --------- Co-authored-by: Pranav <pranav@chatwoot.com> Co-authored-by: Vinay Keerthi <11478411+stonecharioteer@users.noreply.github.com> * feat: hide email forwarding address if INBOUND_EMAIL_DOMAIN is not configured (#12768) #### Summary - Improved email inbox setup flow to handle cases where inbound email forwarding is not configured on the installation - Added conditional display of email forwarding address based on MAILER_INBOUND_EMAIL_DOMAIN environment variable availability - Enhanced user messaging to guide users toward configuring SMTP/IMAP settings when forwarding is unavailable #### Changes **Backend (app/views/api/v1/models/_inbox.json.jbuilder)** - Added forwarding_enabled boolean flag to inbox API response based on MAILER_INBOUND_EMAIL_DOMAIN presence - Made forward_to_email conditional - only included when forwarding is enabled **Frontend - Inbox Creation Flow** - Created new EmailInboxFinish.vue component to handle email inbox setup completion - Shows different messages based on whether forwarding is enabled: - With forwarding: displays forwarding address and encourages SMTP/IMAP configuration - Without forwarding: warns that SMTP/IMAP configuration is required for emails to be processed - Added link to configuration page for easy access to SMTP/IMAP settings <img width="988" height="312" alt="Screenshot 2025-11-18 at 3 27 27 PM" src="https://github.com/user-attachments/assets/928aff78-df73-49fa-9a26-dbbd1297b26a" /> <img width="765" height="489" alt="Screenshot 2025-11-18 at 3 24 46 PM" src="https://github.com/user-attachments/assets/6a182c7d-087f-4e88-92a5-30f147a567a7" /> Fixes https://linear.app/chatwoot/issue/CW-5881/hide-forwaring-email-section-if-inbound-email-domain-is-not-configured ## Type of change - [x] New feature (non-breaking change which adds functionality) ## How Has This Been Tested? - Tested locally ## Checklist: - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented on my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules --------- Co-authored-by: Pranav <pranav@chatwoot.com> * feat: APIs to assign agents_bots as assignee in conversations (#12836) ## Summary - add an assignee_agent_bot_id column as an initital step to prototype this before fully switching to polymorphic assignee - update assignment APIs and conversation list / show endpoints to reflect assignee as agent bot - ensure webhook payloads contains agent bot assignee [Codex Task](https://chatgpt.com/codex/tasks/task_e_6912833377e48326b6641b9eee32d50f) --------- Co-authored-by: Pranav <pranav@chatwoot.com> * Bump version to 4.8.0 * chore: remove migration --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com> Co-authored-by: Shivam Mishra <scm.mymail@gmail.com> Co-authored-by: Chatwoot Bot <92152627+chatwoot-bot@users.noreply.github.com> Co-authored-by: Pranav <pranav@chatwoot.com> Co-authored-by: Sojan Jose <sojan@pepalo.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Muhsin <muhsinkeramam@gmail.com> Co-authored-by: Vinay Keerthi <11478411+stonecharioteer@users.noreply.github.com> Co-authored-by: Vishnu Narayanan <iamwishnu@gmail.com> Co-authored-by: iamsivin <iamsivin@gmail.com> Co-authored-by: Tanmay Deep Sharma <32020192+tds-1@users.noreply.github.com> Co-authored-by: Lê Nam Khánh <55955273+khanhkhanhlele@users.noreply.github.com>
978 lines
46 KiB
JSON
978 lines
46 KiB
JSON
{
|
||
"INTEGRATION_SETTINGS": {
|
||
"SHOPIFY": {
|
||
"DELETE": {
|
||
"TITLE": "Delete Shopify Integration",
|
||
"MESSAGE": "Are you sure you want to delete the Shopify integration?"
|
||
},
|
||
"STORE_URL": {
|
||
"TITLE": "Connect Shopify Store",
|
||
"LABEL": "Store URL",
|
||
"PLACEHOLDER": "your-store.myshopify.com",
|
||
"HELP": "Enter your Shopify store's myshopify.com URL",
|
||
"CANCEL": "キャンセル",
|
||
"SUBMIT": "Connect Store"
|
||
},
|
||
"ERROR": "There was an error connecting to Shopify. Please try again or contact support if the issue persists."
|
||
},
|
||
"HEADER": "連携",
|
||
"DESCRIPTION": "Chatwootは、チームの効率を向上させるために複数のツールやサービスと連携します。以下のリストを探索して、お気に入りのアプリを設定してください。",
|
||
"LEARN_MORE": "連携について詳しく知る",
|
||
"LOADING": "連携を取得中",
|
||
"CAPTAIN": {
|
||
"DISABLED": "Captainはあなたのアカウントで有効になっていません。",
|
||
"CLICK_HERE_TO_CONFIGURE": "設定するにはここをクリック",
|
||
"LOADING_CONSOLE": "Captainコンソールを読み込み中...",
|
||
"FAILED_TO_LOAD_CONSOLE": "Captainコンソールの読み込みに失敗しました。リフレッシュしてもう一度お試しください。"
|
||
},
|
||
"WEBHOOK": {
|
||
"SUBSCRIBED_EVENTS": "購読イベント",
|
||
"LEARN_MORE": "Webhookについて詳しく知る",
|
||
"FORM": {
|
||
"CANCEL": "キャンセル",
|
||
"DESC": "Webhookイベントは、Chatwootアカウントで何が起こっているかについてのリアルタイムの情報を提供します。コールバックを設定するには有効なURLを入力してください。",
|
||
"SUBSCRIPTIONS": {
|
||
"LABEL": "イベント",
|
||
"EVENTS": {
|
||
"CONVERSATION_CREATED": "会話が作成されました",
|
||
"CONVERSATION_STATUS_CHANGED": "会話のステータスが変更されました",
|
||
"CONVERSATION_UPDATED": "会話が更新されました",
|
||
"MESSAGE_CREATED": "メッセージが作成されました",
|
||
"MESSAGE_UPDATED": "メッセージが更新されました",
|
||
"WEBWIDGET_TRIGGERED": "ユーザーによってライブチャットウィジェットが開かれました",
|
||
"CONTACT_CREATED": "連絡先が作成されました",
|
||
"CONTACT_UPDATED": "連絡先が更新されました",
|
||
"CONVERSATION_TYPING_ON": "Conversation Typing On",
|
||
"CONVERSATION_TYPING_OFF": "Conversation Typing Off"
|
||
}
|
||
},
|
||
"NAME": {
|
||
"LABEL": "Webhook Name",
|
||
"PLACEHOLDER": "Enter the name of the webhook"
|
||
},
|
||
"END_POINT": {
|
||
"LABEL": "Webhook URL",
|
||
"PLACEHOLDER": "例: {webhookExampleURL}",
|
||
"ERROR": "有効な URL を入力してください"
|
||
},
|
||
"EDIT_SUBMIT": "Webhookを更新",
|
||
"ADD_SUBMIT": "Webhookを作成"
|
||
},
|
||
"TITLE": "Webhook",
|
||
"CONFIGURE": "設定",
|
||
"HEADER": "Webhookの設定",
|
||
"HEADER_BTN_TXT": "新しいWebhookを追加",
|
||
"LOADING": "添付されたWebhookを取得しています",
|
||
"SEARCH_404": "検索内容(クエリ)に一致する項目はありませんでした",
|
||
"SIDEBAR_TXT": "<p><b>Webhooks</b> </p> <p>Webhooks は、すべてのアカウントで定義可能なHTTP コールバックです。これらは、メッセージの作成などChatwoot上でのイベントをきっかけに実行されます。このアカウントでは、1つ以上のwebhookが作成できます。 <br /><br /> <b>webhook</b>を作成するには、<b>webhookを作成</b>ボタンをクリックしてください。また、作成した webhook を削除ボタンを押して削除することもできます。</p>",
|
||
"LIST": {
|
||
"404": "このアカウントに紐付けされたWebフックはありません。",
|
||
"TITLE": "Webhookの管理",
|
||
"TABLE_HEADER": {
|
||
"WEBHOOK_ENDPOINT": "Webhookエンドポイント",
|
||
"ACTIONS": "操作"
|
||
}
|
||
},
|
||
"EDIT": {
|
||
"BUTTON_TEXT": "編集",
|
||
"TITLE": "Webhookを編集",
|
||
"API": {
|
||
"SUCCESS_MESSAGE": "Webhookの設定が正常に更新されました",
|
||
"ERROR_MESSAGE": "Wootサーバーに接続できませんでした。後でもう一度お試しください。"
|
||
}
|
||
},
|
||
"ADD": {
|
||
"CANCEL": "キャンセル",
|
||
"TITLE": "新しいWebhookを追加",
|
||
"API": {
|
||
"SUCCESS_MESSAGE": "Webhookの設定が正常に追加されました",
|
||
"ERROR_MESSAGE": "Wootサーバーに接続できませんでした。後でもう一度お試しください。"
|
||
}
|
||
},
|
||
"DELETE": {
|
||
"BUTTON_TEXT": "削除",
|
||
"API": {
|
||
"SUCCESS_MESSAGE": "Webhookの削除に成功しました",
|
||
"ERROR_MESSAGE": "Wootサーバーに接続できませんでした。後でもう一度お試しください。"
|
||
},
|
||
"CONFIRM": {
|
||
"TITLE": "削除の確認",
|
||
"MESSAGE": "Webhookを削除してもよろしいですか? ({webhookURL})",
|
||
"YES": "削除する ",
|
||
"NO": "いいえ、保存しておきます"
|
||
}
|
||
}
|
||
},
|
||
"SLACK": {
|
||
"DELETE": "削除",
|
||
"DELETE_CONFIRMATION": {
|
||
"TITLE": "連携の削除",
|
||
"MESSAGE": "連携を削除してもよろしいですか?削除すると、Slackワークスペースでの会話へのアクセスが失われます。"
|
||
},
|
||
"HELP_TEXT": {
|
||
"TITLE": "Slack連携の使用方法",
|
||
"BODY": "この連携を使用すると、すべての受信会話がSlackワークスペースの***{selectedChannelName}***チャンネルに同期されます。チャンネル内で顧客の会話を管理し、メッセージを見逃すことはありません。\n\n連携の主な機能は次のとおりです:\n\n**Slackから会話に返信:** ***{selectedChannelName}*** Slackチャンネルで会話に返信するには、メッセージを入力してスレッドとして送信するだけです。これにより、Chatwootを通じて顧客に返信が作成されます。とても簡単です!\n\n**プライベートノートの作成:** 返信ではなくプライベートノートを作成したい場合は、メッセージの先頭に***`note:`***と入力してください。これにより、メッセージがプライベートに保たれ、顧客には表示されません。\n\n**担当者プロファイルの関連付け:** Slackで返信した人が同じメールアドレスでChatwootに担当者プロファイルを持っている場合、返信は自動的にその担当者プロファイルに関連付けられます。これにより、誰がいつ何を言ったかを簡単に追跡できます。一方、返信者に関連付けられた担当者プロファイルがない場合、返信は顧客に対してボットプロファイルからのものとして表示されます。",
|
||
"SELECTED": "選択済み"
|
||
},
|
||
"SELECT_CHANNEL": {
|
||
"OPTION_LABEL": "チャンネルを選択",
|
||
"UPDATE": "更新",
|
||
"BUTTON_TEXT": "チャンネルを接続",
|
||
"DESCRIPTION": "SlackワークスペースはChatwootとリンクされていますが、連携は現在非アクティブです。連携を有効にしてChatwootにチャンネルを接続するには、以下のボタンをクリックしてください。\n\n**注意:** プライベートチャンネルを接続しようとしている場合は、この手順を進める前にChatwootアプリをSlackチャンネルに追加してください。",
|
||
"ATTENTION_REQUIRED": "注意が必要",
|
||
"EXPIRED": "Slack連携の有効期限が切れました。Slackでメッセージを受信し続けるには、連携を削除してワークスペースを再接続してください。"
|
||
},
|
||
"UPDATE_ERROR": "連携の更新中にエラーが発生しました。もう一度お試しください",
|
||
"UPDATE_SUCCESS": "チャンネルが正常に接続されました",
|
||
"FAILED_TO_FETCH_CHANNELS": "Slackからチャンネルを取得中にエラーが発生しました。もう一度お試しください"
|
||
},
|
||
"DYTE": {
|
||
"CLICK_HERE_TO_JOIN": "ここをクリックして参加",
|
||
"LEAVE_THE_ROOM": "ルームを退出",
|
||
"START_VIDEO_CALL_HELP_TEXT": "顧客と新しいビデオ通話を開始",
|
||
"JOIN_ERROR": "通話に参加中にエラーが発生しました。もう一度お試しください",
|
||
"CREATE_ERROR": "ミーティングリンクの作成中にエラーが発生しました。もう一度お試しください"
|
||
},
|
||
"OPEN_AI": {
|
||
"AI_ASSIST": "AIアシスト",
|
||
"WITH_AI": "AIで{option}",
|
||
"OPTIONS": {
|
||
"REPLY_SUGGESTION": "返信の提案",
|
||
"SUMMARIZE": "要約",
|
||
"REPHRASE": "文章の改善",
|
||
"FIX_SPELLING_GRAMMAR": "スペルと文法の修正",
|
||
"SHORTEN": "短縮",
|
||
"EXPAND": "拡張",
|
||
"MAKE_FRIENDLY": "メッセージのトーンをフレンドリーに変更",
|
||
"MAKE_FORMAL": "フォーマルトーンを使用",
|
||
"SIMPLIFY": "簡素化"
|
||
},
|
||
"ASSISTANCE_MODAL": {
|
||
"DRAFT_TITLE": "下書き内容",
|
||
"GENERATED_TITLE": "生成された内容",
|
||
"AI_WRITING": "AIが執筆中",
|
||
"BUTTONS": {
|
||
"APPLY": "この提案を使用",
|
||
"CANCEL": "キャンセル"
|
||
}
|
||
},
|
||
"CTA_MODAL": {
|
||
"TITLE": "OpenAIと統合",
|
||
"DESC": "OpenAIのGPTモデルを使用して、ダッシュボードに高度なAI機能を導入します。始めるには、OpenAIアカウントのAPIキーを入力してください。",
|
||
"KEY_PLACEHOLDER": "OpenAI APIキーを入力",
|
||
"BUTTONS": {
|
||
"NEED_HELP": "サポートが必要ですか?",
|
||
"DISMISS": "閉じる",
|
||
"FINISH": "設定を完了"
|
||
},
|
||
"DISMISS_MESSAGE": "OpenAIの統合は後でいつでも設定できます。",
|
||
"SUCCESS_MESSAGE": "OpenAIの統合が正常に設定されました"
|
||
},
|
||
"TITLE": "AIで改善",
|
||
"SUMMARY_TITLE": "AIによる要約",
|
||
"REPLY_TITLE": "AIによる返信提案",
|
||
"SUBTITLE": "現在の下書きを基に、AIが改善された返信を生成します。",
|
||
"TONE": {
|
||
"TITLE": "トーン",
|
||
"OPTIONS": {
|
||
"PROFESSIONAL": "プロフェッショナル",
|
||
"FRIENDLY": "フレンドリー"
|
||
}
|
||
},
|
||
"BUTTONS": {
|
||
"GENERATE": "生成",
|
||
"GENERATING": "生成中...",
|
||
"CANCEL": "キャンセル"
|
||
},
|
||
"GENERATE_ERROR": "コンテンツの処理中にエラーが発生しました。もう一度お試しください"
|
||
},
|
||
"DELETE": {
|
||
"BUTTON_TEXT": "削除",
|
||
"API": {
|
||
"SUCCESS_MESSAGE": "連携が正常に削除されました"
|
||
}
|
||
},
|
||
"CONNECT": {
|
||
"BUTTON_TEXT": "接続"
|
||
},
|
||
"DASHBOARD_APPS": {
|
||
"TITLE": "ダッシュボードアプリ",
|
||
"HEADER_BTN_TXT": "新しいダッシュボードアプリを追加",
|
||
"SIDEBAR_TXT": "<p><b>ダッシュボードアプリ</b></p><p>ダッシュボードアプリを使用すると、組織はChatwootダッシュボード内にアプリケーションを埋め込んで、カスタマーサポート担当者にコンテキストを提供できます。この機能により、アプリケーションを独立して作成し、ユーザー情報、注文履歴、または以前の支払い履歴を提供するためにダッシュボード内に埋め込むことができます。</p><p>Chatwootのダッシュボードを使用してアプリケーションを埋め込むと、アプリケーションはウィンドウイベントとして会話と連絡先のコンテキストを取得します。ページ上でメッセージイベントのリスナーを実装してコンテキストを受信します。</p><p>新しいダッシュボードアプリを追加するには、「新しいダッシュボードアプリを追加」ボタンをクリックしてください。</p>",
|
||
"DESCRIPTION": "ダッシュボードアプリを使用すると、組織はダッシュボード内にアプリケーションを埋め込んで、カスタマーサポート担当者にコンテキストを提供できます。この機能により、アプリケーションを独立して作成し、ユーザー情報、注文履歴、または以前の支払い履歴を提供するために埋め込むことができます。",
|
||
"LEARN_MORE": "ダッシュボードアプリについて詳しく知る",
|
||
"LIST": {
|
||
"404": "このアカウントにはまだダッシュボードアプリが設定されていません",
|
||
"LOADING": "ダッシュボードアプリを取得中...",
|
||
"TABLE_HEADER": {
|
||
"NAME": "名前",
|
||
"ENDPOINT": "エンドポイント"
|
||
},
|
||
"EDIT_TOOLTIP": "アプリを編集",
|
||
"DELETE_TOOLTIP": "アプリを削除"
|
||
},
|
||
"FORM": {
|
||
"TITLE_LABEL": "名前",
|
||
"TITLE_PLACEHOLDER": "ダッシュボードアプリの名前を入力",
|
||
"TITLE_ERROR": "ダッシュボードアプリの名前が必要です",
|
||
"URL_LABEL": "エンドポイント",
|
||
"URL_PLACEHOLDER": "アプリがホストされているエンドポイントURLを入力",
|
||
"URL_ERROR": "有効なURLが必要です"
|
||
},
|
||
"CREATE": {
|
||
"HEADER": "新しいダッシュボードアプリを追加",
|
||
"FORM_SUBMIT": "送信",
|
||
"FORM_CANCEL": "キャンセル",
|
||
"API_SUCCESS": "ダッシュボードアプリが正常に設定されました",
|
||
"API_ERROR": "アプリを作成できませんでした。後でもう一度お試しください"
|
||
},
|
||
"UPDATE": {
|
||
"HEADER": "ダッシュボードアプリを編集",
|
||
"FORM_SUBMIT": "更新",
|
||
"FORM_CANCEL": "キャンセル",
|
||
"API_SUCCESS": "ダッシュボードアプリが正常に更新されました",
|
||
"API_ERROR": "アプリを更新できませんでした。後でもう一度お試しください"
|
||
},
|
||
"DELETE": {
|
||
"CONFIRM_YES": "はい、削除します",
|
||
"CONFIRM_NO": "いいえ、保持します",
|
||
"TITLE": "削除の確認",
|
||
"MESSAGE": "アプリを削除してもよろしいですか - {appName}?",
|
||
"API_SUCCESS": "ダッシュボードアプリが正常に削除されました",
|
||
"API_ERROR": "アプリを削除できませんでした。後でもう一度お試しください"
|
||
}
|
||
},
|
||
"LINEAR": {
|
||
"ADD_OR_LINK_BUTTON": "Linear Issueを作成/リンク",
|
||
"LOADING": "Linearの課題を取得中...",
|
||
"LOADING_ERROR": "Linearの課題を取得中にエラーが発生しました。もう一度お試しください",
|
||
"CREATE": "作成",
|
||
"LINK": {
|
||
"SEARCH": "課題を検索",
|
||
"SELECT": "課題を選択",
|
||
"TITLE": "リンク",
|
||
"EMPTY_LIST": "Linearの課題が見つかりません",
|
||
"LOADING": "読み込み中",
|
||
"ERROR": "Linearの課題を取得中にエラーが発生しました。もう一度お試しください",
|
||
"LINK_SUCCESS": "課題が正常にリンクされました",
|
||
"LINK_ERROR": "課題のリンク中にエラーが発生しました。もう一度お試しください",
|
||
"LINK_TITLE": "会話 (#{conversationId}) と {name}"
|
||
},
|
||
"ADD_OR_LINK": {
|
||
"TITLE": "Linearの課題を作成/リンク",
|
||
"DESCRIPTION": "会話からLinearの課題を作成するか、既存の課題をリンクしてシームレスに追跡します。",
|
||
"FORM": {
|
||
"TITLE": {
|
||
"LABEL": "タイトル",
|
||
"PLACEHOLDER": "タイトルを入力",
|
||
"REQUIRED_ERROR": "タイトルは必須です"
|
||
},
|
||
"DESCRIPTION": {
|
||
"LABEL": "説明",
|
||
"PLACEHOLDER": "説明を入力"
|
||
},
|
||
"TEAM": {
|
||
"LABEL": "チーム",
|
||
"PLACEHOLDER": "チームを選択",
|
||
"SEARCH": "チームを検索",
|
||
"REQUIRED_ERROR": "チームは必須です"
|
||
},
|
||
"ASSIGNEE": {
|
||
"LABEL": "担当者",
|
||
"PLACEHOLDER": "担当者を選択",
|
||
"SEARCH": "担当者を検索"
|
||
},
|
||
"PRIORITY": {
|
||
"LABEL": "優先度",
|
||
"PLACEHOLDER": "優先度を選択",
|
||
"SEARCH": "優先度を検索"
|
||
},
|
||
"LABEL": {
|
||
"LABEL": "ラベル",
|
||
"PLACEHOLDER": "ラベルを選択",
|
||
"SEARCH": "ラベルを検索"
|
||
},
|
||
"STATUS": {
|
||
"LABEL": "状況",
|
||
"PLACEHOLDER": "状況を選択",
|
||
"SEARCH": "状況を検索"
|
||
},
|
||
"PROJECT": {
|
||
"LABEL": "プロジェクト",
|
||
"PLACEHOLDER": "プロジェクトを選択",
|
||
"SEARCH": "プロジェクトを検索"
|
||
}
|
||
},
|
||
"CREATE": "作成",
|
||
"CANCEL": "キャンセル",
|
||
"CREATE_SUCCESS": "課題が正常に作成されました",
|
||
"CREATE_ERROR": "課題の作成中にエラーが発生しました。もう一度お試しください",
|
||
"LOADING_TEAM_ERROR": "チームの取得中にエラーが発生しました。もう一度お試しください",
|
||
"LOADING_TEAM_ENTITIES_ERROR": "チームエンティティの取得中にエラーが発生しました。もう一度お試しください"
|
||
},
|
||
"ISSUE": {
|
||
"STATUS": "状況",
|
||
"PRIORITY": "優先度",
|
||
"ASSIGNEE": "担当者",
|
||
"LABELS": "ラベル",
|
||
"CREATED_AT": "{createdAt} に作成"
|
||
},
|
||
"UNLINK": {
|
||
"TITLE": "リンク解除",
|
||
"SUCCESS": "課題のリンクが正常に解除されました",
|
||
"ERROR": "課題のリンク解除中にエラーが発生しました。もう一度お試しください"
|
||
},
|
||
"NO_LINKED_ISSUES": "No linked issues found",
|
||
"DELETE": {
|
||
"TITLE": "Are you sure you want to delete the integration?",
|
||
"MESSAGE": "Are you sure you want to delete the integration?",
|
||
"CONFIRM": "はい、削除します",
|
||
"CANCEL": "キャンセル"
|
||
},
|
||
"CTA": {
|
||
"TITLE": "Connect to Linear",
|
||
"AGENT_DESCRIPTION": "Linear workspace is not connected. Request your administrator to connect a workspace to use this integration.",
|
||
"DESCRIPTION": "Linear workspace is not connected. Click the button below to connect your workspace to use this integration.",
|
||
"BUTTON_TEXT": "Connect Linear workspace"
|
||
}
|
||
},
|
||
"NOTION": {
|
||
"DELETE": {
|
||
"TITLE": "Are you sure you want to delete the Notion integration?",
|
||
"MESSAGE": "Deleting this integration will remove access to your Notion workspace and stop all related functionality.",
|
||
"CONFIRM": "はい、削除します",
|
||
"CANCEL": "キャンセル"
|
||
}
|
||
}
|
||
},
|
||
"CAPTAIN": {
|
||
"NAME": "キャプテン",
|
||
"HEADER_KNOW_MORE": "Know more",
|
||
"ASSISTANT_SWITCHER": {
|
||
"ASSISTANTS": "アシスタント",
|
||
"SWITCH_ASSISTANT": "Switch between assistants",
|
||
"NEW_ASSISTANT": "Create Assistant",
|
||
"EMPTY_LIST": "No assistants found, please create one to get started"
|
||
},
|
||
"COPILOT": {
|
||
"TITLE": "コパイロット",
|
||
"TRY_THESE_PROMPTS": "これらのプロンプトを試してください",
|
||
"PANEL_TITLE": "Get started with Copilot",
|
||
"KICK_OFF_MESSAGE": "Need a quick summary, want to check past conversations, or draft a better reply? Copilot’s here to speed things up.",
|
||
"SEND_MESSAGE": "メッセージを送信...",
|
||
"EMPTY_MESSAGE": "There was an error generating the response. Please try again.",
|
||
"LOADER": "Captainが考え中",
|
||
"YOU": "あなた",
|
||
"USE": "これを使用",
|
||
"RESET": "リセット",
|
||
"SHOW_STEPS": "Show steps",
|
||
"SELECT_ASSISTANT": "Select Assistant",
|
||
"PROMPTS": {
|
||
"SUMMARIZE": {
|
||
"LABEL": "Summarize this conversation",
|
||
"CONTENT": "Summarize the key points discussed between the customer and the support agent, including the customer's concerns, questions, and the solutions or responses provided by the support agent"
|
||
},
|
||
"SUGGEST": {
|
||
"LABEL": "Suggest an answer",
|
||
"CONTENT": "Analyze the customer's inquiry, and draft a response that effectively addresses their concerns or questions. Ensure the reply is clear, concise, and provides helpful information."
|
||
},
|
||
"RATE": {
|
||
"LABEL": "Rate this conversation",
|
||
"CONTENT": "Review the conversation to see how well it meets the customer's needs. Share a rating out of 5 based on tone, clarity, and effectiveness."
|
||
},
|
||
"HIGH_PRIORITY": {
|
||
"LABEL": "High priority conversations",
|
||
"CONTENT": "Give me a summary of all high priority open conversations. Include the conversation ID, customer name (if available), last message content, and assigned agent. Group by status if relevant."
|
||
},
|
||
"LIST_CONTACTS": {
|
||
"LABEL": "List contacts",
|
||
"CONTENT": "Show me the list of top 10 contacts. Include name, email or phone number (if available), last seen time, tags (if any)."
|
||
}
|
||
}
|
||
},
|
||
"PLAYGROUND": {
|
||
"USER": "あなた",
|
||
"ASSISTANT": "アシスタント",
|
||
"MESSAGE_PLACEHOLDER": "Type your message...",
|
||
"HEADER": "Playground",
|
||
"DESCRIPTION": "Use this playground to send messages to your assistant and check if it responds accurately, quickly, and in the tone you expect.",
|
||
"CREDIT_NOTE": "Messages sent here will count toward your Captain credits."
|
||
},
|
||
"PAYWALL": {
|
||
"TITLE": "アップグレードしてCaptain AIを利用する",
|
||
"AVAILABLE_ON": "Captainは無料プランでは利用できません。",
|
||
"UPGRADE_PROMPT": "アシスタント、Copilotなどにアクセスするには、プランをアップグレードしてください。",
|
||
"UPGRADE_NOW": "今すぐアップグレード",
|
||
"CANCEL_ANYTIME": "プランはいつでも変更またはキャンセルできます"
|
||
},
|
||
"ENTERPRISE_PAYWALL": {
|
||
"UPGRADE_PROMPT": "アシスタント、Copilotなどにアクセスするには、プランをアップグレードしてください。",
|
||
"ASK_ADMIN": "管理者にアップグレードを依頼してください。"
|
||
},
|
||
"BANNER": {
|
||
"RESPONSES": "利用制限の 80% を超過しました。引き続き Captain AI を利用するには、アップグレードしてください。",
|
||
"DOCUMENTS": "ドキュメントの上限に達しました。Captain AI を引き続き利用するには、アップグレードしてください。"
|
||
},
|
||
"FORM": {
|
||
"CANCEL": "キャンセル",
|
||
"CREATE": "作成",
|
||
"EDIT": "更新"
|
||
},
|
||
"ASSISTANTS": {
|
||
"HEADER": "アシスタント",
|
||
"NO_ASSISTANTS_AVAILABLE": "There are no assistants available in your account.",
|
||
"ADD_NEW": "新しいアシスタントを作成",
|
||
"DELETE": {
|
||
"TITLE": "アシスタントを削除してもよろしいですか?",
|
||
"DESCRIPTION": "この操作は永久的です。アシスタントを削除すると、すべての接続された受信トレイから削除され、生成されたすべての知識が永久に消去されます。",
|
||
"CONFIRM": "はい、削除します",
|
||
"SUCCESS_MESSAGE": "アシスタントが正常に削除されました",
|
||
"ERROR_MESSAGE": "アシスタントの削除中にエラーが発生しました。もう一度お試しください。"
|
||
},
|
||
"FORM_DESCRIPTION": "以下の詳細を入力して、アシスタントの名前、その目的を説明し、サポートする製品を指定してください。",
|
||
"CREATE": {
|
||
"TITLE": "アシスタントを作成",
|
||
"SUCCESS_MESSAGE": "アシスタントが正常に作成されました",
|
||
"ERROR_MESSAGE": "アシスタントの作成中にエラーが発生しました。もう一度お試しください。"
|
||
},
|
||
"FORM": {
|
||
"UPDATE": "更新",
|
||
"SECTIONS": {
|
||
"BASIC_INFO": "Basic Information",
|
||
"SYSTEM_MESSAGES": "System Messages",
|
||
"INSTRUCTIONS": "Instructions",
|
||
"FEATURES": "機能",
|
||
"TOOLS": "Tools "
|
||
},
|
||
"NAME": {
|
||
"LABEL": "名前",
|
||
"PLACEHOLDER": "Enter assistant name",
|
||
"ERROR": "The name is required"
|
||
},
|
||
"TEMPERATURE": {
|
||
"LABEL": "Response Temperature",
|
||
"DESCRIPTION": "Adjust how creative or restrictive the assistant's responses should be. Lower values produce more focused and deterministic responses, while higher values allow for more creative and varied outputs."
|
||
},
|
||
"DESCRIPTION": {
|
||
"LABEL": "説明",
|
||
"PLACEHOLDER": "Enter assistant description",
|
||
"ERROR": "The description is required"
|
||
},
|
||
"PRODUCT_NAME": {
|
||
"LABEL": "製品名",
|
||
"PLACEHOLDER": "Enter product name",
|
||
"ERROR": "製品名が必要です"
|
||
},
|
||
"WELCOME_MESSAGE": {
|
||
"LABEL": "Welcome Message",
|
||
"PLACEHOLDER": "Enter welcome message"
|
||
},
|
||
"HANDOFF_MESSAGE": {
|
||
"LABEL": "Handoff Message",
|
||
"PLACEHOLDER": "Enter handoff message"
|
||
},
|
||
"RESOLUTION_MESSAGE": {
|
||
"LABEL": "Resolution Message",
|
||
"PLACEHOLDER": "Enter resolution message"
|
||
},
|
||
"INSTRUCTIONS": {
|
||
"LABEL": "Instructions",
|
||
"PLACEHOLDER": "Enter instructions for the assistant"
|
||
},
|
||
"FEATURES": {
|
||
"TITLE": "機能",
|
||
"ALLOW_CONVERSATION_FAQS": "解決済みの会話からFAQを生成",
|
||
"ALLOW_MEMORIES": "顧客とのやり取りから重要な詳細を記憶としてキャプチャ",
|
||
"ALLOW_CITATIONS": "Include source citations in responses"
|
||
}
|
||
},
|
||
"EDIT": {
|
||
"TITLE": "アシスタントを更新",
|
||
"SUCCESS_MESSAGE": "アシスタントが正常に更新されました",
|
||
"ERROR_MESSAGE": "アシスタントの更新中にエラーが発生しました。もう一度お試しください。",
|
||
"NOT_FOUND": "Could not find the assistant. Please try again."
|
||
},
|
||
"SETTINGS": {
|
||
"HEADER": "設定",
|
||
"BASIC_SETTINGS": {
|
||
"TITLE": "Basic settings",
|
||
"DESCRIPTION": "Customize what the assistant says when ending a conversation or transferring to a human."
|
||
},
|
||
"SYSTEM_SETTINGS": {
|
||
"TITLE": "System settings",
|
||
"DESCRIPTION": "Customize what the assistant says when ending a conversation or transferring to a human."
|
||
},
|
||
"CONTROL_ITEMS": {
|
||
"TITLE": "The Fun Stuff",
|
||
"DESCRIPTION": "Add more control to the assistant. (a bit more visual like a story : Query guardrail → scenarios → output) Nudges user to actually utilise these.",
|
||
"OPTIONS": {
|
||
"GUARDRAILS": {
|
||
"TITLE": "Guardrails",
|
||
"DESCRIPTION": "Keeps things on track—only the kinds of questions you want your assistant to answer, nothing off-limits or off-topic."
|
||
},
|
||
"RESPONSE_GUIDELINES": {
|
||
"TITLE": "Response guidelines",
|
||
"DESCRIPTION": "The vibe and structure of your assistant’s replies—clear and friendly? Short and snappy? Detailed and formal?"
|
||
}
|
||
}
|
||
},
|
||
"DELETE": {
|
||
"TITLE": "アシスタントを削除",
|
||
"DESCRIPTION": "この操作は永久的です。アシスタントを削除すると、すべての接続された受信トレイから削除され、生成されたすべての知識が永久に消去されます。",
|
||
"BUTTON_TEXT": "{assistantName}を削除"
|
||
}
|
||
},
|
||
"OPTIONS": {
|
||
"EDIT_ASSISTANT": "アシスタントを編集",
|
||
"DELETE_ASSISTANT": "アシスタントを削除",
|
||
"VIEW_CONNECTED_INBOXES": "接続された受信トレイを表示"
|
||
},
|
||
"EMPTY_STATE": {
|
||
"TITLE": "利用可能なアシスタントがありません",
|
||
"SUBTITLE": "アシスタントを作成して、お客様に迅速かつ正確な回答を提供します。アシスタントは、ヘルプ記事や過去の会話から学習します。",
|
||
"FEATURE_SPOTLIGHT": {
|
||
"TITLE": "Captain Assistant",
|
||
"NOTE": "Captain Assistant engages directly with customers, learns from your help docs and past conversations, and delivers instant, accurate responses. It handles the initial queries, providing quick resolutions before transferring to an agent when needed."
|
||
}
|
||
},
|
||
"GUARDRAILS": {
|
||
"TITLE": "Guardrails",
|
||
"DESCRIPTION": "Keeps things on track—only the kinds of questions you want your assistant to answer, nothing off-limits or off-topic.",
|
||
"BULK_ACTION": {
|
||
"SELECTED": "{count} item selected | {count} items selected",
|
||
"SELECT_ALL": "Select all ({count})",
|
||
"UNSELECT_ALL": "Unselect all ({count})",
|
||
"BULK_DELETE_BUTTON": "削除"
|
||
},
|
||
"ADD": {
|
||
"SUGGESTED": {
|
||
"TITLE": "Example guardrails",
|
||
"ADD": "Add all",
|
||
"ADD_SINGLE": "Add this",
|
||
"SAVE": "Add and save (↵)",
|
||
"PLACEHOLDER": "Type in another guardrail..."
|
||
},
|
||
"NEW": {
|
||
"TITLE": "Add a guardrail",
|
||
"CREATE": "作成",
|
||
"CANCEL": "キャンセル",
|
||
"PLACEHOLDER": "Type in another guardrail...",
|
||
"TEST_ALL": "Test all"
|
||
}
|
||
},
|
||
"LIST": {
|
||
"SEARCH_PLACEHOLDER": "検索..."
|
||
},
|
||
"EMPTY_MESSAGE": "No guardrails found. Create or add examples to begin.",
|
||
"SEARCH_EMPTY_MESSAGE": "No guardrails found for this search.",
|
||
"API": {
|
||
"ADD": {
|
||
"SUCCESS": "Guardrails added successfully",
|
||
"ERROR": "There was an error adding guardrails, please try again."
|
||
},
|
||
"UPDATE": {
|
||
"SUCCESS": "Guardrails updated successfully",
|
||
"ERROR": "There was an error updating guardrails, please try again."
|
||
},
|
||
"DELETE": {
|
||
"SUCCESS": "Guardrails deleted successfully",
|
||
"ERROR": "There was an error deleting guardrails, please try again."
|
||
}
|
||
}
|
||
},
|
||
"RESPONSE_GUIDELINES": {
|
||
"TITLE": "Response Guidelines",
|
||
"DESCRIPTION": "The vibe and structure of your assistant’s replies—clear and friendly? Short and snappy? Detailed and formal?",
|
||
"BULK_ACTION": {
|
||
"SELECTED": "{count} item selected | {count} items selected",
|
||
"SELECT_ALL": "Select all ({count})",
|
||
"UNSELECT_ALL": "Unselect all ({count})",
|
||
"BULK_DELETE_BUTTON": "削除"
|
||
},
|
||
"ADD": {
|
||
"SUGGESTED": {
|
||
"TITLE": "Example response guidelines",
|
||
"ADD": "Add all",
|
||
"ADD_SINGLE": "Add this",
|
||
"SAVE": "Add and save (↵)",
|
||
"PLACEHOLDER": "Type in another response guideline..."
|
||
},
|
||
"NEW": {
|
||
"TITLE": "Add a response guideline",
|
||
"CREATE": "作成",
|
||
"CANCEL": "キャンセル",
|
||
"PLACEHOLDER": "Type in another response guideline...",
|
||
"TEST_ALL": "Test all"
|
||
}
|
||
},
|
||
"LIST": {
|
||
"SEARCH_PLACEHOLDER": "検索..."
|
||
},
|
||
"EMPTY_MESSAGE": "No response guidelines found. Create or add examples to begin.",
|
||
"SEARCH_EMPTY_MESSAGE": "No response guidelines found for this search.",
|
||
"API": {
|
||
"ADD": {
|
||
"SUCCESS": "Response Guidelines added successfully",
|
||
"ERROR": "There was an error adding response guidelines, please try again."
|
||
},
|
||
"UPDATE": {
|
||
"SUCCESS": "Response Guidelines updated successfully",
|
||
"ERROR": "There was an error updating response guidelines, please try again."
|
||
},
|
||
"DELETE": {
|
||
"SUCCESS": "Response Guidelines deleted successfully",
|
||
"ERROR": "There was an error deleting response guidelines, please try again."
|
||
}
|
||
}
|
||
},
|
||
"SCENARIOS": {
|
||
"TITLE": "Scenarios",
|
||
"DESCRIPTION": "Give your assistant some context—like “what to do when a user is stuck,” or “how to act during a refund request.”",
|
||
"BULK_ACTION": {
|
||
"SELECTED": "{count} item selected | {count} items selected",
|
||
"SELECT_ALL": "Select all ({count})",
|
||
"UNSELECT_ALL": "Unselect all ({count})",
|
||
"BULK_DELETE_BUTTON": "削除"
|
||
},
|
||
"ADD": {
|
||
"SUGGESTED": {
|
||
"TITLE": "Example scenarios",
|
||
"ADD": "Add all",
|
||
"ADD_SINGLE": "Add this",
|
||
"TOOLS_USED": "Tools used :"
|
||
},
|
||
"NEW": {
|
||
"CREATE": "Add a scenario",
|
||
"TITLE": "Create a scenario",
|
||
"FORM": {
|
||
"TITLE": {
|
||
"LABEL": "タイトル",
|
||
"PLACEHOLDER": "Enter a name for the scenario",
|
||
"ERROR": "Scenario name is required"
|
||
},
|
||
"DESCRIPTION": {
|
||
"LABEL": "説明",
|
||
"PLACEHOLDER": "Describe how and where this scenario will be used",
|
||
"ERROR": "Scenario description is required"
|
||
},
|
||
"INSTRUCTION": {
|
||
"LABEL": "How to handle",
|
||
"PLACEHOLDER": "Describe how and where this scenario will be handled",
|
||
"ERROR": "Scenario content is required"
|
||
},
|
||
"CREATE": "作成",
|
||
"CANCEL": "キャンセル"
|
||
}
|
||
}
|
||
},
|
||
"UPDATE": {
|
||
"CANCEL": "キャンセル",
|
||
"UPDATE": "Update changes"
|
||
},
|
||
"LIST": {
|
||
"SEARCH_PLACEHOLDER": "検索..."
|
||
},
|
||
"EMPTY_MESSAGE": "No scenarios found. Create or add examples to begin.",
|
||
"SEARCH_EMPTY_MESSAGE": "No scenarios found for this search.",
|
||
"API": {
|
||
"ADD": {
|
||
"SUCCESS": "Scenarios added successfully",
|
||
"ERROR": "There was an error adding scenarios, please try again."
|
||
},
|
||
"UPDATE": {
|
||
"SUCCESS": "Scenarios updated successfully",
|
||
"ERROR": "There was an error updating scenarios, please try again."
|
||
},
|
||
"DELETE": {
|
||
"SUCCESS": "Scenarios deleted successfully",
|
||
"ERROR": "There was an error deleting scenarios, please try again."
|
||
}
|
||
}
|
||
}
|
||
},
|
||
"DOCUMENTS": {
|
||
"HEADER": "ドキュメント",
|
||
"ADD_NEW": "新しいドキュメントを作成",
|
||
"RELATED_RESPONSES": {
|
||
"TITLE": "関連するFAQ",
|
||
"DESCRIPTION": "これらのFAQはドキュメントから直接生成されます。"
|
||
},
|
||
"FORM_DESCRIPTION": "ドキュメントのURLを入力して知識ソースとして追加し、それに関連付けるアシスタントを選択してください。",
|
||
"CREATE": {
|
||
"TITLE": "ドキュメントを追加",
|
||
"SUCCESS_MESSAGE": "ドキュメントが正常に作成されました",
|
||
"ERROR_MESSAGE": "ドキュメントの作成中にエラーが発生しました。もう一度お試しください。"
|
||
},
|
||
"FORM": {
|
||
"TYPE": {
|
||
"LABEL": "Document Type",
|
||
"URL": "URL",
|
||
"PDF": "PDF File"
|
||
},
|
||
"URL": {
|
||
"LABEL": "URL",
|
||
"PLACEHOLDER": "ドキュメントのURLを入力",
|
||
"ERROR": "有効なURLを入力してください"
|
||
},
|
||
"PDF_FILE": {
|
||
"LABEL": "PDF File",
|
||
"CHOOSE_FILE": "Choose PDF file",
|
||
"ERROR": "Please select a PDF file",
|
||
"HELP_TEXT": "Maximum file size: 10MB",
|
||
"INVALID_TYPE": "Please select a valid PDF file",
|
||
"TOO_LARGE": "File size exceeds 10MB limit"
|
||
},
|
||
"NAME": {
|
||
"LABEL": "Document Name (Optional)",
|
||
"PLACEHOLDER": "Enter a name for the document"
|
||
}
|
||
},
|
||
"DELETE": {
|
||
"TITLE": "ドキュメントを削除してもよろしいですか?",
|
||
"DESCRIPTION": "この操作は永久的です。ドキュメントを削除すると、生成されたすべての知識が永久に消去されます。",
|
||
"CONFIRM": "はい、削除します",
|
||
"SUCCESS_MESSAGE": "ドキュメントが正常に削除されました",
|
||
"ERROR_MESSAGE": "ドキュメントの削除中にエラーが発生しました。もう一度お試しください。"
|
||
},
|
||
"OPTIONS": {
|
||
"VIEW_RELATED_RESPONSES": "関連する応答を表示",
|
||
"DELETE_DOCUMENT": "ドキュメントを削除"
|
||
},
|
||
"EMPTY_STATE": {
|
||
"TITLE": "利用可能なドキュメントがありません",
|
||
"SUBTITLE": "ドキュメントはアシスタントがFAQを生成するために使用されます。ドキュメントをインポートしてアシスタントにコンテキストを提供できます。",
|
||
"FEATURE_SPOTLIGHT": {
|
||
"TITLE": "Captain Document",
|
||
"NOTE": "A document in Captain serves as a knowledge resource for the assistant. By connecting your help center or guides, Captain can analyze the content and provide accurate responses for customer inquiries."
|
||
}
|
||
}
|
||
},
|
||
"CUSTOM_TOOLS": {
|
||
"HEADER": "Tools",
|
||
"ADD_NEW": "Create a new tool",
|
||
"EMPTY_STATE": {
|
||
"TITLE": "No custom tools available",
|
||
"SUBTITLE": "Create custom tools to connect your assistant with external APIs and services, enabling it to fetch data and perform actions on your behalf.",
|
||
"FEATURE_SPOTLIGHT": {
|
||
"TITLE": "Custom Tools",
|
||
"NOTE": "Custom tools allow your assistant to interact with external APIs and services. Create tools to fetch data, perform actions, or integrate with your existing systems to enhance your assistant's capabilities."
|
||
}
|
||
},
|
||
"FORM_DESCRIPTION": "Configure your custom tool to connect with external APIs",
|
||
"OPTIONS": {
|
||
"EDIT_TOOL": "Edit tool",
|
||
"DELETE_TOOL": "Delete tool"
|
||
},
|
||
"CREATE": {
|
||
"TITLE": "Create Custom Tool",
|
||
"SUCCESS_MESSAGE": "Custom tool created successfully",
|
||
"ERROR_MESSAGE": "Failed to create custom tool"
|
||
},
|
||
"EDIT": {
|
||
"TITLE": "Edit Custom Tool",
|
||
"SUCCESS_MESSAGE": "Custom tool updated successfully",
|
||
"ERROR_MESSAGE": "Failed to update custom tool"
|
||
},
|
||
"DELETE": {
|
||
"TITLE": "Delete Custom Tool",
|
||
"DESCRIPTION": "Are you sure you want to delete this custom tool? This action cannot be undone.",
|
||
"CONFIRM": "はい、削除します",
|
||
"SUCCESS_MESSAGE": "Custom tool deleted successfully",
|
||
"ERROR_MESSAGE": "Failed to delete custom tool"
|
||
},
|
||
"FORM": {
|
||
"TITLE": {
|
||
"LABEL": "Tool Name",
|
||
"PLACEHOLDER": "Order Lookup",
|
||
"ERROR": "Tool name is required"
|
||
},
|
||
"DESCRIPTION": {
|
||
"LABEL": "説明",
|
||
"PLACEHOLDER": "Looks up order details by order ID"
|
||
},
|
||
"HTTP_METHOD": {
|
||
"LABEL": "Method"
|
||
},
|
||
"ENDPOINT_URL": {
|
||
"LABEL": "Endpoint URL",
|
||
"PLACEHOLDER": "https://api.example.com/orders/{'{{'} order_id {'}}'}",
|
||
"ERROR": "Valid URL is required"
|
||
},
|
||
"AUTH_TYPE": {
|
||
"LABEL": "Authentication Type"
|
||
},
|
||
"AUTH_TYPES": {
|
||
"NONE": "なし",
|
||
"BEARER": "Bearer Token",
|
||
"BASIC": "Basic Auth",
|
||
"API_KEY": "APIキー"
|
||
},
|
||
"AUTH_CONFIG": {
|
||
"BEARER_TOKEN": "Bearer Token",
|
||
"BEARER_TOKEN_PLACEHOLDER": "Enter your bearer token",
|
||
"USERNAME": "Username",
|
||
"USERNAME_PLACEHOLDER": "Enter username",
|
||
"PASSWORD": "パスワード",
|
||
"PASSWORD_PLACEHOLDER": "Enter password",
|
||
"API_KEY": "Header Name",
|
||
"API_KEY_PLACEHOLDER": "X-API-Key",
|
||
"API_VALUE": "Header Value",
|
||
"API_VALUE_PLACEHOLDER": "Enter API key value"
|
||
},
|
||
"PARAMETERS": {
|
||
"LABEL": "Parameters",
|
||
"HELP_TEXT": "Define the parameters that will be extracted from user queries"
|
||
},
|
||
"ADD_PARAMETER": "Add Parameter",
|
||
"PARAM_NAME": {
|
||
"PLACEHOLDER": "Parameter name (e.g., order_id)"
|
||
},
|
||
"PARAM_TYPE": {
|
||
"PLACEHOLDER": "タイプ"
|
||
},
|
||
"PARAM_TYPES": {
|
||
"STRING": "String",
|
||
"NUMBER": "数値",
|
||
"BOOLEAN": "Boolean",
|
||
"ARRAY": "Array",
|
||
"OBJECT": "Object"
|
||
},
|
||
"PARAM_DESCRIPTION": {
|
||
"PLACEHOLDER": "Description of the parameter"
|
||
},
|
||
"PARAM_REQUIRED": {
|
||
"LABEL": "必須"
|
||
},
|
||
"REQUEST_TEMPLATE": {
|
||
"LABEL": "Request Body Template (Optional)",
|
||
"PLACEHOLDER": "{'{'}\n \"order_id\": \"{'{{'} order_id {'}}'}\"\n{'}'}"
|
||
},
|
||
"RESPONSE_TEMPLATE": {
|
||
"LABEL": "Response Template (Optional)",
|
||
"PLACEHOLDER": "Order {'{{'} order_id {'}}'} status: {'{{'} status {'}}'}"
|
||
},
|
||
"ERRORS": {
|
||
"PARAM_NAME_REQUIRED": "Parameter name is required"
|
||
}
|
||
}
|
||
},
|
||
"RESPONSES": {
|
||
"HEADER": "FAQ",
|
||
"PENDING_FAQS": "Pending FAQs",
|
||
"ADD_NEW": "新しいFAQを作成",
|
||
"DOCUMENTABLE": {
|
||
"CONVERSATION": "会話 #{id}"
|
||
},
|
||
"SELECTED": "{count} selected",
|
||
"SELECT_ALL": "Select all ({count})",
|
||
"UNSELECT_ALL": "Unselect all ({count})",
|
||
"SEARCH_PLACEHOLDER": "Search FAQs...",
|
||
"BULK_APPROVE_BUTTON": "Approve",
|
||
"BULK_DELETE_BUTTON": "削除",
|
||
"BULK_APPROVE": {
|
||
"SUCCESS_MESSAGE": "FAQs approved successfully",
|
||
"ERROR_MESSAGE": "There was an error approving the FAQs, please try again."
|
||
},
|
||
"BULK_DELETE": {
|
||
"TITLE": "Delete FAQs?",
|
||
"DESCRIPTION": "Are you sure you want to delete the selected FAQs? This action cannot be undone.",
|
||
"CONFIRM": "Yes, delete all",
|
||
"SUCCESS_MESSAGE": "FAQs deleted successfully",
|
||
"ERROR_MESSAGE": "There was an error deleting the FAQs, please try again."
|
||
},
|
||
"DELETE": {
|
||
"TITLE": "FAQを削除してもよろしいですか?",
|
||
"DESCRIPTION": "",
|
||
"CONFIRM": "はい、削除します",
|
||
"SUCCESS_MESSAGE": "FAQが正常に削除されました",
|
||
"ERROR_MESSAGE": "FAQの削除中にエラーが発生しました。もう一度お試しください。"
|
||
},
|
||
"FILTER": {
|
||
"ASSISTANT": "アシスタント: {selected}",
|
||
"STATUS": "状況: {selected}",
|
||
"ALL_ASSISTANTS": "すべて"
|
||
},
|
||
"STATUS": {
|
||
"TITLE": "状況",
|
||
"PENDING": "保留中",
|
||
"APPROVED": "承認済み",
|
||
"ALL": "すべて"
|
||
},
|
||
"PENDING_BANNER": {
|
||
"TITLE": "Captain has found some FAQs your customers were looking for.",
|
||
"ACTION": "Click here to review"
|
||
},
|
||
"FORM_DESCRIPTION": "質問とその対応する回答をナレッジベースに追加し、それに関連付けるアシスタントを選択してください。",
|
||
"CREATE": {
|
||
"TITLE": "FAQを追加",
|
||
"SUCCESS_MESSAGE": "応答が正常に追加されました。",
|
||
"ERROR_MESSAGE": "応答の追加中にエラーが発生しました。もう一度お試しください。"
|
||
},
|
||
"FORM": {
|
||
"QUESTION": {
|
||
"LABEL": "質問",
|
||
"PLACEHOLDER": "ここに質問を入力",
|
||
"ERROR": "有効な質問を入力してください。"
|
||
},
|
||
"ANSWER": {
|
||
"LABEL": "回答",
|
||
"PLACEHOLDER": "ここに回答を入力",
|
||
"ERROR": "有効な回答を入力してください。"
|
||
}
|
||
},
|
||
"EDIT": {
|
||
"TITLE": "FAQを更新",
|
||
"SUCCESS_MESSAGE": "FAQが正常に更新されました",
|
||
"ERROR_MESSAGE": "FAQの更新中にエラーが発生しました。もう一度お試しください",
|
||
"APPROVE_SUCCESS_MESSAGE": "FAQが承認済みとしてマークされました"
|
||
},
|
||
"OPTIONS": {
|
||
"APPROVE": "Approve",
|
||
"EDIT_RESPONSE": "編集",
|
||
"DELETE_RESPONSE": "削除"
|
||
},
|
||
"EMPTY_STATE": {
|
||
"TITLE": "FAQが見つかりません",
|
||
"NO_PENDING_TITLE": "There are no more pending FAQs to review",
|
||
"SUBTITLE": "FAQは、アシスタントがお客様からの質問に迅速かつ正確に回答するのに役立ちます。コンテンツから自動的に生成することも、手動で追加することもできます。",
|
||
"CLEAR_SEARCH": "Clear active filters",
|
||
"FEATURE_SPOTLIGHT": {
|
||
"TITLE": "Captain FAQ",
|
||
"NOTE": "Captain FAQs detects common customer questions—whether missing from your knowledge base or frequently asked—and generates relevant FAQs to improve support. You can review each suggestion and decide whether to approve or reject it."
|
||
}
|
||
}
|
||
},
|
||
"INBOXES": {
|
||
"HEADER": "接続された受信トレイ",
|
||
"ADD_NEW": "新しい受信トレイを接続",
|
||
"OPTIONS": {
|
||
"DISCONNECT": "切断"
|
||
},
|
||
"DELETE": {
|
||
"TITLE": "受信トレイを切断してもよろしいですか?",
|
||
"DESCRIPTION": "",
|
||
"CONFIRM": "はい、削除します",
|
||
"SUCCESS_MESSAGE": "受信トレイが正常に切断されました。",
|
||
"ERROR_MESSAGE": "受信トレイの切断中にエラーが発生しました。もう一度お試しください。"
|
||
},
|
||
"FORM_DESCRIPTION": "アシスタントと接続する受信トレイを選択してください。",
|
||
"CREATE": {
|
||
"TITLE": "受信トレイを接続",
|
||
"SUCCESS_MESSAGE": "受信トレイが正常に接続されました。",
|
||
"ERROR_MESSAGE": "受信トレイの接続中にエラーが発生しました。もう一度お試しください。"
|
||
},
|
||
"FORM": {
|
||
"INBOX": {
|
||
"LABEL": "受信トレイ",
|
||
"PLACEHOLDER": "アシスタントを展開する受信トレイを選択",
|
||
"ERROR": "受信トレイの選択が必要です。"
|
||
}
|
||
},
|
||
"EMPTY_STATE": {
|
||
"TITLE": "接続された受信トレイがありません",
|
||
"SUBTITLE": "受信トレイに接続すると、アシスタントがお客様からの最初の質問を対応し、その後あなたに引き継ぐことができます。"
|
||
}
|
||
}
|
||
}
|
||
}
|