Skip to content

Commit

Permalink
Others
Browse files Browse the repository at this point in the history
  • Loading branch information
jesushernandez committed Nov 23, 2023
1 parent 6c4faba commit bcf6056
Show file tree
Hide file tree
Showing 10 changed files with 14 additions and 14 deletions.
2 changes: 1 addition & 1 deletion api-reference/graphql/customers/customer-groups.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: 'Customer groups'

Customer groups can be used to group and segment your customers. For example you could organise your customers by their tier "Free", "Growth, "Enterprise" or make use of groups to keep track of customers trialing beta features.

Customers can belong to one or many groups. You can filter your customers by group, allowing you to quickly focus on a subset of your customers.
Customers can belong to one or many groups. You can filter customer threads by group, allowing you to quickly focus on a subset of them.

This guide will show you how to add customers to groups using the API. You can also do this with the UI in Plain if you prefer.

Expand Down
4 changes: 2 additions & 2 deletions api-reference/graphql/threads.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,11 @@ title: 'Threads'
sidebarTitle: Overview
---

Threads are the core of Plain's data model and equivalent to tickets or conversations in other support platforms. When you use Plain to help a customer you assign yourself to a thread and then mark the thread as done once you're done helping.
Threads are the core of Plain's data model and equivalent to tickets or conversations in other support platforms. When you use Plain to help a customer you assign yourself to a thread and then mark the thread as `Done` once you're done helping.

Threads are automatically created when a new email is received but can also be created via the API (when a customer submits a contact form for example).

Threads have a status which can be in either **Todo**, **Snoozed** or **Done** and can only be assigned to one person.
Threads have a status which can be in either `Todo`, `Snoozed` or `Done` and can only be assigned to one person.

Threads belong to one customer but can contain multiple email threads and customers.

Expand Down
8 changes: 4 additions & 4 deletions api-reference/graphql/threads/status-changes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ To change a threads status you need an API key with the following permissions:
- `thread:edit`
- `thread:read`

### Mark thread as done
### Mark thread as `Done`

When any activity happens in a thread, it will move back to `Todo`.

Expand All @@ -36,7 +36,7 @@ Unlike traditional ticketing software, we expect a ticket to move between `Todo`

You can snooze threads for a duration of time defined in seconds.

When any activity happens in a thread, it will be automatically unsnoozed and move to **Todo**. Otherwise threads will be unsnoozed when the timer runs out.
When any activity happens in a thread, it will be automatically unsnoozed and move to `Todo`. Otherwise threads will be unsnoozed when the timer runs out.

<Tabs>
<Tab title="Typescript SDK">
Expand All @@ -47,9 +47,9 @@ When any activity happens in a thread, it will be automatically unsnoozed and mo
</Tab>
</Tabs>

### Mark thread as Todo
### Mark thread as `Todo`

This is useful if you mistakenly marked a thread as done or snoozed a thread and want to unsnooze it. Otherwise just write a message or do what you want to do and the thread will be automatically moved back to do **Todo**.
This is useful if you mistakenly marked a thread as `Done` or snoozed a thread and want to unsnooze it. Otherwise just write a message or do what you want to do and the thread will be automatically moved back to do **Todo**.

<Tabs items={['Typescript SDK', 'GraphQL']}>
<Tab>
Expand Down
2 changes: 1 addition & 1 deletion api-reference/migrate-to-threads.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ In the ✨ **new** ✨ version of Plain:

- A customer has multiple threads
- A thread can be assigned
- A thread has a status which is either Todo, Snoozed or Done
- A thread has a status which is either `Todo`, `Snoozed` or `Done`
- A thread has labels (e.g. "Bug report")
- A thread has a priority
- All emails and comms belong to a specific thread
Expand Down
2 changes: 1 addition & 1 deletion assignment.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ If you want to assign a thread manually, you can use the shortcut **A** or use *

By default in Plain, once you are assigned to a thread, you will never be automatically unassigned. This ensures that if you pick up a support request, you can see it through. We call this behavior "sticky assignment".

If you'd like to change this behavior, you can do so in **Settings****Workflow**. Here you can choose to be automatically unassigned when a thread is marked as done or snoozed.
If you'd like to change this behavior, you can do so in **Settings****Workflow**. Here you can choose to be automatically unassigned when a thread is marked as `Done` or `Snoozed`.

We recommend turning sticky assignment off if your team has a shared support rota. That way, whoever is on-call can pick up any threads you didn't finish.

Expand Down
2 changes: 1 addition & 1 deletion linear.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,6 @@ To do this, head to **Settings** → **Linear integration** and connect your wor

Once this set-up is done, you can add a Linear issue from the right hand side of a thread or by pressing the shortcut `i`.

Once a Linear issue is linked, the thread will move back to Todo when the Linear issue is completed or cancelled.
Once a Linear issue is linked, the thread will move back to `Todo` when the Linear issue is completed or cancelled.

This means that you can update customers when a bug or feature request that they reported has been fixed.
2 changes: 1 addition & 1 deletion mint.json
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@
]
},
{
"group": "Add context",
"group": "Adding context",
"pages": ["customer-cards", "customer-groups", "events"]
},
{
Expand Down
2 changes: 1 addition & 1 deletion quickstart.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ You can connect to Linear from **Settings** → **Linear**.

</AccordionGroup>

### Add context
### Adding context

To provide support more quickly, get more context into Plain from your own systems.

Expand Down
2 changes: 1 addition & 1 deletion reporting.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ When viewing your threads queue you can at a glance see key metrics on your curr

You can see:

- The breakdown of why a thread is in Todo (whether it's new threads, replies, Linear issues, etc.)
- The breakdown of why a thread is in `Todo` (whether it's new threads, replies, Linear issues, etc.)
- Distribution of threads by priority
- A preview of how many threads will be unsnoozed in the next 24 hours
- Counts of assigned vs. unassigned threads
Expand Down
2 changes: 1 addition & 1 deletion shortcuts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ This is the list of available keyboard shortcuts in Plain:
- **A** - Assign the thread
- **P** - Change thread priority
- **N** - Add a note to a thread
- **E** - Mark a thread as done
- **E** - Mark a thread as `Done`
- **Z** - Snooze a thread
- **!** - Mark customer as spam
- **⌘ + .** - Show/hide queue
Expand Down

0 comments on commit bcf6056

Please sign in to comment.