May 1, 2026 • 6 min read
Most platforms that ship a "suite" make you adopt all of it. You wanted the CRM, but to get the CRM you also need their email tool, their helpdesk, their phone system, and a long onboarding for departments that didn't ask to be onboarded.
Slokoto is built differently. We ship three products, Sales, Support, and Communication, and each one is designed to work on its own. Pick the one your team actually needs. The rest is opt-in.
Here is the rule we hold ourselves to.
Slokoto Sales Works Without Anything Else
Slokoto Sales is a complete sales product on day one, with or without the rest of the platform.
That means it has its own native ways to bring leads in, route them, and move them through a pipeline. None of those depend on Support or Communication being enabled.
The native sales intake is everything you would expect from a real CRM:
- •A native CRM record with leads, contacts, accounts, and deals
- •Inbound email parsed straight into leads (no third-party connector required)
- •Web forms and lead capture, including AI-generated forms from your own marketing site
- •Manual lead creation for the rep who just got off a hallway conversation
- •Bulk imports from spreadsheets or another CRM you are migrating away from
- •API ingestion for your own integrations
Pick any of those, ignore the rest. The pipeline, the routing rules, the AI follow-ups, the templates, the reporting, all of it works the same regardless of where the lead came from. A team that wants Slokoto only as a CRM should never feel like they are running a half-empty version.
Slokoto Support Works Without Anything Else
Slokoto Support is the same idea on the support side.
It has its own native ticketing, its own intake channels, and its own workflows. You can run it without ever turning Sales on, and without ever turning Communication on.
The native support intake is the full set of channels a support team actually uses:
- •A native ticket model with statuses, queues, SLAs, and escalations
- •Inbound support email parsed into tickets
- •Customer-facing forms and contact pages
- •Manual ticket creation for the agent on the phone or in the hallway
- •Future channels we add (chat widget, knowledge base deflection, etc.) plug into the same ticket model
A support-only customer should be able to run a complete support operation, dispatch tickets, hit SLAs, escalate, report, without buying or enabling Sales or Communication. Support is not a side feature of a CRM. It is its own product.
Slokoto Communication Works Without Anything Else
Communication is the third product, and it is the easiest one to mis-describe. It is not "the dialer for the CRM." It is a standalone communication platform.
That means it has its own native primitives:
- •Calls (inbound, outbound, browser-based, queues, IVR, recording, transcription)
- •Chat
- •A unified inbox
A team can adopt Slokoto Communication purely as a calls/chat/inbox platform with no CRM and no helpdesk attached. It gives them a complete way to talk to customers and capture those conversations.
If you only want a phone system that does not lock you into a CRM, you can stop here.
When Two Products Meet, Communication Becomes a Bridge
This is the part that matters for teams running more than one Slokoto product.
When you turn Communication on alongside Sales or Support, it does not stop being a standalone product. It gains an extra role: it becomes an optional shared intake source and handoff provider for the other products.
In practice that means:
- •An inbound call into Communication can create or attach to a lead in Sales, if the workspace has Sales enabled and the user opts in
- •A chat conversation can open a ticket in Support, if Support is enabled and the user opts in
- •A rep on a Sales record can place a call through Communication without leaving the record
- •A support agent on a ticket can hand the conversation off to Sales (or vice versa) through a single shared identity for the customer
The keyword in every one of those sentences is optional. Communication never silently writes into Sales or Support. The bridge is something a workspace turns on, and it can be turned off without breaking either side.
If you only have Communication, the bridge code is dormant. If you have Sales but not Communication, Sales still has its own native intake and works perfectly. If you have all three, Communication becomes the connective tissue, never the dependency.
Why This Matters
Three reasons.
1. Honest pricing. You pay for what you use. A support team should not subsidize a sales feature they will never enable. A sales team should not be forced to license a phone system to get a working CRM.
2. Honest adoption. A pilot in one department does not require buy-in from the other two. The Sales team can ship Slokoto Sales next month. Support can take six more months to evaluate. Communication can be a separate decision entirely.
3. Honest engineering. Forcing yourself to ship every product as if it has to stand alone is a brutal but useful constraint. It kills the lazy assumption that "the other product will provide that." If Sales needs a contact identity, Sales has to own it. If Support needs SLAs, Support has to own them. The result is three real products, not three thin shells around a shared monolith.
What This Is Not
This is not a story about three products that secretly need each other.
It is also not a story about three products that pretend the others do not exist. They are clearly part of one platform. The same workspace, the same identity model, the same admin surface, the same billing. When you turn on more than one, they cooperate gracefully.
What it is, is a promise: every Slokoto product is a complete product on its own. We will not ship a feature in Sales that secretly requires Support. We will not gate basic Support workflows behind Communication. We will not pretend that adopting one means committing to the others.
You bought a product. You should get a product.
What's Next
Over the next few months we will be writing more posts about each product individually. Use the filter at the top of the blog to see only the product you care about, or hit "All Posts" to see everything.
If you want to start small, that is exactly the point. Pick one. The rest will be there when you are ready.