Kortelo.
EN
Use cases

Tier-1 support drowning in repeat tickets

If this is you, keep reading.

The problem

Your support team answers the same 30 questions every week. Different customers, same answers, never written down.

New hires take 6 months to ramp because tribal knowledge lives in 4 people's heads and 200 email threads.

Customers wait 2 days for answers that already exist somewhere — they just can't find them.

Your team can't take vacations without leaving angry tickets behind. Burnout is the cost of being responsive.

What we'd build
  • 1 AI tech-support copilot trained on your actual documentation, past tickets and product specs
  • 2 Customer-facing self-service portal answering tier-1 questions 24/7 in Polish and English
  • 3 Internal knowledge base auto-built from resolved tickets — no manual writing
  • 4 Modern Python/FastAPI backend with Claude or open-source LLM (your choice, your keys)
  • 5 Your code, your data, full export anytime — no SaaS hostage scenario
  • 6 Escalation flow that hands complex tickets to humans with full context attached
How long it takes
4–8 weeks

Pilot

Test the concept on one slice of the problem. Fixed scope. Fixed price. Working software at week 1.

3–6 months

Project

Production-ready system covering the full scope. Iterative. Weekly demos. Your repo from day 1.

12 months+

Platform

Continuous evolution. New features. Predictable monthly. No surprise license audits.

Investment

Built for SMEs, priced for SMEs.

  • ·Pilot: less than 1 Asseco consultant-week.
  • ·Project: less than what enterprise vendors charge just for needs analysis.
  • ·Platform: predictable monthly, no surprise license audits.

Free 30-min audit. Zero commitment. We'll give you actual numbers.

Outcome
01

60% of tier-1 tickets deflected (typical first-quarter result)

02

New-hire ramp from 6 months to 6 weeks

03

Support team takes vacations again

Enterprise capabilities. SME pricing.