Frequently asked
questions.

Yes. The web editor is free: proofreading, explanations, and word lookups, with no card required.

By organization size and deployment model (cloud, sovereign cloud, or on-premises). Book a demo and we will scope it with you; government and education have dedicated tracks.

Yes. Every surface is included: Office add-ins, browser extensions, Google surfaces, the Windows app, and the API and SDK.

Paraphraser, Summarizer, Expander, Tashkeeler, Humanizer, AI Detector, Email Writer, and AI Chat, all inside the editor's AI panel. Agents that transform text work on your selection or the whole document.

No. Every agent produces a suggestion attached to the text it would change. You review it, then accept, copy, or ignore it. If the document changed while the agent was working, the suggestion is skipped rather than misapplied.

Through AI credits included in paid plans. Each request is checked against your balance before it runs, so usage is predictable for individuals and administrable for institutions.

The engine distinguishes 12 error classes, surfaced in the editor as 8 color-coded categories: spelling, grammar, morphology, semantics, style, punctuation and formatting, proper names, and institutional style guide violations. Sub-checks include quotations, dates, and numbers.

On the company benchmark sentence, Microsoft Word flags 2 errors; WriteX flags 6, each with the grammatical rule explained. Arabic morphology and semantics are simply not modeled by generic checkers.

Yes. Guides are assigned to team members, so the newsroom, legal, and social teams each write under their own rules, while admins manage everything from one screen.

Each guide starts from a national writing standard (for example Saudi Arabia's official conventions) and you override from there, so you configure only what makes your institution different.

The paraphraser is built to preserve meaning while changing form. You always see original and suggestion side by side, and nothing is applied until you accept.

Yes. The institutional dictionary and name lexicons let you register executives, brands, and place names so they are enforced exactly as approved, and never flagged as errors.

Yes. Arabic corrections explain in Arabic grammatical terms; English corrections explain in plain English. The interface itself is bilingual.

Yes. Dashboards export to reports for management reviews, and the same numbers are available per team and per writer.

No. Writers see their own statistics; managers see team and organization rollups according to the roles your admin configures.

From Microsoft AppSource, or directly inside Word, PowerPoint, and Outlook via the built-in add-in store. Search for Lisan, sign in, and the task pane is live.

Yes. The REST API takes text and returns classified corrections; the JavaScript SDK embeds live checking in your own web systems. Both are available on institutional plans.

Both. The engine detects the language per passage and applies the right rule set, so bilingual documents, common in Gulf institutions, are fully covered.

A shipped Spanish writing assistant (web app, Chrome extension, Word add-in), purpose-built Spanish correction and NER models, tone and formality technology, and the team behind them. Spanish support in WriteX is built on that foundation.

Yes. The engine is language-modular, and the roadmap adds languages based on institutional demand.

No. The on-premises deployment keeps documents, models, and analytics inside your network. Updates are delivered as packages your team applies on your schedule.

Yes. White-labeling is available for institutional deployments; the Saudi Electricity Company runs its customized copy as Faseeh.

No. The engine is Lisan's own Relay Architecture: 32 specialised AI components developed in-house, which is why it runs on-premises, responds in real time, and explains every correction.

Yes. Sign in with your Lisan account anywhere; your style guides, dictionaries, and statistics follow you.

Office add-ins and browser extensions deploy centrally via your management tooling, and the engine itself can run on-premises. Your IT team gets a deployment guide during onboarding.

Yes. The full engine deploys on-premises, including models and analytics, and is efficient enough to run without GPU infrastructure.

Deploy the Office add-ins and browser extensions centrally, assign style guides to teams, and manage everything from the admin console. The engine scales horizontally; the SDK covers your internal systems.

Yes. The browser extensions check any web text field, and the SDK embeds the engine directly in a custom CMS with your style book attached.

Institutional education plans exist for universities and schools; contact us with your cohort size and we will quote accordingly.

Technically yes, but teams consolidate quickly: one engine, one style guide, and one analytics view across all three languages beats maintaining two subscriptions.

No. WriteX is a Word add-in from AppSource: a task pane beside your document with the full engine behind it.

Yes, and they often do: teams draft with an LLM, then run WriteX as the compliance and correctness gate before anything is published or sent.

Yes. Text you type here is checked by the same WriteX engine that serves app.lisan.com; the suggestions and explanations are its real output, not a canned demo. The page demo is capped at 1500 characters; the full editor has no such limit.

No. The demo passes your text to the engine for checking and returns the suggestions. Nothing you type on this page is saved to a document or used to train anything.

The on-page demo checks Arabic, WriteX's flagship language. The full editor also corrects English at sentence level and Spanish through the Correcto models; start free and try all three.

Umm al-Qura, the civil calendar of Saudi Arabia, via the browser's built-in Intl engine. Religious observance based on moon sighting can differ from the civil calendar by a day.

Literally 'and nothing else': the traditional closing on cheque and contract amounts that prevents anything being appended to the figure.

The letters stay identical, but ambiguity returns: عَلِمَ and عُلِمَ both become علم. If you need the reverse, selective tashkeel that marks only ambiguous words, that is a WriteX writing tool.

No. Diacritics attach to their word under Unicode word rules, so a fully vowelled word counts exactly once, and character counts include the marks only in the character total.

Full tashkeel vowels every letter, which suits teaching material and speeches. Selective tashkeel marks only the words a reader could misread, keeping ordinary prose clean. WriteX offers both as one-click transformers.

Arabic builds words from roots and patterns, so a word can be spelled plausibly yet built wrongly, like an incorrect plural pattern. Spelling lists cannot catch that; morphological analysis can.

It is WriteX's headline quality score: the share of text free of detected errors, tracked per writer, team, and organization in the analytics dashboards.

WriteX is Lisan's AI writing assistant: an educational proofreader that checks Arabic, English, and Spanish across 12 error types, enforces institutional style guides, and reports language-quality analytics. It runs in a web editor, Microsoft Office, browser extensions, Google Docs and Gmail, Windows, and via API and SDK.

The web editor has a free tier so anyone can start writing immediately. Institutional plans add style guides, team analytics, admin controls, and deployment options; contact us for a demo and pricing.

Arabic is the flagship, with the deepest coverage anywhere: spelling, grammar, morphology, semantics, tashkeel, and named entities. English includes sentence-level correction. Spanish joined through the Correcto acquisition, with purpose-built Spanish correction models.

Chatbots rewrite text and cannot tell you why. WriteX classifies each error, shows the rule behind the fix, keeps your text under your control, and can run entirely on your own infrastructure. It is real-time, explainable, and auditable.

Yes. WriteX deploys to the cloud, sovereign clouds, or fully on-premises, so ministries and enterprises keep every document inside their own perimeter. The engine is efficient enough that no GPU farm is required.

Yes. The web editor is free to start: open it, paste text, and see the corrections immediately. Institutional features like style guides and analytics are demonstrated in a guided demo; book one from the contact page.

Yes. The engine detects the language per passage, applies the right rule set, and the interface itself is bilingual with full RTL support.