@bigbinary/neeto-assist-frontend 0.0.0-stage → 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +243 -2
- package/app/javascript/src/translations/ar.json +5 -0
- package/app/javascript/src/translations/bg.json +5 -0
- package/app/javascript/src/translations/ca.json +5 -0
- package/app/javascript/src/translations/cs.json +5 -0
- package/app/javascript/src/translations/da.json +5 -0
- package/app/javascript/src/translations/de.json +5 -0
- package/app/javascript/src/translations/en.json +75 -0
- package/app/javascript/src/translations/es-MX.json +5 -0
- package/app/javascript/src/translations/es.json +5 -0
- package/app/javascript/src/translations/et.json +5 -0
- package/app/javascript/src/translations/fi.json +5 -0
- package/app/javascript/src/translations/fil.json +5 -0
- package/app/javascript/src/translations/fr.json +5 -0
- package/app/javascript/src/translations/he.json +5 -0
- package/app/javascript/src/translations/hi.json +5 -0
- package/app/javascript/src/translations/hr.json +5 -0
- package/app/javascript/src/translations/hu.json +5 -0
- package/app/javascript/src/translations/id.json +5 -0
- package/app/javascript/src/translations/index.js +3 -0
- package/app/javascript/src/translations/it.json +5 -0
- package/app/javascript/src/translations/ja.json +5 -0
- package/app/javascript/src/translations/ko.json +5 -0
- package/app/javascript/src/translations/nl.json +5 -0
- package/app/javascript/src/translations/pl.json +5 -0
- package/app/javascript/src/translations/pt-BR.json +5 -0
- package/app/javascript/src/translations/pt.json +5 -0
- package/app/javascript/src/translations/ro.json +5 -0
- package/app/javascript/src/translations/ru.json +5 -0
- package/app/javascript/src/translations/sk.json +5 -0
- package/app/javascript/src/translations/sl.json +5 -0
- package/app/javascript/src/translations/sv.json +5 -0
- package/app/javascript/src/translations/th.json +5 -0
- package/app/javascript/src/translations/tr.json +5 -0
- package/app/javascript/src/translations/uk.json +5 -0
- package/app/javascript/src/translations/vi.json +5 -0
- package/app/javascript/src/translations/zh-CN.json +5 -0
- package/app/javascript/src/translations/zh-TW.json +5 -0
- package/dist/.ready +1 -0
- package/dist/NeetoAssistButton.js +98 -0
- package/dist/NeetoAssistButton.js.map +1 -0
- package/dist/NeetoAssistPane.js +975 -0
- package/dist/NeetoAssistPane.js.map +1 -0
- package/dist/cjs/NeetoAssistButton.js +100 -0
- package/dist/cjs/NeetoAssistButton.js.map +1 -0
- package/dist/cjs/NeetoAssistPane.js +977 -0
- package/dist/cjs/NeetoAssistPane.js.map +1 -0
- package/dist/cjs/index.js +30 -0
- package/dist/cjs/index.js.map +1 -0
- package/dist/cjs/useNeetoAssistStatus.js +18 -0
- package/dist/cjs/useNeetoAssistStatus.js.map +1 -0
- package/dist/index.js +22 -0
- package/dist/index.js.map +1 -0
- package/dist/neeto_assist-BbwXxKis.js +121 -0
- package/dist/neeto_assist-BbwXxKis.js.map +1 -0
- package/dist/neeto_assist-Ha049T0Q.js +102 -0
- package/dist/neeto_assist-Ha049T0Q.js.map +1 -0
- package/dist/useNeetoAssistStatus.js +16 -0
- package/dist/useNeetoAssistStatus.js.map +1 -0
- package/dist/useNeetoAssistStore-B5U7FFgQ.js +218 -0
- package/dist/useNeetoAssistStore-B5U7FFgQ.js.map +1 -0
- package/dist/useNeetoAssistStore-C4fEnA_y.js +232 -0
- package/dist/useNeetoAssistStore-C4fEnA_y.js.map +1 -0
- package/package.json +231 -4
- package/types.d.ts +53 -0
package/README.md
CHANGED
|
@@ -1,3 +1,244 @@
|
|
|
1
|
-
#
|
|
1
|
+
# neeto-assist-nano
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
NeetoAssist for Neeto products: the `neeto-assist-engine` Rails engine and the `@bigbinary/neeto-assist-frontend`
|
|
4
|
+
package. A host product, NeetoChat first, installs both to show its support reps what NeetoAssist would reply to a
|
|
5
|
+
visitor, let them ask NeetoAssist about a conversation, and rate its answers. NeetoAssist never writes into the
|
|
6
|
+
conversation and never talks to the visitor: a rep decides what to send.
|
|
7
|
+
|
|
8
|
+
The engine calls NeetoAssist's product API (`https://{subdomain}.neetoassist.com`) for the workspace the rep works
|
|
9
|
+
in, and passes NeetoAssist's answers through to the pane.
|
|
10
|
+
|
|
11
|
+
## Contents
|
|
12
|
+
|
|
13
|
+
1. [Engine](#engine)
|
|
14
|
+
- [Installation](#installation)
|
|
15
|
+
- [Configuration](#configuration)
|
|
16
|
+
- [Host adapter](#host-adapter)
|
|
17
|
+
- [Asking for a reply suggestion](#asking-for-a-reply-suggestion)
|
|
18
|
+
- [Endpoints](#endpoints)
|
|
19
|
+
2. [Frontend package](#frontend-package)
|
|
20
|
+
- [Installation](#installation-1)
|
|
21
|
+
- [Usage](#usage)
|
|
22
|
+
3. [Development](#development)
|
|
23
|
+
4. [Instructions for Publishing](#instructions-for-publishing)
|
|
24
|
+
|
|
25
|
+
## Engine
|
|
26
|
+
|
|
27
|
+
### Installation
|
|
28
|
+
|
|
29
|
+
1. Add the gem to the host's Gemfile, inside the private gem source:
|
|
30
|
+
|
|
31
|
+
```ruby
|
|
32
|
+
source "NEETO_GEM_SERVER_URL" do
|
|
33
|
+
# ..existing gems
|
|
34
|
+
|
|
35
|
+
gem "neeto-assist-engine"
|
|
36
|
+
end
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
2. Install it:
|
|
40
|
+
|
|
41
|
+
```shell
|
|
42
|
+
bundle install
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
3. Mount the engine in `config/routes.rb`. The frontend package calls it at `/neeto_assist`, so mount it there:
|
|
46
|
+
|
|
47
|
+
```ruby
|
|
48
|
+
mount NeetoAssistEngine::Engine, at: "/neeto_assist"
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
The engine has no tables, so there are no migrations to copy.
|
|
52
|
+
|
|
53
|
+
### Configuration
|
|
54
|
+
|
|
55
|
+
Configure the engine in `config/initializers/neeto_assist.rb`, reading the values from the host's secrets:
|
|
56
|
+
|
|
57
|
+
```ruby
|
|
58
|
+
NeetoAssistEngine.configure do |config|
|
|
59
|
+
# The host's name in NeetoAssist.
|
|
60
|
+
config.product = "chat"
|
|
61
|
+
# NeetoAssist's address. %{subdomain} becomes the workspace's subdomain.
|
|
62
|
+
# Development: "http://%{subdomain}.lvh.me:9050".
|
|
63
|
+
config.api_base_url = Rails.application.vault.neeto_assist_api_base_url
|
|
64
|
+
# The token NeetoAssist issued to this product.
|
|
65
|
+
config.api_token = Rails.application.vault.neeto_assist_api_token
|
|
66
|
+
# The host's adapter, by class name so it is loaded on use.
|
|
67
|
+
config.host_adapter = "NeetoAssist::HostAdapter"
|
|
68
|
+
# Optional, in seconds. These are the defaults.
|
|
69
|
+
config.open_timeout = 2
|
|
70
|
+
config.read_timeout = 10
|
|
71
|
+
end
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
Until `product`, `api_base_url`, `api_token` and `host_adapter` are all set, the engine stays off: the job does
|
|
75
|
+
nothing, the status endpoint answers `{ "enabled": false }` and the conversation endpoints answer 404.
|
|
76
|
+
|
|
77
|
+
After a call times out or cannot connect, the engine's calls fail at once for 30 seconds, so a NeetoAssist that stops
|
|
78
|
+
answering cannot tie up the host's threads. The cool off is kept in `Rails.cache`.
|
|
79
|
+
|
|
80
|
+
### Host adapter
|
|
81
|
+
|
|
82
|
+
The engine learns everything about the host's workspaces, reps and conversations from one class the host provides, a
|
|
83
|
+
subclass of `NeetoAssistEngine::HostAdapter`:
|
|
84
|
+
|
|
85
|
+
| Method | Returns |
|
|
86
|
+
| --- | --- |
|
|
87
|
+
| `enabled?(organization)` | Whether NeetoAssist is on for the workspace: the host's rollout gate, such as a Flipper flag on `Organization`. |
|
|
88
|
+
| `find_conversation(organization, conversation_id)` | The conversation with that id in that workspace, or `nil`. |
|
|
89
|
+
| `can_use?(user, conversation)` | Whether this rep may see NeetoAssist on the conversation. |
|
|
90
|
+
| `can_buy_credits?(user)` | Whether this rep may buy NeetoAssist credits, such as a workspace admin. Defaults to `false`. Only they get the link to buy more once the workspace runs out. |
|
|
91
|
+
| `conversation_payload(conversation)` | The conversation as NeetoAssist takes it (below), built when it is sent. |
|
|
92
|
+
| `conversation_external_id(conversation)` | The conversation's id in NeetoAssist. Defaults to `conversation.id.to_s`. |
|
|
93
|
+
|
|
94
|
+
```ruby
|
|
95
|
+
module NeetoAssist
|
|
96
|
+
class HostAdapter < NeetoAssistEngine::HostAdapter
|
|
97
|
+
def enabled?(organization)
|
|
98
|
+
organization.neeto_assist_enabled?
|
|
99
|
+
end
|
|
100
|
+
|
|
101
|
+
def find_conversation(organization, conversation_id)
|
|
102
|
+
organization.conversations.find_by(id: conversation_id)
|
|
103
|
+
end
|
|
104
|
+
|
|
105
|
+
def can_use?(user, conversation)
|
|
106
|
+
user.organization_id == conversation.organization_id &&
|
|
107
|
+
ChatPolicy.new(user, conversation).can_manage_messages?
|
|
108
|
+
end
|
|
109
|
+
|
|
110
|
+
def conversation_payload(conversation)
|
|
111
|
+
ConversationPayloadService.new(conversation).process
|
|
112
|
+
end
|
|
113
|
+
end
|
|
114
|
+
end
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
`conversation_payload` returns `url`, `status`, `assigned_to_human`, `page_url`, `visitor` (`name`, `email`,
|
|
118
|
+
`identity`: `unverified` unless the host vouches for the email) and `messages`: at most the last 30, oldest first,
|
|
119
|
+
each with `id`, `author` (`visitor`, `agent` or `bot`), `author_name`, `body` (plain text, at most 4,000 characters)
|
|
120
|
+
and `created_at`. Leave private notes out.
|
|
121
|
+
|
|
122
|
+
### Asking for a reply suggestion
|
|
123
|
+
|
|
124
|
+
Enqueue the job after every visitor message, for example from the message's `after_create_commit`:
|
|
125
|
+
|
|
126
|
+
```ruby
|
|
127
|
+
NeetoAssistEngine::SuggestReplyJob.perform_async(organization.id, conversation.id, message.id)
|
|
128
|
+
```
|
|
129
|
+
|
|
130
|
+
Do not wait or debounce: NeetoAssist waits for the visitor's burst of messages to end and answers only the latest.
|
|
131
|
+
The job runs on the `within_5_seconds` queue. It does nothing unless the engine is configured, the workspace exists,
|
|
132
|
+
`enabled?` is true and `find_conversation` finds the conversation. It builds the payload when it runs and asks
|
|
133
|
+
NeetoAssist for a `reply_suggestion`. When NeetoAssist is down, too slow or answers with a 5xx, the job raises
|
|
134
|
+
`NeetoCommonsBackend::TransientError`, which Sidekiq retries up to 3 times without reporting every attempt. A refusal
|
|
135
|
+
(a 4xx, such as `409 disabled` once the workspace switched NeetoAssist off) is only logged, since a retry would get
|
|
136
|
+
the same answer.
|
|
137
|
+
|
|
138
|
+
### Endpoints
|
|
139
|
+
|
|
140
|
+
The pane calls these for the signed-in rep, under the mount path:
|
|
141
|
+
|
|
142
|
+
| Endpoint | Does |
|
|
143
|
+
| --- | --- |
|
|
144
|
+
| `GET /neeto_assist/api/v1/status` | `200 { "enabled": true }` or `{ "enabled": false }`, for any signed-in rep. |
|
|
145
|
+
| `GET /neeto_assist/api/v1/conversations/:conversation_id/runs` | NeetoAssist's runs for the conversation, newest first, and the workspace's credits: `{ "runs": [...], "credits": { "exhausted", "remaining", "buy_url" } }`. `buy_url` is `null` unless `can_buy_credits?` is true for the rep. |
|
|
146
|
+
| `POST /neeto_assist/api/v1/conversations/:conversation_id/runs` | Asks NeetoAssist the rep's question: `{ "run": { "question": "..." } }`. |
|
|
147
|
+
| `PUT /neeto_assist/api/v1/conversations/:conversation_id/runs/:run_id/feedback` | Rates a run: `{ "feedback": { "rating": "up", "note": "..." } }`. |
|
|
148
|
+
|
|
149
|
+
- The conversation endpoints answer 404 unless `enabled?`, `find_conversation` and `can_use?` all pass.
|
|
150
|
+
- Who asks or rates is always the signed-in rep (id, name, email), never anything in the request.
|
|
151
|
+
- A blank question, one over 2,000 characters, or a rating other than `up` or `down` is
|
|
152
|
+
`422 { "error": "invalid", "details": { ... } }`, without calling NeetoAssist.
|
|
153
|
+
- NeetoAssist being down, slow, answering with a 5xx, or refusing the product token is
|
|
154
|
+
`503 { "error": "unavailable" }`. A refused token is not passed on as a 401, which would sign the rep out of the
|
|
155
|
+
host.
|
|
156
|
+
- Any other answer from NeetoAssist passes through with its status and body, such as `404 not_found`,
|
|
157
|
+
`409 disabled` or `422 invalid`.
|
|
158
|
+
|
|
159
|
+
## Frontend package
|
|
160
|
+
|
|
161
|
+
### Installation
|
|
162
|
+
|
|
163
|
+
```shell
|
|
164
|
+
yarn add @bigbinary/neeto-assist-frontend
|
|
165
|
+
```
|
|
166
|
+
|
|
167
|
+
Its peers are the usual Neeto frontend stack (neeto-commons-frontend, React Query, axios, i18next and ramda) plus
|
|
168
|
+
`@bigbinary/neeto-atoms` and `lucide-react`, which hosts on neeto-atoms already have. It needs a React Query client
|
|
169
|
+
in context (neeto-commons-frontend's `AppContainer` provides one) and the axios neeto-commons-frontend sets up. Its
|
|
170
|
+
copy lives under the `neetoAssist` key in `app/javascript/src/translations/en.json`, which neeto-commons-frontend's
|
|
171
|
+
build merges into the host's translations, as it does for every `@bigbinary` package.
|
|
172
|
+
|
|
173
|
+
### Usage
|
|
174
|
+
|
|
175
|
+
Two pieces, the same way in every product. The pane goes in the layout once, as the last child of the flex row that
|
|
176
|
+
holds the page, so it opens on the right and pushes the page to the left. The button goes on the ticket.
|
|
177
|
+
|
|
178
|
+
```jsx
|
|
179
|
+
import {
|
|
180
|
+
NeetoAssistButton,
|
|
181
|
+
NeetoAssistPane,
|
|
182
|
+
useNeetoAssistStatus,
|
|
183
|
+
} from "@bigbinary/neeto-assist-frontend";
|
|
184
|
+
|
|
185
|
+
const Layout = ({ children }) => (
|
|
186
|
+
<div className="flex h-screen">
|
|
187
|
+
<Sidebar />
|
|
188
|
+
<main className="min-w-0 flex-1">{children}</main>
|
|
189
|
+
<NeetoAssistPane />
|
|
190
|
+
</div>
|
|
191
|
+
);
|
|
192
|
+
|
|
193
|
+
const TicketHeader = ({ conversationId, insertIntoComposer }) => {
|
|
194
|
+
const { data: neetoAssistStatus } = useNeetoAssistStatus();
|
|
195
|
+
|
|
196
|
+
if (!neetoAssistStatus?.enabled) return null;
|
|
197
|
+
|
|
198
|
+
return (
|
|
199
|
+
<NeetoAssistButton
|
|
200
|
+
{...{ conversationId }}
|
|
201
|
+
onUseReply={(text, html) => insertIntoComposer({ text, html })}
|
|
202
|
+
/>
|
|
203
|
+
);
|
|
204
|
+
};
|
|
205
|
+
```
|
|
206
|
+
|
|
207
|
+
- `useNeetoAssistStatus()` returns the React Query result of the status endpoint. Read `data?.enabled`: it is empty
|
|
208
|
+
while loading and after a failure, and a failure never shows the rep a toast.
|
|
209
|
+
- `NeetoAssistPane` takes no props and no room until a button opens it. It looks and works like Neeti's pane in
|
|
210
|
+
NeetoCal: 400px wide, with an expand button that takes it to half the window (at most 800px, and the choice is
|
|
211
|
+
remembered), and a close button. While open it sets `data-neeto-assist-open` on the document's root element, to
|
|
212
|
+
`default` or `expanded`, for a host that needs CSS to make room. It follows the ticket: moving to another ticket moves it along, and leaving the
|
|
213
|
+
tickets tucks it away until the rep comes back to one.
|
|
214
|
+
- `NeetoAssistButton` takes `conversationId`, the host's own conversation id, and `onUseReply`. It opens and closes
|
|
215
|
+
the pane, tells the pane which ticket it is about for as long as the button is on screen, and shows a dot when a
|
|
216
|
+
suggested reply is waiting.
|
|
217
|
+
- The pane shows everything NeetoAssist did on the ticket, oldest first: what the customer wrote with the suggested
|
|
218
|
+
reply, "Use reply", "Copy" and the help articles it came from; the rep's own questions as a chat; the reason it
|
|
219
|
+
skipped or found no answer; thumbs up or down with an optional note; then a box to ask more. A ticket with none of
|
|
220
|
+
these starts with a short introduction and a few suggested questions. It polls every 3 seconds while a run is pending
|
|
221
|
+
and every 30 seconds otherwise, and shows its errors inside the pane, never as a toast or an error page.
|
|
222
|
+
- `onUseReply(text, html)` is called when the rep clicks "Use reply". Put the reply in the composer and send
|
|
223
|
+
nothing. `text` is the reply as NeetoAssist wrote it, in light markdown (paragraphs split by blank lines,
|
|
224
|
+
`**bold**`, `1.` numbered and `-` bulleted lists, `##` headings). `html` is the same reply for a rich-text
|
|
225
|
+
composer: escaped text inside only `p`, `br`, `strong`, `ol`, `ul`, `li` and `h2`, with no attributes, so no
|
|
226
|
+
markup from the conversation survives as HTML. Leave `onUseReply` out to show only "Copy".
|
|
227
|
+
- The pane shows replies and notes with the same formatting, built as React elements around plain text.
|
|
228
|
+
|
|
229
|
+
## Development
|
|
230
|
+
|
|
231
|
+
- `bundle exec rails test` runs the engine's tests against the dummy app in `test/dummy`, whose
|
|
232
|
+
`NeetoAssist::HostAdapter` stands in for a host's. WebMock stubs every call to NeetoAssist.
|
|
233
|
+
- `yarn test` runs the frontend's unit tests with Node's test runner.
|
|
234
|
+
- `yarn build` builds the package and `yarn release` builds it and pushes it to the local yalc store, from where a
|
|
235
|
+
host adds it with `yalc add @bigbinary/neeto-assist-frontend`. The
|
|
236
|
+
[frontend package development guide](https://neeto-engineering.neetokb.com/p/a-d34cb4b0) has the steps.
|
|
237
|
+
- The dummy app previews the pane at `/?conversation_id=<a dummy conversation id>` once NeetoAssist is on for its
|
|
238
|
+
workspace.
|
|
239
|
+
|
|
240
|
+
## Instructions for Publishing
|
|
241
|
+
|
|
242
|
+
Consult the
|
|
243
|
+
[building and releasing packages](https://neeto-engineering.neetokb.com/articles/building-and-releasing-packages) guide
|
|
244
|
+
for details on how to publish.
|
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
{
|
|
2
|
+
"neetoAssist": {
|
|
3
|
+
"title": "NeetoAssist",
|
|
4
|
+
"beta": "BETA",
|
|
5
|
+
"betaNote": "NeetoAssist drafts replies from your help articles for your reps. It runs next to your current setup and never writes to a customer.",
|
|
6
|
+
"askButton": "Ask NeetoAssist",
|
|
7
|
+
"draftReady": "A suggested reply is ready",
|
|
8
|
+
"expand": "Expand",
|
|
9
|
+
"collapse": "Collapse",
|
|
10
|
+
"close": "Close NeetoAssist",
|
|
11
|
+
"shadowNote": "Customers never see this chat.",
|
|
12
|
+
"intro": {
|
|
13
|
+
"title": "Hi, I'm NeetoAssist.",
|
|
14
|
+
"description": "When the customer writes, I draft a reply from your help articles. Ask me anything about this conversation, or try one of these."
|
|
15
|
+
},
|
|
16
|
+
"suggestions": {
|
|
17
|
+
"summarize": "Summarize this conversation",
|
|
18
|
+
"whatToReply": "What should I reply?",
|
|
19
|
+
"whatToCheck": "What should I check first?"
|
|
20
|
+
},
|
|
21
|
+
"run": {
|
|
22
|
+
"repAsked": "{{name, anyCase}} asked",
|
|
23
|
+
"pending": "Thinking...",
|
|
24
|
+
"suggestedReply": "Suggested reply",
|
|
25
|
+
"useReply": "Use reply",
|
|
26
|
+
"copy": "Copy",
|
|
27
|
+
"copied": "Reply copied",
|
|
28
|
+
"noAnswer": "NeetoAssist found no confident answer",
|
|
29
|
+
"failed": "NeetoAssist could not answer this one",
|
|
30
|
+
"skipped": "NeetoAssist skipped this one",
|
|
31
|
+
"customerWrote": "Customer wrote",
|
|
32
|
+
"sources": "From your help articles",
|
|
33
|
+
"needsFollowUp": "This reply tells the customer the team will act on their request, so someone needs to follow up."
|
|
34
|
+
},
|
|
35
|
+
"skippedReasons": {
|
|
36
|
+
"greeting": "Skipped: the customer only said hello.",
|
|
37
|
+
"acknowledgment": "Skipped: the customer only acknowledged or said thanks, so there was nothing to answer.",
|
|
38
|
+
"agentHandoff": "Skipped: the customer asked for a person.",
|
|
39
|
+
"unclear": "Skipped: the message was not clear enough to answer.",
|
|
40
|
+
"otherProduct": "Skipped: the question is about another Neeto product.",
|
|
41
|
+
"noKnowledgeSource": "Skipped: no knowledge base is connected to NeetoAssist yet.",
|
|
42
|
+
"disabled": "Skipped: NeetoAssist is switched off for this workspace.",
|
|
43
|
+
"noQuestion": "Skipped: the message had no words to answer.",
|
|
44
|
+
"outOfCredits": "Skipped: this workspace is out of NeetoAssist credits.",
|
|
45
|
+
"assignedToHuman": "Skipped: a rep owns this conversation, so NeetoAssist stays quiet. A workspace admin can change this in NeetoAssist's settings.",
|
|
46
|
+
"handedOff": "Skipped: this conversation is waiting for a person, because the customer asked for one or an earlier answer promised the team would follow up. NeetoAssist stays quiet for the rest of it.",
|
|
47
|
+
"noAnswerCooldown": "Skipped: NeetoAssist could not answer a moment ago, and the customer's next messages usually ask the same thing, so it waits a little before trying again."
|
|
48
|
+
},
|
|
49
|
+
"credits": {
|
|
50
|
+
"exhausted": "This workspace is out of NeetoAssist credits, so new questions get no answer until more are bought.",
|
|
51
|
+
"buy": "Buy credits",
|
|
52
|
+
"askAdmin": "Ask a workspace admin to buy more."
|
|
53
|
+
},
|
|
54
|
+
"feedback": {
|
|
55
|
+
"helpful": "Helpful",
|
|
56
|
+
"notHelpful": "Not helpful",
|
|
57
|
+
"notePlaceholder": "Add a note (optional)",
|
|
58
|
+
"save": "Save",
|
|
59
|
+
"close": "Close",
|
|
60
|
+
"ratedHelpful": "{{name, anyCase}} found this helpful",
|
|
61
|
+
"ratedNotHelpful": "{{name, anyCase}} found this not helpful"
|
|
62
|
+
},
|
|
63
|
+
"ask": {
|
|
64
|
+
"placeholder": "Ask about this conversation...",
|
|
65
|
+
"submit": "Send to NeetoAssist"
|
|
66
|
+
},
|
|
67
|
+
"errors": {
|
|
68
|
+
"unavailable": "NeetoAssist cannot be reached right now. It will try again shortly.",
|
|
69
|
+
"disabled": "NeetoAssist is switched off for this workspace.",
|
|
70
|
+
"notFound": "NeetoAssist is not available for this conversation.",
|
|
71
|
+
"invalid": "NeetoAssist could not take that. Check it and try again.",
|
|
72
|
+
"generic": "Something went wrong with NeetoAssist. Try again."
|
|
73
|
+
}
|
|
74
|
+
}
|
|
75
|
+
}
|
package/dist/.ready
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
Built at 2026-11-06T05:06:15.827Z
|