Skip to content

Commit a4b8c0d

Browse files
Faria1212gitbook-bot
authored andcommitted
GitBook: [master] 798 pages modified
1 parent 9878e02 commit a4b8c0d

File tree

13 files changed

+56
-64
lines changed

13 files changed

+56
-64
lines changed

guides/administrator-guides/administration/import/csv.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
# CSV
22

3-
The CSV importer allows you to import your own plain text files, however it does require the zip file to be in a specific format for the importer to understand.
3+
The CSV importer allows you to import your own plain text files. However, it does require the zip file to be in a specific format for the importer to understand.
44

55
## The Zip File
66

7-
The zip file must be a **flat zip**, which means there can **not** be a "root" or "sub" folder in which the items reside in the zip file. The importer looks for the files `channels.csv` and `users.csv` immediately inside the zip and not inside of any folder. If you have any questions about this, please ask in [\#support channel on the Community server](https://open.rocket.chat/channel/support).
7+
The zip file must be a **flat zip**, which means there can **not** be a "root" or "sub" folder in which the items reside in the zip file. The importer looks for the files `channels.csv` and `users.csv` immediately inside the zip and not inside of any folder. If you have any questions about this, please ask in the [\#support channel on the Community server](https://open.rocket.chat/channel/support).
88

9-
The **directmessages** directory is a special directory name, check **Direct Messages** section below.
9+
The **directmessages** directory is a special directory name. Check the **Direct Messages** section below.
1010

1111
```text
1212
fileToImport.zip
@@ -38,7 +38,7 @@ The `channels.csv` requires a **very** specific structure and layout. Each line
3838

3939
1. Channel name
4040
2. Username of the channel creator
41-
3. Whether the channel is public or private. If the last argument is not `private` it is assumed the channel is public.
41+
3. Whether the channel is public or private. If the last argument is not `private` it is assumed the channel is public
4242
4. List of users in the channel, separated by semicolons. If only the creator is in the channel, then there must be empty quotes.
4343

4444
```text
@@ -50,7 +50,7 @@ The `channels.csv` requires a **very** specific structure and layout. Each line
5050

5151
## users.csv Format
5252

53-
The `users.csv` is a file which contains the user details, each line containing a new user and the user details is:
53+
The `users.csv` is a file that contains the user details, each line containing a new user, and the user details are:
5454

5555
1. Username \(must not contain @ and some other special characters\)
5656
2. Email
@@ -64,11 +64,11 @@ graywolf336,graywolf336@example.com,GrayWolf336
6464

6565
## Message Files
6666

67-
The message csv files require a **very** specific format. Each line contains a new message, every piece of information is **requires** quotes to surround it, there cannot be any spaces between the commas. The details required are:
67+
The message CSV files require a particular format. Each line contains a new message, every piece of information is **required** quotes to surround it, there cannot be any spaces between the commas. The details required are:
6868

6969
1. Username who sent the message
7070
2. The timestamp in milliseconds
71-
3. The message, quotes are highly recommended especially if the message text contains a comma.
71+
3. The message, quotes are highly recommended, especially if the message text contains a comma.
7272

7373
```text
7474
"bradley.hilton","1479162481336","this is a test message"
@@ -82,9 +82,9 @@ Direct Channels / Direct Messages are imported from a special directory named **
8282
1. Username who sent the message
8383
2. Username who received the message
8484
3. The timestamp in milliseconds
85-
4. The message, quotes are highly recommended especially if the message text contains a comma.
85+
4. The message, quotes are highly recommended, especially if the message text contains a comma.
8686

87-
It's **required** to keep conversations in **distinct files**, for example, a conversation between user A and B compose a file \(`messages1.csv`\), and the conversation between user B and C compose another file \(`messages2.csv`\).
87+
It's **required** to keep conversations in **distinct files;** for example, a conversation between user A and B compose a file \(`messages1.csv`\), and the conversation between user B and C compose another file \(`messages2.csv`\).
8888

8989
```text
9090
"bradley.hilton","billy.bob","1479162481336","this is a test message"

guides/administrator-guides/administration/import/hipchat/cloud.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# HipChat Cloud
22

3-
To start importing values from HipChat you first need to have an instance of Rocket.Chat running. You can do that by [your own](https://docs.rocket.chat/developer-guides/quick-start/).
3+
To start importing values from HipChat you first need to have an instance of Rocket.Chat running. You can do that on [your own](https://docs.rocket.chat/developer-guides/quick-start/).
44

55
If you already have an instance running and administration privileges, you can follow these steps:
66

guides/administrator-guides/administration/import/hipchat/enterprise.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,18 +6,18 @@ To import your current data from HipChat Server / Data Center into Rocket.Chat,
66

77
This is a copy from the HipChat Server / Data Center Documentation:
88

9-
1. Browse to the fully qualified domain name you've configured for your HipChat Server, for example `https://hipchat.yourcompany.com/`.
10-
2. Log into the web user interface \(UI\) using your administrator email and password.
11-
3. Click **Server admin > Export.**
12-
4. To include files and one-to-one chat history in the export, select the check boxes.
13-
5. In the **Password** and **Confirm Password** fields, create a password to protect your archive file. You're required to provide this password when you import your data into HipChat Server. We don't store this password, so be sure to remember it.
14-
6. Click **Export**. Depending on how much data you have, it may take a few hours to export the data. When it's finished, you'll receive an email with a link to download the file.
15-
7. When you receive the email, click the link in the email to download the archive file.
9+
1. Browse to the fully qualified domain name you've configured for your HipChat Server, for example `https://hipchat.yourcompany.com/`
10+
2. Log into the web user interface \(UI\) using your administrator email and password
11+
3. Click **Server admin > Export**
12+
4. To include files and one-to-one chat history in the export, select the checkboxes
13+
5. In the **Password** and **Confirm Password** fields, create a password to protect your archive file. You're required to provide this password when you import your data into HipChat Server. We don't store this password, so be sure to remember it
14+
6. Click **Export**. Depending on how much data you have, it may take a few hours to export the data. When it's finished, you'll receive an email with a link to download the file
15+
7. When you receive the email, click the link in the email to download the archive file
1616

1717
## Import into Rocket.Chat
1818

19-
1. Decrypt the exported file: `openssl aes-256-cbc -d -in path_to_encrypted_file.tar.gz.aes -out path_to_decrypted_file.tar.gz -pass pass:your_password` See the table below for descriptions of the command line arguments.
20-
2. Ensure the file generated is a `tar.gz` file, otherwise Rocket.Chat won't accept it.
19+
1. Decrypt the exported file: `openssl aes-256-cbc -d -in path_to_encrypted_file.tar.gz.aes -out path_to_decrypted_file.tar.gz -pass pass:your_password` See the table below for descriptions of the command line arguments
20+
2. Ensure the file generated is a `tar.gz` file, otherwise Rocket.Chat won't accept it
2121
3. Go to `https://[your_rocketchat]/admin/import/prepare/hipchatenterprise`
2222
4. Choose your decrypted `tar.gz` file and wait until Rocket.Chat can read it \(it can take a few minutes, depending on the size of your export\)
2323
5. Deselect any items you **don't** want to import

guides/administrator-guides/administration/import/slack/slackbridge.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ To enable it, you have to create a Custom Bot in Slack and add it to the desired
1717
1. Go to `https://[your_host]/admin/SlackBridge`
1818
2. Enable SlackBridge
1919
3. Add your API Token, copied in step 4 above
20-
4. Restart you Rocket.Chat server
20+
4. Restart your Rocket.Chat server
2121

2222
When done, you can now invite/add the bot to the channel or private group you want to mirror from
2323

guides/administrator-guides/settings/federation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,9 +128,9 @@ Some DNS providers will not allow setting `_https` or `_http` on SRV records, so
128128
* Host: `rocketchat-tcp-protocol.chat.mydomain.com`
129129
* Value: `https` or `http`
130130

131-
#### Test your configuration from cli
131+
#### Test your configuration from CLI
132132

133-
From your cli, issue the following commands and make sure the answers look like the following:
133+
From your CLI, issue the following commands and make sure the answers look like the following:
134134

135135
```text
136136
dig srv _rocketchat._https.chat.mydomain.com

guides/omnichannel-guides/omnichannel-manger-guides/agents.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,11 @@ Settings appear, as shown below:
2222

2323
![](../../../.gitbook/assets/2%20%284%29.png)
2424

25-
1. Hit **Add**.
25+
2. Hit **Add**.
2626

2727
![](../../../.gitbook/assets/3%20%284%29.png)
2828

29-
1. The user has the Agent role now, as shown below:
29+
3. The user has the Agent role now, as shown below:
3030

3131
![](../../../.gitbook/assets/4%20%285%29.png)
3232

guides/omnichannel-guides/omnichannel-manger-guides/departments.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ If you want the omnichannel conversations to be directed to different department
44

55
To access **Departments** settings:
66

7-
1. Goto the dots menu and hit **Omnichannel**. Omnichannel settings will open up.
7+
1. Go to the dots menu and hit **Omnichannel**. Omnichannel settings will open up.
88

99
![](../../../.gitbook/assets/0%20%282%29%20%281%29.png)
1010

@@ -30,77 +30,77 @@ The new department's settings page will appear, as shown below:
3030

3131
![](../../../.gitbook/assets/5%20%282%29.png)
3232

33-
3. Type in a description. It's optional.
33+
4. Type in a description. It's optional.
3434

3535
![](../../../.gitbook/assets/6%20%282%29.png)
3636

37-
4. Allow your visitor to have the option to choose the department they want to talk to, as shown below:
37+
5. Allow your visitor to have the option to choose the department they want to talk to, as shown below:
3838

3939
![](../../../.gitbook/assets/7%20%282%29.png)
4040

4141
The option will appear to your customer in the livechat widget, as shown below:
4242

4343
![](../../../.gitbook/assets/8%20%281%29.png)
4444

45-
5. Forward your omnichannel conversations to the email address of your choice, during the hours you are offline, as shown below:
45+
6. Forward your omnichannel conversations to the email address of your choice, during the hours you are offline, as shown below:
4646

4747
![](../../../.gitbook/assets/9%20%281%29.png)
4848

49-
6. Enable the radio button below if you want your department to show offline during off business hours.
49+
7. Enable the radio button below if you want your department to show offline during off business hours.
5050

5151
![](../../../.gitbook/assets/10%20%281%29.png)
5252

5353
If you enable it will appear in the widget, as shown below:
5454

5555
![](../../../.gitbook/assets/11%20%281%29.png)
5656

57-
7. Mention the name of the channel you want to direct the offline messages to.
57+
9. Mention the name of the channel you want to direct the offline messages to.
5858

5959
![](../../../.gitbook/assets/12%20%281%29.png)
6060

61-
8. Request your agent to set tags for the conversation for later searching purposes if you want.
61+
9. Request your agent to set tags for the conversation for later searching purposes if you want.
6262

6363
![](../../../.gitbook/assets/13%20%281%29.png)
6464

65-
9. An agent can add conversation tags they want to use for this department.
65+
10. An agent can add conversation tags they want to use for this department.
6666

6767
![](../../../.gitbook/assets/14%20%281%29.png)
6868

6969
![](../../../.gitbook/assets/15%20%281%29.png)
7070

7171
![](../../../.gitbook/assets/16%20%281%29.png)
7272

73-
10. Assign the maximum number of simultaneous chats you want your agent to attend.
73+
11. Assign the maximum number of simultaneous chats you want your agent to attend.
7474

7575
![](../../../.gitbook/assets/17%20%281%29.png)
7676

77-
11. Mention the number of seconds you want to wait to consider visitor abandonment.
77+
12. Mention the number of seconds you want to wait to consider visitor abandonment.
7878

7979
![](../../../.gitbook/assets/18%20%281%29.png)
8080

81-
12. Mention the custom message you want to be displayed when the room is closed automatically by visitor inactivity.
81+
13. Mention the custom message you want to be displayed when the room is closed automatically by visitor inactivity.
8282

8383
![](../../../.gitbook/assets/19%20%281%29.png)
8484

85-
13. Mention the custom message you want to be displayed when the user is waiting in the queue.
85+
14. Mention the custom message you want to be displayed when the user is waiting in the queue.
8686

8787
![](../../../.gitbook/assets/20%20%281%29.png)
8888

89-
14. List the name of departments you would like to forward your department's chat to. ![](../../../.gitbook/assets/21%20%281%29.png)
89+
15. List the name of departments you would like to forward your department's chat to. ![](../../../.gitbook/assets/21%20%281%29.png)
9090

91-
15. After your new department is created, their assigned business hour will be displayed here.
91+
16. After your new department is created, their assigned business hour will be displayed here.
9292

9393
![](../../../.gitbook/assets/22%20%281%29.png)
9494

95-
16. Assign the agents to this department, as shown below:
95+
17. Assign the agents to this department, as shown below:
9696

9797
![](../../../.gitbook/assets/23%20%281%29.png)
9898

99-
17. Successfully added agents would be listed, as shown below:
99+
18. Successfully added agents would be listed, as shown below:
100100

101101
![](../../../.gitbook/assets/24%20%281%29.png)
102102

103-
18. Hit save.
103+
19. Hit save.
104104

105105
![](../../../.gitbook/assets/25%20%281%29.png)
106106

@@ -112,7 +112,7 @@ Your newly created department is displayed in the list of departments, as shown
112112

113113
You can have the following behavior depending on how many departments you have created:
114114

115-
* No departments: all Livechat agents will receive incoming chats using a round-robin rule;
116-
* One department: all incoming chats will be offered to agents **only** on that department using a round-robin rule;
115+
* No departments: all Livechat agents will receive incoming chats using a round-robin rule.
116+
* One department: all incoming chats will be offered to agents **only** on that department using a round-robin rule.
117117
* More than one department: the visitor will have to choose what department he wants to talk to at registration.
118118

guides/omnichannel-guides/omnichannel-manger-guides/livechat-widget-installation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ description: >-
88

99
To access **Livechat Installation** settings:
1010

11-
1. Go to **Livechat Installation** in the omnichannel panel settings, as shown below:
11+
Go to **Livechat Installation** in the omnichannel panel settings, as shown below:
1212

1313
![](../../../.gitbook/assets/0%20%2810%29.png)
1414

guides/omnichannel-guides/omnichannel-manger-guides/monitors.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,11 @@ Settings appear, as shown below:
2222

2323
![](../../../.gitbook/assets/2%20%286%29.png)
2424

25-
1. Hit **Add**.
25+
2. Hit **Add**.
2626

2727
![](../../../.gitbook/assets/3%20%285%29.png)
2828

29-
1. The user has the Monitor role now, as shown below:
29+
3. The user has the Monitor role now, as shown below:
3030

3131
![](../../../.gitbook/assets/4%20%284%29.png)
3232

guides/omnichannel-guides/omnichannel-manger-guides/multiple-business-hours.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ The feature turns on the omnichannel toggle for the set business hours automatic
88

99
To access **Business** **Hours** settings:
1010

11-
1. Goto the dots menu and hit **Omnichannel**. Omnichannel settings will open up.
11+
1. Go to the dots menu and hit **Omnichannel**. Omnichannel settings will open up.
1212

1313
![](../../../.gitbook/assets/0%20%282%29.png)
1414

0 commit comments

Comments
 (0)