What Happens When Linxa Support Needs a Person
How Linxa decides between a grounded answer, a clarification, and a human handoff—and what happens in each case.
Most AI support tools have a simple decision tree: try to answer, and if the model isn't confident, show a contact form. Linxa's support widget and marketing-site chat work differently. This post explains the three paths a support conversation can take, how privacy is handled for anonymous visitors, and what to expect if your request needs a human.
Three response types
The question has a documented answer
Linxa searches its knowledge base—product documentation, feature guides, pricing details, setup instructions—and gives a specific, citable response. If the source is a known article, the answer includes a reference.
You get the answer in chat. No handoff, no waiting.
The question is ambiguous or partially answered
Linxa asks a focused follow-up question to narrow the request before giving an answer. For example: "Are you asking about the browser extension or the dashboard?"
One or two clarifying exchanges, then a grounded answer or handoff.
The question needs a person
Account-specific issues (billing disputes, data access requests, account recovery), complex technical debugging, or anything requiring Linxa staff judgment goes to a human. The chat explains why and initiates the handoff.
A team member picks up the conversation. You don't start over.
How known contacts work
If you are a logged-in Linxa user, the support widget already knows your account context. You don't need to re-enter your email or explain your plan. When a handoff happens, the human picking up your conversation sees the same context the chat had—your account, the question, and the conversation so far.
If you have contacted Linxa support before from the same email address, that contact record is reused. You won't be treated as a new contact when you return with a follow-up question.
Delivery confirmation and retry behavior
When a handoff is initiated, Linxa confirms that the message has been received by the support team before closing the handoff state in chat. If the delivery confirmation fails, the chat enters a retry loop—up to three attempts—before showing you a fallback option (direct email link).
Anonymous sessions on the marketing site
The support chat on the marketing site (uselinxa.com) does not require login. Anonymous visitors can ask questions and get grounded answers without creating an account.
Anonymous session privacy
Anonymous conversations are not linked to any account. If a handoff is needed, you will be asked for a contact email at that point—not before. The conversation transcript is transmitted to the support team only when you consent to the handoff.
Shared knowledge, consistent answers
The in-app support widget and the marketing-site chat both use the same grounded knowledge base. A question about pricing gets the same answer whether you are logged in or browsing the site for the first time. Updates to the knowledge base propagate to both surfaces simultaneously.
This also means that when a human team member picks up a handoff, they have access to the same information the chat used. If the chat gave you a partial or incorrect answer, the human can see exactly what was said and correct it.
Questions about Linxa?
The support chat is in the bottom-right corner of every page. Ask anything—you'll get a grounded answer or a person, whichever the question needs.
Visit Support