Skip to content
AskVault Docs
Try Free →

Why we built AskVault

Written by , Founder, AskVault · Reviewed by Aashiq
Last updated: · 5 min read

The three broken patterns

In B2B SaaS, customer support has three patterns that don't work:

Pattern 1: customer can't find the answer. Your docs exist. Customers don't find them. They open a ticket. About 60 to 80% of tickets ask things already documented.

Pattern 2: agents waste time on repetitive questions. Same WISMO question 30 times this week. Same refund-policy question 20 times. Skilled agents do entry-level work.

Pattern 3: existing bots hallucinate. Flow-builder bots can't handle unscripted questions. RAG bots without grounding make up facts. Customers stop trusting bots after one bad answer.

What we set out to build

The opposite of those patterns:

  • Customers find answers fast. Bot answers from your docs in under 2 seconds.
  • Agents focus on hard cases. Bot handles repetitive; humans handle real escalations.
  • Bot answers are source-cited. Every claim has a clickable source.
  • No hallucination. Architecture grounds answers in retrieval; no free-form generation.
  • Quick setup. Under 60 seconds for the first widget.
  • Native multi-channel. 13 channels supported.

Why source citations matter

A bot that says "Our refund policy is 14 days" without citation is unverifiable. Customers don't know if it's true. Agents have to double-check. Trust erodes.

A bot that says "Per the Refund Policy, refunds are 14 days. Last updated May 1." is verifiable. Customers trust it. Agents skip verification. Compliance teams sign off.

We made this architectural, not optional. Every answer cites.

Why no per-seat or per-query billing

Pricing should align with value:

  • Per-seat punishes team growth.
  • Per-query punishes customer engagement.
  • Per-MB indexed content aligns with value (more knowledge = better bot).

We picked the alignment. See why MB-cap.

What we're not

Three honest exclusions:

  • Not a general-purpose chatbot. We're optimized for customer support and helpdesk.
  • Not a flow-builder. We're RAG-first.
  • Not the cheapest. We're the value-aligned. Cheaper alternatives exist; usually with surprise costs.

Why India-first

We're based in India:

  • INR-first billing. Native pricing in our home market.
  • GST-compliant invoices out of the box.
  • Indian payment methods (UPI, eMandate, Net banking).
  • 24/7 support coverage including IST timezone.

Global support too; India is just where we started.

The Anti-Chatbase angle

When we started, Chatbase was the obvious competitor. Their approach:

  • High per-MB cost ($400/mo for 40 MB).
  • Widget-only; other channels via add-ons.
  • Limited skills.

We respected their UX but felt the pricing was punitive and channel-coverage limited. So we built differently.

The roadmap mindset

We treat documentation as commitments:

  • Features we have are documented in detail.
  • Features we plan are marked as roadmap.
  • Features we don't have are explicit.

You won't find aspirational features pitched as real. We use docs as the spec, then build.

Values

Three core values:

  1. Trust through transparency. Source citations, clear pricing, public roadmap.
  2. Customer-aligned billing. No surprise charges, no per-seat tax.
  3. Build for the long term. Not a quick exit; we want AskVault to compound for a decade.

How to reach us

  • Sales. sales@askvault.co.
  • Support. support@askvault.co.
  • Founder. Email me directly if it matters: aashiq@askvault.co.

Most CEO emails get a response within 48 hours.

Limits

  • What we promise. Source-cited answers, no training on your data, transparent pricing.
  • What we don't promise. Perfect bot, zero hallucination, all features today.

FAQ

Are you VC-funded?

Bootstrapped today; considering raise. Aligned incentives matter.

Will you be acquired?

Long-term play; no acquisition plans.

Where's your office?

India. Remote-friendly team across regions.

Was this page helpful?