Book a call

Kommo CRM · Messaging & Sales Workflows

Kommo CRM setup for messaging-based sales.

For service businesses, retailers, and ecommerce teams managing assisted sales.

Connect customer conversations with clear ownership and follow-up. We help configure Kommo around your sales process, selected channels, relevant customer data, and the tasks your team needs to manage.

Schedule a meetingExplore the Kommo scope
Inbox · all channels
LGLucía GómezWhatsAppHi! Is the blue jacket in M?
MTMaya TorresInstagramDo you ship to Bogotá?
LPLeo ParkWhatsAppThanks, I’ll check sizes
ARAna RuizMessengerIs the sale still on?
SCSam ColeWhatsAppOk, see you then
LGLucía GómezWhatsApp Hi! Is the blue jacket in M?Yes, size M is in stock. Want me to reserve one?Yes please, I can pick it up Saturday.
Customer context2 past orders · size MStore: Bogotá Centro OwnerDMDiego M. Lead stageNew inquiryReserved · pickup Hold jacket · size MDue Sat · Diego M.
Illustrative sales conversation workflow

A conversation needs context, an owner, and a next action.

Customer messages may reach the team while follow-up depends on individual memory or separate records. We review how Kommo should connect the conversation with the commercial process. The starting point may be a new Kommo setup or an existing account that needs clearer operating rules.

  • No clear responsibility

    Define who receives the inquiry and who continues the conversation.

  • Missing customer context

    Identify the information needed for a useful response and next step.

  • Follow-up outside the process

    Connect a task and review condition with the opportunity stage.

  • Automation that repeats or conflicts

    Review entry rules, active sequences, and the response to a change in context.

Configure Kommo around your sales process and selected channels.

We agree on the information, responsibilities, and actions the team needs before configuring the pipeline or adding automation. Pipelines, channels, users, bots, data, integrations, and ongoing responsibilities are agreed for each project.

  • CRM and customer data

    Define relevant contact information, fields, record relationships, and access.

  • Pipeline and stages

    Set up agreed stages with clear criteria and the information needed to move forward.

  • Messaging channels

    Connect selected channels and define how incoming conversations reach the team.

  • Ownership and follow-up

    Configure agreed responsibilities, tasks, and review conditions.

  • Salesbot workflows

    Build selected rule-based sequences for information gathering and process actions.

  • Integrations and adoption

    Define supported connections, test representative tasks, and prepare the team handover.

Use Salesbot for defined steps, with a clear path to the team.

A selected Salesbot flow can gather useful information, update an agreed field, or prepare the next task.

We define what starts the flow, what information is needed, what can happen automatically, what requires a person, and what changes the next action—including replies outside the expected path, missing information, closure, and other active sequences.

Rule-based Salesbot flows and AI agents are different capabilities. Any AI work requires its own scope, information sources, review, and handoff rules.

Illustrative Salesbot flow Path A · Expected answer Path B · Reply outside the flow

A practical method for conversations, configuration, and adoption.

Measurement runs throughout the work, linking data and process quality with the commercial outcomes the setup is intended to support.

  1. Discover

    Review how inquiries arrive, what the team needs to know, and how conversations become tasks or opportunities.

  2. Define

    Agree on the Kommo scope, stages, data, ownership, workflow rules, and acceptance criteria.

  3. Develop

    Configure the selected setup, connect agreed channels and tools, and test representative paths and exceptions.

  4. Deliver

    Review acceptance, document the configuration, train the team, and hand over ongoing responsibilities.

A documented setup your team can use and maintain.

Licenses, channel charges, integrations, service work, and ongoing support are defined separately.

  • Setup scope: selected processes, priorities, dependencies, and acceptance criteria
  • CRM configuration: agreed data fields, stages, record relationships, and user access
  • Channel and ownership rules: connected channels, responsibilities, and handling of incoming inquiries
  • Salesbot specification, when included: triggers, conditions, actions, exceptions, and the path to a team member
  • Integration record: supported data, mappings, update rules, and responsibilities for selected connections
  • Testing and team handover: task-based checks, outstanding issues, operating instructions, and training

Connect commerce data where it supports the conversation.

When a store connection is part of the project, we define which customer or order information the team needs in Kommo. Supported data and update behavior determine the integration scope.

Measure the process beyond messages sent. Useful checks can include ownership, relevant customer information, follow-up tasks, unresolved conversations, and workflow exceptions. Commercial outcomes need agreed definitions and reliable sources.

Conversation with contextStore data the team needs in the chatIllustrative
Customer chat Hi, can I exchange the shirt for a larger size? Of course. I can see order #1042 — let me check size L.
Lead cardFrom store Last order#1042 · ShippedItemsLinen shirt · MOwnerSales team · AnaNext taskConfirm size exchange · Today
Context supports the reply, not the other way round
Illustrative conversation context

From the Blog

Further reading.

Articles from our blog on the topics this page covers.

View all articles

Questions about Kommo CRM setup.

Businesses and teams managing customer inquiries or assisted sales through messaging. We assess the process, data, and responsibilities to define where Kommo fits.

We can review the current configuration, stages, connected channels, tasks, and bots, then define a practical improvement scope. Access and existing dependencies are part of that assessment.

The scope can include data fields, pipelines, selected channels, ownership rules, tasks, Salesbot flows, integrations, testing, documentation, and training. The proposal defines the components and responsibilities.

We assess the selected WhatsApp connection, account requirements, communication conditions, and team process. Templates, preferences, and the available channel features are part of the setup.

Salesbot supports flows built around defined steps and rules. An AI agent is a different capability with its own information sources, limits, and review needs. It is not included automatically in a Salesbot implementation.

An official integration is available. We assess the supported data, account requirements, update behavior, and changes the connection may introduce to your store before defining the project scope.

Cost depends on the account, process, data, channels, workflows, connections, and training required. Platform licensing, channel charges, and external services are defined separately from implementation.

Check the current offer for your plan, users, billing region, subscription term, and purchase route. The direct subscription and Shopify app offer should be reviewed separately from our service proposal.

Kommo announced its rebrand from amoCRM in 2022. This page uses the current Kommo name.

A connected inbox gives the team access to selected conversations. Useful follow-up also needs defined data, ownership, stages, tasks, and operating rules.

Connect the platform with the work around it.

Define a Kommo setup your team can work with.

Share your current account, messaging channels, and sales process.

We can discuss the configuration, workflows, connections, and handover your business needs.

Schedule a meeting

Prefer to write first? Tell us about your project.

Tell us about your project