Knowledge Base
> Getting Started
Get help from Talinty support
Three paths to a useful answer, in order of speed. Pick the one that fits the question.
| 5 Min Read
The three paths
Path one: ask the Talinty Assistant. Every screen in Talinty has a chat bar at the bottom labeled "Need help? Ask Talinty AI". Click it,
type your question in plain language, and you get an answer drawn from the help center and from the context of the screen you are
on. Good for "how do I" questions, navigation questions, and anything you would type into a search bar. The Assistant is covered in
detail in Using the Talinty Assistant in the Working with the AI category.
Path two: open the in-product help. The headset icon at the bottom of the main navigation sidebar (on the left side of every Talinty
screen) opens the help panel. From there you can browse this help center, search by keyword, or open a support conversation if
your question is not covered. Use this when you want to read rather than chat, or when you are exploring a topic rather than fixing a
specific problem.
Path three: email Talinty directly. Write to info@talinty.com. Use this for anything that involves account changes (changing your
sign-in email, transferring workspace ownership, deletion of the workspace), anything that involves billing, anything that requires a
written response you can keep on file, and anything sensitive or confidential. Email is also the right path when the in-product help is
unreachable, which is rare but happens (network issues, scheduled maintenance windows).
The Assistant handles the largest share of questions, the help center handles the second-largest, and email handles the smallest
share but the most important ones.
[Illustration: Three horizontal panels stacked vertically. Top panel: the Assistant chat bar with a sample question. Middle panel: the
headset icon in the navigation sidebar with the help panel open. Bottom panel: an email envelope with the address
info@talinty.com. Each panel labeled with the path number (1, 2, 3) in Talinty Green. Forest typography, Signal White backgrounds,
Sage Gray separators.]
What to include when you contact support
The shorter your support email, the slower the response, because every missing detail is one round trip we have to ask for. Include
the following from the start:
The workspace name and your account email. We use these to locate the right environment. If you have more than one workspace,
tell us which one the question is about.
The role you have in the workspace (Admin, Recruiter, Manager, Viewer, or a custom role). Some answers depend on your
permissions.
A clear description of what you were trying to do, what you expected to happen, and what actually happened. "It doesn't work" is
the slowest possible message; "I clicked Advance on the candidate Maya Reyes for the role Senior Backend Engineer at 14:32 today
and got a red error banner that said Permission denied" is the fastest.
A screenshot if the question is visual. The screenshot saves us several minutes of guessing what you are looking at.
The browser and operating system, if the question is about something visual or interactive that might be a rendering issue. Most
issues are not browser-specific but the ones that are can take days to reproduce without this.
Response expectations
Talinty replies to support emails within one business day in most cases. Urgent issues affecting access or data are prioritized within
the same business day. Non-urgent questions and feature requests are answered within two business days.
We are honest about our response times because vague promises (something like "we'll get back to you soon") are worse than a
real number. If your situation is more urgent than a one-business-day window and you have not had a reply, send a follow-up reply
on the same email thread with the word "Urgent" in the body and a one-line explanation of why. We will see it move to the top of the
queue.
When the issue is the AI specifically
Most AI questions are configuration questions and resolve faster through the Talinty Assistant or through Troubleshooting when AI
output doesn't look right than through support. Try those first. Reach for email when the AI is doing something that the
troubleshooting article cannot explain, when the issue is persistent across multiple roles, or when you need a written answer for an
internal review.
