Heppu Knowledge · Knowledge Platform
One knowledge platform.For humans, systems and AI agents.
Heppu’s success is based on a three-part knowledge bank: websites, systems (API) and documents. From our customers’ needs a whole product was born, Heppu Knowledge. Now it is available for all teams to use.

Returns
4 answers- Return period is 30 days12 tickets · updated 3 d agoUp to date
- Saved reply: Return NEWSays 14 days · edited 2024Outdated
- Guide: Product returnDiffers from October ticketsCheck
- Returns from abroadAsked 7 times, no answerMissing
Proposal: change saved reply from 14 days to 30 days
ApproveEditRatings and clients
End customers rate Heppu 4.3 out of 5, across 729 ratings.
Heppu works at companies like these.
“Our salespeople also use Heppu for tricky customer questions. So Heppu helps our own team serve our customers better, too.”
Markku PrättäläSales Director, Tulikivi OyjRead the Tulikivi story (in Finnish) · Translated from FinnishWho it is for
Same knowledge bank, three user groups.
One knowledge bank underneath, for your own staff, company systems and AI agents to use.
- Humans
Ask Heppu first
Customer service, sales, finance and new employees ask Heppu directly, which reduces internal asking around.
- Onboarding
- Sales & support
- Source shown
- Systems
Guides kept up to date
Return periods, product updates and technical info go straight to your support site and saved replies.
- Service Desk
- Support site
- API & webhooks
- AI agents
Same info behind every agent
Website chat, phone line and internal Copilot or Gemini agents all work on the basis of the same knowledge bank, in 90 different languages.
- Chat & phone
- Copilot/Gemini
- 90 languages
Sources connected at kickoff
Your website, solved tickets, saved replies and internal guides are connected into the knowledge bank in the 45-minute kickoff.
Sources
- Solved tickets12 480
- Saved replies214
- Guides and web pages96
Proposals checked in review
When solved tickets differ from an old guide, Heppu makes an update proposal for your named contact person or team to approve.
One knowledge bank
- Return periodUp to date
- Double chargeUp to date
- Delivery address changeCheck
In use across your company
Customer service, sales, website chat and internal AI agents read from the same knowledge bank.
In use
- Customer serviceReply to ticket
- Sales and financeAsks Heppu
- AI chatAnswers customer
Three-part knowledge base
What does Heppu’s knowledge bank consist of?
Usually a company’s info sits in three places. We connect all three into the knowledge bank at kickoff.
- Websites
Public pages and support site
Product info, support site, FAQ and publishing platforms stay included automatically.
- Systems (API)
Tickets, CRM and dev tools
Ticketing system, solved tickets, CRM, Jira, Linear and phone system in the same flow.
- Documents
Internal guides and PDF files
Internal instructions, user guides, product updates and security documentation in the same search.
Joonas · Sales
Is the return period 14 or 30 days now?
30 days. The return period changed in October and customer service already replies with 30 days.
Sources
- #47710 · October
- #47902 · October
- Guide · Product returns
Human in controlHeppu proposes, a human presses approve.
When Heppu notices a change in solved tickets, it makes a proposal. Your own team checks the proposal and decides whether to put it into force.
Info circulation
Info moves across team borders.
Customer service, sales, internal teams and product development all work on the basis of the same knowledge bank.
Website
Content
- • Chat
- • Support site
- • Product info
Systems
CMSChat serviceInternal teams
Content
- • Internal instructions
- • Internal AI agents
Systems
Slack / TeamsCopilot / GeminiCustomer service
Content
- • Saved replies
- • Articles and FAQ
- • User guides
Systems
Service DeskPhone systemProduct development
Content
- • Product updates
- • Technical features
- • Security documentation
Systems
Jira / LinearDocumentation
How info circulates in Heppu
- Loop 01
Tickets → Agents
Solved tickets update info where applicable for website chat agents and internal use.
- Loop 02
Releases → Guides
Product releases update instructions, saved replies, help articles and agents.
- Loop 03
Chats → Prioritisation
Conversations at the customer interface show what new info is needed for product development prioritisation.
Always included
Always included in the Knowledge Platform.
We build the knowledge bank together with your team in a 45-minute kickoff and follow up in 30 min meetings.

Website and support site integration
Your website and support site are connected into the knowledge bank at kickoff.
Document import
Internal guides, PDFs and saved replies are imported into the knowledge bank.
Dedicated customer lead
Your named contact person runs onboarding and 30 min follow-up meetings.
Get started
Company info into one place?
Leave your contact details, so we can check together where your team looks for answers now and how Heppu Knowledge connects to your systems.
- Reply from our team within one business day.
- Joint mapping of where your company’s info sits today.
- Live walkthrough on your own material.
Contact request
Contact · Sales
