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>
990 lines
45 KiB
JSON
990 lines
45 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": "Cancelar",
|
|
"SUBMIT": "Connect Store"
|
|
},
|
|
"ERROR": "There was an error connecting to Shopify. Please try again or contact support if the issue persists."
|
|
},
|
|
"HEADER": "Integrações",
|
|
"DESCRIPTION": "Chatwoot se integra com várias ferramentas e serviços para melhorar a eficiência de seu time. Explore a lista abaixo para configurar seus aplicativos favoritos.",
|
|
"LEARN_MORE": "Aprenda mais sobre integrações",
|
|
"LOADING": "Obtendo integrações",
|
|
"CAPTAIN": {
|
|
"DISABLED": "O capitão não está ativado na sua conta.",
|
|
"CLICK_HERE_TO_CONFIGURE": "Clique aqui para configurar",
|
|
"LOADING_CONSOLE": "Carregando console do Capitão...",
|
|
"FAILED_TO_LOAD_CONSOLE": "Falha ao carregar o Console do Capitão. Atualize e tente novamente."
|
|
},
|
|
"WEBHOOK": {
|
|
"SUBSCRIBED_EVENTS": "Eventos Inscritos",
|
|
"LEARN_MORE": "Saiba mais sobre webhooks",
|
|
"FORM": {
|
|
"CANCEL": "Cancelar",
|
|
"DESC": "Webhook Os eventos fornecem informações em tempo real sobre o que está acontecendo na sua conta do Chatwoot. Digite um URL válido para configurar um retorno de chamada.",
|
|
"SUBSCRIPTIONS": {
|
|
"LABEL": "Eventos",
|
|
"EVENTS": {
|
|
"CONVERSATION_CREATED": "Conversa Criada",
|
|
"CONVERSATION_STATUS_CHANGED": "Status de conversa alterado",
|
|
"CONVERSATION_UPDATED": "Conversa Atualizada",
|
|
"MESSAGE_CREATED": "Mensagem criada",
|
|
"MESSAGE_UPDATED": "Mensagem atualizada",
|
|
"WEBWIDGET_TRIGGERED": "Widget de chat aberto pelo usuário",
|
|
"CONTACT_CREATED": "Contato criado",
|
|
"CONTACT_UPDATED": "Contato atualizado",
|
|
"CONVERSATION_TYPING_ON": "Status de Digitação ativado",
|
|
"CONVERSATION_TYPING_OFF": "Status de Digitação desativado",
|
|
"PROVIDER_EVENT_RECEIVED": "Evento do Provedor Recebido"
|
|
}
|
|
},
|
|
"NAME": {
|
|
"LABEL": "Nome do Webhook",
|
|
"PLACEHOLDER": "Insira o nome do webhook"
|
|
},
|
|
"INBOX": {
|
|
"LABEL": "Caixa de Entrada",
|
|
"TITLE": "Selecione a caixa de entrada",
|
|
"PLACEHOLDER": "Todas as caixas de entrada",
|
|
"NO_RESULTS": "Nenhuma caixa de entrada encontrada",
|
|
"INPUT_PLACEHOLDER": "Buscar caixa de entrada"
|
|
},
|
|
"END_POINT": {
|
|
"LABEL": "URL do Webhook",
|
|
"PLACEHOLDER": "Exemplo: {webhookExampleURL}",
|
|
"ERROR": "Por favor, insira uma URL válida"
|
|
},
|
|
"EDIT_SUBMIT": "Atualizar webhook",
|
|
"ADD_SUBMIT": "Criar webhook"
|
|
},
|
|
"TITLE": "Webhook",
|
|
"CONFIGURE": "Configurar",
|
|
"HEADER": "Configurações do Webhook",
|
|
"HEADER_BTN_TXT": "Adicionar novo Webhook",
|
|
"LOADING": "Buscando Webhooks anexados",
|
|
"SEARCH_404": "Não existem itens correspondentes a esta consulta",
|
|
"SIDEBAR_TXT": "<p><b>Webhooks</b> </p> <p>Webhooks são retornos de chamada HTTP que podem ser definidos para todas as contas. Eles são acionados por eventos como a criação de mensagens no Chatwoot. Você pode criar mais de um webhook para esta conta. <br /> <br /> Para criar um <b> webhook </b>, clique no botão <b> Adicionar novo webhook </b>. Você também pode remover qualquer webhook existente clicando no botão Excluir.</p>",
|
|
"LIST": {
|
|
"404": "Não há webhooks configurados para esta conta.",
|
|
"TITLE": "Gerenciar webhooks",
|
|
"TABLE_HEADER": {
|
|
"WEBHOOK_ENDPOINT": "Webhook URL (endpoint)",
|
|
"ACTIONS": "Ações"
|
|
}
|
|
},
|
|
"EDIT": {
|
|
"BUTTON_TEXT": "Alterar",
|
|
"TITLE": "Editar webhook",
|
|
"API": {
|
|
"SUCCESS_MESSAGE": "Configuração de Webhook atualizada com sucesso",
|
|
"ERROR_MESSAGE": "Não foi possível conectar ao servidor Woot, por favor tente novamente mais tarde"
|
|
}
|
|
},
|
|
"ADD": {
|
|
"CANCEL": "Cancelar",
|
|
"TITLE": "Adicionar novo webhook",
|
|
"API": {
|
|
"SUCCESS_MESSAGE": "Configuração de Webhook adicionada com sucesso",
|
|
"ERROR_MESSAGE": "Não foi possível conectar ao servidor Woot, por favor tente novamente mais tarde"
|
|
}
|
|
},
|
|
"DELETE": {
|
|
"BUTTON_TEXT": "Excluir",
|
|
"API": {
|
|
"SUCCESS_MESSAGE": "Webhook excluído com sucesso",
|
|
"ERROR_MESSAGE": "Não foi possível conectar ao servidor Woot, por favor tente novamente mais tarde"
|
|
},
|
|
"CONFIRM": {
|
|
"TITLE": "Confirmar exclusão",
|
|
"MESSAGE": "Tem certeza que deseja excluir o webhook? ({webhookURL})",
|
|
"YES": "Sim, excluir ",
|
|
"NO": "Não, mantenha"
|
|
}
|
|
}
|
|
},
|
|
"SLACK": {
|
|
"DELETE": "Excluir",
|
|
"DELETE_CONFIRMATION": {
|
|
"TITLE": "Excluir integração",
|
|
"MESSAGE": "Tem certeza que deseja excluir a integração? Isso resultará na perda de acesso a conversas no seu espaço de trabalho Slack."
|
|
},
|
|
"HELP_TEXT": {
|
|
"TITLE": "Usando a integração com Slack",
|
|
"BODY": "Com essa integração, todas as suas conversas recebidas serão sincronizadas com o canal ***{selectedChannelName}*** em seu espaço de trabalho Slack. Você pode gerenciar todas as suas conversas com clientes diretamente no canal e nunca perder uma mensagem.\n\nAqui estão os principais recursos da integração:\n\n**Responda a conversas de dentro do Slack:** Para responder a uma conversa no canal ***{selectedChannelName}*** Slack, simplesmente digite a sua mensagem e envie-a como um tópico. Isso criará uma resposta ao cliente através do Chatwoot. É tão simples!\n\n **Crie notas privadas:** Se você quiser criar notas privadas em vez de respostas, inicie sua mensagem com ***`nota:`***. Isso garante que sua mensagem seja privada e não seja visível para o cliente.\n\n**Associar um perfil de agente:** Se a pessoa que respondeu no Slack tem um perfil de agente no Chatwoot sob o mesmo e-mail, as respostas serão associadas automaticamente com esse perfil de agente. Isso significa que você pode facilmente controlar quem disse o quê e quando. Por outro lado, quando o respondente não tiver um perfil de agente associado, as respostas aparecerão do perfil do bot para o cliente.",
|
|
"SELECTED": "selecionar"
|
|
},
|
|
"SELECT_CHANNEL": {
|
|
"OPTION_LABEL": "Selecione um canal",
|
|
"UPDATE": "Atualizar",
|
|
"BUTTON_TEXT": "Conectar canal",
|
|
"DESCRIPTION": "Seu espaço de trabalho Slack agora está ligado com o Chatwoot. No entanto, a integração está inativa no momento. Para ativar a integração e conectar um canal ao Chatwoot, por favor, clique no botão abaixo.\n\n**Nota:** Se você está tentando conectar-se a um canal privado, adicione o aplicativo Chatwoot no canal do Slack antes de prosseguir com esta etapa.",
|
|
"ATTENTION_REQUIRED": "Atenção necessária",
|
|
"EXPIRED": "Sua integração com o Slack expirou. Para continuar recebendo mensagens no Slack, exclua a integração e conecte seu espaço de trabalho novamente."
|
|
},
|
|
"UPDATE_ERROR": "Ocorreu um erro ao atualizar a integração, por favor, tente novamente",
|
|
"UPDATE_SUCCESS": "O canal foi conectado com sucesso",
|
|
"FAILED_TO_FETCH_CHANNELS": "Ocorreu um erro ao obter os canais do Slack, por favor, tente novamente"
|
|
},
|
|
"DYTE": {
|
|
"CLICK_HERE_TO_JOIN": "Clique aqui para entrar",
|
|
"LEAVE_THE_ROOM": "Sair da sala",
|
|
"START_VIDEO_CALL_HELP_TEXT": "Iniciar uma nova chamada de vídeo com o cliente",
|
|
"JOIN_ERROR": "Houve um erro ao entrar na chamada, por favor tente novamente",
|
|
"CREATE_ERROR": "Houve um erro ao criar o link da reunião, por favor tente novamente"
|
|
},
|
|
"OPEN_AI": {
|
|
"AI_ASSIST": "Inteligência Artificial",
|
|
"WITH_AI": " {option} com IA ",
|
|
"OPTIONS": {
|
|
"REPLY_SUGGESTION": "Sugestão de resposta",
|
|
"SUMMARIZE": "Resumir",
|
|
"REPHRASE": "Melhorar Escrita",
|
|
"FIX_SPELLING_GRAMMAR": "Corrigir Ortografia e Gramática",
|
|
"SHORTEN": "Encurtar",
|
|
"EXPAND": "Expandir",
|
|
"MAKE_FRIENDLY": "Alterar o tom de mensagem para amigável",
|
|
"MAKE_FORMAL": "Usar tom formal",
|
|
"SIMPLIFY": "Simplificar"
|
|
},
|
|
"ASSISTANCE_MODAL": {
|
|
"DRAFT_TITLE": "Conteúdo do rascunho",
|
|
"GENERATED_TITLE": "Conteúdo gerado",
|
|
"AI_WRITING": "A Inteligência Artificial está escrevendo",
|
|
"BUTTONS": {
|
|
"APPLY": "Use esta sugestão",
|
|
"CANCEL": "Cancelar"
|
|
}
|
|
},
|
|
"CTA_MODAL": {
|
|
"TITLE": "Integração com o OpenAI",
|
|
"DESC": "Traga funcionalidades avançadas de IA para o seu painel com os modelos GPT da OpenAI. Para começar, insira a chave API da sua conta OpenAI.",
|
|
"KEY_PLACEHOLDER": "Insira sua chave de API da OpenAI",
|
|
"BUTTONS": {
|
|
"NEED_HELP": "Precisa de ajuda?",
|
|
"DISMISS": "Recusar",
|
|
"FINISH": "Concluir Configuração"
|
|
},
|
|
"DISMISS_MESSAGE": "Você pode configurar a integração com o OpenAI mais tarde.",
|
|
"SUCCESS_MESSAGE": "Integração com o OpenAI configurada com sucesso"
|
|
},
|
|
"TITLE": "Melhorar com IA",
|
|
"SUMMARY_TITLE": "Resumir com IA",
|
|
"REPLY_TITLE": "Responder sugestão com IA",
|
|
"SUBTITLE": "Uma resposta melhor será gerada usando IA, com base no seu rascunho atual.",
|
|
"TONE": {
|
|
"TITLE": "Tom",
|
|
"OPTIONS": {
|
|
"PROFESSIONAL": "Profissional",
|
|
"FRIENDLY": "Amigável"
|
|
}
|
|
},
|
|
"BUTTONS": {
|
|
"GENERATE": "Gerar",
|
|
"GENERATING": "Gerando...",
|
|
"CANCEL": "Cancelar"
|
|
},
|
|
"GENERATE_ERROR": "Ocorreu um erro ao processar o conteúdo, por favor, tente novamente"
|
|
},
|
|
"DELETE": {
|
|
"BUTTON_TEXT": "Excluir",
|
|
"API": {
|
|
"SUCCESS_MESSAGE": "Integração excluída com sucesso"
|
|
}
|
|
},
|
|
"CONNECT": {
|
|
"BUTTON_TEXT": "Conectar"
|
|
},
|
|
"DASHBOARD_APPS": {
|
|
"TITLE": "Painel de Aplicativos",
|
|
"HEADER_BTN_TXT": "Adicionar um novo aplicativo",
|
|
"SIDEBAR_TXT": "<p><b>Painel de Aplicativos</b></p><p>O Painel de Aplicativos permite que as organizações incorporem um aplicativo dentro do Painel de Aplicativos do Chatwoot para fornecer o contexto para agentes de suporte ao cliente. Este recurso permite-lhe criar uma aplicação independente e incorporá-la dentro da dashboard para fornecer informações do usuário, seus pedidos ou seu histórico de pagamentos anteriores.</p><p>Quando você incorpora seu aplicativo usando o Painel de Aplicativos do Chatwoot, sua aplicação irá obter o contexto da conversa e entrar em contato como um evento de janela. Implementar um ouvinte para o evento de mensagem em sua página receber o contexto.</p><p>Para adicionar um novo aplicativo no Painel de Aplicativos, clique no botão 'Adicionar um novo aplicativo'.</p>",
|
|
"DESCRIPTION": "O Painel de Aplicativos permite que organizações incorporem um aplicativo dentro do painel para fornecer o contexto para agentes de suporte ao cliente. Este recurso permite que você crie uma aplicação independente e incorpore para fornecer informações de usuário, seus pedidos ou seu histórico de pagamentos anteriores.",
|
|
"LEARN_MORE": "Saiba mais sobre o Painel de Aplicativos",
|
|
"LIST": {
|
|
"404": "Ainda não há aplicativos nesta conta",
|
|
"LOADING": "Buscando aplicativos...",
|
|
"TABLE_HEADER": {
|
|
"NAME": "Nome",
|
|
"ENDPOINT": "Endpoint"
|
|
},
|
|
"EDIT_TOOLTIP": "Alterar aplicativo",
|
|
"DELETE_TOOLTIP": "Excluir aplicativo"
|
|
},
|
|
"VIEW": {
|
|
"NOT_FOUND": "Não encontramos este aplicativo do painel."
|
|
},
|
|
"FORM": {
|
|
"TITLE_LABEL": "Nome",
|
|
"TITLE_PLACEHOLDER": "Digite um nome para o aplicativo",
|
|
"TITLE_ERROR": "É necessário um nome para o aplicativo",
|
|
"URL_LABEL": "Endpoint",
|
|
"URL_PLACEHOLDER": "Digite a URL do endpoint onde seu aplicativo está hospedado",
|
|
"URL_ERROR": "É necessário uma URL válida",
|
|
"SHOW_ON_SIDEBAR_LABEL": "Mostrar na barra lateral"
|
|
},
|
|
"CREATE": {
|
|
"HEADER": "Adicionar um novo aplicativo",
|
|
"FORM_SUBMIT": "Enviar",
|
|
"FORM_CANCEL": "Cancelar",
|
|
"API_SUCCESS": "Aplicativo configurado com sucesso",
|
|
"API_ERROR": "Não conseguimos criar um aplicativo. Por favor, tente novamente mais tarde"
|
|
},
|
|
"UPDATE": {
|
|
"HEADER": "Alterar aplicativo",
|
|
"FORM_SUBMIT": "Atualizar",
|
|
"FORM_CANCEL": "Cancelar",
|
|
"API_SUCCESS": "Aplicativo atualizado com sucesso",
|
|
"API_ERROR": "Não conseguimos atualizar o aplicativo. Por favor, tente novamente mais tarde"
|
|
},
|
|
"DELETE": {
|
|
"CONFIRM_YES": "Sim, exclua-o",
|
|
"CONFIRM_NO": "Não, mantenha-o",
|
|
"TITLE": "Confirmar exclusão",
|
|
"MESSAGE": "Tem certeza que deseja excluir o aplicativo - {appName}?",
|
|
"API_SUCCESS": "Aplicativo excluído com sucesso",
|
|
"API_ERROR": "Não conseguimos excluir o aplicativo. Por favor, tente novamente mais tarde"
|
|
}
|
|
},
|
|
"LINEAR": {
|
|
"ADD_OR_LINK_BUTTON": "Criar/Ligar Issue Linear",
|
|
"LOADING": "Buscando problemas lineares...",
|
|
"LOADING_ERROR": "Houve um erro ao buscar as entidades do time, por favor, tente novamente",
|
|
"CREATE": "Criar",
|
|
"LINK": {
|
|
"SEARCH": "Pesquisar issues",
|
|
"SELECT": "Selecionar problema",
|
|
"TITLE": "Link",
|
|
"EMPTY_LIST": "Nenhum problema linear encontrado",
|
|
"LOADING": "Carregando",
|
|
"ERROR": "Houve um erro ao buscar as questões lineares, por favor, tente novamente",
|
|
"LINK_SUCCESS": "Questão vinculada com sucesso",
|
|
"LINK_ERROR": "Houve um erro ao vincular a questão, tente novamente mais tarde",
|
|
"LINK_TITLE": "Conversa (#{conversationId}) com {name}"
|
|
},
|
|
"ADD_OR_LINK": {
|
|
"TITLE": "Criar/ligar questão linear",
|
|
"DESCRIPTION": "Crie issues no Linear a partir de conversas, ou vincule às existentes para um rastreamento integrado.",
|
|
"FORM": {
|
|
"TITLE": {
|
|
"LABEL": "Título",
|
|
"PLACEHOLDER": "Insira o título",
|
|
"REQUIRED_ERROR": "Título é obrigatório"
|
|
},
|
|
"DESCRIPTION": {
|
|
"LABEL": "Descrição",
|
|
"PLACEHOLDER": "Insira a descrição"
|
|
},
|
|
"TEAM": {
|
|
"LABEL": "Times",
|
|
"PLACEHOLDER": "Selecionar time",
|
|
"SEARCH": "Pesquisar time",
|
|
"REQUIRED_ERROR": "O time é obrigatório"
|
|
},
|
|
"ASSIGNEE": {
|
|
"LABEL": "Responsável",
|
|
"PLACEHOLDER": "Selecione o atribuído",
|
|
"SEARCH": "Pesquisar atribuído"
|
|
},
|
|
"PRIORITY": {
|
|
"LABEL": "Prioridade",
|
|
"PLACEHOLDER": "Selecionar prioridade",
|
|
"SEARCH": "Pesquisar prioridade"
|
|
},
|
|
"LABEL": {
|
|
"LABEL": "Nome do campo",
|
|
"PLACEHOLDER": "Selecione a etiqueta",
|
|
"SEARCH": "Pesquisar etiqueta"
|
|
},
|
|
"STATUS": {
|
|
"LABEL": "Status",
|
|
"PLACEHOLDER": "Selecione Status",
|
|
"SEARCH": "Pesquisar status"
|
|
},
|
|
"PROJECT": {
|
|
"LABEL": "Projeto",
|
|
"PLACEHOLDER": "Selecionar projeto",
|
|
"SEARCH": "Pesquisar projeto"
|
|
}
|
|
},
|
|
"CREATE": "Criar",
|
|
"CANCEL": "Cancelar",
|
|
"CREATE_SUCCESS": "Pasta criada com sucesso",
|
|
"CREATE_ERROR": "Houve um erro ao criar a questão, por favor, tente novamente",
|
|
"LOADING_TEAM_ERROR": "Houve um erro ao buscar os times, por favor, tente novamente",
|
|
"LOADING_TEAM_ENTITIES_ERROR": "Houve um erro ao buscar as entidades do time, por favor, tente novamente"
|
|
},
|
|
"ISSUE": {
|
|
"STATUS": "Status",
|
|
"PRIORITY": "Prioridade",
|
|
"ASSIGNEE": "Responsável",
|
|
"LABELS": "Etiquetas",
|
|
"CREATED_AT": "Criado em {createdAt}"
|
|
},
|
|
"UNLINK": {
|
|
"TITLE": "Desvincular",
|
|
"SUCCESS": "Issue desvinculada com sucesso",
|
|
"ERROR": "Houve um erro ao desvincular o atributo, por favor, tente novamente"
|
|
},
|
|
"NO_LINKED_ISSUES": "Nenhuma tarefa vinculada foi encontrada",
|
|
"DELETE": {
|
|
"TITLE": "Tem certeza que deseja excluir esta integração?",
|
|
"MESSAGE": "Tem certeza que deseja excluir esta integração?",
|
|
"CONFIRM": "Sim, excluir",
|
|
"CANCEL": "Cancelar"
|
|
},
|
|
"CTA": {
|
|
"TITLE": "Conectar ao Linear",
|
|
"AGENT_DESCRIPTION": "O espaço de trabalho do Linear não está conectado. Solicite ao seu administrador para conectar um espaço de trabalho para usar essa integração.",
|
|
"DESCRIPTION": "O espaço de trabalho do Linear não está conectado. Clique no botão abaixo para conectar seu espaço de trabalho para usar essa integração.",
|
|
"BUTTON_TEXT": "Conectar espaço de trabalho do Linear"
|
|
}
|
|
},
|
|
"NOTION": {
|
|
"DELETE": {
|
|
"TITLE": "Você tem certeza que deseja excluir a integração com Notion?",
|
|
"MESSAGE": "Excluir essa integração removerá o acesso ao seu espaço de trabalho Notion e encerrará todas as funcionalidades relacionadas.",
|
|
"CONFIRM": "Sim, excluir",
|
|
"CANCEL": "Cancelar"
|
|
}
|
|
}
|
|
},
|
|
"CAPTAIN": {
|
|
"NAME": "Capitão",
|
|
"HEADER_KNOW_MORE": "Know more",
|
|
"ASSISTANT_SWITCHER": {
|
|
"ASSISTANTS": "Assistentes",
|
|
"SWITCH_ASSISTANT": "Switch between assistants",
|
|
"NEW_ASSISTANT": "Create Assistant",
|
|
"EMPTY_LIST": "No assistants found, please create one to get started"
|
|
},
|
|
"COPILOT": {
|
|
"TITLE": "Copiloto",
|
|
"TRY_THESE_PROMPTS": "Experimente estes comandos",
|
|
"PANEL_TITLE": "Comece a usar o Copiloto",
|
|
"KICK_OFF_MESSAGE": "Precisa de um resumo rápido, quer verificar conversas passadas ou redigir uma resposta melhor? O Copiloto está aqui para acelerar as coisas.",
|
|
"SEND_MESSAGE": "Enviar mensagem...",
|
|
"EMPTY_MESSAGE": "Houve um erro ao gerar a resposta. Por favor, tente novamente.",
|
|
"LOADER": "Capitão está pensando",
|
|
"YOU": "Você",
|
|
"USE": "Use isto",
|
|
"RESET": "Reiniciar",
|
|
"SHOW_STEPS": "Mostrar etapas",
|
|
"SELECT_ASSISTANT": "Selecione o Assistente",
|
|
"PROMPTS": {
|
|
"SUMMARIZE": {
|
|
"LABEL": "Resumir esta conversa",
|
|
"CONTENT": "Resuma os pontos-chave discutidos entre o cliente e o agente de suporte, incluindo as preocupações do cliente, as questões e as soluções ou respostas dadas pelo agente de suporte"
|
|
},
|
|
"SUGGEST": {
|
|
"LABEL": "Sugerir uma resposta",
|
|
"CONTENT": "Analise a pergunta do cliente e elabore uma resposta que responda efetivamente às suas preocupações ou perguntas. Certifique-se de que a resposta seja clara, concisa e forneça informações úteis."
|
|
},
|
|
"RATE": {
|
|
"LABEL": "Avaliar esta conversa",
|
|
"CONTENT": "Revise a conversa para ver o quanto ela atende às necessidades do cliente. Compartilhe uma classificação de 0 a 5 com base em tom, clareza e eficácia."
|
|
},
|
|
"HIGH_PRIORITY": {
|
|
"LABEL": "Conversas de alta prioridade",
|
|
"CONTENT": "Dê um resumo de todas as conversas abertas com prioridade alta. Incluir o ID da conversa, nome do cliente (se disponível), o conteúdo da última mensagem e o agente atribuído. O grupo por status, se relevante."
|
|
},
|
|
"LIST_CONTACTS": {
|
|
"LABEL": "Listar contatos",
|
|
"CONTENT": "Mostre-me a lista dos 10 contatos mais frequentes. Inclua nome, e-mail ou número de telefone (se disponível), visto por última vez, etiquetas (se houver)."
|
|
}
|
|
}
|
|
},
|
|
"PLAYGROUND": {
|
|
"USER": "Você",
|
|
"ASSISTANT": "Assistente",
|
|
"MESSAGE_PLACEHOLDER": "Digite sua mensagem...",
|
|
"HEADER": "Playground",
|
|
"DESCRIPTION": "Use este playground para enviar mensagens para seu assistente e verificar se ele responde com precisão, rápido e no tom que você espera.",
|
|
"CREDIT_NOTE": "As mensagens enviadas aqui usam os créditos do seu Capitão."
|
|
},
|
|
"PAYWALL": {
|
|
"TITLE": "Atualize para usar o Capitão IA",
|
|
"AVAILABLE_ON": "O Capitão não está disponível no plano gratuito.",
|
|
"UPGRADE_PROMPT": "Atualize seu plano para ter acesso aos nossos assistentes, copilotos e muito mais.",
|
|
"UPGRADE_NOW": "Atualizar agora",
|
|
"CANCEL_ANYTIME": "Você pode alterar ou cancelar seu plano a qualquer momento"
|
|
},
|
|
"ENTERPRISE_PAYWALL": {
|
|
"UPGRADE_PROMPT": "Atualize seu plano para ter acesso aos nossos assistentes, copilotos e muito mais.",
|
|
"ASK_ADMIN": "Entre em contato com seu administrador para fazer a atualização."
|
|
},
|
|
"BANNER": {
|
|
"RESPONSES": "Você usou mais de 80% do seu limite de respostas. Para continuar usando o Capitão AI, faça o upgrade.",
|
|
"DOCUMENTS": "Limite de documentos atingido. Atualize para continuar usando o Capitão AI."
|
|
},
|
|
"FORM": {
|
|
"CANCEL": "Cancelar",
|
|
"CREATE": "Criar",
|
|
"EDIT": "Atualizar"
|
|
},
|
|
"ASSISTANTS": {
|
|
"HEADER": "Assistentes",
|
|
"NO_ASSISTANTS_AVAILABLE": "Não há assistentes disponíveis em sua conta.",
|
|
"ADD_NEW": "Criar um novo assistente",
|
|
"DELETE": {
|
|
"TITLE": "Tem certeza que deseja excluir o assistente?",
|
|
"DESCRIPTION": "Esta ação é permanente. Excluir este assistente irá removê-lo de todas as caixas de entrada conectadas e apagará permanentemente todo o conhecimento gerado.",
|
|
"CONFIRM": "Sim, excluir",
|
|
"SUCCESS_MESSAGE": "O assistente foi excluído com sucesso",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao excluir o assistente, por favor tente novamente."
|
|
},
|
|
"FORM_DESCRIPTION": "Preencha os detalhes abaixo para nomear seu assistente, descrever sua finalidade e especificar o produto que ele oferecerá suporte.",
|
|
"CREATE": {
|
|
"TITLE": "Criar um assistente",
|
|
"SUCCESS_MESSAGE": "O assistente foi criado com sucesso",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao criar o assistente, por favor tente novamente."
|
|
},
|
|
"FORM": {
|
|
"UPDATE": "Atualizar",
|
|
"SECTIONS": {
|
|
"BASIC_INFO": "Informações Básicas",
|
|
"SYSTEM_MESSAGES": "Mensagens do Sistema",
|
|
"INSTRUCTIONS": "Instruções",
|
|
"FEATURES": "Funcionalidades",
|
|
"TOOLS": "Ferramentas "
|
|
},
|
|
"NAME": {
|
|
"LABEL": "Nome",
|
|
"PLACEHOLDER": "Digite o nome do assistente",
|
|
"ERROR": "O nome é obrigatório"
|
|
},
|
|
"TEMPERATURE": {
|
|
"LABEL": "Temperatura da resposta",
|
|
"DESCRIPTION": "Ajuste o quão criativo ou restritivo as respostas do assistente devem ser. Valores mais baixos produzem respostas mais focadas e deterministas, enquanto valores mais altos permitem resultados mais criativos e variados."
|
|
},
|
|
"DESCRIPTION": {
|
|
"LABEL": "Descrição",
|
|
"PLACEHOLDER": "Digite a descrição do assistente",
|
|
"ERROR": "A descrição é obrigatória"
|
|
},
|
|
"PRODUCT_NAME": {
|
|
"LABEL": "Nome do Produto",
|
|
"PLACEHOLDER": "Digite o nome do produto",
|
|
"ERROR": "O nome do produto é obrigatório"
|
|
},
|
|
"WELCOME_MESSAGE": {
|
|
"LABEL": "Mensagem de boas-vindas",
|
|
"PLACEHOLDER": "Digite a mensagem de boas-vindas"
|
|
},
|
|
"HANDOFF_MESSAGE": {
|
|
"LABEL": "Mensagem de transferência",
|
|
"PLACEHOLDER": "Digite a mensagem de transferência"
|
|
},
|
|
"RESOLUTION_MESSAGE": {
|
|
"LABEL": "Mensagem de resolução",
|
|
"PLACEHOLDER": "Digite a mensagem de resolução"
|
|
},
|
|
"INSTRUCTIONS": {
|
|
"LABEL": "Instruções",
|
|
"PLACEHOLDER": "Digite as instruções para o assistente"
|
|
},
|
|
"FEATURES": {
|
|
"TITLE": "Funcionalidades",
|
|
"ALLOW_CONVERSATION_FAQS": "Gerar perguntas frequentes a partir de conversas resolvidas",
|
|
"ALLOW_MEMORIES": "Capture os principais detalhes como memórias de interações do cliente.",
|
|
"ALLOW_CITATIONS": "Incluir fonte de citações nas respostas"
|
|
}
|
|
},
|
|
"EDIT": {
|
|
"TITLE": "Atualizar o assistente",
|
|
"SUCCESS_MESSAGE": "O assistente foi criado com sucesso",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao criar o assistente, por favor tente novamente.",
|
|
"NOT_FOUND": "Não foi possível encontrar o assistente. Tente novamente."
|
|
},
|
|
"SETTINGS": {
|
|
"HEADER": "Configurações",
|
|
"BASIC_SETTINGS": {
|
|
"TITLE": "Configurações básicas",
|
|
"DESCRIPTION": "Personalize o que o assistente diz quando termina uma conversa ou transfere para um humano."
|
|
},
|
|
"SYSTEM_SETTINGS": {
|
|
"TITLE": "Configurações do sistema",
|
|
"DESCRIPTION": "Personalize o que o assistente diz quando termina uma conversa ou transfere para um humano."
|
|
},
|
|
"CONTROL_ITEMS": {
|
|
"TITLE": "As Coisas Divertidas",
|
|
"DESCRIPTION": "Adicione mais controle ao assistente. (algo mais visual como uma história: Consulta → cenários → saída) Força o usuário para realmente utilizá-los.",
|
|
"OPTIONS": {
|
|
"GUARDRAILS": {
|
|
"TITLE": "Proteções",
|
|
"DESCRIPTION": "Mantém as coisas no caminho — apenas os tipos de perguntas que você quer que seu assistente responda, nada fora de limites ou fora do tópico."
|
|
},
|
|
"RESPONSE_GUIDELINES": {
|
|
"TITLE": "Diretrizes de resposta",
|
|
"DESCRIPTION": "O jeito e a estrutura das respostas do seu assistente — tranquilo e amigável? Curto e ágil? Detalhado e formal?"
|
|
}
|
|
}
|
|
},
|
|
"DELETE": {
|
|
"TITLE": "Excluir Assistente",
|
|
"DESCRIPTION": "Esta ação é permanente. Excluir este assistente irá removê-lo de todas as caixas de entrada conectadas e apagará permanentemente todo o conhecimento gerado.",
|
|
"BUTTON_TEXT": "Excluir {assistantName}"
|
|
}
|
|
},
|
|
"OPTIONS": {
|
|
"EDIT_ASSISTANT": "Editar Assistente",
|
|
"DELETE_ASSISTANT": "Excluir Assistente",
|
|
"VIEW_CONNECTED_INBOXES": "Ver caixas de entrada conectadas"
|
|
},
|
|
"EMPTY_STATE": {
|
|
"TITLE": "Não há assistentes disponíveis",
|
|
"SUBTITLE": "Crie um assistente para fornecer respostas rápidas e precisas aos seus usuários. Ele pode aprender com seus artigos de ajuda e conversas passadas.",
|
|
"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": "Proteções",
|
|
"DESCRIPTION": "Mantém as coisas no caminho — apenas os tipos de perguntas que você quer que seu assistente responda, nada fora de limites ou fora do tópico.",
|
|
"BULK_ACTION": {
|
|
"SELECTED": "{count} item selecionado | {count} itens selecionados",
|
|
"SELECT_ALL": "Selecionar todos ({count})",
|
|
"UNSELECT_ALL": "Desmarcar todos ({count})",
|
|
"BULK_DELETE_BUTTON": "Excluir"
|
|
},
|
|
"ADD": {
|
|
"SUGGESTED": {
|
|
"TITLE": "Exemplos de proteções",
|
|
"ADD": "Adicionar todos",
|
|
"ADD_SINGLE": "Adicionar este",
|
|
"SAVE": "Adicionar e salvar (↵)",
|
|
"PLACEHOLDER": "Escreva outra proteção"
|
|
},
|
|
"NEW": {
|
|
"TITLE": "Adicionar proteção",
|
|
"CREATE": "Criar",
|
|
"CANCEL": "Cancelar",
|
|
"PLACEHOLDER": "Escreva outra proteção",
|
|
"TEST_ALL": "Testar tudo"
|
|
}
|
|
},
|
|
"LIST": {
|
|
"SEARCH_PLACEHOLDER": "Pesquisar..."
|
|
},
|
|
"EMPTY_MESSAGE": "Nenhuma proteção encontrada. Crie uma ou adicione exemplos para começar.",
|
|
"SEARCH_EMPTY_MESSAGE": "Nenhuma proteção encontrada para essa pesquisa.",
|
|
"API": {
|
|
"ADD": {
|
|
"SUCCESS": "Proteções adicionadas com sucesso",
|
|
"ERROR": "Ocorreu um erro ao adicionar as proteções. Por favor, tente novamente."
|
|
},
|
|
"UPDATE": {
|
|
"SUCCESS": "Proteções atualizados com sucesso",
|
|
"ERROR": "Ocorreu um erro ao atualizar as proteções. Por favor, tente novamente."
|
|
},
|
|
"DELETE": {
|
|
"SUCCESS": "Proteções removidas com sucesso",
|
|
"ERROR": "Ocorreu um erro ao excluir as proteções, por favor, tente novamente."
|
|
}
|
|
}
|
|
},
|
|
"RESPONSE_GUIDELINES": {
|
|
"TITLE": "Diretrizes de Resposta",
|
|
"DESCRIPTION": "O jeito e a estrutura das respostas do seu assistente — tranquilo e amigável? Curto e ágil? Detalhado e formal?",
|
|
"BULK_ACTION": {
|
|
"SELECTED": "{count} item selecionado | {count} itens selecionados",
|
|
"SELECT_ALL": "Selecionar todos ({count})",
|
|
"UNSELECT_ALL": "Desmarcar todos ({count})",
|
|
"BULK_DELETE_BUTTON": "Excluir"
|
|
},
|
|
"ADD": {
|
|
"SUGGESTED": {
|
|
"TITLE": "Exemplos de diretrizes de resposta",
|
|
"ADD": "Adicionar todos",
|
|
"ADD_SINGLE": "Adicionar este",
|
|
"SAVE": "Adicionar e salvar (↵)",
|
|
"PLACEHOLDER": "Escreva uma outra diretriz de resposta..."
|
|
},
|
|
"NEW": {
|
|
"TITLE": "Adicione uma diretriz de resposta",
|
|
"CREATE": "Criar",
|
|
"CANCEL": "Cancelar",
|
|
"PLACEHOLDER": "Escreva uma outra diretriz de resposta...",
|
|
"TEST_ALL": "Testar tudo"
|
|
}
|
|
},
|
|
"LIST": {
|
|
"SEARCH_PLACEHOLDER": "Pesquisar..."
|
|
},
|
|
"EMPTY_MESSAGE": "Nenhuma diretriz de resposta encontrada. Crie uma ou adicione exemplos para começar.",
|
|
"SEARCH_EMPTY_MESSAGE": "Nenhuma diretriz de resposta encotrada para essa pesquisa.",
|
|
"API": {
|
|
"ADD": {
|
|
"SUCCESS": "Diretrizes de resposta adicionadas com sucesso",
|
|
"ERROR": "Houve um erro ao adicionar diretrizes de resposta, por favor, tente novamente."
|
|
},
|
|
"UPDATE": {
|
|
"SUCCESS": "Diretrizes de Resposta atualizadas com sucesso",
|
|
"ERROR": "Houve um erro ao atualizar as diretrizes de resposta, por favor, tente novamente."
|
|
},
|
|
"DELETE": {
|
|
"SUCCESS": "Diretrizes de resposta removidas com sucesso",
|
|
"ERROR": "Houve um erro ao excluir as diretrizes de resposta, por favor, tente novamente."
|
|
}
|
|
}
|
|
},
|
|
"SCENARIOS": {
|
|
"TITLE": "Cenários",
|
|
"DESCRIPTION": "Dê algum contexto ao seu assistente — como \"o que fazer quando um usuário estiver com problemas\", ou \"como agir durante uma solicitação de reembolso\".",
|
|
"BULK_ACTION": {
|
|
"SELECTED": "{count} item selecionado | {count} itens selecionados",
|
|
"SELECT_ALL": "Selecionar todos ({count})",
|
|
"UNSELECT_ALL": "Desmarcar todos ({count})",
|
|
"BULK_DELETE_BUTTON": "Excluir"
|
|
},
|
|
"ADD": {
|
|
"SUGGESTED": {
|
|
"TITLE": "Exemplos de cenários",
|
|
"ADD": "Adicionar todos",
|
|
"ADD_SINGLE": "Adicionar este",
|
|
"TOOLS_USED": "Ferramentas usadas :"
|
|
},
|
|
"NEW": {
|
|
"CREATE": "Adicionar um cenário",
|
|
"TITLE": "Criar um cenário",
|
|
"FORM": {
|
|
"TITLE": {
|
|
"LABEL": "Título",
|
|
"PLACEHOLDER": "Digite um nome para o cenário",
|
|
"ERROR": "O nome do cenário é obrigatório"
|
|
},
|
|
"DESCRIPTION": {
|
|
"LABEL": "Descrição",
|
|
"PLACEHOLDER": "Descreva como e onde este cenário será utilizado",
|
|
"ERROR": "Descrição do cenário é obrigatória"
|
|
},
|
|
"INSTRUCTION": {
|
|
"LABEL": "Como lidar",
|
|
"PLACEHOLDER": "Descreva como e onde este cenário será utilizado",
|
|
"ERROR": "Conteúdo do cenário é obrigatório"
|
|
},
|
|
"CREATE": "Criar",
|
|
"CANCEL": "Cancelar"
|
|
}
|
|
}
|
|
},
|
|
"UPDATE": {
|
|
"CANCEL": "Cancelar",
|
|
"UPDATE": "Atualizar alterações"
|
|
},
|
|
"LIST": {
|
|
"SEARCH_PLACEHOLDER": "Pesquisar..."
|
|
},
|
|
"EMPTY_MESSAGE": "Nenhum cenário encontrado. Crie ou adicione exemplos para começar.",
|
|
"SEARCH_EMPTY_MESSAGE": "Nenhum cenário encontrado para esta pesquisa.",
|
|
"API": {
|
|
"ADD": {
|
|
"SUCCESS": "Cenários adicionados com sucesso",
|
|
"ERROR": "Ocorreu um erro ao adicionar cenários, por favor tente novamente."
|
|
},
|
|
"UPDATE": {
|
|
"SUCCESS": "Cenários atualizados com sucesso",
|
|
"ERROR": "Ocorreu um erro ao atualizar cenários, por favor tente novamente."
|
|
},
|
|
"DELETE": {
|
|
"SUCCESS": "Cenários excluídos com sucesso",
|
|
"ERROR": "Ocorreu um erro ao excluir os cenários, por favor tente novamente."
|
|
}
|
|
}
|
|
}
|
|
},
|
|
"DOCUMENTS": {
|
|
"HEADER": "Documentos",
|
|
"ADD_NEW": "Criar um novo documento",
|
|
"RELATED_RESPONSES": {
|
|
"TITLE": "FAQs Relacionadas",
|
|
"DESCRIPTION": "Estes FAQs são gerados diretamente a partir do documento."
|
|
},
|
|
"FORM_DESCRIPTION": "Digite o URL do documento para adicioná-lo como fonte de conhecimento e escolha o assistente para associá-lo.",
|
|
"CREATE": {
|
|
"TITLE": "Adicionar um documento",
|
|
"SUCCESS_MESSAGE": "O documento foi criado com sucesso",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao criar o documento, por favor, tente novamente."
|
|
},
|
|
"FORM": {
|
|
"TYPE": {
|
|
"LABEL": "Tipo do documento",
|
|
"URL": "URL:",
|
|
"PDF": "Arquivo PDF"
|
|
},
|
|
"URL": {
|
|
"LABEL": "URL:",
|
|
"PLACEHOLDER": "Insira a URL do documento",
|
|
"ERROR": "Por favor forneça uma URL válida para o documento"
|
|
},
|
|
"PDF_FILE": {
|
|
"LABEL": "Arquivo PDF",
|
|
"CHOOSE_FILE": "Escolher arquivo PDF",
|
|
"ERROR": "Por favor, selecione um arquivo PDF",
|
|
"HELP_TEXT": "Tamanho máximo do arquivo: 10 MB",
|
|
"INVALID_TYPE": "Por favor, selecione um arquivo PDF válido",
|
|
"TOO_LARGE": "O tamanho do arquivo excede o limite de 10 MB"
|
|
},
|
|
"NAME": {
|
|
"LABEL": "Nome do documento (opcional)",
|
|
"PLACEHOLDER": "Insira um nome para o documento"
|
|
}
|
|
},
|
|
"DELETE": {
|
|
"TITLE": "Tem certeza de que deseja excluir este documento?",
|
|
"DESCRIPTION": "Esta ação é permanente. Eliminar este documento irá apagar permanentemente todo o conhecimento gerado.",
|
|
"CONFIRM": "Sim, excluir",
|
|
"SUCCESS_MESSAGE": "O documento foi excluído com sucesso",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao excluir o documento, por favor, tente novamente."
|
|
},
|
|
"OPTIONS": {
|
|
"VIEW_RELATED_RESPONSES": "Visualizar Respostas relacionadas",
|
|
"DELETE_DOCUMENT": "Excluir Documento"
|
|
},
|
|
"EMPTY_STATE": {
|
|
"TITLE": "Nenhum documento disponível",
|
|
"SUBTITLE": "Os documentos são usados pelo seu assistente para gerar perguntas frequentes. Pode importar documentos para fornecer um contexto para seu assistente.",
|
|
"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": "Ferramentas",
|
|
"ADD_NEW": "Criar ferramenta",
|
|
"EMPTY_STATE": {
|
|
"TITLE": "Não há ferramentas personalizadas disponíveis",
|
|
"SUBTITLE": "Crie ferramentas personalizadas para conectar com APIs e serviços externos, permitindo obter dados e agir por você.",
|
|
"FEATURE_SPOTLIGHT": {
|
|
"TITLE": "Ferramentas Personalizadas",
|
|
"NOTE": "Ferramentas personalizadas permitem seu assistente interagir com APIs e serviços externos. Crie ferramentas para obter dados, realizar ações ou integre com seus sistemas existentes para melhorar as capacidades do seu assistente."
|
|
}
|
|
},
|
|
"FORM_DESCRIPTION": "Configure your custom tool to connect with external APIs",
|
|
"OPTIONS": {
|
|
"EDIT_TOOL": "Edit tool",
|
|
"DELETE_TOOL": "Delete tool"
|
|
},
|
|
"CREATE": {
|
|
"TITLE": "Create Custom Tool",
|
|
"SUCCESS_MESSAGE": "Custom tool created successfully",
|
|
"ERROR_MESSAGE": "Failed to create custom tool"
|
|
},
|
|
"EDIT": {
|
|
"TITLE": "Edit Custom Tool",
|
|
"SUCCESS_MESSAGE": "Custom tool updated successfully",
|
|
"ERROR_MESSAGE": "Failed to update custom tool"
|
|
},
|
|
"DELETE": {
|
|
"TITLE": "Delete Custom Tool",
|
|
"DESCRIPTION": "Tem certeza que deseja excluir está ferramenta customizável? Está ação não pode ser desfeita.",
|
|
"CONFIRM": "Sim, excluir",
|
|
"SUCCESS_MESSAGE": "Custom tool deleted successfully",
|
|
"ERROR_MESSAGE": "Failed to delete custom tool"
|
|
},
|
|
"FORM": {
|
|
"TITLE": {
|
|
"LABEL": "Nome da Ferramenta",
|
|
"PLACEHOLDER": "Order Lookup",
|
|
"ERROR": "Nome da ferramente obrigatória"
|
|
},
|
|
"DESCRIPTION": {
|
|
"LABEL": "Descrição",
|
|
"PLACEHOLDER": "Looks up order details by order ID"
|
|
},
|
|
"HTTP_METHOD": {
|
|
"LABEL": "Method"
|
|
},
|
|
"ENDPOINT_URL": {
|
|
"LABEL": "Endpoint URL",
|
|
"PLACEHOLDER": "https://api.example.com/orders/{'{{'} order_id {'}}'}",
|
|
"ERROR": "Valid URL is required"
|
|
},
|
|
"AUTH_TYPE": {
|
|
"LABEL": "Authentication Type"
|
|
},
|
|
"AUTH_TYPES": {
|
|
"NONE": "Nenhuma",
|
|
"BEARER": "Bearer Token",
|
|
"BASIC": "Basic Auth",
|
|
"API_KEY": "Chave API"
|
|
},
|
|
"AUTH_CONFIG": {
|
|
"BEARER_TOKEN": "Bearer Token",
|
|
"BEARER_TOKEN_PLACEHOLDER": "Enter your bearer token",
|
|
"USERNAME": "Username",
|
|
"USERNAME_PLACEHOLDER": "Enter username",
|
|
"PASSWORD": "Senha",
|
|
"PASSWORD_PLACEHOLDER": "Enter password",
|
|
"API_KEY": "Header Name",
|
|
"API_KEY_PLACEHOLDER": "X-API-Key",
|
|
"API_VALUE": "Header Value",
|
|
"API_VALUE_PLACEHOLDER": "Enter API key value"
|
|
},
|
|
"PARAMETERS": {
|
|
"LABEL": "Parameters",
|
|
"HELP_TEXT": "Define the parameters that will be extracted from user queries"
|
|
},
|
|
"ADD_PARAMETER": "Add Parameter",
|
|
"PARAM_NAME": {
|
|
"PLACEHOLDER": "Parameter name (e.g., order_id)"
|
|
},
|
|
"PARAM_TYPE": {
|
|
"PLACEHOLDER": "Tipo"
|
|
},
|
|
"PARAM_TYPES": {
|
|
"STRING": "String",
|
|
"NUMBER": "Número",
|
|
"BOOLEAN": "Boolean",
|
|
"ARRAY": "Array",
|
|
"OBJECT": "Object"
|
|
},
|
|
"PARAM_DESCRIPTION": {
|
|
"PLACEHOLDER": "Description of the parameter"
|
|
},
|
|
"PARAM_REQUIRED": {
|
|
"LABEL": "Obrigatório"
|
|
},
|
|
"REQUEST_TEMPLATE": {
|
|
"LABEL": "Request Body Template (Optional)",
|
|
"PLACEHOLDER": "{'{'}\n \"order_id\": \"{'{{'} order_id {'}}'}\"\n{'}'}"
|
|
},
|
|
"RESPONSE_TEMPLATE": {
|
|
"LABEL": "Response Template (Optional)",
|
|
"PLACEHOLDER": "Order {'{{'} order_id {'}}'} status: {'{{'} status {'}}'}"
|
|
},
|
|
"ERRORS": {
|
|
"PARAM_NAME_REQUIRED": "Parameter name is required"
|
|
}
|
|
}
|
|
},
|
|
"RESPONSES": {
|
|
"HEADER": "FAQs",
|
|
"PENDING_FAQS": "Pending FAQs",
|
|
"ADD_NEW": "Criar nova FAQ",
|
|
"DOCUMENTABLE": {
|
|
"CONVERSATION": "Conversação #{id}"
|
|
},
|
|
"SELECTED": "{count} selecionado",
|
|
"SELECT_ALL": "Selecionar todos ({count})",
|
|
"UNSELECT_ALL": "Desmarcar todos ({count})",
|
|
"SEARCH_PLACEHOLDER": "Pesquisar FAQs...",
|
|
"BULK_APPROVE_BUTTON": "Aprovar",
|
|
"BULK_DELETE_BUTTON": "Excluir",
|
|
"BULK_APPROVE": {
|
|
"SUCCESS_MESSAGE": "Perguntas Frequentes aprovadas com sucesso",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao aprovar as Perguntas Frequentes. Tente novamente."
|
|
},
|
|
"BULK_DELETE": {
|
|
"TITLE": "Excluir as Perguntas Frequentes?",
|
|
"DESCRIPTION": "Tem certeza que deseja excluir as Perguntas Frequentes selecionadas? Esta ação não pode ser desfeita.",
|
|
"CONFIRM": "Sim, excluir todas",
|
|
"SUCCESS_MESSAGE": "Perguntas Frequentes excluídas com sucesso/",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao excluir as Perguntas Frequentes, por favor tente novamente."
|
|
},
|
|
"DELETE": {
|
|
"TITLE": "Tem certeza que deseja excluir o FAQ?",
|
|
"DESCRIPTION": "",
|
|
"CONFIRM": "Sim, excluir",
|
|
"SUCCESS_MESSAGE": "FAQ excluída com sucesso",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao excluir a FAQ, por favor tente novamente."
|
|
},
|
|
"FILTER": {
|
|
"ASSISTANT": "Assistente: {selected}",
|
|
"STATUS": "Status: {selected}",
|
|
"ALL_ASSISTANTS": "Todos"
|
|
},
|
|
"STATUS": {
|
|
"TITLE": "Status",
|
|
"PENDING": "Pendentes",
|
|
"APPROVED": "Aceito",
|
|
"ALL": "Todos"
|
|
},
|
|
"PENDING_BANNER": {
|
|
"TITLE": "Captain has found some FAQs your customers were looking for.",
|
|
"ACTION": "Click here to review"
|
|
},
|
|
"FORM_DESCRIPTION": "Adicione uma pergunta e sua resposta correspondente à base de conhecimento e selecione o assistente ao qual deve estar associado.",
|
|
"CREATE": {
|
|
"TITLE": "Adicionar uma FAQ",
|
|
"SUCCESS_MESSAGE": "A resposta foi adicionada com sucesso.",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao adicionar a resposta. Por favor, tente novamente."
|
|
},
|
|
"FORM": {
|
|
"QUESTION": {
|
|
"LABEL": "Pergunta",
|
|
"PLACEHOLDER": "Digite a pergunta aqui",
|
|
"ERROR": "Por favor, forneça uma pergunta válida."
|
|
},
|
|
"ANSWER": {
|
|
"LABEL": "Responder",
|
|
"PLACEHOLDER": "Digite a resposta aqui",
|
|
"ERROR": "Por favor, forneça uma resposta válida."
|
|
}
|
|
},
|
|
"EDIT": {
|
|
"TITLE": "Atualizar as Perguntas Frequentes",
|
|
"SUCCESS_MESSAGE": "As Perguntas Frequentes foram atualizadas com sucesso",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao atualizar as Perguntas Frequentes, por favor tente novamente",
|
|
"APPROVE_SUCCESS_MESSAGE": "As Perguntas Frequentes foram marcadas como aprovadas"
|
|
},
|
|
"OPTIONS": {
|
|
"APPROVE": "Aprovar",
|
|
"EDIT_RESPONSE": "Alterar",
|
|
"DELETE_RESPONSE": "Excluir"
|
|
},
|
|
"EMPTY_STATE": {
|
|
"TITLE": "Nenhuma FAQ encontrada",
|
|
"NO_PENDING_TITLE": "There are no more pending FAQs to review",
|
|
"SUBTITLE": "Perguntas Frequentes ajudam seu assistente a fornecer respostas rápidas e precisas para perguntas de seus clientes. Eles podem ser gerados automaticamente a partir do seu conteúdo ou podem ser adicionados manualmente.",
|
|
"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": "Caixas de entrada conectadas",
|
|
"ADD_NEW": "Conectar uma nova caixa de entrada",
|
|
"OPTIONS": {
|
|
"DISCONNECT": "Desconectar"
|
|
},
|
|
"DELETE": {
|
|
"TITLE": "Tem certeza que deseja desconectar a caixa de entrada?",
|
|
"DESCRIPTION": "",
|
|
"CONFIRM": "Sim, excluir",
|
|
"SUCCESS_MESSAGE": "A caixa de entrada foi desconectada com sucesso.",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao desconectar a caixa de entrada, por favor, tente novamente."
|
|
},
|
|
"FORM_DESCRIPTION": "Escolha uma caixa de entrada para conectar com o assistente.",
|
|
"CREATE": {
|
|
"TITLE": "Conecte uma caixa de entrada",
|
|
"SUCCESS_MESSAGE": "A caixa de entrada foi conectada com sucesso.",
|
|
"ERROR_MESSAGE": "Ocorreu um erro ao conectar à caixa de entrada. Por favor, tente novamente."
|
|
},
|
|
"FORM": {
|
|
"INBOX": {
|
|
"LABEL": "Caixa de Entrada",
|
|
"PLACEHOLDER": "Selecione a caixa de entrada para implantar o assistente.",
|
|
"ERROR": "É obrigatório selecionar uma caixa de entrada."
|
|
}
|
|
},
|
|
"EMPTY_STATE": {
|
|
"TITLE": "Caixa de entrada não conectada",
|
|
"SUBTITLE": "Conectar uma caixa de entrada permite ao assistente lidar com perguntas iniciais de seus clientes antes de transferi-las para você."
|
|
}
|
|
}
|
|
}
|
|
}
|