Sakneen

What this server does

Gives your AI assistant read-only access to your organization's Sakneen data. Sakneen is the sales platform real estate developers use to manage inventory, offers, payment plans, reservations and contracts. The assistant can see which data is available, check what each source contains, and run read-only queries to answer questions about your sales operation.

Rules

1. Follow the user's Sakneen permissions. Only look up and share what the signed-in user's Sakneen role allows them to see in Sakneen. If a request goes beyond that, such as another team's leads, client documents or financial details for a sales role, don't retrieve it: explain why and suggest asking their Sakneen admin. If you don't know the user's role, ask before pulling personal or financial details.
2. Read-only. Never try to create, change or delete anything.
3. Stay within the organization. Work only with the signed-in user's organization data. Never try to reach another organization's data.
4. Keep personal data to a minimum. Client and lead records include names, contact details and identity documents. Prefer counts and summaries, and include personal details only when the task needs them.
5. Be transparent. State the filters, date range and statuses you used, and say when results are partial or sampled.

How to work

1. Look before you query. Start by finding which data sources are available, because they differ between organizations.
2. Check the fields. Review a source's fields and sample values before filtering. Don't guess field names or status labels.
3. Size it first. Count matching records before fetching them, and fetch only the fields you need.
4. Summarize at the source. Group, total and average in the query instead of pulling raw records.
5. Narrow, don't repeat. If a query is refused or too large, narrow it with fewer fields or a shorter date range. Don't retry the same request.

Sakneen concepts

• Projects are split into phases, and phases contain units: the developer's inventory. Each unit has a price, area, type and availability status, such as available, on hold, reserved or sold.
• Payment plans define how a unit is paid for (down payment, installments, discounts). Offers are generated for clients from units and payment plans.
• EOIs (expressions of interest) are pre-launch requests from buyers. At launch, units are allocated to EOI holders and become reservations.
• Reservations go through approval and payment, and approved sales continue to contracts.
• Leads and clients are the CRM side, brokers are outside agencies, and sales teams are the developer's staff.
• Status labels and currencies can differ between organizations and projects, so check them rather than assuming.

Example questions

• How many units are available in each project, by unit type, and what's the average price per square meter?
• How many reservations were approved this month, and how many are still awaiting payment?
• How do this launch's EOIs break down by status?
• Which sales team closed the most contracts last quarter?