b03dfdb751
* 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
60 KiB
JSON
978 lines
60 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": "Капитан не включен на вашем аккаунте.",
|
||
"CLICK_HERE_TO_CONFIGURE": "Нажмите здесь, чтобы настроить",
|
||
"LOADING_CONSOLE": "Загрузка консоли Капитана...",
|
||
"FAILED_TO_LOAD_CONSOLE": "Не удалось загрузить консоль Капитана. Пожалуйста, обновите страницу и повторите попытку."
|
||
},
|
||
"WEBHOOK": {
|
||
"SUBSCRIBED_EVENTS": "События с подпиской",
|
||
"LEARN_MORE": "Узнать больше о вебхуках",
|
||
"FORM": {
|
||
"CANCEL": "Отменить",
|
||
"DESC": "Вебхуки позволяют получить вам информацию о том, что происходит в вашей учетной записи 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_OFF": "Печатание во время разговора выключено"
|
||
}
|
||
},
|
||
"NAME": {
|
||
"LABEL": "Webhook Name",
|
||
"PLACEHOLDER": "Enter the name of the webhook"
|
||
},
|
||
"END_POINT": {
|
||
"LABEL": "URL вебхука",
|
||
"PLACEHOLDER": "Пример: {webhookExampleURL}",
|
||
"ERROR": "Пожалуйста, введите правильный URL"
|
||
},
|
||
"EDIT_SUBMIT": "Обновить webhook",
|
||
"ADD_SUBMIT": "Создать вебхук"
|
||
},
|
||
"TITLE": "Вебхук",
|
||
"CONFIGURE": "Настроить",
|
||
"HEADER": "Настройки вебхуков",
|
||
"HEADER_BTN_TXT": "Добавить новый вебхук",
|
||
"LOADING": "Получение подключенных вебхуков",
|
||
"SEARCH_404": "Нет вебхуков, соответствующих запросу",
|
||
"SIDEBAR_TXT": "<p><b>Вебхуки</b> </p> <p>Вебхуки – это HTTP запросы, которые можно установить для любого аккаунта. Они вызываются по событиям: например, при создании новых сообщений в Chatwoot. Вы можете создать сколько угодно вебхуков для этой учетной записи. <br /><br /> Для создания <b>вебхука</b>, нажмите на кнопку <b>Добавить новый вебхук</b>. Вы также можете удалить любой существующий вебхук, нажав на кнопку Удалить.</p>",
|
||
"LIST": {
|
||
"404": "У вас нет вебхуков.",
|
||
"TITLE": "Управление вебхуками",
|
||
"TABLE_HEADER": {
|
||
"WEBHOOK_ENDPOINT": "Адрес вебхука",
|
||
"ACTIONS": "Действия"
|
||
}
|
||
},
|
||
"EDIT": {
|
||
"BUTTON_TEXT": "Редактировать",
|
||
"TITLE": "Редактировать вебхук",
|
||
"API": {
|
||
"SUCCESS_MESSAGE": "Конфигурация вебхука успешно обновлена",
|
||
"ERROR_MESSAGE": "Не удается соединиться с сервером Woot, попробуйте позже"
|
||
}
|
||
},
|
||
"ADD": {
|
||
"CANCEL": "Отменить",
|
||
"TITLE": "Добавить новый вебхук",
|
||
"API": {
|
||
"SUCCESS_MESSAGE": "Конфигурация вебхука успешно добавлена",
|
||
"ERROR_MESSAGE": "Не удается соединиться с сервером Woot, попробуйте позже"
|
||
}
|
||
},
|
||
"DELETE": {
|
||
"BUTTON_TEXT": "Удалить",
|
||
"API": {
|
||
"SUCCESS_MESSAGE": "Вебхук удален",
|
||
"ERROR_MESSAGE": "Не удается соединиться с сервером Woot, попробуйте позже"
|
||
},
|
||
"CONFIRM": {
|
||
"TITLE": "Подтвердите удаление",
|
||
"MESSAGE": "Вы уверены, что хотите удалить вебхук? ({webhookURL})",
|
||
"YES": "Да, удалить ",
|
||
"NO": "Нет, не удалять"
|
||
}
|
||
}
|
||
},
|
||
"SLACK": {
|
||
"DELETE": "Удалить",
|
||
"DELETE_CONFIRMATION": {
|
||
"TITLE": "Удалить интеграцию",
|
||
"MESSAGE": "Вы уверены, что хотите удалить интеграцию? Это приведет к потере доступа к диалогам на вашем рабочем пространстве."
|
||
},
|
||
"HELP_TEXT": {
|
||
"TITLE": "Как использовать интеграцию Slack?",
|
||
"BODY": "С этой интеграцией, все входящие диалоги будут синхронизированы с **{selectedChannelName}*** каналом в вашей рабочей области Slack. Вы можете управлять переписками клиентов прямо на канале и никогда не пропускать сообщения.\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. Однако интеграция в настоящее время неактивна. Чтобы активировать интеграцию и подключить канал к чату, нажмите на кнопку ниже.\n\n**Примечание:** Если вы пытаетесь подключить частный канал, добавьте приложение Чатвут в канал 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": "Помощь ИИ",
|
||
"WITH_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": "ИИ пишет",
|
||
"BUTTONS": {
|
||
"APPLY": "Использовать этот вариант перевода",
|
||
"CANCEL": "Отменить"
|
||
}
|
||
},
|
||
"CTA_MODAL": {
|
||
"TITLE": "Интеграция с OpenAI",
|
||
"DESC": "Принесите дополнительные функции AI на вашу панель управления с помощью моделей GPT OpenAI. Чтобы начать, введите API ключ из вашей учетной записи OpenAI.",
|
||
"KEY_PLACEHOLDER": "Введите ваш OpenAI API ключ",
|
||
"BUTTONS": {
|
||
"NEED_HELP": "Нужна помощь?",
|
||
"DISMISS": "Отклонить",
|
||
"FINISH": "Завершить установку"
|
||
},
|
||
"DISMISS_MESSAGE": "Вы можете настроить интеграцию OpenAI позже, когда хотите.",
|
||
"SUCCESS_MESSAGE": "Интеграция OpenAI успешно настроена"
|
||
},
|
||
"TITLE": "Улучшить с ИИ",
|
||
"SUMMARY_TITLE": "Сводка с ИИ",
|
||
"REPLY_TITLE": "Ответить с помощью ИИ",
|
||
"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": "Endpoint"
|
||
},
|
||
"EDIT_TOOLTIP": "Редактировать приложение",
|
||
"DELETE_TOOLTIP": "Удалить приложение"
|
||
},
|
||
"FORM": {
|
||
"TITLE_LABEL": "Имя",
|
||
"TITLE_PLACEHOLDER": "Введите имя для вашего приложения",
|
||
"TITLE_ERROR": "Требуется название для панели приложений",
|
||
"URL_LABEL": "Endpoint",
|
||
"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": "Создать/Связать Задачу",
|
||
"LOADING": "Загрузка связанных задач...",
|
||
"LOADING_ERROR": "Ошибка получения данных о связанных задачах, пожалуйста попробуйте еще раз",
|
||
"CREATE": "Создать",
|
||
"LINK": {
|
||
"SEARCH": "Поиск задач",
|
||
"SELECT": "Выбрать задачу",
|
||
"TITLE": "Ссылка",
|
||
"EMPTY_LIST": "Связанных проблем не найдено",
|
||
"LOADING": "Загрузка",
|
||
"ERROR": "Ошибка получения данных о связанных задачах, пожалуйста попробуйте еще раз",
|
||
"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": "Не найдено связанных задач",
|
||
"DELETE": {
|
||
"TITLE": "Вы уверены, что хотите удалить интеграцию?",
|
||
"MESSAGE": "Вы уверены, что хотите удалить интеграцию?",
|
||
"CONFIRM": "Да, удалить",
|
||
"CANCEL": "Отменить"
|
||
},
|
||
"CTA": {
|
||
"TITLE": "Подключение к Linear",
|
||
"AGENT_DESCRIPTION": "Linear workspace не подключено. Попросите администратора подключить рабочую область, чтобы использовать эту интеграцию.",
|
||
"DESCRIPTION": "Linear workspace не подключено. Нажмите на кнопку ниже, чтобы подключить рабочую область, чтобы использовать эту интеграцию.",
|
||
"BUTTON_TEXT": "Подключить Linear workspace"
|
||
}
|
||
},
|
||
"NOTION": {
|
||
"DELETE": {
|
||
"TITLE": "Вы уверены, что хотите удалить интеграцию с Notion?",
|
||
"MESSAGE": "Удаление этой интеграции приведет к удалению доступа к вашему проекту Notion и остановит все связанные функции.",
|
||
"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": "Copilot",
|
||
"TRY_THESE_PROMPTS": "Попробуйте эти запросы",
|
||
"PANEL_TITLE": "Начать работу с Copilot",
|
||
"KICK_OFF_MESSAGE": "Хотите узнать суть или проверить прошлые диалоги или написать лучший ответ? Copilot здесь, чтобы ускорить работу.",
|
||
"SEND_MESSAGE": "Отправить сообщение...",
|
||
"EMPTY_MESSAGE": "Произошла ошибка при генерации ответа. Пожалуйста, попробуйте еще раз.",
|
||
"LOADER": "Капитан думает",
|
||
"YOU": "Вы",
|
||
"USE": "Использовать это",
|
||
"RESET": "Сброс",
|
||
"SHOW_STEPS": "Показать шаги",
|
||
"SELECT_ASSISTANT": "Выбрать ассистента",
|
||
"PROMPTS": {
|
||
"SUMMARIZE": {
|
||
"LABEL": "Подвести итог этого диалога",
|
||
"CONTENT": "Кратко изложить основные моменты, обсуждавшиеся между клиентом и агентом поддержки, включая пожелания клиента, вопросы и решения или ответы, предоставляемые агентом поддержки"
|
||
},
|
||
"SUGGEST": {
|
||
"LABEL": "Предложить ответ",
|
||
"CONTENT": "Анализируйте запрос клиента и составляйте ответ, который эффективно учитывает его проблемы или вопросы. Убедитесь, что ответ является четким, кратким и содержит полезную информацию."
|
||
},
|
||
"RATE": {
|
||
"LABEL": "Оцените этот диалог",
|
||
"CONTENT": "Оцените разговор, чтобы узнать, насколько он соответствует потребностям клиента. Поделитесь оценкой из 5 на основе тона, ясности и эффективности."
|
||
},
|
||
"HIGH_PRIORITY": {
|
||
"LABEL": "Диалоги с высоким приоритетом",
|
||
"CONTENT": "Дайте мне суть всех высокоприоритетных открытых разговоров, включая идентификатор разговора, имя клиента (если есть), содержимое последнего сообщения и назначенный агент. Если нужно, группа по статусу."
|
||
},
|
||
"LIST_CONTACTS": {
|
||
"LABEL": "Список контактов",
|
||
"CONTENT": "Покажите мне список 10 топ контактов. Включая имя, email или номер телефона (если доступно), последний просмотренный время, тэги (если есть)."
|
||
}
|
||
}
|
||
},
|
||
"PLAYGROUND": {
|
||
"USER": "Вы",
|
||
"ASSISTANT": "Ассистент",
|
||
"MESSAGE_PLACEHOLDER": "Введите сообщение...",
|
||
"HEADER": "Площадка",
|
||
"DESCRIPTION": "Используйте эту площадку, чтобы отправлять сообщения своему ассистенту и проверять правильность ответа, быстро и в том тоне, который вы ожидали.",
|
||
"CREDIT_NOTE": "Отправленные здесь сообщения будут учитываться в кредитах Captain."
|
||
},
|
||
"PAYWALL": {
|
||
"TITLE": "Обновите тарифный план, чтобы использовать Captain AI",
|
||
"AVAILABLE_ON": "Капитан недоступен на бесплатном тарифном плане.",
|
||
"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": "У вас нет ни одного доступного помощника.",
|
||
"ADD_NEW": "Создать нового ассистента",
|
||
"DELETE": {
|
||
"TITLE": "Вы уверены, что хотите удалить ассистента?",
|
||
"DESCRIPTION": "Это действие необратимо. Удаление этого ассистента удалит его из всех подключенных источников и навсегда удалит все сгенерированные знания.",
|
||
"CONFIRM": "Да, удалить",
|
||
"SUCCESS_MESSAGE": "Ассистент успешно удален",
|
||
"ERROR_MESSAGE": "При удалении ассистента произошла ошибка. Пожалуйста, попробуйте еще раз."
|
||
},
|
||
"FORM_DESCRIPTION": "Заполните приведенные ниже сведения, чтобы назвать своего ассистента, описать его цель и указать поддерживаемый продукт.",
|
||
"CREATE": {
|
||
"TITLE": "Создать ассистента",
|
||
"SUCCESS_MESSAGE": "Ассистент успешно создан",
|
||
"ERROR_MESSAGE": "При создании ассистента произошла ошибка, пожалуйста, попробуйте еще раз."
|
||
},
|
||
"FORM": {
|
||
"UPDATE": "Обновить",
|
||
"SECTIONS": {
|
||
"BASIC_INFO": "Основная информация",
|
||
"SYSTEM_MESSAGES": "Системные сообщения",
|
||
"INSTRUCTIONS": "Инструкции",
|
||
"FEATURES": "Возможности",
|
||
"TOOLS": "Инструменты "
|
||
},
|
||
"NAME": {
|
||
"LABEL": "Имя",
|
||
"PLACEHOLDER": "Введите имя помощника",
|
||
"ERROR": "Имя обязательно"
|
||
},
|
||
"TEMPERATURE": {
|
||
"LABEL": "Температура ответа",
|
||
"DESCRIPTION": "Настройте творческие или ограничительные реакции помощника. Меньшие ценности дают более сфокусированные и детерминированные отклики, а более высокие ценности позволяют более творчески и разнообразно вырабатывать результаты."
|
||
},
|
||
"DESCRIPTION": {
|
||
"LABEL": "Описание",
|
||
"PLACEHOLDER": "Введите описание помощника",
|
||
"ERROR": "Описание обязательно"
|
||
},
|
||
"PRODUCT_NAME": {
|
||
"LABEL": "Название продукта",
|
||
"PLACEHOLDER": "Введите название продукта",
|
||
"ERROR": "Требуется название продукта"
|
||
},
|
||
"WELCOME_MESSAGE": {
|
||
"LABEL": "Приветственное сообщение",
|
||
"PLACEHOLDER": "Введите приветственное сообщение"
|
||
},
|
||
"HANDOFF_MESSAGE": {
|
||
"LABEL": "Сообщение о передачи",
|
||
"PLACEHOLDER": "Введите сообщение о передачи"
|
||
},
|
||
"RESOLUTION_MESSAGE": {
|
||
"LABEL": "Сообщение разрешения",
|
||
"PLACEHOLDER": "Введите сообщение разрешения"
|
||
},
|
||
"INSTRUCTIONS": {
|
||
"LABEL": "Инструкции",
|
||
"PLACEHOLDER": "Введите инструкции для помощника"
|
||
},
|
||
"FEATURES": {
|
||
"TITLE": "Возможности",
|
||
"ALLOW_CONVERSATION_FAQS": "Создать FAQ из решённых диалогов",
|
||
"ALLOW_MEMORIES": "Сохраняйте ключевые детали в виде воспоминаний о взаимодействии с клиентами.",
|
||
"ALLOW_CITATIONS": "Включить цитаты источника в ответы"
|
||
}
|
||
},
|
||
"EDIT": {
|
||
"TITLE": "Обновить ассистента",
|
||
"SUCCESS_MESSAGE": "Ассистент успешно обновлен",
|
||
"ERROR_MESSAGE": "При обновлении ассистента произошла ошибка, пожалуйста, попробуйте еще раз.",
|
||
"NOT_FOUND": "Не удалось найти помощника. Пожалуйста, попробуйте еще раз."
|
||
},
|
||
"SETTINGS": {
|
||
"HEADER": "Настройки",
|
||
"BASIC_SETTINGS": {
|
||
"TITLE": "Основные настройки",
|
||
"DESCRIPTION": "Настройте то, что говорит ассистент, завершая диалог или передавая человеку."
|
||
},
|
||
"SYSTEM_SETTINGS": {
|
||
"TITLE": "Системные настройки",
|
||
"DESCRIPTION": "Настройте то, что говорит ассистент, завершая диалог или передавая человеку."
|
||
},
|
||
"CONTROL_ITEMS": {
|
||
"TITLE": "Веселые вещи",
|
||
"DESCRIPTION": "Добавить больше контроля к ассистенту. (немного визуально, как история : Query guardrail → Сценарии → Выход) пользователь Nudges на самом деле их использует.",
|
||
"OPTIONS": {
|
||
"GUARDRAILS": {
|
||
"TITLE": "Ограждения",
|
||
"DESCRIPTION": "Сохраняет вещи в нужном контексте — только те вопросы, которые вы хотите, чтобы ваш ассистент отвечал, ничего запрещённого или не по теме."
|
||
},
|
||
"RESPONSE_GUIDELINES": {
|
||
"TITLE": "Рекомендации по ответу",
|
||
"DESCRIPTION": "Вайб и структура ответов помощника – ясные и дружелюбные? Коротко и непросто? Детально и формально?"
|
||
}
|
||
}
|
||
},
|
||
"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": "Ограждения",
|
||
"DESCRIPTION": "Сохраняет вещи в нужном контексте — только те вопросы, которые вы хотите, чтобы ваш ассистент отвечал, ничего запрещённого или не по теме.",
|
||
"BULK_ACTION": {
|
||
"SELECTED": "{count} элемент выбран | {count} элементов выбрано",
|
||
"SELECT_ALL": "Выбрать все ({count})",
|
||
"UNSELECT_ALL": "Сбросить все ({count})",
|
||
"BULK_DELETE_BUTTON": "Удалить"
|
||
},
|
||
"ADD": {
|
||
"SUGGESTED": {
|
||
"TITLE": "Примеры ограждений",
|
||
"ADD": "Добавить все",
|
||
"ADD_SINGLE": "Добавить это",
|
||
"SAVE": "Добавить и сохранить (↵)",
|
||
"PLACEHOLDER": "Введите другое ограждение..."
|
||
},
|
||
"NEW": {
|
||
"TITLE": "Добавить гарант",
|
||
"CREATE": "Создать",
|
||
"CANCEL": "Отменить",
|
||
"PLACEHOLDER": "Введите другое ограждение...",
|
||
"TEST_ALL": "Проверить все"
|
||
}
|
||
},
|
||
"LIST": {
|
||
"SEARCH_PLACEHOLDER": "Поиск..."
|
||
},
|
||
"EMPTY_MESSAGE": "Ограждений не найдено. Создайте или добавьте примеры, чтобы начать.",
|
||
"SEARCH_EMPTY_MESSAGE": "Не найдено ограждений для этого поиска.",
|
||
"API": {
|
||
"ADD": {
|
||
"SUCCESS": "Ограждение успешно добавлен",
|
||
"ERROR": "Произошла ошибка при добавлении ограждения, пожалуйста, попробуйте еще раз."
|
||
},
|
||
"UPDATE": {
|
||
"SUCCESS": "Ограждение успешно обновлено",
|
||
"ERROR": "Произошла ошибка при обновлении ограждения, попробуйте еще раз."
|
||
},
|
||
"DELETE": {
|
||
"SUCCESS": "Ограждение успешно удалено",
|
||
"ERROR": "Произошла ошибка при удалении ограждения, пожалуйста, попробуйте еще раз."
|
||
}
|
||
}
|
||
},
|
||
"RESPONSE_GUIDELINES": {
|
||
"TITLE": "Руководство по ограждению",
|
||
"DESCRIPTION": "Вайб и структура ответов помощника – ясные и дружелюбные? Коротко и непросто? Детально и формально?",
|
||
"BULK_ACTION": {
|
||
"SELECTED": "{count} элемент выбран | {count} элементов выбрано",
|
||
"SELECT_ALL": "Выбрать все ({count})",
|
||
"UNSELECT_ALL": "Сбросить все ({count})",
|
||
"BULK_DELETE_BUTTON": "Удалить"
|
||
},
|
||
"ADD": {
|
||
"SUGGESTED": {
|
||
"TITLE": "Пример рекомендации по ответам",
|
||
"ADD": "Добавить все",
|
||
"ADD_SINGLE": "Добавить это",
|
||
"SAVE": "Добавить и сохранить (↵)",
|
||
"PLACEHOLDER": "Введите рекомендации по ответам..."
|
||
},
|
||
"NEW": {
|
||
"TITLE": "Добавить руководство по ответу",
|
||
"CREATE": "Создать",
|
||
"CANCEL": "Отменить",
|
||
"PLACEHOLDER": "Введите рекомендации по ответам...",
|
||
"TEST_ALL": "Проверить все"
|
||
}
|
||
},
|
||
"LIST": {
|
||
"SEARCH_PLACEHOLDER": "Поиск..."
|
||
},
|
||
"EMPTY_MESSAGE": "Руководство по ответу не найдено. Создайте или добавьте примеры, чтобы начать.",
|
||
"SEARCH_EMPTY_MESSAGE": "По данному поиску не найдено ни одного руководства.",
|
||
"API": {
|
||
"ADD": {
|
||
"SUCCESS": "Руководство по ответу успешно добавлено",
|
||
"ERROR": "Произошла ошибка при добавлении правил ответа, пожалуйста, попробуйте еще раз."
|
||
},
|
||
"UPDATE": {
|
||
"SUCCESS": "Руководства по ответу успешно обновлены",
|
||
"ERROR": "Произошла ошибка при обновлении руководства для ответа, пожалуйста, попробуйте еще раз."
|
||
},
|
||
"DELETE": {
|
||
"SUCCESS": "Руководства для ответа успешно удалены",
|
||
"ERROR": "Произошла ошибка при удалении руководства для ответа, пожалуйста, попробуйте еще раз."
|
||
}
|
||
}
|
||
},
|
||
"SCENARIOS": {
|
||
"TITLE": "Сценарии",
|
||
"DESCRIPTION": "Дайте своему ассистенту определенный контекст, например «что делать, когда пользователь застрял» или «как действовать во время запроса на возмещение».",
|
||
"BULK_ACTION": {
|
||
"SELECTED": "{count} элемент выбран | {count} элементов выбрано",
|
||
"SELECT_ALL": "Выбрать все ({count})",
|
||
"UNSELECT_ALL": "Сбросить все ({count})",
|
||
"BULK_DELETE_BUTTON": "Удалить"
|
||
},
|
||
"ADD": {
|
||
"SUGGESTED": {
|
||
"TITLE": "Примеры сценариев",
|
||
"ADD": "Добавить все",
|
||
"ADD_SINGLE": "Добавить это",
|
||
"TOOLS_USED": "Используемые инструменты:"
|
||
},
|
||
"NEW": {
|
||
"CREATE": "Добавить сценарий",
|
||
"TITLE": "Создать сценарий",
|
||
"FORM": {
|
||
"TITLE": {
|
||
"LABEL": "Название",
|
||
"PLACEHOLDER": "Введите название сценария",
|
||
"ERROR": "Название сценария обязательно"
|
||
},
|
||
"DESCRIPTION": {
|
||
"LABEL": "Описание",
|
||
"PLACEHOLDER": "Опишите как и где будет использоваться этот сценарий",
|
||
"ERROR": "Описание сценария обязательно"
|
||
},
|
||
"INSTRUCTION": {
|
||
"LABEL": "Как обрабатывать",
|
||
"PLACEHOLDER": "Опишите, как и где будет обрабатываться этот сценарий",
|
||
"ERROR": "Содержимое сценария обязательно"
|
||
},
|
||
"CREATE": "Создать",
|
||
"CANCEL": "Отменить"
|
||
}
|
||
}
|
||
},
|
||
"UPDATE": {
|
||
"CANCEL": "Отменить",
|
||
"UPDATE": "Обновить изменения"
|
||
},
|
||
"LIST": {
|
||
"SEARCH_PLACEHOLDER": "Поиск..."
|
||
},
|
||
"EMPTY_MESSAGE": "Сценарии не найдены. Создайте или добавьте примеры для начала.",
|
||
"SEARCH_EMPTY_MESSAGE": "Не найдено сценариев для этого поиска.",
|
||
"API": {
|
||
"ADD": {
|
||
"SUCCESS": "Сценарии успешно добавлены",
|
||
"ERROR": "Произошла ошибка при добавлении сценариев, пожалуйста, попробуйте еще раз."
|
||
},
|
||
"UPDATE": {
|
||
"SUCCESS": "Сценарий успешно обновлены",
|
||
"ERROR": "Произошла ошибка при обновлении сценария, пожалуйста, попробуйте еще раз."
|
||
},
|
||
"DELETE": {
|
||
"SUCCESS": "Сценарий успешно удалены",
|
||
"ERROR": "При удалении сценария произошла ошибка. Пожалуйста, попробуйте еще раз."
|
||
}
|
||
}
|
||
}
|
||
},
|
||
"DOCUMENTS": {
|
||
"HEADER": "Документы",
|
||
"ADD_NEW": "Создать новый документ",
|
||
"RELATED_RESPONSES": {
|
||
"TITLE": "Связанные FAQ",
|
||
"DESCRIPTION": "Эти FAQ генерируются напрямую из документа."
|
||
},
|
||
"FORM_DESCRIPTION": "Введите URL документа, чтобы добавить его в качестве источника знаний и выберите ассистента, с которым он свяжется.",
|
||
"CREATE": {
|
||
"TITLE": "Добавить документ",
|
||
"SUCCESS_MESSAGE": "Документ успешно создан",
|
||
"ERROR_MESSAGE": "Произошла ошибка при создании документа, пожалуйста, попробуйте еще раз."
|
||
},
|
||
"FORM": {
|
||
"TYPE": {
|
||
"LABEL": "Тип документа",
|
||
"URL": "URL",
|
||
"PDF": "PDF файл"
|
||
},
|
||
"URL": {
|
||
"LABEL": "URL",
|
||
"PLACEHOLDER": "Введите URL документа",
|
||
"ERROR": "Пожалуйста, укажите корректный URL для документа"
|
||
},
|
||
"PDF_FILE": {
|
||
"LABEL": "PDF файл",
|
||
"CHOOSE_FILE": "Выберите PDF файл",
|
||
"ERROR": "Пожалуйста, выберите PDF файл",
|
||
"HELP_TEXT": "Максимальный размер файла: 10MB",
|
||
"INVALID_TYPE": "Пожалуйста, выберите корректный файл PDF",
|
||
"TOO_LARGE": "Размер файла превышает 10MB"
|
||
},
|
||
"NAME": {
|
||
"LABEL": "Название документа (необязательно)",
|
||
"PLACEHOLDER": "Введите название документа"
|
||
}
|
||
},
|
||
"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": "Инструменты",
|
||
"ADD_NEW": "Создать новый инструмент",
|
||
"EMPTY_STATE": {
|
||
"TITLE": "Нет доступных пользовательских инструментов",
|
||
"SUBTITLE": "Создавайте пользовательские инструменты, чтобы подключить ассистента к внешним API и сервисам, позволяя получать данные и выполнять действия от вашего имени.",
|
||
"FEATURE_SPOTLIGHT": {
|
||
"TITLE": "Пользовательские инструменты",
|
||
"NOTE": "Пользовательские инструменты позволяют ассистенту взаимодействовать с внешними API и сервисами. Создавайте инструменты для получения данных, выполнения действий или интеграции с существующими системами для расширения возможностей вашего помощника."
|
||
}
|
||
},
|
||
"FORM_DESCRIPTION": "Настройте пользовательский инструмент для соединения с внешними API",
|
||
"OPTIONS": {
|
||
"EDIT_TOOL": "Редактировать инструмент",
|
||
"DELETE_TOOL": "Удалить инструмент"
|
||
},
|
||
"CREATE": {
|
||
"TITLE": "Создать пользовательский инструмент",
|
||
"SUCCESS_MESSAGE": "Пользовательский инструмент успешно создан",
|
||
"ERROR_MESSAGE": "Не удалось создать пользовательский инструмент"
|
||
},
|
||
"EDIT": {
|
||
"TITLE": "Редактировать пользовательский инструмент",
|
||
"SUCCESS_MESSAGE": "Пользовательский инструмент успешно обновлен",
|
||
"ERROR_MESSAGE": "Не удалось обновить пользовательский инструмент"
|
||
},
|
||
"DELETE": {
|
||
"TITLE": "Удаление пользовательского инструмента",
|
||
"DESCRIPTION": "Вы уверены, что хотите удалить этот пользовательский инструмент? Это действие нельзя отменить.",
|
||
"CONFIRM": "Да, удалить",
|
||
"SUCCESS_MESSAGE": "Пользовательский инструмент успешно удален",
|
||
"ERROR_MESSAGE": "Не удалось удалить пользовательский инструмент"
|
||
},
|
||
"FORM": {
|
||
"TITLE": {
|
||
"LABEL": "Название инструмента",
|
||
"PLACEHOLDER": "Поиск заказа",
|
||
"ERROR": "Название инструмента обязательно"
|
||
},
|
||
"DESCRIPTION": {
|
||
"LABEL": "Описание",
|
||
"PLACEHOLDER": "Поиск деталей заказа по ID"
|
||
},
|
||
"HTTP_METHOD": {
|
||
"LABEL": "Метод"
|
||
},
|
||
"ENDPOINT_URL": {
|
||
"LABEL": "Endpoint URL",
|
||
"PLACEHOLDER": "https://api.example.com/orders/{'{{'} order_id {'}}'}",
|
||
"ERROR": "Требуется корректный URL"
|
||
},
|
||
"AUTH_TYPE": {
|
||
"LABEL": "Тип аутентификации"
|
||
},
|
||
"AUTH_TYPES": {
|
||
"NONE": "Ничего",
|
||
"BEARER": "Bearer Token",
|
||
"BASIC": "Basic Auth",
|
||
"API_KEY": "Ключ API"
|
||
},
|
||
"AUTH_CONFIG": {
|
||
"BEARER_TOKEN": "Bearer Token",
|
||
"BEARER_TOKEN_PLACEHOLDER": "Введите ваш bearer token",
|
||
"USERNAME": "Имя пользователя",
|
||
"USERNAME_PLACEHOLDER": "Введите имя пользователя",
|
||
"PASSWORD": "Пароль",
|
||
"PASSWORD_PLACEHOLDER": "Введите пароль",
|
||
"API_KEY": "Имя заголовка",
|
||
"API_KEY_PLACEHOLDER": "X-API-Key",
|
||
"API_VALUE": "Значение заголовка",
|
||
"API_VALUE_PLACEHOLDER": "Введите значения API key"
|
||
},
|
||
"PARAMETERS": {
|
||
"LABEL": "Параметры",
|
||
"HELP_TEXT": "Определите параметры, которые будут извлечены из запросов пользователей"
|
||
},
|
||
"ADD_PARAMETER": "Добавить параметр",
|
||
"PARAM_NAME": {
|
||
"PLACEHOLDER": "Имя параметра (например, order_id)"
|
||
},
|
||
"PARAM_TYPE": {
|
||
"PLACEHOLDER": "Тип"
|
||
},
|
||
"PARAM_TYPES": {
|
||
"STRING": "Строка",
|
||
"NUMBER": "Число",
|
||
"BOOLEAN": "Boolean",
|
||
"ARRAY": "Массив",
|
||
"OBJECT": "Объект"
|
||
},
|
||
"PARAM_DESCRIPTION": {
|
||
"PLACEHOLDER": "Описание параметра"
|
||
},
|
||
"PARAM_REQUIRED": {
|
||
"LABEL": "Обязательно"
|
||
},
|
||
"REQUEST_TEMPLATE": {
|
||
"LABEL": "Шаблон тела запроса (необязательно)",
|
||
"PLACEHOLDER": "{'{'}\n \"order_id\": \"{'{{'} order_id {'}}'}\"\n{'}'}"
|
||
},
|
||
"RESPONSE_TEMPLATE": {
|
||
"LABEL": "Шаблон ответа (необязательно)",
|
||
"PLACEHOLDER": "Заказ {'{{'} order_id {'}}'} status: {'{{'} status {'}}'}"
|
||
},
|
||
"ERRORS": {
|
||
"PARAM_NAME_REQUIRED": "Имя параметра обязательно"
|
||
}
|
||
}
|
||
},
|
||
"RESPONSES": {
|
||
"HEADER": "FAQ",
|
||
"PENDING_FAQS": "Pending FAQs",
|
||
"ADD_NEW": "Создать новый FAQ",
|
||
"DOCUMENTABLE": {
|
||
"CONVERSATION": "Диалог #{id}"
|
||
},
|
||
"SELECTED": "Выбрано {count}",
|
||
"SELECT_ALL": "Выбрать все ({count})",
|
||
"UNSELECT_ALL": "Сбросить все ({count})",
|
||
"SEARCH_PLACEHOLDER": "Поиск по FAQ...",
|
||
"BULK_APPROVE_BUTTON": "Одобрить",
|
||
"BULK_DELETE_BUTTON": "Удалить",
|
||
"BULK_APPROVE": {
|
||
"SUCCESS_MESSAGE": "FAQ успешно одобрены",
|
||
"ERROR_MESSAGE": "Произошла ошибка при одобрении FAQ, пожалуйста, попробуйте ещё раз."
|
||
},
|
||
"BULK_DELETE": {
|
||
"TITLE": "Удалить FAQ?",
|
||
"DESCRIPTION": "Вы уверены, что хотите удалить выбранные FAQ? Это действие невозможно отменить.",
|
||
"CONFIRM": "Да, удалить всё",
|
||
"SUCCESS_MESSAGE": "FAQ успешно удалены",
|
||
"ERROR_MESSAGE": "Произошла ошибка при удалении FAQ, пожалуйста, попробуйте ещё раз."
|
||
},
|
||
"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": "Одобрить",
|
||
"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": "Подключение источника входящих позволяет ассистенту обрабатывать первые вопросы ваших клиентов до их передачи вам."
|
||
}
|
||
}
|
||
}
|
||
}
|