Crescentek

AI Chatbots for Websites

Your website's smartest visitor.

AI chat agents that qualify leads, score the conversation as it happens, capture email at the right moment, and hand off the right enquiries to your team — instead of just answering FAQs into the void.

Live on this page right now
Score-aware handoff
Built in Ireland
Crescentek Assistant
Online
Type a message…
Conversation score (live)
Streaming
0
Exploring
0–39Exploring
40–69Warming
70+Qualified
What ours do that most don't

Beyond FAQ-in-a-box.

Most website chatbots are glorified search boxes. Ours qualify leads, ground every reply in your real content, and know exactly when to step aside for a human.

Score every turn
The agent emits a hidden score with each reply. Conversations are sorted in real time — you stop wasting time on tyre-kickers.
Capture email at the right moment
An email gate appears when intent crosses a threshold — not on entry, not as a popup, but when the visitor has actually shown interest.
Ground answers in your content
The bot only answers from your real services, pricing, and policies — anti-hallucination rules ban it from inventing platforms, prices, or promises.
Hand off cleanly
Qualified leads trigger a confirmation email + admin alert + PDF transcript saved in the CMS. No-one falls between the cracks.
Inside the conversation

Every visitor turn updates the lead model.

Score, email-gate state, and handoff trigger are all derived from the live conversation. By the time a visitor hits 70+, the team already has a saved transcript, a PDF summary, and an alert.

01
Visitor message
Each turn classified — service interest, budget signal, urgency, decision authority.
02
Score update
Hidden META score moves up or down. Stored in session, visible to the agent next turn.
03
Email gate
Score crosses 60 → inline email field appears. Hard gate, not a popup.
04
Handoff
Score crosses 70 → admin alert + customer confirmation + PDF transcript saved.
05
CMS record
Full transcript, score history, lead data live in Payload CMS — searchable, exportable.
This is the same architecture running on this very page — every conversation feeds a structured lead record, not a Slack channel.
Built on

Models, tools, and infrastructure we use.

OpenAI GPT-4 / GPT-4oClaude (Anthropic)Pinecone (vector DB)LangChainNext.jsPayload CMSNode.jsEC2 / AWSPDFKitPostgresWebhooksn8n
What our chatbots never do

Three lines no chatbot of ours will cross.

Invent facts
If a visitor asks about a service, platform, or price not in the brief, the bot says 'I'll check with the team' — never makes one up. Hallucinations are a banned action, not a tuning problem.
Promise what it can't deliver
It will not say 'I've booked you in', 'a developer will call you in 5 minutes', or quote prices. Promises that need a human are always handed off to a human.
Leak data
All conversations stay in your Payload CMS — not in a third-party SaaS dashboard. GDPR-friendly by default. Visitors can request transcript deletion.
Who they work for

Four common shapes.

SME lead capture
Service businesses (clinics, agencies, consultancies) where a 15-minute conversation does more than a contact form ever would.
Ecommerce concierge
Product recommendations, sizing help, stock checks, returns guidance — grounded in your real catalogue.
Booking qualifier
Pre-screen booking requests by service type, urgency, and fit — only confirmed bookings reach reception.
Support deflection
Top 30 support questions answered instantly with grounded answers; everything else routed to a real human with full context.
Data lives in your CMS, not a SaaS dashboard
GDPR-friendly, EU-hosted infrastructure
Self-hosted on your domain — no vendor lock
Frequently asked

AI chatbot questions.

Mostly yes — through three layers: (1) a strict system prompt that bans inventing platforms, prices, or promises; (2) retrieval grounding against your actual service pages and FAQs; (3) explicit fallback phrasing ('I'll check with the team') for anything outside that scope. We test this with adversarial prompts before launch.
Embedded drawer in the bottom-right by default, exactly like the one on this page. It can also be a full-page experience (e.g. for a knowledge-base hub) or a drop-in HTML embed for non-React sites. We avoid intrusive auto-open popups — they hurt conversion.
Three channels fire simultaneously when score crosses your handoff threshold: (1) a confirmation email to the visitor summarising the conversation, (2) an internal alert email to your team with a PDF transcript attached, (3) a structured record saved in Payload CMS for follow-up + reporting.
Yes — common integrations include HubSpot, Salesforce, Zoho, Pipedrive (lead push), Calendly/Cal.com (booking handoff), and your existing email infrastructure (Postmark/SendGrid/SES). Custom CRMs are handled via API or webhook bridge.
Setup is usually €4,500–€12,000 depending on integration depth and content volume. Ongoing costs run €150–€400/mo for typical SME traffic (model usage + hosting + tuning). Voice or multi-language variants are quoted separately.
Standard timeline is 3–5 weeks: week 1 = content + brand audit, week 2 = build + content grounding, week 3 = QA + adversarial testing, week 4 = soft launch + tuning. Faster is possible for simpler scopes.
Depends on the use case. For most lead-capture chat we use GPT-4o or Claude Sonnet — both work well. For high-volume support deflection where cost matters we route easy questions to a smaller model and escalate hard ones. We don't lock you into one vendor.

The chatbot on this page just watched you read it.

Open it and ask anything about pricing, timelines, or how the handoff works. If your visit is qualified, our team gets a structured lead before you've left the page.