Your prospects have questions your website can't answer.
Pepline's advisor answers them from your own documents — grounded, sources named — admits what the sources don't cover, and probes the assumptions underneath. The visitor leaves with a written recap. You see the whole conversation.
Set up with you, on your documents — free while in beta.
The answers exist. They're just not on the page.
Visitors arrive mid-decision — buy or build, this package or that one, is this even the right kind of help. What they need to decide is in your guides, your past proposals, the email you've written a dozen times.
What your site offers instead is an FAQ page that answers six generic questions and none of theirs. So the real question either leaves with the visitor, or turns into a call you take just to say something a document already says.
Answers with sources named.
The advisor grounds every answer in your knowledge library and names the document it leaned on. No improvising from general knowledge.
It knows what it doesn't know.
When a question falls outside your documents, it says so and flags the question to you. Gaps become curation, not confident guesses.
It asks back.
A visitor asking "how much" is often deciding something else. The advisor probes the assumption underneath, the way you would on a good first call.
The recap is the answer, in writing.
Chatbots route. Forms collect. Pepline writes. When an advisor conversation ends, the visitor gets a recap by email: what was discussed, the answers — grounded in your documents, sources named — and a suggested next step. You get the same conversation in your dashboard, with every quoted source pinned to the exchange that used it.
When your documents don't cover a question, the recap says so. An honest gap outlives a confident guess.
Start the conversation →You run a small logistics company and want a customer portal for tracking shipments. Your core question was whether to build one yourself or buy something off the shelf. You noted that your tracking is mostly standard, but your routing logic is custom — dispatchers currently juggle it in spreadsheets.
The buy-vs-build decision hinges on one thing: whether your shipment data and process are standard, or whether you have quirks — specific carriers, custom statuses, internal systems — that off-the-shelf tools can't map to cleanly. Buying is faster and cheaper when you're tracking generic parcel movement. Building starts to win when the portal has to reflect how you actually operate.
"Custom routing logic that lives outside the tracking system is the most common reason off-the-shelf portals get abandoned."
Your dispatchers' spreadsheets are exactly that kind of logic.
Trial one off-the-shelf portal against a week of real shipments before deciding to build.
We set it up with you.
No template picker, no knowledge-base migration project. Your advisor goes live as a working session with us, on your documents — then the library, the voice, and the boundaries stay yours to edit from the dashboard.
Start with a conversation.
We load your documents with you — guides, handbooks, the answers you type twice a week — and set the boundaries: what it may answer, what it must flag to you instead.
Embed one script tag.
Inline, popup, slider, popover, or a side tab. No site to put it on? Link to its hosted full-page chat instead. Small, cookie-free, well behaved.
Read recaps, not repeated emails.
Every conversation lands in your dashboard with the quoted sources pinned to the exchange that used them. The questions your documents couldn’t answer become the next thing you write.
Stop repeating yourself.
The questions you answer twice a week can be answered while you sleep — in your words, sources named, recapped in writing. It starts as a conversation with us.