A clear setup for each project
Keep channels, AI rules, customers, tasks, and staff access separated when one company runs several businesses or teams.
Connect business channels, let project-specific AI Agents handle routine requests, and keep every handoff, lead, task, and human reply in one shared workspace.
Gaku Support
Telegram
Lead updated
CRM context saved
Team ready
Handoff stays in Inbox
Connected by project
Keep every channel, customer, task, and employee inside the right business context from the first message.
Keep channels, AI rules, customers, tasks, and staff access separated when one company runs several businesses or teams.
Customer conversations stay in one place with ownership, internal notes, tags, status, and a clear manual or AI mode.
Each Agent uses only its project knowledge, follows privacy and action limits, and hands off instead of guessing.
Leads, customer cards, conversation history, tasks, deadlines, and manager follow-up stay connected.
Setup without a rebuild later
Create a project for your business or brand
Connect the exact channel customers use
Give its AI Agent approved knowledge and rules
Choose the team responsible for handoffs and tasks
Test the conversation, then manage it from Inbox and CRM
Start with one real workflow
Connect one channel, give its AI Agent approved knowledge and actions, then route every handoff into the same Inbox, CRM, and task queue.
Clear before setup
The practical questions teams ask before connecting their first channel.
Yes. Each project keeps its channels, customer cards, tasks, AI rules, groups, and employee access separated inside the same company account.
No. Choose a project and channel, add approved business information, set the Agent rules and handoff route, then test the conversation before activation.
Yes. A teammate can pause the AI Agent, continue the same conversation, add notes or tags, assign it, and return it to AI when appropriate.
It follows the handoff rules you configure instead of inventing an answer. The conversation, customer context, and follow-up task can be routed to the responsible person or group.
Yes. You can save an OpenAI, Anthropic, Gemini, Groq, or compatible custom API provider for a specific project and reuse it across that project.
Yes. A website can send a lead through the secure intake API, create or update the customer card, and route a task to the selected team without mixing projects.
Yes. Owners and admins can invite staff, assign roles, groups, projects, channels, and workload limits so operators do not see unrelated business data or settings.