Your team should be building your product not the support infrastructure around it. ReleaseDock provides a unified support inbox, a support agent that can not only answer questions but also take action. A hosted help center and changelog. And a widget that embeds right into your website with announcements, support, etc. P.S. ReleaseDock is currently offering a Lifetime Deal for founding memebers!
ReleaseDock
Congrats on the launch. I like the idea of support, docs, and changelogs living closer together.
As a founder, repeated support questions are usually a signal that something needs to change, either in the product, the docs, or the onboarding flow.
Does ReleaseDock help surface those patterns, or is it more focused on managing the support flow itself?
ReleaseDock
@kevin_napier Hey, ReleaseDock also has self correcting documentation, after repeat messages pile in ReleaseDock automatically notifies you of suggested changes which can be accepted with the click of a button.
This way your documentation always optimizes to answer your most asked questions. Although, many users tend to ask the AI these questions anyway because it is easier for them to do this rather than scroll through a help center. So website messaging/copywriting is always what will matter the most.
Mailwarm
What kind of actions can it do today, like refunds, plan changes, or updating account settings?
ReleaseDock
@thamibenjelloun Hey Thami, Yes! ReleaseDock's AI agent can be connected to your already existing API via custom actions.
Custom actions can be configured to:
1. Call GET, POST, PATCH, PUT & DELETE requests
2. Pass parameters from the chat. (you can configure accepted values)
3. Pass customer identity (if they are logged in) securely via X-releasedock-verified-identity header.
You will need a technical person to implement it but custom actions saves days to weeks of coding work & tons of support staff time if you get a lot of refund requests, etc.
Release notes are one of those docs that are always out of date or written in a rush. Auto-generating them from PR titles and commit messages is the right approach. Do you support custom templates so teams can keep their own formatting style? Congrats on the launch!