Book a free consultation

The platform

Everything the layer does, and where it stops.

EASM sits across the software you already run and answers, acts and records on top of it. This page is the whole mechanism: what happens to a request, what the four engines do, why the answers can be trusted, and the limits the layer operates under.

Book a free consultation Start with a single request
  • Sits on
    The software you already run
  • Runs in
    Your cloud, private cloud or server room
  • Regions
    Pakistan · UAE · Saudi Arabia
  • Source of truth
    Stays in your systems

    • Step by step

    One request, from arrival to audit line.

    Six steps, always in this order. Nothing is skipped because a question looks simple, and nothing is invented because a system is slow to answer.

    01

    Input

    Something gets asked

    A question, a call, a form, a photo of a document.

    It can arrive on your website, on WhatsApp, over the phone, or from inside a system your staff already use. Whichever door it comes through, it lands in the same layer, so there is one place to look when you want to know what happened.

    02

    AI judgement

    The layer works out who is asking

    Identity first, answer second.

    A member of the public, a signed-in student, a supplier and a member of staff get different things — because they already have different access in your systems. The layer reads that access rather than inventing its own, so nobody sees a record they could not have opened themselves.

    03

    AI judgement

    It finds the relevant material

    Your documents and your live records, together.

    Your approved policies, manuals, price lists and past cases are searched alongside the live state of the relevant record — the order, the account, the application. Both halves matter: the document says what the rule is, the record says what is actually true today.

    04

    AI judgement

    It checks the answer against the source

    If your material does not support it, it does not get said.

    The draft answer is checked back against what was retrieved. Anything the source material does not support is dropped. When nothing supports an answer at all, the layer says it does not know and hands over to a person, rather than filling the gap.

    05

    Action

    It does the thing

    Only the actions you have signed off.

    Booking the slot, raising the ticket, updating the record, sending the confirmation. Each action is a specific, approved call into your system with the parameters checked first. Anything above the threshold you set waits for a person to approve it.

    06

    Action

    It writes down what it did

    Every answer, source and action, kept.

    The question, the material used, the answer given, the action taken and who authorised it are all recorded. Months later you can reconstruct exactly why the layer said what it said.

    Your systemsUnchanged
    • ERP and finance
    • CRM and service desk
    • Student or HR records
    • POS, stock, delivery
    • Document stores
    • Databases and intranet
    The layerReads and checks
    • Works out who is asking
    • Searches your material
    • Reads live records
    • Checks against source
    • Drafts the answer
    • Refuses when unsupported
    What comes outApproved actions only
    • An answer, with its source
    • A booking or a ticket
    • A record updated
    • A confirmation sent
    • A person brought in
    • A line in the audit log

    What runs on top

    Four engines. One layer underneath.

    They share the same index, the same permissions and the same audit trail. Start with one; adding another is configuration, not a second project.

    01 Retrieval

    Knowledge

    Answers drawn from everything your business already knows.

    Policies, contracts, manuals, price lists, circulars and past tickets are indexed once and kept current. Search is both meaning-based and literal, so "what is the refund window" and an exact clause number both land on the right passage. Every answer carries the document and section it came from.

    • NeedsDocuments in any common format, plus read access to the records the answer depends on.
    • Gives youAn answer with its source attached, or an honest "not covered" and a handover.
    1. Your documents
    2. Indexed
    3. Searched
    4. Checked
    5. Answer with source
    02 Speech

    Voice

    Calls answered, handled and closed.

    Phone, WhatsApp and web calls arrive at the same layer, in English or Urdu. The agent works out what the caller needs, looks up the same records your team would, completes the task and confirms it before the call ends. When a person is needed they pick up with the full history already in front of them — the caller never repeats themselves.

    • NeedsA number or WhatsApp line we can route, and the systems the caller is asking about.
    • Gives youA completed task and a transcript, or a warm handover with context attached.
    1. Call comes in
    2. Understood
    3. Records checked
    4. Action taken
    5. Confirmed
    03 Face and document

    Vision

    Faces verified, documents read.

    Staff and students check in by face instead of signing a register. IDs, invoices, forms and receipts are photographed and read straight into the right fields, so nobody retypes them. People are enrolled with their consent and can be removed on request; every check is recorded with time and place.

    • NeedsA camera at the point of check-in, or a phone. Consent records for anyone enrolled.
    • Gives youA verified check-in written to your system, or structured fields from a document.
    1. Photo or scan
    2. Recognised
    3. Details extracted
    4. Written to system
    5. Recorded
    04 Analytics

    Insight

    See what people ask for, and where work gets stuck.

    Every conversation the layer handles becomes usable data. What people ask most, which questions your own documents cannot answer, which steps take too long, which branch keeps hitting the same problem. Updated as it happens, rather than assembled by hand each quarter.

    • NeedsNothing extra. It is produced by the other three engines doing their work.
    • Gives youLive demand, unanswered questions and bottlenecks, by team, branch and channel.
    1. Every conversation
    2. Grouped
    3. Gaps found
    4. Reported
    5. Acted on

    How it decides

    Why you can trust what it says.

    A confident wrong answer is worse than no answer. Six rules govern how the layer reaches an answer, and all six are visible to the person reading it.

    It searches your material, not the internet

    The index holds what you approved and nothing else. There is no general web lookup behind an answer about your refund policy.

    The source travels with the answer

    Each response names the document and section behind it, so the person reading it can check rather than trust.

    Unsupported claims are dropped

    The draft is compared back against what was retrieved. Anything the material does not carry is removed before the answer is sent.

    Not knowing is a valid answer

    When your material does not cover the question, the layer says so and passes it to a person. That is the designed behaviour, not a failure.

    Stale documents get flagged

    When a superseded policy keeps getting cited, it surfaces as a content gap instead of quietly continuing to answer from the old version.

    Private records are never pooled

    Public information and individual records sit in separate indexes. A public question cannot reach into a student or customer file.

    The behaviour that matters most

    When your own material does not answer the question, the layer says so and brings in a person. It is measured on the questions it correctly refuses as much as on the ones it answers — and those refusals are exactly the list of documents you are missing.

    Boundaries

    AI that respects the rules you already have.

    Knowledge, voice and vision all touch real records and real people. That only works if the limits are explicit, so here they are — the same six we hold ourselves to on every deployment.

    Ask us about your requirements
    1. 01
      Your systems stay in charge

      EASM works through your existing applications. It never becomes a second version of the truth, and switching it off leaves your systems exactly as they were.

    2. 02
      People see only what they should

      Access is inherited from your own identity provider and role model. The layer cannot widen anyone’s permissions, including its own.

    3. 03
      It only does what you approve

      Each action is an explicit, named capability you have signed off. Anything outside that list is not available to the layer at all.

    4. 04
      Large actions wait for a person

      You set the thresholds — value, risk, customer tier. Above them, the layer prepares the action and a person confirms it.

    5. 05
      Everything is on the record

      Question, sources, answer, action and approver are all retained and exportable, for audit or for a dispute months later.

    6. 06
      Your data is not training material

      Your documents and conversations are used to answer your questions. They are not pooled with other customers or used to train shared models.

    Integrations

    It connects to what you already bought.

    Nothing is replaced and nothing is migrated. The layer reads live state from your systems and writes back through their own interfaces, the same way your staff do.

    Category Systems we connect What the layer does with it
    Finance and ERP SAP · Oracle · Odoo · Microsoft Dynamics · local ERPs Read live order, invoice and account state; post approved entries.
    Customers and service Salesforce · HubSpot · Zoho · Zendesk · Freshdesk Qualify, log, route and follow up without leaving your pipeline.
    Students and staff PeopleSoft · Moodle · custom SIS · HRMS · payroll Answer from the official record, and write check-ins and applications back.
    Commerce and stock Cloud POS · warehouse and stock systems · e-commerce · courier APIs One view across branches and channels, with dispatch and returns handled.
    Conversation channels WhatsApp Business · telephony and PBX · web chat · email Same layer behind every channel, so context survives the switch.
    Everything else REST and GraphQL APIs · SQL databases · SharePoint and file shares · CSV and SFTP If it has an interface or a document store, it can be connected.

    Deployment

    Runs where your data is allowed to be.

    Some institutions can use a hosted service. Some cannot let a record leave the building. Both are supported, and the layer behaves identically either way.

    • CloudHosted and run by us, in the region you choose. The fastest way to get a first workflow live.
    • Private cloudInside your own cloud account and network. You keep the keys, the logs and the boundary.
    • On premisesOn servers in your building, for institutions whose data is not permitted to leave it.
    • Data residencyRecords stay in the region you nominate. Pakistan, UAE and Saudi Arabia are all supported.
    • IdentitySingle sign-on through your existing provider. No second set of accounts and passwords to manage.
    • ComplianceEncryption in transit and at rest, retention windows you set, and audit exports on demand.

    Next step

    Bring us your stack.

    Tell us what software you run and one process you would like to fix. We will map how the layer sits on it, which engines you actually need, and what the first deployment looks like.

    Book a free consultation See what teams use it for