Remote sales department on Kommo CRM

A remote sales department isn't an office that moved home. It's a different management model. The distinction isn't geography — it's what you actually control. A classic manager controls the process: showed up on time, sitting at their desk, looks busy with something. A remote manager has no access to the process at all. They control the result.

For international teams selling cross-border, this shift is the entire game. Your team is scattered across three to five time zones. Your customers pay in dollars. The "control by presence" model is physically impossible, and forcing it onto a remote team anyway is the number-one reason these teams fall apart in the first year.

The one shift: process vs. result

Remember this single distinction — it changes everything downstream:

• Classic sales team: control the people.
• Remote sales team: control the results.

Once you start looking at results instead of presence, half your management rituals disappear. The daily 9:00 stand-up, the "what did you do today" report, the explanations for being late — all gone. They get replaced by a single public scoreboard: how many leads handled, how many deals advanced, how much money each person brought in by Friday. The numbers either exist or they don't, and there's nothing left to discuss.

That discipline arrives with infrastructure, not with rules. The next sections cover how to build it.

When remote beats office in dollar terms

Rough comparison for a typical international SaaS team:

Where office still wins: enterprise deals with long cycles where the team needs whiteboard brainstorms; sales academies for new reps who need daily in-person coaching; showroom sales where you physically meet the customer. For everything else, remote is cheaper, faster, and gives you a wider hiring net.

Infrastructure: Kommo, WhatsApp Business API, team channel

CRM — Kommo

This is the central hub. Deals, contacts, conversation history, manager tasks, reports — all in Kommo. International billing, no regional restrictions, broad partner ecosystem. For an international cross-border team this is the cleanest option in the SMB-to-mid-market range.

Customer channel — WhatsApp Business API

For international B2B, WhatsApp is the default messaging channel — connected through a certified Business Solution Provider (BSP), not through unofficial scrapers (which Meta blocks within 2–8 weeks on average). Telegram is still relevant for the post-Soviet segment, but as a sole channel it doesn't work — European and LATAM customers barely use it. Email remains essential for heavy documents and longer B2B threads.

If your customers speak multiple languages

A five-person team doesn't cover six languages. That's where a separate layer kicks in — automatic translation of every conversation inside Kommo. AnyLinga does exactly that: your rep writes in their language, the customer reads in theirs, neither side has to think about it. This decouples hiring from language: you don't need multilingual reps anymore, you need reps who can sell.

Internal team channel

Slack, Telegram, or Discord — whatever stuck. One rule: one topic, one channel/thread. No "side conversations" in DMs. When everything is public, a new hire is up to speed in a day instead of a month.

IP telephony — optional

If customers actually call you (inbound ads, support lines), wire up Zadarma, MyAsterisk, or a local provider from your main market's country. If all inbound is via messengers and forms, skip telephony — don't pay for what the team won't use.

Hiring across borders (contractors, not employees)

The typical hiring process for an SDR or account manager on an international team:

1. Role profile (1–2 pages)

Spell it out concretely: what the role owns, what the KPIs are, which tools they need to know, which time zones they have to overlap with, what the rate is, and what the commission structure looks like. State the currency (USD/EUR), payment rails (Wise / Deel / Payoneer / SWIFT), and the contract jurisdiction up front. Without this, you waste time on candidates who fall off at the first call.

2. Sourcing channels

• LinkedIn — primary for English-speaking, Western-market-focused candidates.
• Upwork / Toptal — for project-based work or a paid trial task before the full offer.
• Local job boards per region — much higher signal than the global aggregators in any one country.
• Community Slack/Discord channels in your target industry — best for senior candidates.
• Referrals from your existing team — by far the best channel once the team exists.

3. Trial period — 5–7 days, not two months

One week of real work shows you everything. The candidate either sells in your niche or they don't. Long trial periods are a leftover from the office era, when you paid for time and assumed two months would pay back later. On remote, you pay for results from day one — and one week of real calls or meetings gives you either decent conversion or none. The decision becomes cheap.

4. Contractor onboarding

Standard path: your company (Estonia OÜ / UAE FZ / Cyprus Ltd / US LLC / local sole prop) signs a service agreement with the contractor. Payments via Wise (low fees, multi-currency), Deel (if you want automated compliance across dozens of countries), Payoneer (popular in LATAM), or SWIFT (when amounts are large and the recipient can wait a week).

Pay for results, not hours

Concrete compensation structures that work on international teams:

Remote SDR (cold caller / appointment setter)

• $5 per call that reached a live conversation (not voicemail);
• $25 per qualified appointment (customer agreed to a meeting with an account manager);
• optional $200/month base for those who want a floor.

Monthly total for a top SDR: $1,800–2,800. For the bottom tier: $300–600 — and they self-select out, because that doesn't cover rent anywhere reasonable. This is self-regulating.

Account manager (closer)

• 5–10% of the signed contract value (depends on product margin);
• optional $500–1,000/month base;
• renewal/upsell bonus separately: $50–200 per renewal.

A top closer in international SaaS easily clears $4,000–8,000/month. When you see those numbers, that's the right person.

Head of sales / team lead

Here pure "pay for results" breaks down — a team lead's commission shouldn't be on their own closes, it should be on team performance. Typical structure: $2,000–3,500/month base + 1–2% of team revenue. The lead is incentivized to raise the team, not to close personally.

Control without surveillance

Three Kommo widgets that make this kind of control visible:

Activity Panel — live team activity dashboard

Activity Panel shows every manager with rolling counters: calls, chats, tasks, deal-stage transitions — today, this week, this month. One look tells you who's actually working, who's faking, who's having a slow day, who's on a streak. It's the same activity report that used to come on paper Friday afternoons — except this one is live, refreshing on every Kommo event.

Peresmenka — who's on shift, across time zones

When your team is in four or five time zones, a simple question like "is anyone available right now for an inbound lead from Singapore?" gets non-trivial. Peresmenka tracks which managers are currently on shift, and routes incoming leads only to those who are online. When someone goes off shift, their active deals get reassigned automatically.

SLA First Touch Control — speed of first reply

In international sales, the time to first reply after a lead lands often decides the conversion. SLA First Touch Control measures the gap between lead assignment and the first real touch (call / message / email), calculating with the rep's working hours and time zone in mind, and flags violations. When a team sees its own response times in public, those times start coming down on their own — no enforcement needed, just the visibility of the metric.

Seven common mistakes when building a remote sales team

1. Hiring first, then figuring out what they should do. No infrastructure means no point hiring. Kommo + WABA + team channel + playbooks ship first; the first hire ships after. Otherwise they'll chase you with "where do I find leads?" questions while you try to do your actual job.
2. Long trial periods. Remote is good precisely because there are many candidates and you can evaluate fast. Five to seven days of real work. Anything longer is you burning resources on people who already showed they don't fit.
3. Paying for time instead of results. Salary for "8 hours on remote" = a paid promise to look busy. If you want a base salary in the structure, fine — but anchor it to a minimum KPI ("base pays out at 80% of monthly call target hit").
4. No written playbooks or scripts. If a new hire has no documentation, they will ask you the same question every day for a month. Write the playbook once; from then on, the team reads it.
5. Only contacting the team when something's wrong. A remote contractor whose only interaction with you is "you missed again this week" will quit within three months. Run a weekly all-hands call; walk through wins, ask for ideas, give recognition. This isn't for the contractors — it's for the team holding together as a team.
6. Applying full-time-employee logic to international contractors. A contractor isn't a salaried employee. Don't pay them for "sick days," don't issue them "vacation time," don't count "seniority." It's a different relationship; your job is to pay for delivered work, their job is to deliver it. Social benefits sit on their side (they pay their own taxes and insurance in their own jurisdiction).
7. One time zone for every team meeting. A team in four or five time zones with a "global all-hands at 10:00 Dubai time" means 2:00 AM in Bali. Rotate meeting times across zones, or make the critical syncs asynchronous (recorded video + threaded comments). Respecting time zones isn't politeness, it's retention.