Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typos #73

Merged
merged 2 commits into from
Jul 24, 2024
Merged

Typos #73

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9b83581
Fix minor typos
mattvagni Jul 24, 2024
97822f3
change which tiers headless portal is available in
mattvagni Jul 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions api-reference/headless-portal.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,10 @@ If in Step 1 you opted for not using Tenants then you can also filter by custome

This will give you back a list of threads but not give you back the content of a thread. To do so you must use this query. This will fetch all relevant message timeline entries. This example is showing how to do this via GraphQL directly but this can also be done with our SDK using the `rawRequest` method.

<Snippet file="graphql/get-thread-timeline.mdx" />
<Accordion title="GraphQL query">
<Snippet file="graphql/get-thread-timeline.mdx" />
</Accordion>

</Step>

<Step title="Allow customers to submit new threads">
Expand Down Expand Up @@ -97,6 +100,6 @@ Depending on the channels you support your UI here might vary. For example if yo

---

There is a lot of more nuanced detail that these docs do not cove such as rich formatting, attachments etc. Our team can help you plan and scope out the necessary work depending on your exact requirements and stack, debug technical issues as well as actually help with the implementation.
There is a lot of more nuance and detail that these docs do not cover such as rich formatting, attachments etc. We can help you plan and scope out the necessary work depending on your exact requirements and stack. We can also debug technical issues as well as actually help with the implementation in your code base.

If based on this high-level overview you are interested in building a headless support portal, please reach out to us on [email protected].
If you are interested in building a headless support portal based on this high-level overview, please reach out to us on [email protected].
Loading