Where Israeli buyers actually talk to you.

Ask your CRM anything. Take the draft. Nothing sends itself.

A streaming chat over your CRM data, strictly scoped to what the operator is already allowed to see. It drafts a reply straight into the composer and builds documents, tables and charts on request — but sending is your tap, and every write to the CRM goes through an explicit approval, so no change lands on a record without someone approving it by name.

• Streaming chat over contacts, deals and threads
• Strictly permission-scoped — it sees only what you see
• A draft in the composer — sending is your tap
• Writes to the CRM take an explicit approval, every time
• Works in Hebrew and English
• One question away, on every screen of the desk

Documents, tables and charts — out of a conversation.

Ask the copilot for this week's pipeline summary, a table of unanswered leads or a chart of response times, and the artifact is built live next to the chat from live CRM data. Export it as CSV or PNG and take it into the Monday meeting — or keep going in the chat and ask for a different cut.

• Documents, tables and charts on demand
• Built from live CRM data
• CSV export for the spreadsheet
• PNG export for the deck
• Iterate in chat — "now split it by project"

From first message to signed deal. Drag by drag.

A kanban pipeline where deals move between stages with a drag. Every deal is born from a thread — the bot or an agent opens it — and carries the full WhatsApp history with it, so no conversation starts from zero at the next stage. Pipeline value and stage conversion sit one glance away, and a qualified lead carries on into Aura for the sales floor.

• Kanban board — drag deals between stages
• Deals opened from qualified threads
• Full WhatsApp history attached to every deal
• Pipeline value and stage conversion, live
• A qualified lead carries on into Aura, on the sales floor

One person. One record. However many times they write.

Contacts keyed by phone number, with automatic dedup — the same buyer writing twice does not become two records and two deals. Import your existing list from CSV and Axiom matches, merges and flags whatever looks like a duplicate before it lands.

• Phone-number dedup, automatic
• CSV import with duplicate detection before the write
• Full thread and deal history per contact
• Tags, fields and segments for targeting

One message, a whole audience — and every delivery recorded.

Send Meta-approved template messages to a whole segment, with per-recipient variable substitution and delivery and read tracking one by one. Meta's approval lifecycle is managed inside Axiom rather than on somebody else's screen, and the consent gate stands in front of every send — no consent, no send.

• Meta's template approval lifecycle, managed in-app
• Per-recipient variables — name, project, apartment
• Delivery and read tracking per recipient
• Segmented audiences from contact fields
• A consent gate before every send — no consent, no send
• Replies land in the shared inbox

Design the conversation. No code, and no prompt to write.

A visual canvas for deterministic chatbot flows — messages, buttons, lists, collect-input steps, conditions and handoff nodes. Start from real-estate templates and edit them. And when a flow, an automation and the bot all want the same thread, the flow you wrote wins, every time. This is the surface where you approve in advance instead of approving message by message.

• Visual node canvas — drag, connect, publish
• Buttons, lists and collect-input steps
• Conditions and branching
• Handoff node — route to a person mid-flow
• Starter templates for real-estate scripts
• Deterministic — the flow you wrote outranks the AI

If this, then that — with patience.

No-code automations with triggers, branches, durable waits and actions — each one a rule you wrote, not a decision the system took for itself. New lead? Wait a day and send the follow-up template, unless an agent already replied: an automation does not step on a person who is in the thread. The waits survive a restart and the logic survives a handoff.

• Triggers on messages, deals and contact events
• Branching logic — if / else paths
• Durable waits — hours, days, weeks
• Actions — send a template, assign, move stage, tag
• An agent's reply halts the rule — nobody gets stepped on

Amendment 40 — handled in the architecture, not in the fine print.

A documented consent ledger for every contact, automatic suppression against the Do-Not-Call registry, Hebrew and English STOP and opt-out matching, and a full audit export. All of it is enforced as a hard gate in front of every broadcast — the send button simply will not fire without consent. For an Israeli developer this is not a feature; it is the licence to market on WhatsApp at all.

• A consent ledger — who agreed, when, and on which channel
• Do-Not-Call registry suppression, automatic
• STOP and opt-out matching in Hebrew and English
• A hard gate on broadcasts — no consent, no send
• Audit export for the lawyer, one click
• Built for Israel's Communications Law — Amendment 40