galenry.We carry the pager for our own advice
Two products we build and run ourselves. Running them keeps us honest about what we advise, because the wrong answers and the model bills are ours to deal with.
Answers from your own docs. For support teams drowning in questions the docs already answer.
What it does
Chat over your own knowledge base. When it isn’t sure enough, it hands off to a person instead of guessing, and every answer cites where it came from.
What it includes
- Answers from your content
- Hand-off to a person
- Confidence limits
- Sources cited on every answer
- Conversation analytics
What we can point at
Answering from our own documentation in production, with citations on every reply.
Finds the trip, then hands it over. For operators whose booking flow loses people mid-journey.
What it does
Travellers find trips by chatting with your own catalogue: tours, packages and day-by-day itineraries in one thread, each linking straight into your booking flow. Quotes, visas and custom plans go to your team through a tracked hand-off instead of a guess.
What it includes
- Finding trips in conversation
- Day-by-day itineraries in chat
- Tracked hand-off to your team
- Links into your booking flow
- Tour and package recommendation
What we can point at
Live with one travel client, answering from their catalogue and checking every figure against source data before a reply is shown.
Three ways on. Depending on how close one of these is.
See one in use
A walkthrough on real questions, including what it does when it doesn’t know the answer.
Ask for a walkthroughStart from a working product
If one is close to what you need but not quite it, starting from something that runs usually beats starting from nothing.
Tell us what’s differentBuild something of your own
The same engineering, applied to your data and your customers, is what our AI practice does.
See how we build AITell us what you’re trying to build. We’ll tell you where we’d start.
Bring an idea, a stalled project, or a system that has outgrown itself.
Send us a brief
The problem, what you have tried, and what success looks like. A few lines is enough to start.
Prefer email? contact@galenry.com
What happens next
- 01Reply within one business dayFrom one of our engineers.
- 02First call: 30 minutes, no deckA working call about the problem. We ask questions rather than present slides.
- 03An honest answerWhere we would start, or, if we are not the right team, who might be.