Portfolio sites have a consistent problem: people land, skim two project thumbnails, and leave. The case studies you spent a weekend writing mostly go unread.
A chatbot on the page changes the interaction. Instead of hoping someone reads your third project write-up, they ask "have you done anything with payments?" and get the relevant part immediately. This guide covers what to feed it, how to add it, and how to make sure it never overstates you.
What visitors actually ask
Portfolio traffic is mostly recruiters, hiring managers, and potential clients. Their questions are predictable:
- "Have you worked with a specific technology?"
- "What was your actual role on this project?"
- "Have you done anything in my industry?"
- "Are you available for freelance?"
- "How long does a project like this take you?"
Every one is answerable from things you have already written. They just are not answerable quickly in the current format.
Build the source document
Your portfolio copy alone is usually too thin; it is written to look good, not to answer questions. Write one document with:
- Each project: the problem, your specific role, the stack, the outcome, what you would change
- Your skills with honest depth ("used daily for two years", not "expert")
- Working style: remote, timezone, how you like to collaborate
- Availability and engagement types, if you freelance
- Background: education, previous roles, how you got here
Aim for detail you would never put on the site because it would bury the visuals. That is exactly what the chatbot is for. A PDF exported from any document editor is fine; the PDF chatbot guide covers what makes a good source file.
Add it to your site
Create the chatbot, copy the key, and paste the snippet before your closing </body> tag:
<link rel="stylesheet" href="https://cdn.cortexvia.in/chatbotsdk-web.css" />
<script src="https://cdn.cortexvia.in/chatbotsdk-web.iife.js"></script>
<div id="cv-chat"></div>
<script>
window.ChatbotSDK.mount("#cv-chat", {
chatbotKey: "ctx-cb-xxxxxxxxxxxxxxxx",
config: { mode: "chatbot" }
});
</script>That works on plain HTML, Webflow, Framer, Wix, Squarespace, or anything else that lets you add custom code to the footer. The platform guides show the exact spot for each.
On React or Next.js, mount it in an effect with cleanup rather than pasting a raw script tag; otherwise route changes leave duplicate widgets behind. The React guide has the component.
If you would rather it sit inline on a dedicated "Ask me anything" page than float in the corner, use mode: "chat" in a container with a fixed height.
Configure it for strangers
Name it clearly. "Ask about Ananya's work" beats "Chat".
Write a welcome message that prompts. "Ask about my projects, stack, or availability." Generic greetings get generic silence.
Set your email as the support contact. Anything it cannot answer routes to you. On a portfolio that is the whole point: an unanswered question should become an email, not a bounce.
Match your brand. Colours, header name, and logo are configurable. A widget in default colours on a carefully designed portfolio looks bolted on.
Test it honestly
Ask the five questions from the top of this post. Then ask something your document does not cover. It should say so and point at your email rather than inventing a project you never worked on.
That check matters more here than almost anywhere. A chatbot claiming you have experience you do not will get found out in the interview, and it will be your problem, not the tool's.
For freelancers
There is a second benefit beyond screening: qualification. A prospective client asking about scope, timelines, and engagement types gets answers at 11pm without waiting on your reply. The ones who then email you are already better informed.
Worth including in your document:
- Typical project timelines
- How you scope and quote
- What you do not take on
- Current availability
Being explicit about what you do not do filters out the enquiries you would have declined anyway.
Keep it current
It answers from the document you gave it. New project, updated document. Changed availability, updated document.
A portfolio chatbot saying you are available when you booked out two months ago is worse than not having one.
Frequently asked questions
Do I need a website for this? No. Every chatbot has a hosted page and a link, so you can share it from your resume or LinkedIn profile before you have a site at all.
What does it cost? The free plan covers a portfolio chatbot with a document or two. Paid plans remove the Cortexvia badge and add a custom domain for the hosted page.
Will it answer in my voice? It answers from your document, so write the document the way you speak. Set the welcome message and name to match, and it reads as you rather than as a product.
