What an organisation gets
One knowledge layer for every team,
and every agent you run.
Ishara joins the market outside with what your teams already know, then gives people, models and agents the same context, each under the access they have been given.
Private context across the organisation
Email from Google Workspace and Microsoft 365, meetings and calls in Arabic and English, WhatsApp Business conversations, files and CRM records, resolved into people, decisions and next steps. Each thread and call keeps its own visibility.
Private context →
Agent access at scale
The Context API and the MCP server give your models and agents the same context, one scoped key per agent or integration, every read logged with its purpose, and changes wait as proposals for a person to approve by default.
Agent access →
The market already inside
1.2B people profiles and positions, 17M companies covered and 32,822 investors in the directory, with government tenders across Qatar, Bahrain, Saudi Arabia, Kuwait, Oman and the UAE.
Market intelligence →
Coverage scoped to your work
The markets, sectors and buyers your teams follow, and the signals each team needs to hear about, set up with you.
Signals →
Onboarding with our team
Records, owners and notes brought in from your current CRM or spreadsheets, roles and access rules set with your admins, and teams invited when their part is ready.
Imports →
A security review that gets answers
Clear answers to the questions a review asks first, below, and your questionnaire answered in writing.
Security and trust →
Security answers
The questions your security review asks first
Is our data used to train models?
Your private context is supplied at the moment of a request and is never used to train models.
Who can see what?
Each workspace is isolated in the database itself. Four roles, from owner to viewer, decide what members can do, and every email thread and call carries its own visibility: only me, the people on it, my team, or everyone.
What can agents reach?
Only what the key's owner can see, narrowed by its scopes. Agents propose changes, a person applies them, and an administrator can switch context sharing off for the whole workspace.
Does WhatsApp mean personal chats?
No. An admin connects your WhatsApp Business account. Ishara brings in its business conversations, never personal chats.
Where does our data live?
On Ishara's own dedicated database stack, separate from other Lisan products, with TLS on every connection and nightly backups. The hosting region and the sub-processor list are available on request.
Can we leave with our data?
Yes. Every view exports to CSV and the whole workspace exports to a spreadsheet. Nothing is deleted when a plan ends, and there is no exit fee.
Every control is on the security and trust page. Questionnaires and specific questions go to our team by email.
Rollout
From walkthrough to working teams, in three steps
Ishara is in early access. For an organisation, it starts with a conversation about your teams and your rules, before anyone connects a mailbox.
- 1
Scope it togetherA walkthrough with your team: the markets you work in, the teams who will use Ishara, the systems you run today and the questions your security review asks.
- 2
Connect, under your rulesYour admins set roles and access rules first, then connect mailboxes and calendars, a WhatsApp Business account and your CRM records and files.
- 3
Open it to teams and agentsInvite each team when its part is ready, issue scoped keys for your agents and integrations, and decide what an agent may propose.