The questions we hear before someone signs up.

CRM, LinkedIn prospecting, a shared email and SMS inbox, scheduling, and workflow automation — one composable workspace instead of six disconnected tools.

Sales teams and revenue operations who prospect on LinkedIn, run outbound across multiple channels, and need the resulting activity to land in one CRM record instead of scattered across separate tools.

A typical stack of a CRM, a LinkedIn prospecting tool, an email sequencing tool, a shared inbox tool, and a calendar-booking tool — LexisOS runs all five as one connected system.

Both, genuinely. Leads, Contacts, Deals, and Vendors are full CRM record types with custom fields, configurable pipelines, and saved views, and LinkedIn prospecting and actioning are built on top of that same CRM, not bolted on separately.

LexisOS installs as a Progressive Web App with offline support for notes, tasks, and tags that syncs once you're back online — there is no separate native app-store app.

Through a paired Chrome extension that calls LinkedIn's own API from inside your already-logged-in browser tab, using your session. It is not a headless scraper and it does not read LinkedIn's page HTML.

All ten: connect, message, like, comment, post, visit profile, follow, unfollow, withdraw invite, and endorse skill. Connect and message can also run through your stored session server-side; the other eight run through your paired browser by design.

That is your choice, made per step. Set a LinkedIn, email, or SMS step to require approval and the workflow holds the message as a Draft and pauses until a person signs off. Set it to send automatically and it goes out under your account's daily and weekly caps.

Admin-configurable daily and weekly caps per action type, enforced at the moment a job is claimed, and routing eight of the ten action types through your own paired browser session rather than an unattended server call, which is the higher-risk pattern LinkedIn watches for.

AI generation for drafting — emails, LinkedIn messages, SMS, workflow content — runs on Anthropic exclusively. Separately, LexisOS's semantic search over LinkedIn profiles uses OpenAI embeddings and a Pinecone vector index, which is a distinct, real dependency alongside Anthropic — the two shouldn't be conflated.

No. Every send that a workflow drives — email, LinkedIn message, or SMS — is inserted as a Draft, and the workflow run itself pauses and waits until a person acts. That pause is enforced by the workflow itself, not by a setting that can be silently switched off.

Everyday chat and read-only questions run on a self-hosted local model. If you ask it to make a change to your CRM, it hands off to Claude to draft the exact proposed action, which then waits for your explicit approval before anything executes — nothing acts on its own.

Yes. An organization can bring its own Anthropic API key, or use a platform-default key under a monthly spending cap an admin sets.

No. Scoring is a transparent, admin-defined table of point values per event type — a stage change, a tag added, an email reply — that an admin can see and edit directly. It is not a predictive model.

Every stored credential — mailbox tokens, CRM tokens, LinkedIn session data — is encrypted at rest using a key derived specifically for your organization, so it can never be decrypted using another organization's key.

Yes. CSV/Excel import with explicit column-to-field mapping you control, up to 50,000 rows per import.

Yes. Files stored in WorkDrive can be opened and edited as real .docx documents directly in the browser, with autosave and conflict detection if a teammate has changed the file since you opened it.

Zoho CRM and HubSpot, both two-way: push individual records out, pull whole modules back in, with field mapping and a conflict-resolution log.

Yes. LexisOS runs a real external MCP server with 248 tools across 24 categories and genuine OAuth 2.1 authentication, so an MCP client like Claude Desktop can read and act on your CRM data directly, with every write audit-logged.

Yes — a two-way team SMS inbox with MMS, scheduled sends, and consent tracking, plus browser-based outbound calling with recording playback. Both run on your own Twilio account.

Yes. LexisOS doesn't sell or provision phone numbers — you connect an existing Twilio account and LexisOS syncs and shares the numbers on it.

Yes — a drag-and-drop builder for both single forms and full landing pages, with conditional field logic, A/B variant testing, and progressive profiling for returning visitors as separate add-ons. Published forms get a hosted URL, and you can point your own custom domain at one.