A purpose-built college assistant — grounded in your catalog, policies, and website. Answers in seconds, in your voice. No student private data is stored or released.
The ClikServ Chatbot is:
Answers only from your catalog, your policies, your current schedule, your faculty directory. When it doesn't know, it says so — and hands off to a human.
Connected to your website and event calendars. Registration windows, financial aid dates, tuition, and course offerings reflect today — not whatever was on the internet two years ago.
The student never leaves your site, and the conversation stays as your data — not training material for someone else's model.
You see what students are asking, where they're stuck, and where your website is failing them. Every conversation is logged, auditable, and reviewed by your team — so the assistant gets sharper every week.
A general chatbot is a tourist.
Yours is staff.
Built around one job, done well: answering student questions from your catalog, policies, and website — adapts to the browser language, on your own domain. Nothing made up, nothing guessed.
The bot is reviewed by your team, runs every message through a safety pipeline, and bypasses the LLM entirely on crisis keywords to surface 988 (helpline number) or your counseling center in one tap.
Easy questions answer instantly. Hard ones stream as the model reasons.
Add catalog PDFs, policy handbooks, advisor-only memos, even internal FAQs. We chunk them, embed them, and the bot cites the right page back to the student.
Every conversation is logged for your team to review. You get summaries of what your users are asking. Database is rebuilt nightly so registration dates and tuition reflect today, not two years ago.
WCAG 2.2 AA. Focus trap. Keyboard-first. Screen-reader friendly.
Enough volume that staff is drowning in repeats.
Information is there — but no one can find it.
Answering the same five questions by phone for the third time today.
Not the right fit? We'll say so. We've turned down deployments where the fit was wrong — your time is better spent than on a tool that won't move the needle.
Typical pilot-to-production timeline: 30 days. No long-term contract for the pilot.
We bring in your catalog, policies, FAQs, and website content. No scraping — we work with your web team. Upload PDFs and DOCX policy handbooks straight into the index.
sources:
- catalog.your-college.edu
- policies/handbook.pdf
- website://articles
- faqs/registrar.docxPersona, scope, escalation paths, and refusal rules are set with your team. Brand voice. Out-of-scope handoffs to the right advisor. Quiet hours. All reviewable, all editable.
persona: "warm, factual, brief"
scope: ["admissions", "aid", "registrar"]
escalate_to:
finance: aid@your-college.edu
crisis: 988 + counseling centerLaunch on one department or audience — usually admissions or financial aid — for 12 weeks. We hand you a dashboard of what students actually asked and where your site sent them in circles.
pilot:
department: admissions
duration: 12 weeks
cost: $0
contract: none requiredScale based on what the pilot data actually shows — never on what we promised. Typical pilot-to-production timeline: 30 days after the pilot ends.
expand:
↳ pilot showed 72% deflection
↳ add: registrar, advising
↳ go-live: 30 days
↳ contract: month-to-monthTypical pilot-to-production timeline: 30 days. No long-term contract for the pilot.
We bring in your catalog, policies, FAQs, and website content. No scraping — we work with your web team. Upload PDFs and DOCX policy handbooks straight into the index.
Persona, scope, escalation paths, and refusal rules are set with your team. Brand voice. Out-of-scope handoffs to the right advisor. Quiet hours. All reviewable, all editable.
Launch on one department or audience — usually admissions or financial aid — for 12 weeks. We hand you a dashboard of what students actually asked and where your site sent them in circles.
Scale based on what the pilot data actually shows — never on what we promised. Typical pilot-to-production timeline: 30 days after the pilot ends.
sources:
- catalog.your-college.edu
- policies/handbook.pdf
- website://articles
- faqs/registrar.docxpersona: "warm, factual, brief"
scope: ["admissions", "aid", "registrar"]
escalate_to:
finance: aid@your-college.edu
crisis: 988 + counseling centerpilot:
department: admissions
duration: 12 weeks
cost: $0
contract: none requiredexpand:
↳ pilot showed 72% deflection
↳ add: registrar, advising
↳ go-live: 30 days
↳ contract: month-to-monthEvery feature came from a real conversation with a real higher-ed team. No hype, no magic — just the pipeline you'd build if you had a year and the right ML hires.
Students wait 3 days for an answer their college's website already has.
Instant, cited answers — pulled live from your own admissions, aid, and registrar pages.
Off-the-shelf chatbots hallucinate tuition, deadlines, and program names.
Hallucination guard verifies every phone number, dollar amount, course code, and URL against retrieved chunks.
Your existing chatbot doesn't speak Spanish, Vietnamese, or Mandarin.
Multilingual by default. Same grounded pipeline, native language for every student.
Procurement says no SaaS for student data.
Run on your hardware. Ollama-compatible LLMs. SQLite, Chroma, BM25 all local. Nothing leaves the campus.
“We went from a 3-day email queue to instant, cited answers. Our staff finally got their afternoons back.”
“Procurement was the hardest sell. FERPA-aware logs is what got it across the line.”
“I have never seen a vendor ship a chatbot that actually cites the source paragraph. This is what students deserve.”
“Our Spanish-speaking parents stopped calling the front desk at 7am. That alone justified the pilot.”
ClikServ started in a classroom. Piyush has taught at Austin Community College since 2004 and built two of its tech programs from scratch, which meant twenty-two years of watching capable students stall on things that had nothing to do with the coursework. A prerequisite nobody could explain. A financial-aid deadline three clicks deeper than anyone would think to look. An advisor whose inbox was two weeks behind.
Arindam and Nihal knew the other side of it. Between Texas A&M, IIT Delhi and Iowa State, and across years spent as teaching assistants fielding the same questions over and over, they had done the hunt themselves: open the catalog PDF, open the department page, open a policy memo from 2019 that may or may not still apply, then give up and email someone anyway. The answer was almost always published somewhere. It just wasn't findable.
That gap is the whole reason we exist. Colleges don't have an information problem; they have a retrieval problem. So we built ClikServ to turn the information a college already publishes into a grounded assistant that answers in plain language, cites where the answer came from, and says “I don't know, here's who does” instead of guessing. From there, the same grounded knowledge does more than answer questions.
Where this goes is bigger than search. Education has always been one-to-many: one instructor, one syllabus, and a room full of people who are catching up. AI is the first thing that has the potential to address these: ClikServ Guide that knows what a student has already been told, and ClikServ Tutor that knows what they already understand. We would rather be accurate than fast, and we would rather a student reach mastery than an answer. ClikServ Chat makes a college's own knowledge reliable; ClikServ Tutor turns that same grounded knowledge into learning.
Founder & CEO
The teacher who watches students stall on the wrong things.
An instructor at Austin Community College since 2004, where he founded its Software Developer Bootcamp (2016) and AI Engineering Program (2026), after twenty-five years building production systems for publishing, manufacturing and technology companies. Piyush now builds ClikServ to catch what office hours can't.
B.S. IIT Bombay, M.S. USC Los Angeles, MBA, Acton Business School, Austin.
Found performing magic for kids in his spare time and his fantasy is to become an inspirational speaker.
LinkedInFounding team, AI Research
The researcher who makes sure the answer is actually right.
Deep-learning researcher and IIT Delhi alumnus with a pending patent for automating bioengineering imaging data analysis with deterministic AI models. As a graduate researcher at Iowa State and Los Alamos National Laboratory, he built models to solve inverse problems, the mathematical science of finding the ground truth from noisy data. A former university TA, he now applies that same scientific construction to ClikServ's AI, owning the retrieval pipelines, hallucination prevention, and evaluations that ensure every student gets an accurate, cited answer.
B.S. IIT Delhi, M.S. Iowa State University, Ames
Found traveling to dark sky preserves to capture long-exposure photos of distant galaxies and objects. His fantasy is to develop tools that serve and that he can be proud of.
LinkedInFounding team, AI & Engineering
The engineer who builds the thing, end to end.
AI engineer and full-stack software developer. He has built ClikServ from scratch: the ingestion and retrieval pipeline that grounds every cited answer, the chatbot students talk to, the adaptive session engine inside ClikServ Tutor, and the site you're reading this on.
B.S. Texas A&M, 3 years as a teaching assistant on the other end of students' questions.
Found behind the wheel or turning a late-night idea into something real and his fantasy is to create something millions of students rely on every day.
LinkedInBetween the three of us that's two decades of teaching, four universities, a patent pending in deep learning, and a lot of time spent on both ends of a question nobody could find the answer to. You'll talk to us directly, not a sales floor, from the first demo onward.
We price on conversations, not enrollment. A pilot that succeeds shouldn't cost more than one that fails. Full pricing is shared after we've seen your scope — too many variables to put a single number on the page.
One department or audience to start. We turn it on, you watch what students actually ask.
Full rollout across your domain. Pricing scales with conversations and deployment scope, not enrollment — so growing usage stays predictable.
Your servers, your network, your audit trail. Runs entirely on your hardware — no student data leaves the campus. We handle deployment, retraining, and ops.
Campus pricing scales with actual usage and the LLM provider you choose (local Ollama, hosted, or your own inference endpoint). We'll send a one-page quote within 48 hours of the pilot kickoff.
Twelve weeks, on us, on one department or audience of your choosing — usually admissions or financial aid. We provision a hosted demo URL within 48 hours, you point internal users at it for twelve weeks, and we hand you a digest of what students actually asked. No credit card, no contract, no auto-conversion to paid. If you want to extend or expand into a production-style pilot, that's a separate conversation.
Let's talk
Book a 30-minute pilot conversation. We'll show you what your students are actually asking — and where your site is sending them in circles.
Prefer email? support@clikservinc.com
Honest, no-nonsense privacy: no FERPA-covered, student-identified data is stored in our model or our logs. You see every conversation. You own every word.