مورق
Docs
Documentation that assumes you're about to ship
Everything you need to take a NOOR from “interesting†to “liveâ€: setup, the API, how agents are configured — and exactly how the safety layer works, because that's the part you'll be asked about.
Getting started
Workspace setup
Create a workspace, invite your team, and set your timezone, languages, and support hours. ~15 minutes.
Your first agent
Name it, describe its job in plain language, pick its channels, and deploy a supervised test agent to your team only.
Approved facts onboarding
The part that makes NOOR trustworthy: turn your price sheets, room lists, and policies into the facts the agent may assert. We do it with you, not for you.
Shadow week
NOOR drafts, your team approves. One week of side-by-side before any customer-facing handover.
Going live
Flip the switch per flow. Monitor the handoff queue. The dashboard is your cockpit.
Quick check
curl -X POST https://api.noor.sa/api/agents \ -H "Authorization: Bearer $NOOR_TEST_KEY" \ -d '{ "name": "Front Desk", "channels": ["whatsapp"], "facts": "facts:nakheel-rooms-v3", "templates": { "recorded": "tpl:recorded-ar-en", "forward": "tpl:forward-ar-en" }, "escalation": { "on_intent": ["complaint", "legal", "media"], "to": "frontdesk@yourbusiness.sa" } }'API reference
POST /api/agents
Create an agent: persona, channel assignments, facts list IDs, mandatory reply templates, escalation rules.
POST /api/agents/:id/test
Send a test message to a supervised agent without touching real channels.
GET /api/conversations
List conversations with filters: channel, agent, time range, status, and extraction fields.
POST /api/conversations/:id/resolve
Human takes over / marks resolved with a note; the note is prepended to the customer's next message.
GET /api/analytics/digest
Weekly digest: volume by channel, resolve rate, escalation reasons, top questions.
Webhooks
conversation.recorded, conversation.escalated, booking.recorded, booking.confirmed, agent.updated. Signed with your workspace secret.
Agents
Persona & tone
Described the way you'd brief a new hire: name, role, register, language lock, and the one sentence a stranger should recognize as you.
Approved facts
Structured or plain text. The platform checks every factual assertion against this list before a reply is sent. Outside the list → your forward script, verbatim.
Mandatory reply templates
For outcomes that matter (recorded, forwarded, declined, out-of-list): you write the exact words, in both languages, and the platform sends those words.
Escalation rules
Keyword-based, sentiment-based, or intent-based. Every escalation carries the full context: transcript, extraction, and the last three replies.
Security
Data handling
Encrypted in transit (TLS 1.3) and at rest. Access scoped per team member with role-based permissions. Export and deletion available on request, at any time.
Retention
Your policy, your controls: configurable retention per workspace, from 30 days to your records requirement. Legal holds supported.
Model boundaries
Conversations are processed in-region. We do not resell your data and do not train shared models on it without explicit, written, per-workspace consent.
Compliance review
Enterprise customers get our security documentation pack, DPA, and the rule-layer architecture walkthrough for your auditors.