Messaging tools that finish a defined task.
A useful chatbot answers repeatable questions, collects a booking or lead, and hands the rest to a person. We configure that flow around your services and rules.
- 10
- Products built in-house
- 12
- Web projects in the portfolio
- 04
- Site languages: EN, TR, ES, DE
- UTC+3
- Overlaps US mornings and the full EU workday
WhatsApp is already where many customers ask about hours, prices, and availability. Automation helps when those questions follow stable rules and the answer can be stored as a record. It fails when the bot is asked to negotiate, apologize, or invent policy. METEK Technologies scopes chatbots around the first of those jobs.
Start from the conversations you already have
The useful brief is a set of real threads, not a brochure. Group them into information, booking, changes, sales, and complaints. Only the rule-based groups belong in the first release.
Staff must agree on the answers before software repeats them. If deposits and cancellation windows differ by person, the bot will simply scale the confusion. Policy first, flow second.
Handoff is a product decision
The assistant should know when to stop. Unusual requests, complaints, and quotes that need judgment move to the team with a short summary: name, service, time, unanswered question. Asking the customer to repeat the whole chat wastes the automation.
Staff also need a way to pause the bot in an active thread. Two voices in one conversation is worse than no bot at all.
Bookings need one calendar
Appointment automation only works when WhatsApp, the front desk, and Instagram (if used) read the same availability. Hours, duration, buffers, holidays, and cancellation rules all belong in that source.
A polished chat that writes into a separate spreadsheet will double-book. We connect the conversation to the panel or calendar the team already trusts, or we build that panel in the same project.
Where this sits among our services
Chatbot work is often paired with a website inquiry path and a CRM or booking screen. Ahi AI in the portfolio is a public example of an appointment assistant. The public site still has to explain the offer; the bot should not be the only place a service exists.
If you only need a simple WhatsApp link from the website, that is a contact path, not a chatbot project. Say so in the inquiry. We will not sell you a flow you will not maintain.
Lead Capture & Triage
Instant response without robotic dead ends
Structured intake in seconds
Collects product SKU, quantity, destination city, or appointment window on WhatsApp, Instagram, or web chat immediately.
Human handoff with full context
Routes qualified inquiries to the right salesperson or coordinator with a clean summary instead of trapping the buyer in a loop.
Guardrailed AI agents
Agents read from your verified catalog and pricing rules and require human approval before executing sensitive actions.
Scope
What is included
Replies based on your services and pricing
Opening-hours and appointment rules
Protection for unavailable time slots
Cancellation handling
Appointment reminders
Sales or booking panel connection
Setup and team training
How a project runs
From first conversation to launch
Discovery
We document the business goal, audience, available material, and technical constraints.
Scope
Pages, features, priorities, responsibilities, and review criteria are written down.
Design
We establish the interface, component rules, and a CSS design system when the project needs one.
Development
We implement the approved interface and connect the required panels, CRM functions, or messaging tools.
Quality review
We review mobile behavior, performance, core accessibility requirements, and technical SEO.
Launch
The approved release goes live with the agreed support period and content handoff.
Technology used in this work
- WhatsApp Cloud API
- n8n
- Python
- PostgreSQL
- Instagram Graph API
- Supabase
Questions we are asked
Do you set up WhatsApp Business API chatbots?
We configure WhatsApp and Instagram assistants around your services, hours, and handoff rules. The exact provider and API path is chosen during scope, based on volume, the country you serve, and whether a booking panel is included.
Will the bot replace our staff?
No. It takes the repetitive questions and structured bookings. Staff keep the conversations that need judgment. A project that promises full replacement is usually underspecifying the exceptions.
Can the chatbot create records in a CRM?
Yes, when the CRM or custom panel is part of scope and the fields are defined. A bot that only lives in the chat thread leaves the team searching for names and times later.
Show us the messages you want handled.
A handful of anonymized conversations plus your hours and booking rules is enough to see whether automation fits.