Every module, one platform

What a "module" means in SaleInline

In most CRM suites a "module" is a product boundary: a separate app with its own price, its own data store and an integration layer in between. You notice the boundary when a contact exists in two places with two different phone numbers, or when a permission you set in one place does not apply in another.

In SaleInline a module is a screen and a set of permissions over shared data. There is one contact record, one owner field, one activity history. The inbox module and the phone module are different views onto the same conversation history; the finance module reads the same deals the pipeline module writes. This is why turning on a module never requires a migration or a mapping exercise — there is nothing to map.

The practical test is what happens when a customer calls about a quote you sent last week. In a stitched-together stack you open the phone tool to answer, the CRM to find the quote and the shared inbox to check what was agreed on WhatsApp. Here all three are the same screen.

The twelve modules at a glance

Each links to a page describing it in detail.

There is also a work-time module covering shift calendars, clock in/out and break tracking, which feeds the lead response-time report described below.

How the modules connect

The value is in the joins, not the individual features. These are the connections that matter most in daily use:

Inbox → lead

A WhatsApp, Instagram or Messenger message from an unknown number creates a lead, normalises the phone number to E.164 so the same person is not stored three ways, checks for duplicates and assigns an owner round-robin among the agents on that channel.

Phone → lead → report

Every call made or received in the browser softphone is logged against the lead with its duration, disposition and recording. Those logs are a dataset in the pivot report builder, so "calls per agent per outcome" is a report you build, not a request you file.

Deal won → stock → expense → commission

Marking a deal won deducts the attached products from stock, writes the cost of goods as an expense, and calculates the salesperson's commission as a flat amount or a percentage. Deal profitability then shows margin rather than revenue.

Stage change → automation → task or message

Moving a lead or deal to a new stage can create a follow-up task, send a WhatsApp or email, update a field — including relative dates like "three days from today" — or notify a manager.

Shift calendar → response time

First-contact and first-reply timestamps are subtracted against each person's working hours, so response time is measured in working minutes. A message at 23:40 answered at 09:12 counts as 12 minutes.

Department chart → every module

The org chart decides whose records each person can open, and that scope applies identically in leads, deals, the inbox, the phone log, reports and finance. You set it once.

The underlying data model

Knowing how the data is shaped makes the modules easier to reason about, and it is short:

• Contact — a person, with a canonical E.164 phone number. Everything else hangs off this.
• Lead — an enquiry from a contact, on a pipeline, at a stage, with an owner and a score.
• Deal — a qualified opportunity, on its own pipeline, with products attached and a value.
• Activity — messages, calls, notes, appointments and field changes, in one timeline.
• Custom fields — added per entity, of type text, number, date, list or checkbox, usable as filters, automation conditions and report dimensions. Country and language are system fields derived from the phone country code, filled only when empty so your manual edits survive.

You can run several pipelines side by side — for example one for new business and one for renewals — each with its own stages, and move records between them in bulk. Lead detail layouts are configurable per role, so a manager and an agent can see the same record arranged differently.

What SaleInline connects to

Integrations are built in rather than bought from a marketplace:

• WhatsApp Business — two-way messaging on your own number, images included, with round-robin distribution per channel.
• Instagram Direct and Facebook Messenger — through the official Meta integration, in the same shared inbox.
• SIP telephony — a line from us, or the line you already have with your existing provider bridged to the browser.
• Email — outbound notifications, sequences and campaigns, plus event-based automatic mails for assignments, quotes, tasks and appointments.
• SMS — available as a gateway add-on for reminders and automation messages.
• Inbound webhook — a URL that creates leads from ad platforms or your own site, including custom-field values and automatic source creation.
• Bitrix24 import — leads, contacts, deals, products, custom fields and history, resumable and idempotent.
• CSV — import and export for leads, products and reports.
• API access — available on the Enterprise plan.

Because the messaging and telephony integrations are native rather than brokered through a marketplace connector, there is no third party sitting between your customer and your database. A WhatsApp message does not travel through an automation service before reaching the lead record, and a call does not depend on a connector staying authorised. That matters less on the day you set it up than on the day something breaks: there is one place to look, and one party responsible for it.

The integrations that are not built in are handled the way most teams actually need them — by the inbound webhook for anything that can send an HTTP request, and by CSV for anything that cannot. Between those two, most ad platforms, landing-page builders and legacy systems can feed SaleInline without custom development work.

How far you can customise it

Most of the shape of the system is yours to set without asking anyone:

1. FieldsAdd custom fields to leads, deals and products in five types, mark them required, and use them everywhere — list columns, filters, automation conditions and report dimensions.
2. Pipelines and stagesCreate separate pipelines for different sales processes, name your own stages, and require specific fields before a record can move forward.
3. LayoutsBuild several lead-detail layouts, decide which sections and tabs appear, and assign a layout per role.
4. AutomationsEleven triggers and fifteen actions, combined per stage or across the whole workspace, with a log showing what fired and what it changed.
5. Views and reportsSave filter combinations as personal or shared views, and build pivot reports across leads, deals, tasks, calls and products.
6. PermissionsSet create, read, update and delete rights per module, then layer the department hierarchy on top to decide whose records are visible.

What you cannot change without us is the underlying schema — you are configuring a CRM, not building one. In practice the limit people reach first is usually a reporting question that needs a field nobody created yet, which takes a minute to fix.