
Kommo
Your sales team uses Kommo to close deals through messenger-based selling. Your AI agent accelerates that process by qualifying visitors in chat, creating leads with deal values and pipeline stages, and logging follow-up tasks, all pushed directly into Kommo before a rep even picks up the conversation.




Your AI agent works alongside Kommo's sales pipeline to capture leads, organize contacts, and manage tasks so your team focuses on closing instead of data entry.
Kommo
See how businesses use AI agents to fill Kommo with qualified leads, move deals forward, and assign follow-ups, all from the messaging channels their customers already use.
A prospect messages your business on WhatsApp asking about pricing. Your AI Agent qualifies them by asking about team size, budget, and timeline, then creates a Kommo lead with a deal value, assigns it to the right pipeline stage, and tags it as 'inbound-whatsapp.' The sales rep gets a notification with full context. No lead form needed, no manual CRM entry, and the prospect's buying intent is captured at the peak of their interest.
A website visitor completes a product demo request through the AI agent. The agent creates the lead in Kommo, then generates a follow-up task assigned to the account executive with a 24-hour deadline and a summary of the prospect's requirements. The AE opens Kommo the next morning with a prioritized to-do list. Nothing falls through the cracks, and response time drops to hours instead of days.
A customer who previously purchased messages your Instagram bot with a new question. Your AI Agent looks up their contact in Kommo by email, finds their existing lead history and company record, and greets them by name with context about their last interaction. The customer feels recognized immediately. Your team avoids asking redundant questions, and the conversation picks up right where it left off.

Kommo
FAQs
The agent uses Kommo's Create Lead endpoint, passing the pipeline_id and status_id fields to place the lead in the correct pipeline and stage. It retrieves available pipelines and stages via the List Leads Pipelines and List Pipeline Stages endpoints, then matches the prospect's qualification answers to your configured routing rules to determine the right placement.
The agent connects via OAuth with read and write scopes. It does not require admin privileges. A standard Kommo user account with permissions to create and update leads, contacts, companies, and tasks is sufficient. The OAuth token is scoped to your subdomain and can be revoked anytime from Kommo's integration settings.
Yes. Kommo's API supports custom_fields_values on leads, contacts, and companies. The agent passes custom field updates as an array with field IDs and values. This allows it to capture information like 'industry,' 'product interest,' or 'budget range' from the conversation and map it directly to your Kommo custom fields.
No. Tars queries Kommo's API in real time during conversations. Contact details, lead information, and company records are fetched live and used only to personalize the current interaction. No CRM data is cached or stored on Tars servers outside of conversation transcripts governed by your retention settings.
Yes. The Create Task endpoint accepts a responsible_user_id field. The agent can assign tasks to specific reps based on routing rules you define, such as round-robin, territory, or deal size. It can also set task type, deadline (complete_till), duration, and link the task to a specific lead or contact entity.
Kommo's Salesbot operates within Kommo's messenger integrations using predefined automation flows. Tars AI Agent uses large language models to hold genuine conversations, understand nuanced questions, and dynamically qualify leads based on context. It also works across channels beyond Kommo's native integrations and connects to 600+ other tools.
The agent can query existing leads by contact name, email, or custom field values using the List Leads endpoint. If a match is found, it updates the existing lead's stage, price, or tags instead of creating a duplicate. You control whether the agent merges or creates separate leads based on your business rules.
Yes. The List Leads endpoint supports filters for pipeline IDs, status objects, price ranges, responsible user IDs, creation dates, and custom field values. The agent can retrieve 'all leads in the Enterprise pipeline above $10,000' or 'leads updated this week assigned to Sarah' and summarize the results conversationally.
Don't limit your AI Agent to basic conversations. Watch how to configure and add powerful tools making your agent smarter and more functional.

Privacy & Security
At Tars, we take privacy and security very seriously. We are compliant with GDPR, ISO, SOC 2, and HIPAA.