Is Kebunate just a chatbot?
No. The target system connects customer intake, AI reasoning, workflow routing, execution, verification and delivery. Conversation is only one interface.
FAQTRUTH FIRST
How Kebunate AI automation works
The public promise is simple: automate standard work, preserve evidence and stop only at exceptional boundaries.
Does every AI action need human approval?
No. Standard catalog work is designed to run automatically. Internal human gates are limited to two exception classes: exceptional commercial/legal overrides and security or irreversible actions.
Does a customer payment require Kebunate owner approval?
Not for a standard catalog order. The customer completes the provider payment flow and the system should verify it from provider read-back/webhook. Exceptional refunds, custom commitments or material commercial overrides may trigger Gate 1.
How does Kebunate decide that work is complete?
Completion requires evidence and read-back. Executor claims alone are not enough for VERIFIED_PASS.
Can Kebunate work with existing tools?
Yes. The architecture is integration-oriented: website, APIs, workflow engines, AI providers and business channels can be connected without forcing one AI vendor.
What is currently proven versus still being completed?
The public website has an existing Sales API lead intake path and internal execution/reliability evidence. Full customer commerce states such as quote, order, provider payment, mission and delivery must still be promoted only after fresh runtime/provider evidence.
Which language is primary?
English is now the canonical public language. Thai and other supported locales are secondary translations.
How do I start?
Submit a real brief through Customer Order or Contact. The site only claims the lead was accepted when the existing Sales API confirms it was stored.
Test the real intake path
Use a real business brief instead of a demo description.