1
Bring a customer question.
Paste a ticket, or share a ticket link after connecting Freshdesk.
A LITTLE HELP FOR THE HUMANS IN SUPPORT
Turn customer tickets
into replies you can send.
Give Lexikon a customer question. It checks your product’s help docs and prepares a reply you can review, copy, and send.
J
JamieCustomer question
DemoI got a new phone and my purchase is gone. Do I really have to pay again?
Hi Jamie! You shouldn’t need to buy it again. Please check that you’re signed into the App Store with the Apple ID you used to purchase, then open Settings → Restore Purchases in the app. If it still doesn’t appear, let us know what you see and we’ll help.
FROM “WHAT DO I SAY?” TO “HAPPY TO HELP.”
A good reply.
Without all the digging.
You bring the question. Lexikon helps with the homework.
2
Let Lexikon do the digging.
It checks your connected help docs and code to find useful answers.
3
Copy. Paste. Help someone.
Read the draft, make any edits, then send it from your help desk.
ANSWERS WITH SOMETHING BEHIND THEM
Where your
replies come from.
Lexikon uses the information you connect. Here’s what each source adds.
Your help docs
Google Drive
Finds the steps and answers your team already trusts.
The customer’s story
Freshdesk or pasted ticket
Reads the question and, with Freshdesk, the conversation and internal notes.
How your product works
GitHub or Azure DevOps · Optional
Looks through connected code to help explain bugs and product behavior.
A reply you can check, then send.
Review the sources and suggested steps. You decide what reaches the customer.
Start with a Google Drive folder of help docs or a code connection. Freshdesk adds ticket context. Adding both docs and code requires Pro.
GOOD WORK, WORTH SHARING
Help your team
see what you see.
Turn a ticket into a clear bug report.
Ask Lexikon to draft a bug report or feature request with the details your team needs.
The day’s themes. Your week’s wins.
Share common questions, tickets handled, and customer thanks in a quick recap.
A LITTLE HELP GOES A LONG WAY
Try it on your next ticket.
Start free. Choose Pro when you need more room.
Free
Start freeGet a feel for Lexikon.
$0/ month
- One person
- One Drive folder or code repository
- One question every eight hours
- Use Lexikon on the web
- Draft replies and check sources
Pro
Get startedMake it part of your workday.
$20/ user / month
- Add teammates at $20 per user
- Connect more docs and repositories
- No eight-hour wait between questions
- 20,000 monthly credits per paid seat, shared by your team
- Use Lexikon on the web, Slack, and Teams
- Draft replies and check sources
Questions use credits. Usage limits apply.
Good questions.
Do I need to know how to code?
No. Start by connecting a Google Drive folder containing your product’s help docs. Code is optional; someone with repository access can connect it for deeper investigation. You can tell Lexikon your preferred tone and format in each conversation.
Can I give it a ticket from my help desk?
Yes. Paste the ticket text, or connect Freshdesk and provide a ticket number or link. The Freshdesk connection reads the conversation and internal notes. It does not read screenshots or attachments, so include relevant error messages as text.
Will it send anything to my customers?
No. Lexikon prepares a draft for you to review, edit, and send from your help desk. It can also help draft follow-up questions when information is missing.
What if it’s not sure?
Check the sources and steps before sending. Lexikon may not know which account a customer uses or whether another service is down. Ask what is missing and when to bring in your team.
What happens to our code and ticket data?
Your admin chooses which docs and code to connect. Lexikon stores a searchable copy for your workspace. OpenAI helps process this content, and your chosen AI provider uses relevant content and ticket text to write answers. Lexikon can read your code but cannot change it. Leave sensitive customer details out of tickets you share. Our privacy policy has more details.
YOUR NEXT REPLY STARTS HERE